Hello, I'm playing with the XeTeX font syntax, and I found a very strange behaviour on the way \font argument is passed to the callback define_font... Here is a very small sample with which you will see strange differences between the \font argument and what is passed to define_font. Thank you in advance, -- Elie
Elie Roux wrote:
Hello,
I'm playing with the XeTeX font syntax, and I found a very strange behaviour on the way \font argument is passed to the callback define_font...
Here is a very small sample with which you will see strange differences between the \font argument and what is passed to define_font.
The font parser may think this is something in a subdirectory (I am guessing, can't run the executable from here). You could try putting the font name in braces for now, that should work better: \font\foo={first strage/B:ehaviour} \foo \font\bar={[second-strange]/B:ehaviour} \bar I will still need to be fixing the binary though, the quoted approach should work just as well. Best wishes, Taco
Taco Hoekwater a écrit :
The font parser may think this is something in a subdirectory (I am guessing, can't run the executable from here). You could try putting the font name in braces for now, that should work better:
\font\foo={first strage/B:ehaviour} \foo \font\bar={[second-strange]/B:ehaviour} \bar
I will still need to be fixing the binary though, the quoted approach should work just as well.
You're right: it works well with braces. Also I forgot to ask in my first mail: in XeTeX it's possible to declare a font on several lines. It works well with braces in LuaTeX, but not with quotes... Would it be possible to add it? The attachment is a test case for all this, to save you some time... Thank you in advance, -- Elie
Sorry to bother you again, I added another buggy behaviour in the test file in case you'll be working on it tonight... -- Elie
participants (2)
-
Elie Roux -
Taco Hoekwater