ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: [Fwd: Re: ec encoding and tcaron]
Date: Tue, 16 Aug 2005 20:41:15 +0200	[thread overview]
Message-ID: <6faad9f005081611414a199fdb@mail.gmail.com> (raw)
In-Reply-To: <4301B300.8060202@wxs.nl>

Hans Hagen wrote:
> well, since mojca want some additional glyphs as well, why not make an  ecx.enc file that fixes these things; actually, you only need that file for generating metrics and rename the ecx-* files to ec-* afterwards; we can tweak texfotn to use a different encoding name and output name if needed.

I don't need any additional glyphs, it's only that the stuff that
should work, doesn't work.

> Should the ec enc file be changed?

Thanks, Patrick for pointing me to this files in CTAN. Now I saw
another couple of strange things, that HAVE TO be corrected in order
to make things work properly.

- In ec encoding, dstroke (dcroat according to the Adobe glyph name)
is named dbar. In my opinion, this should be renamed as soon as
possible and also synchronized for the fonts present in CTAN. dbar is
against any standard naming scheme.
- In xl2 encoding, which states to be T1 + ISO Latin 2 in the upper
part, someone made a mistake at the glyph F0, which is eth, but should
be dcroat !!! The mistake was easy to make since Eth equals Dcroat,
but eth does not equal dcroat. The one who wrote the file didn't
notice that. (consecutively, D0 is also wrong)

The Vietnamese encoding seems to be the only one when things were done OK.

Can someone do anything about that? It seems to be a similar "bug" as tcaron.


And about the ConTeXt-specific: dcroat and Eth are both already
present in ec encoding, so I'm not asking for any additional glyphs.
It's not OK to use Eth when someone asks for Dcroat (Dstroke), but
it's better than using the improvized (althoug corrected) version,
pseudoencodedDJ.
My question was: can anything be done, so that dcroat will be chosen
instead of \pseudoencodeddj and that Eth will be chosen instead of
\pseudoencodedDJ when someone types \dstroke or \Dstroke (when in ec
encoding)?

Btw: which languages use Eth? Is it more common than Dcroat?

Hans, thank you for including the new version of \pseudoencodedDJ in
the distribution before I even managed to go online :)

Thank you,
    Mojca

  reply	other threads:[~2005-08-16 18:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16  9:33 Hans Hagen
2005-08-16 18:41 ` Mojca Miklavec [this message]
2005-08-16 19:19   ` Hans Hagen
2005-08-17 12:45     ` Mojca Miklavec
2005-08-17 13:45       ` Hans Hagen
2005-08-17 14:29         ` Mojca Miklavec
2005-08-17 15:08           ` modules.pdf luigi.scarso
2005-08-17 15:19             ` modules.pdf Mojca Miklavec
2005-08-17 17:01               ` modules.pdf luigi.scarso
2005-08-17 19:13                 ` modules.pdf Hans Hagen
2005-08-17 19:02             ` modules.pdf Hans Hagen
2005-08-17 15:18           ` [Fwd: Re: ec encoding and tcaron] Hans Hagen
2005-08-17 17:05             ` Mojca Miklavec
2005-08-17 19:48               ` Hans Hagen
2005-08-17 21:35               ` Hans Hagen
2005-08-17 19:35           ` 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=6faad9f005081611414a199fdb@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).