On Thu, Oct 10, 2013 at 5:51 PM, Hans Hagen
On 10/10/2013 9:18 AM, Hans Hagen wrote:
On 10/10/2013 6:58 AM, Pablo Rodriguez wrote:
Dear list,
I have the following sample:
\usemodule[simplefonts] \setmainfont[Gill Sans MT] \setsansfont[Arial Narrow] \starttext \input knuth\par \ss\input knuth \stoptext
It works right in Linux (http://www.ousia.tk/gs-linux.**pdfhttp://www.ousia.tk/gs-linux.pdfand http://www.ousia.tk/gs-linux.**log http://www.ousia.tk/gs-linux.log), but it shows crappy font metrics and size in Windows (http://www.ousia.tk/gs-win.**pdfhttp://www.ousia.tk/gs-win.pdfand http://www.ousia.tk/gs-win.log**).
Both use a beta from 07/10/2013 and the Windows version was downloaded in Linux.
Isn”t this a bug?
Normally that's an indication that the units are unknown. They are different fontfiles so you cannot compare their behaviour. You can try renaming the wrong ttf to otf.
thanks to luigi testing to the extreme with these files we figured out that we can catch the issue (more checking at the context end, maybe some day some better checking at the luatex backend end)
so, the upcoming beta might work beta, which doesn't mean that one should be sloppy with filenames (as mixed usage of foo.TTF FOO.TTF FOO.ttf foo.ttf will for sure have side effects) .. one reason why i often lowercase font filenames and keep 'm all in texmf-fonts
This is also my way. In this case I rename ARIALN.TTF in arialn.ttf, put it into the mkiv standalone, and keep ARIALN.TTF in a separate folder of the project. If someone ask me for the font , I give ARIALN.TTF, but I used arialn.ttf in the pdf. The reason is that I keep separate OS fonts from the fonts of the projects --- I can move the projects in different machines, I can update OS etc. Of course there are also licensing issues to consider, but I consider it a robust way. -- luigi