Jens-Uwe Morawski writes: Hello Jens and others,

...

\setupencoding[default=8r]

what is the advantage of using 8r instead of ec or texnansi?

It is a matter of taste and the characters you need. There is no big difference for my german and english texts. texnansi does not work with the preinstalled (psnfss) fonts from teTeX. So this leaves my preferred coding system to 8r or ec. Sometimes I need glyphs that are encoded in 8r but not in ec (euro sign for example). I never use glyphs that are encoded in ec but not in 8r. Patrick

Maarten Sneep writes: Hello Maarten,

But the disadvantage of 8r is that in most languages the line-breaking algorithm performs badly. Take the dutch "verifi\"{e}ren".

so the 'funny' character is ediaeresis ? It is defined in 8r as well as in ec, so the hyphenation does not make any differences here. (In my test, I could not get rid of the accent, but the 8r and ec hyphenation were identical.) You are right though, this is why I wrote "in my german and english texts".

In the default 8r it doesn't break correcly, near the accent. In ec it does break well.

I could not confirm it here.

I don't know about texnansi.

It should be exactly like ec/8r.

I'm sure others can give better examples, and explain why the wordbreaking doesn't work correctly.

Because of the \accent macro??? Patrick

On Tue, 18 Mar 2003 23:39:15 +0100 Patrick Gundlach wrote:

Jens-Uwe Morawski writes:

...

...

\setupencoding[default=8r]

what is the advantage of using 8r instead of ec or texnansi?

It is a matter of taste and the characters you need. There is no big difference for my german and english texts.

Sometimes I need glyphs that are encoded in 8r but not in ec (euro sign for example). I never use glyphs that are encoded in ec but not in 8r.

some time ago Hans and me discussed how to make TS1 symbols available. I've never tried it but it sounds interesting since it is an unified way to access the symbols. For example for Palatino add to the typescripts \definefontsynonym [PalatinoSymbols] [<TS1-Font>] \definefontsynonym [PalatinoSymbolsBold] [<TS1-Bold-Font>] \definefontsynonym [SerifSymbols] [PalatinoSymbols] \definefontsynonym [SerifSymbolsBold] [PalatinoSymbolsBold] and define the symbols in a symbol-typescript \definesymbol[textregistered] [{\symbol[\currentencoding-registered]}] \definesymbol[ec-registered][\getglygh{SerifSymbols}{\char123}] this could add the capability that the LaTeX textcomp package provides Jens

On Wed, 19 Mar 2003 14:58:48 +0100 Patrick Gundlach wrote:

Jens-Uwe Morawski writes:

Hello Jens and others,

...

some time ago Hans and me discussed how to make TS1 symbols available. I've never tried it but it sounds interesting since it is an unified way to access the symbols. For example for Palatino

add to the typescripts

\definefontsynonym [PalatinoSymbols] [<TS1-Font>] \definefontsynonym [PalatinoSymbolsBold] [<TS1-Bold-Font>]

\definefontsynonym [SerifSymbols] [PalatinoSymbols] \definefontsynonym [SerifSymbolsBold] [PalatinoSymbolsBold]

and define the symbols in a symbol-typescript

\definesymbol[textregistered] [{\symbol[\currentencoding-registered]}] \definesymbol[ec-registered][\getglygh{SerifSymbols}{\char123}]

this could add the capability that the LaTeX textcomp package provides

At a quick glance this would fail for example for the euro sign/ec. (Not there in ec). Why not access the existing virtual fonts or generate new ones if needed? (phvr8c.vf for example - let us not fall back to the urw/adobe discussion yet :)

