Re: [NTG-context] Going crazy with font conversion (macron)!
Adam Lindsay
Hum. I haven't tried to replicate that here, but that looks like it might be an encoding problem: ConTeXt doesn't know that you're using a texnansi encoding, so it synthesises the characters using the definitions in enco-def. Is the above file the only way you tested it?
No, also with other conversion and in other files it is the same.
Does this help?
\loadmapline[+Helvetica Helvetica " TeXnANSIEncoding ReEncodeFont "
\starttext \definedfont[texnansi-Helvetica] R\d{o} R{\=o} R\~o \stoptext
Well, then the tilde moves in its right position. But the macron stays left. A font wizard knows what that means?! Steffen
On 23 Mar 2005, at 11:54, Steffen Wolfrum wrote:
Well, then the tilde moves in its right position. But the macron stays left.
A font wizard knows what that means?!
It means that there's no \omacron in texnansi (or the other major western encodings used for TeX fonts), and you're asking ConTeXt to synthesise it from an 'o' and a 'textmacron'. It wouldn't surprise me one bit to hear that the Mac handles combining accents differently from TeX, and so the converted font's metrics is going to result in mistakes in building text accents. Interpretation: you're using artificial test cases to verify the font installation. Stick to what you need and know, and you'll probably end up with a character in the encoding. If you do need \omacron and the like, then you could hand-tune macros that accommodate the specific font--see Idris's recent thread on accents, or you could cook up an "expert" encoding (since MacOSX's Helvetica does include that character) like Vit, and switch to that encoding when you need the character, or you could even go with a big unicode font install. I'll be documenting that process sometime. adam
participants (2)
-
Adam Lindsay -
Steffen Wolfrum