[NTG-context] ISO Latin 2 input under the new ConTeXt

2005-10-04 Thread Michal Kvasnička
Good evening. Many thanks to all of you that helped me to install teTeX 3.0. I found that I can really use SuSE 9.3 rpms under my SuSE 9.2, which quite surprised me. (I can't use Mr. Hagen's minimumdistribution, because there is no MetaFont in it, and I still use some bitmapped fonts, e.g.

Re: [NTG-context] ISO Latin 2 input under the new ConTeXt

2005-10-04 Thread Michal Kvasnička
Mojca Miklavec wrote: There are two things: input encoding or regime (\enableregime[utf] inyour case) and font Many thanks, \enableregime did what I needed. But I still have some minor questions: 1) Where should I put \loadmapfile[psclean.map]? (I can't include it in pdftex.cnf, since

Re: [NTG-context] ISO Latin 2 input under the new ConTeXt

2005-10-04 Thread Vit Zyka
Michal Kvasnička wrote: Mojca Miklavec wrote: There are two things: input encoding or regime (\enableregime[utf] inyour case) and font Many thanks, \enableregime did what I needed. But I still have some minor questions: 1) Where should I put \loadmapfile[psclean.map]? (I can't include it

Re: [NTG-context] iso latin 2 ; storm fonts

2005-03-16 Thread Hans Hagen
Vit Zyka wrote: But I get error: !Math formula deleted: Insufficient symbol fonts. Where is the problem? it means that your font is not a proper math font, taco may know how to deal with this ? - \starttypescript [*] [fallback] is generaly useful. Is a good idea replaced by a (faster) setup) to

Re: [NTG-context] iso latin 2 ; storm fonts

2005-03-15 Thread Hans Hagen
Vit Zyka wrote: Adam Lindsay wrote: Vit Zyka said this at Wed, 9 Feb 2005 22:34:13 +0100: The question is how to elegantly switch from standard (st2) tfm to extended (st3) tfm when the glyph is not present in st2 - with preserving \rm, \bf, \it, \bi. basically, you declare a variant set for a

Re: [NTG-context] iso latin 2 ; storm fonts

2005-03-15 Thread Adam Lindsay
Vit Zyka said this at Tue, 15 Mar 2005 19:23:05 +0100: enco-st1.tex - ec encoding with storm glyph extension enco-st2.tex - xl2 encoding with storm glyph extension enco-st3.tex - variants (additional glyph) for enco-st1 and enco-st2 Vit, I would refer you to this thread with Thomas

Re: [NTG-context] iso latin 2

2005-02-11 Thread Vit Zyka
Hans Hagen wrote: Vit Zyka wrote: ) I feel stronger and stronger that csr should coexist with lm for future. Perhaps like a option (not present in minimal distr?), but with full functionality if extra loaded. about how many to be czechified chars are we talking? About 33 Czech glyphs (+5 or 7

Re: [NTG-context] iso latin 2

2005-02-11 Thread Vit Zyka
Hans Hagen wrote: Adam Lindsay wrote: Vit Zyka said this at Thu, 10 Feb 2005 00:33:59 +0100: But ... seeing Andulka, some support has already exists there, has not it? I would not like to discover wheel ;-) no, it's just a trick of the light. I picked that font name just as a dummy example to

Re: [NTG-context] iso latin 2

2005-02-10 Thread Hans Hagen
Vit Zyka wrote: ) I feel stronger and stronger that csr should coexist with lm for future. Perhaps like a option (not present in minimal distr?), but with full functionality if extra loaded. about how many to be czechified chars are we talking? So I would like il2 will be preserved as it is and

Re: [NTG-context] iso latin 2

2005-02-10 Thread Hans Hagen
Adam Lindsay wrote: Vit Zyka said this at Thu, 10 Feb 2005 00:33:59 +0100: But ... seeing Andulka, some support has already exists there, has not it? I would not like to discover wheel ;-) no, it's just a trick of the light. I picked that font name just as a dummy example to get your

[NTG-context] iso latin 2

2005-02-09 Thread Hans Hagen
I wonder, \definecharacter Aring {\ilencodedrA} \definecharacter Lstroke {\ilencodedL} \definecharacter lstroke {\ilencodedl} where do these come from? is that because csr does not provide those glyphs? (which makes il2 like aer (almoet ec) something almost il2 -) Hans

Re: [NTG-context] iso latin 2

2005-02-09 Thread Vit Zyka
Hans Hagen wrote: I wonder, \definecharacter Aring {\ilencodedrA} \definecharacter Lstroke {\ilencodedL} \definecharacter lstroke {\ilencodedl} where do these come from? is that because csr does not provide those glyphs? il2 encoding is not ISO-8859-2 but encoding of CS fonts

Re: [NTG-context] iso latin 2

2005-02-09 Thread Hans Hagen
Vit Zyka wrote: Hans Hagen wrote: I wonder, \definecharacter Aring {\ilencodedrA} \definecharacter Lstroke {\ilencodedL} \definecharacter lstroke {\ilencodedl} where do these come from? is that because csr does not provide those glyphs? il2 encoding is not ISO-8859-2 but

Re: [NTG-context] iso latin 2

2005-02-09 Thread Adam Lindsay
Vit Zyka said this at Wed, 9 Feb 2005 22:34:13 +0100: The question is how to elegantly switch from standard (st2) tfm to extended (st3) tfm when the glyph is not present in st2 - with preserving \rm, \bf, \it, \bi. Example: {\bf Bold text with special char \textplus} where \texplus is bold

Re: [NTG-context] iso latin 2

2005-02-09 Thread Vit Zyka
Adam Lindsay wrote: Vit Zyka said this at Wed, 9 Feb 2005 22:34:13 +0100: The question is how to elegantly switch from standard (st2) tfm to extended (st3) tfm when the glyph is not present in st2 - with preserving \rm, \bf, \it, \bi. Example: {\bf Bold text with special char \textplus} where

Re: [NTG-context] iso latin 2

2005-02-09 Thread Adam Lindsay
Vit Zyka said this at Thu, 10 Feb 2005 00:33:59 +0100: But ... seeing Andulka, some support has already exists there, has not it? I would not like to discover wheel ;-) no, it's just a trick of the light. I picked that font name just as a dummy example to get your attention. :) I can't afford