On Tue, Apr 8, 2008 at 10:13 AM, Hans Hagen wrote:
Mojca Miklavec wrote:
Hello Hraban,
thanks for pointing this out.
To Hans: the \typescriptthree indeed needs to go out of those definitions (line 300 in type-otf).
hm, can you post the line? i have this
300-311 (301-310), this are the fixed ones, but probably broken across lines: \definefontsynonym [\typescriptprefix{n:\typescripttwo}-Regular] [file:texgyre\typescriptprefix{f:\typescripttwo}-regular] [features=default] \definefontsynonym [\typescriptprefix{n:\typescripttwo}-Italic] [file:texgyre\typescriptprefix{f:\typescripttwo}-italic] [features=default] \definefontsynonym [\typescriptprefix{n:\typescripttwo}-Bold] [file:texgyre\typescriptprefix{f:\typescripttwo}-bold] [features=default] \definefontsynonym [\typescriptprefix{n:\typescripttwo}-BoldItalic] [file:texgyre\typescriptprefix{f:\typescripttwo}-bolditalic] [features=default] \definefontsynonym [\typescriptprefix{n:\typescripttwo}-Caps] [file:texgyre\typescriptprefix{f:\typescripttwo}-regular] [features=oldstyle] \definefontsynonym [\typescriptprefix{n:\typescripttwo}-ItalicCaps] [file:texgyre\typescriptprefix{f:\typescripttwo}-italic] [features=oldstyle] \definefontsynonym [\typescriptprefix{n:\typescripttwo}-BoldCaps] [file:texgyre\typescriptprefix{f:\typescripttwo}-bold] [features=oldstyle] \definefontsynonym [\typescriptprefix{n:\typescripttwo}-BoldItalicCaps] [file:texgyre\typescriptprefix{f:\typescripttwo}-bolditalic] [features=oldstyle] \definefontsynonym [\typescriptprefix{n:\typescripttwo}-Slanted] [\typescriptprefix{n:\typescripttwo}-Italic] [features=default] \definefontsynonym [\typescriptprefix{n:\typescripttwo}-BoldSlanted] [\typescriptprefix{n:\typescripttwo}-BoldItalic] [features=default]
type-xtx contains quite some "uc" leftovers, but I'm not sure if "fixing" them is a wise idea or not (backward compatibility).
i dunno either ... this may date from the time that not that many open type fonts were around, so we may consider dropping it (i.e. we kind of assume that xetex users use open type)
There are definitions like this one: \starttypescript[sans][arial][uc] \definefontsynonym[Arial] [name:Arial] [features=default] \definefontsynonym[ArialItalic] [name:Arial Italic] [features=default] \definefontsynonym[ArialBold] [name:Arial Bold] [features=default] \definefontsynonym[ArialBoldItalic][name:Arial Bold Italic][features=default] \stoptypescript It just predefines some (mostly Mac) typescripts. Some of those typescripts might be usable in luaTeX as well. I have no idea how many people have ever used \usetypescript[arial][uc] [uc] could be removed, but if these lines are deleted, the documents will be broken (which is probably true for quite some XeTeX documents from past which used the old notation). And on the other hand, the definitions could be made more generic (to be usable in LuaTeX as well). Mojca To Hraban: oh, I did not understand you joke at first :-) Now I see what you were trying to say with "extending the font to the full unicode range" :-) And sure enough - LuaTeX doesn't do that either. What I meant was - in afm files you have: C 235 ; WX 355 ; N ordmasculine ; B 38 369 317 710 ; C 241 ; WX 791 ; N ae ; B 45 -10 741 460 ; C 245 ; WX 283 ; N dotlessi ; B 75 -10 263 450 ; C 248 ; WX 328 ; N lslash ; B 20 -10 308 700 ; C 249 ; WX 497 ; N oslash ; B 55 -39 442 489 ; C 250 ; WX 792 ; N oe ; B 55 -10 742 460 ; C 251 ; WX 488 ; N germandbls ; B 80 -10 448 710 ; C -1 ; WX 620 ; N afii10017 ; B 10 0 610 700 ; C -1 ; WX 626 ; N afii10020 ; B 100 0 576 700 ; C -1 ; WX 626 ; N afii10050 ; B 100 0 576 770 ; C -1 ; WX 685 ; N afii10018 ; B 100 -10 625 700 ; C -1 ; WX 685 ; N afii10046 ; B 100 -10 625 700 ; C -1 ; WX 745 ; N afii10044 ; B 10 -10 685 700 ; C -1 ; WX 957 ; N afii10045 ; B 100 -10 857 700 ; C -1 ; WX 685 ; N afii10019 ; B 100 -10 625 710 ; C -1 ; WX 626 ; N afii10052 ; B 100 0 576 880 ; And there is probably no way for XeTeX to access afiiXXXXX, whatever that is, while LuaTeX tries to guess the unicode point from the glyph name and uses that one when available. But - I will stop talking about LuaTeX, as I have promised you already in the last email.