your glance was too quick. :) The chain is: starting with texteuro symbol --> if in ec-encoding it becomes ec-texteuro symbol --> it takes char 0xBF from the current ...Symbol... font (the symbol macro should be able to resolve Serif.., Sans..., Serif...Bold etc automatically) --> the current ...Symbol... font is *NOT* a EC-encoded font but a TS1 (aka 8c) encoded one that is associated via typescript with the T1 encoded font (as i have already written above: <TS1-Font>) This would easily allow for other text encodings to define the usual symbols, for example for 8r one can declare either \definesymbol[8r-texteuro][\getglygh{Serif}{\char128}] or better \definefontsynonym [SerifSymbols] [Serif] \definesymbol[8r-texteuro][\getglygh{SerifSymbols}{\char128}] since in 8r or texnansi there are no special symbol fonts. Thus, when you switch the encoding in your document from ec to 8r to texnansi then the euro is from the users view always the symbol texteuro, but for ec taken from the associated 8c-font and for 8r or texnansi taken directly from the text-font. So, we should look if the macro-names from textcomp package conflict with macro-names already defined in ConTeXT. If there is no conflict we can define all text-symbols according to 'textcomp' in some typescripts: \starttypescript[textsymbols] ... \definesymbol[texteuro] [{\symbol[\currentencoding-texteuro]}] ... \stoptypescript \starttypescript[textsymbols][ec] ... \definesymbol[ec-texteuro] [\getglygh{Textsymbol}{\char191}] ... \stoptypescript \starttypescript[textsymbols][8r] ... \definesymbol[8r-texteuro] [\getglygh{Textsymbol}{\char128}] ... \stoptypescript the font typescripts then have to declare what 'Textsymbol' is: \starttypescript [serif] [Adobe Times] [name] \definefontsynonym [Serif] [Times-Roman] \definefontsynonym [SerifBold] [Times-Bold] \definefontsynonym [SerifItalic] [Times-Italic] \definefontsynonym [SerifSlanted] [Times-Italic] \definefontsynonym [SerifBoldItalic] [Times-BoldItalic] \definefontsynonym [SerifBoldSlanted] [Times-BoldItalic] \definefontsynonym [SerifCaps] [Times-Roman] \definefontsynonym [TextsymbolSerif] [TextsymbolTimes-Roman] \definefontsynonym [TextsymbolSerifBold] [TextsymbolTimes-Bold] \definefontsynonym [TextsymbolSerifItalic] [TextsymbolTimes-Italic] \definefontsynonym [TextsymbolSerifSlanted] [TextsymbolTimes-Italic] \definefontsynonym [TextsymbolSerifBoldItalic] [TextsymbolTimes-BoldItalic] \definefontsynonym [TextsymbolSerifBoldSlanted] [TextsymbolTimes-BoldItalic] \definefontsynonym [TextsymbolSerifCaps] [TextsymbolTimes-Roman] \stoptypescript \starttypescript [serif] [Adobe Times] [ec] \definefontsynonym [Times-Roman] [ptmr8t] [encoding=ec] \definefontsynonym [Times-Bold] [ptmb8t] [encoding=ec] \definefontsynonym [Times-Italic] [ptmri8t] [encoding=ec] \definefontsynonym [Times-BoldItalic] [ptmbi8t] [encoding=ec] \definefontsynonym [TextsymbolTimes-Roman] [ptmr8c] \definefontsynonym [TextsymbolTimes-Bold] [ptmb8c] \definefontsynonym [TextsymbolTimes-Italic] [ptmri8c] \definefontsynonym [TextsymbolTimes-BoldItalic] [ptmbi8c] \stoptypescript % the encoding=?? is only needed for mapping input; since we access symbols % directly (\char...) the encoding for 'Textsymbol' fonts should not be important \starttypescript [serif] [Adobe Times] [8r] \definefontsynonym [Times-Roman] [ptmr8r] [encoding=8r] \definefontsynonym [Times-Bold] [ptmb8r] [encoding=8r] \definefontsynonym [Times-Italic] [ptmri8r] [encoding=8r] \definefontsynonym [Times-BoldItalic] [ptmbi8r] [encoding=8r] \definefontsynonym [TextsymbolTimes-Roman] [ptmr8r] [encoding=8r] \definefontsynonym [TextsymbolTimes-Bold] [ptmb8r] [encoding=8r] \definefontsynonym [TextsymbolTimes-Italic] [ptmri8r] [encoding=8r] \definefontsynonym [TextsymbolTimes-BoldItalic] [ptmbi8r] [encoding=8r] \stoptypescript Jens

Hello, just for those who have the same problems.

...

you can use an alternative to the berry typescript. Get adobekb.tex from http://levana.de/context and use

\setupencoding[default=8r] \usetypescript[adobekb][\defaultencoding] \usetypescript[palatino][\defaultencoding] \setupbodyfont[palatino]

I forgot to say that you need to load the file with \usetypescriptfile[adobekb] Sorry about that. Patrick

Guo Yang writes: Hello Guo,

Sorry if this question is very silly.

I don't think it is.

Where does this 'palatino' come from? I tried 'helvetica', 'helvet' and 'utopia' but none of them worked, while 'times' worked well.

It comes from the file "type-exa.tex" that is shipped with ConTeXt: \starttypescript [palatino] [texnansi,ec,8r] \definetypeface [palatino] [rm] [serif] [palatino] [default] [encoding=\typescripttwo] \definetypeface [palatino] [mm] [math] [palatino] [default] [encoding=\typescripttwo] \definetypeface [palatino] [tt] [mono] [computer-modern] [default] [rscale=1.075] \stoptypescript there are also defined: \starttypescript [modern] [ec,il2,pl0,default] \starttypescript [postscript] [texnansi,ec,8r] \starttypescript [times] [texnansi,ec,8r] \starttypescript [lucida] [texnansi,ec,8r] and some others, not directly related. Patrick