From: Hans Hagen <pragma@wxs.nl>
Subject: Re: missing Dstroke & dstroke - "solved"
Date: Fri, 31 Jan 2003 23:28:41 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20030131232537.03d78e20@server-1> (raw)
In-Reply-To: <20030128165419.GA5265@mail.inet.hr>
At 05:54 PM 1/28/2003 +0100, Gour wrote:
>I "solved" the problem by putting the following in enco-def.tex:
>
>\definecharacter Dstroke {\DJ}
>\definecharacter dstroke {\dj}
better is (enco-def)
\definecharacter dstroke {\pseudoencodeddj}
\definecharacter Dstroke {\pseudoencodedDJ}
and (in enco-mis)
\definecharacter dj {\dstroke}
\definecharacter Dj {\Dstroke}
\definecharacter DJ {\Dstroke}
>However I'm not sure whether it's a correct solution. It works with cmr
>font, but
>I have to see what will happen with the properly filled Unicode font which has
>glyphs for dstroke & Dstroke.
Being dutch, I never saw them as the same glyphs -)
[btw, there is an excellent doc about hungarian typo things, written by
Gyongyi Bujdoso from the matex user group]
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2003-01-31 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 13:22 missing Dstroke & dstroke Gour
2003-01-23 21:12 ` Simon Pepping
2003-01-24 13:58 ` Gour
2003-01-24 20:27 ` Simon Pepping
2003-01-25 8:24 ` Gour
2003-01-28 16:54 ` missing Dstroke & dstroke - "solved" Gour
2003-01-31 22:28 ` Hans Hagen [this message]
2003-02-01 11:54 ` Zeljko Vrba
2003-02-01 13:36 ` Hans Hagen
2003-02-01 15:05 ` Zeljko Vrba
2003-02-01 13:59 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.1.0.14.1.20030131232537.03d78e20@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).