Greetings all, Taco mentioned the command \uppercased{to get all uppercase letters}, and it works just fine…until I try to use my self-installed fonts. The quirks come up with diacritics, and this leads me to believe that there is an [encoding] or [regime] issue here, as I had similar issues earlier with the font in general. For example, with \uppercased{Krübel} I receive: KRüBEL. Do I need to "make a statement of my intent" in a typescript file or somewhere else to resolve this? Kind regards, David
David Wooten wrote:
Greetings all,
Taco mentioned the command \uppercased{to get all uppercase letters}, and it works just fine…until I try to use my self-installed fonts. The quirks come up with diacritics, and this leads me to believe that there is an [encoding] or [regime]/ /issue here, as I had similar issues
Yes, \uccode and \lccode are encoding-dependent and are defined in enco-*.tex files. So, look into the encoding file you are using and add the their definition between \startmapping[st1] \definecasemap 152 184 152 \stopmapping with meaning: character 152 has lower counterpart 184 and upper one 152 (152 is uppercase letter). (or for continuous sequence there is abbreviation \definecasemaps 160 to 188 lc +32 uc 0 with meaning: \definecasemap 160 182 160 \definecasemap 161 183 161 ... \definecasemap 188 220 188 ) vit
Greetings Vit, all, Thanks for the response. I'm finally getting around to looking into this again. My first attempts haven't yielded any good results. Could you (or someone) say a little more (newbie-explicit)? I assume that the enco-*.tex files you're referring to are in .../context/base/, where there are a series of 30 or so such files. It isn't clear to me which one to use. Does the encoding refer to font encoding? —in which case there is no "enco-8r.tex" — or to something else? — enco-pdf.tex for example. Thanks very much, David Wooten On Mar 26, 2005, at 11:35 AM, Vit Zyka wrote:
David Wooten wrote:
Greetings all, Taco mentioned the command \uppercased{to get all uppercase letters}, and it works just fine…until I try to use my self-installed fonts. The quirks come up with diacritics, and this leads me to believe that there is an [encoding] or [regime]/ /issue here, as I had similar issues
Yes, \uccode and \lccode are encoding-dependent and are defined in enco-*.tex files. So, look into the encoding file you are using and add the their definition between \startmapping[st1] \definecasemap 152 184 152 \stopmapping with meaning: character 152 has lower counterpart 184 and upper one 152 (152 is uppercase letter).
(or for continuous sequence there is abbreviation \definecasemaps 160 to 188 lc +32 uc 0 with meaning: \definecasemap 160 182 160 \definecasemap 161 183 161 ... \definecasemap 188 220 188 )
vit
David Wooten wrote:
so such files. It isn't clear to me which one to use. Does the encoding refer to font encoding?
Yes. It describes where the glyph name is presented in the font.
—in which case there is no "enco-8r.tex" — or to something else? — enco-pdf.tex for example.
I think you are looking for enco-ans.tex: texnansi encoding. Vit
I came across the command \WORD{} in the manual (nice place to look, eh?). This does all capitals (it can be more than one word) and doesn't have the issue with diacritics that \uppercased was having for me. Thanks, David On Mar 25, 2005, at 5:30 PM, David Wooten wrote:
Greetings all,
Taco mentioned the command \uppercased{to get all uppercase letters}, and it works just fine…until I try to use my self-installed fonts. The quirks come up with diacritics, and this leads me to believe that there is an [encoding] or [regime] issue here, as I had similar issues earlier with the font in general. For example, with \uppercased{Krübel} I receive: KRüBEL.
Do I need to "make a statement of my intent" in a typescript file or somewhere else to resolve this?
Kind regards, David
participants (2)
-
David Wooten -
Vit Zyka