## LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

 Options: Use Classic View Use Monospaced Font Show Text Part by Default Show All Mail Headers Topic: [<< First] [< Prev] [Next >] [Last >>]

 Re: Multilingual Encodings Summary 2.2 Robin Fairbairns <[log in to unmask]> Tue, 15 May 2001 10:24:53 +0100 text/plain (33 lines) > >>The same should apply to, say, Greek. If I write "barbaros" [well, > >>imagine it written in Greek] using the same beta, sometimes I would like to > >>see the first one using a differenf glyph from the second one (a medial > >>beta, not used currently). > > > > And then I suggest that you do this by selecting a (top level) font in > > which the beta has the medial form, not by using a special \medialbeta > > command or by requesting that the LICR should incorporate something > > equivalent to this. > > Thus, we need 2 virtual font for every font encoding. Don't forget > that iota can be rendered below a letter or "in-line" (2), > iota and upsilon can be rendered inverted (2), and there is > the lunate sigma (2). Since these options are independent, are you > suggesting the creation of 16 (!) vf files and tfm files for every > font (and encoding)? (And regarding that, Greek is easy compared > with scripts like Devanagari or Arabic.) isn't this sort of thing done by ligaturing a "boundary character", so   "bnd" "beta" -> "initial beta"   ...   "sigma" "bnd" -> "terminal sigma" and so on? (i've never really understood boundary characters so i may have this wrong). whatever, such behaviour would take the issue beyond the realms that latex would deal with, since (to first order) there's no control over ligaturing in macro code.