Font problems with latest minimals on Linux

Vasile Gaburici

12 Aug 2008 12 Aug '08

5:50 a.m.

I've switched to the rsync-ed minimals on Linux. There are still some problems with fonts: 1) Bold is still missing from fonts pulled via OSFONTDIR, e.g.: verdana Verdana /usr/share/fonts/vista/Verdana.ttf verdana bold italic Verdana Bold Italic /usr/share/fonts/vista/Verdanaz.ttf verdana italic Verdana Italic /usr/share/fonts/vista/Verdanai.ttf 2) OSFONTDIR is not recursive. To get the above I used "export OSFONTDIR=/usr/share/fonts/vista/", just "export OSFONTDIR=/usr/share/fonts/" doesn't work.

Show replies by date

Taco Hoekwater

13 Aug 13 Aug

1:43 a.m.

Vasile Gaburici wrote:

...

I've switched to the rsync-ed minimals on Linux. There are still some problems with fonts:

1) Bold is still missing from fonts pulled via OSFONTDIR, e.g.:

verdana Verdana /usr/share/fonts/vista/Verdana.ttf verdana bold italic Verdana Bold Italic /usr/share/fonts/vista/Verdanaz.ttf verdana italic Verdana Italic /usr/share/fonts/vista/Verdanai.ttf

This works OK for ttf fonts on my linux machine, but I don't have the ttf version of verdana, so perhaps it is something special to that font.

...

2) OSFONTDIR is not recursive. To get the above I used "export OSFONTDIR=/usr/share/fonts/vista/", just "export OSFONTDIR=/usr/share/fonts/" doesn't work.

Yes, recursion would be nice. Best wishes, Taco

Hans Hagen

2:31 a.m.

Taco Hoekwater wrote:

...

Vasile Gaburici wrote:

...
I've switched to the rsync-ed minimals on Linux. There are still some problems with fonts:

1) Bold is still missing from fonts pulled via OSFONTDIR, e.g.:

verdana Verdana /usr/share/fonts/vista/Verdana.ttf verdana bold italic Verdana Bold Italic /usr/share/fonts/vista/Verdanaz.ttf verdana italic Verdana Italic /usr/share/fonts/vista/Verdanai.ttf

This works OK for ttf fonts on my linux machine, but I don't have the ttf version of verdana, so perhaps it is something special to that font.

...
2) OSFONTDIR is not recursive. To get the above I used "export OSFONTDIR=/usr/share/fonts/vista/", just "export OSFONTDIR=/usr/share/fonts/" doesn't work.

Yes, recursion would be nice.

font-syn.lua, line 190: path = input.clean_path(path .. "/") path = path:gsub("/+","/") path = path .. "**/" insert the last line and see what happens (untested because i have a flat system path) ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Vasile Gaburici

3:21 a.m.

On Wed, Aug 13, 2008 at 11:31 AM, Hans Hagen wrote:

...

...
Yes, recursion would be nice. font-syn.lua, line 190:

path = input.clean_path(path .. "/") path = path:gsub("/+","/") path = path .. "**/"

insert the last line and see what happens (untested because i have a flat system path)

It works.

...

----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Hans Hagen

4:04 a.m.

Vasile Gaburici wrote:

...

On Wed, Aug 13, 2008 at 11:31 AM, Hans Hagen wrote:

...
...
Yes, recursion would be nice. font-syn.lua, line 190:

path = input.clean_path(path .. "/") path = path:gsub("/+","/") path = path .. "**/"

insert the last line and see what happens (untested because i have a flat system path)

It works.

there will be a beta later today; taco and i tested a different patch on win/lin and it looks like it works; you need to regenerate the font database then ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Vasile Gaburici

4:05 a.m.

As for the missing bold, it seems there's a bug in the naming scheme: Ii the bold italic file gets read from the disk before the bold, then you don't get the right entries. It so happens that most of the fonts in that dir had bold before bold italic, e.g. fontnames | identifying ttf font /usr/share/fonts/vista/Verdanai.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdana.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdanaz.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdanab.ttf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Italic.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold.otf So, I've added some extra code (patch attached) to print the names it adds to the hash. As you can see there is a clash: both bold italic and bold want to "own" bold... fontnames | identifying ttf font /usr/share/fonts/vista/Verdanaz.ttf add | verdana bold italic -> {ttf, Verdana Bold Italic, /usr/share/fonts/vista/Verdanaz.ttf, ...} add | verdanabolditalic -> {ttf, Verdana Bold Italic, /usr/share/fonts/vista/Verdanaz.ttf, ...} add | verdana-bolditalic -> {ttf, Verdana Bold Italic, /usr/share/fonts/vista/Verdanaz.ttf, ...} add | verdanabolditalic -> {ttf, Verdana Bold Italic, /usr/share/fonts/vista/Verdanaz.ttf, ...} add | verdana bold -> {ttf, Verdana Bold Italic, /usr/share/fonts/vista/Verdanaz.ttf, ...} add | verdanabold -> {ttf, Verdana Bold Italic, /usr/share/fonts/vista/Verdanaz.ttf, ...} fontnames | identifying ttf font /usr/share/fonts/vista/Verdanab.ttf add | verdana bold -> {ttf, Verdana Bold, /usr/share/fonts/vista/Verdanab.ttf, ...} add | verdanabold -> {ttf, Verdana Bold, /usr/share/fonts/vista/Verdanab.ttf, ...} add | verdana-bold -> {ttf, Verdana Bold, /usr/share/fonts/vista/Verdanab.ttf, ...} add | verdanabold -> {ttf, Verdana Bold, /usr/share/fonts/vista/Verdanab.ttf, ...} add | verdana bold -> {ttf, Verdana Bold, /usr/share/fonts/vista/Verdanab.ttf, ...} add | verdanabold -> {ttf, Verdana Bold, /usr/share/fonts/vista/Verdanab.ttf, ...} fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf add | calibri bold italic -> {otf, Calibri Bold Italic, /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf, ...} add | calibribolditalic -> {otf, Calibri Bold Italic, /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf, ...} add | calibri-bolditalic -> {otf, Calibri Bold Italic, /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf, ...} add | calibribolditalic -> {otf, Calibri Bold Italic, /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf, ...} add | calibri bold -> {otf, Calibri Bold Italic, /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf, ...} add | calibribold -> {otf, Calibri Bold Italic, /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf, ...} fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold.otf add | calibri bold -> {otf, Calibri Bold, /usr/share/fonts/vista/C-series/Calibri Bold.otf, ...} add | calibribold -> {otf, Calibri Bold, /usr/share/fonts/vista/C-series/Calibri Bold.otf, ...} add | calibri-bold -> {otf, Calibri Bold, /usr/share/fonts/vista/C-series/Calibri Bold.otf, ...} add | calibribold -> {otf, Calibri Bold, /usr/share/fonts/vista/C-series/Calibri Bold.otf, ...} add | calibri bold -> {otf, Calibri Bold, /usr/share/fonts/vista/C-series/Calibri Bold.otf, ...} add | calibribold -> {otf, Calibri Bold, /usr/share/fonts/vista/C-series/Calibri Bold.otf, ...} I don't know how to fix since it's not clear to me what names you actually want... On Wed, Aug 13, 2008 at 10:43 AM, Taco Hoekwater wrote:

...

Vasile Gaburici wrote:

...
I've switched to the rsync-ed minimals on Linux. There are still some problems with fonts:

1) Bold is still missing from fonts pulled via OSFONTDIR, e.g.:

verdana Verdana /usr/share/fonts/vista/Verdana.ttf verdana bold italic Verdana Bold Italic /usr/share/fonts/vista/Verdanaz.ttf verdana italic Verdana Italic /usr/share/fonts/vista/Verdanai.ttf

This works OK for ttf fonts on my linux machine, but I don't have the ttf version of verdana, so perhaps it is something special to that font.

...
2) OSFONTDIR is not recursive. To get the above I used "export OSFONTDIR=/usr/share/fonts/vista/", just "export OSFONTDIR=/usr/share/fonts/" doesn't work.

Yes, recursion would be nice.

Best wishes, Taco

Hans Hagen

5:20 a.m.

Vasile Gaburici wrote:

...

As for the missing bold, it seems there's a bug in the naming scheme: Ii the bold italic file gets read from the disk before the bold, then you don't get the right entries. It so happens that most of the fonts in that dir had bold before bold italic, e.g.

fontnames | identifying ttf font /usr/share/fonts/vista/Verdanai.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdana.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdanaz.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdanab.ttf

fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Italic.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold.otf

So, I've added some extra code (patch attached) to print the names it adds to the hash. As you can see there is a clash: both bold italic and bold want to "own" bold...

how do you define the font; don't use spaces! ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Vasile Gaburici

5:47 a.m.

On Wed, Aug 13, 2008 at 2:20 PM, Hans Hagen wrote:

...

Vasile Gaburici wrote:

...
As for the missing bold, it seems there's a bug in the naming scheme: Ii the bold italic file gets read from the disk before the bold, then you don't get the right entries. It so happens that most of the fonts in that dir had bold before bold italic, e.g.

fontnames | identifying ttf font /usr/share/fonts/vista/Verdanai.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdana.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdanaz.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdanab.ttf

fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Italic.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold.otf

So, I've added some extra code (patch attached) to print the names it adds to the hash. As you can see there is a clash: both bold italic and bold want to "own" bold...

how do you define the font; don't use spaces!

??? If your're complaining that Calibri has spaces in the file name, it's a non-issue here. Verdana has the same "bold not listed" problem, even though there are no spaces in the file name...

...

----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Wolfgang Schuster

7:46 a.m.

On Wed, Aug 13, 2008 at 1:47 PM, Vasile Gaburici wrote:

...

On Wed, Aug 13, 2008 at 2:20 PM, Hans Hagen wrote:

...
Vasile Gaburici wrote:

...
As for the missing bold, it seems there's a bug in the naming scheme: Ii the bold italic file gets read from the disk before the bold, then you don't get the right entries. It so happens that most of the fonts in that dir had bold before bold italic, e.g.

fontnames | identifying ttf font /usr/share/fonts/vista/Verdanai.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdana.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdanaz.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdanab.ttf

fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Italic.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold.otf

So, I've added some extra code (patch attached) to print the names it adds to the hash. As you can see there is a clash: both bold italic and bold want to "own" bold...

how do you define the font; don't use spaces!

??? If your're complaining that Calibri has spaces in the file name, it's a non-issue here. Verdana has the same "bold not listed" problem, even though there are no spaces in the file name...

Where do you got the vista fonts, i know them only in TrueType format and more verbose names. Wolfgang

Vasile Gaburici

9:49 a.m.

Before I get anymore strawman arguments, here's the definitive experiment: $ ls -U1 /usr/share/fonts/vista/ | grep erda Verdanai.ttf Verdana.ttf Verdanaz.ttf Verdanab.ttf $ ls -U1 /xp/wtf/ Verdana.ttf Verdanab.ttf Verdanai.ttf Verdanaz.ttf Notice that the directory order is different, bold comes before bold italic in wtf. I actually had to copy the files to a non-ext3 partition (NTFS actually) to get the order to change. Why? Because with ext3 htree you have *no* control over the order in which the directory is "laid out", because it's not a linear list anymore. So, guess what happens if I do: $ export OSFONTDIR=/xp/wtf/ $ mtxrun --script fonts --reload $ mtxrun --script fonts --list | grep erda verdana Verdana /xp/wtf/Verdana.ttf verdana bold Verdana Bold /xp/wtf/Verdanab.ttf verdana bold italic Verdana Bold Italic /xp/wtf/Verdanaz.ttf verdana italic Verdana Italic /xp/wtf/Verdanai.ttf $ context taco.tex | grep Verdana ) and the correct bold font is loaded in the PDF. If you still think somehow that this is a problem with Verdana, look carefully at this list of DejaVu fonts. Some get the bold, and for some it's missing. It's haphazard depending on the disk order: $ mtxrun --script fonts --list | grep eja dejavu lgc sans DejaVu LGC Sans /usr/share/fonts/dejavu/DejaVuLGCSans.ttf dejavu lgc sans bold oblique DejaVu LGC Sans Bold Oblique /usr/share/fonts/dejavu/DejaVuLGCSans-BoldOblique.ttf dejavu lgc sans condensed DejaVu LGC Sans Condensed /usr/share/fonts/dejavu/DejaVuLGCSansCondensed.ttf dejavu lgc sans condensed bold oblique DejaVu LGC Sans Condensed Bold Oblique /usr/share/fonts/dejavu/DejaVuLGCSansCondensed-BoldOblique.ttf dejavu lgc sans condensed oblique DejaVu LGC Sans Condensed Oblique /usr/share/fonts/dejavu/DejaVuLGCSansCondensed-Oblique.ttf dejavu lgc sans extralight DejaVu LGC Sans ExtraLight /usr/share/fonts/dejavu/DejaVuLGCSans-ExtraLight.ttf dejavu lgc sans mono DejaVu LGC Sans Mono /usr/share/fonts/dejavu/DejaVuLGCSansMono.ttf dejavu lgc sans mono bold DejaVu LGC Sans Mono Bold /usr/share/fonts/dejavu/DejaVuLGCSansMono-Bold.ttf dejavu lgc sans mono bold oblique DejaVu LGC Sans Mono Bold Oblique /usr/share/fonts/dejavu/DejaVuLGCSansMono-BoldOblique.ttf dejavu lgc sans mono oblique DejaVu LGC Sans Mono Oblique /usr/share/fonts/dejavu/DejaVuLGCSansMono-Oblique.ttf dejavu lgc sans oblique DejaVu LGC Sans Oblique /usr/share/fonts/dejavu/DejaVuLGCSans-Oblique.ttf dejavu lgc serif DejaVu LGC Serif /usr/share/fonts/dejavu/DejaVuLGCSerif.ttf dejavu lgc serif bold italic DejaVu LGC Serif Bold Italic /usr/share/fonts/dejavu/DejaVuLGCSerif-BoldItalic.ttf dejavu lgc serif condensed DejaVu LGC Serif Condensed /usr/share/fonts/dejavu/DejaVuLGCSerifCondensed.ttf dejavu lgc serif condensed bold DejaVu LGC Serif Condensed Bold /usr/share/fonts/dejavu/DejaVuLGCSerifCondensed-Bold.ttf dejavu lgc serif condensed bold italic DejaVu LGC Serif Condensed Bold Italic /usr/share/fonts/dejavu/DejaVuLGCSerifCondensed-BoldItalic.ttf dejavu lgc serif italic DejaVu LGC Serif Italic /usr/share/fonts/dejavu/DejaVuLGCSerif-Italic.ttf dejavu lgc serif italic condensed DejaVu LGC Serif Italic Condensed /usr/share/fonts/dejavu/DejaVuLGCSerifCondensed-Italic.ttf dejavu sans DejaVu Sans /usr/share/fonts/dejavu/DejaVuSans.ttf dejavu sans bold DejaVu Sans Bold /usr/share/fonts/dejavu/DejaVuSans-Bold.ttf dejavu sans bold oblique DejaVu Sans Bold Oblique /usr/share/fonts/dejavu/DejaVuSans-BoldOblique.ttf dejavu sans condensed DejaVu Sans Condensed /usr/share/fonts/dejavu/DejaVuSansCondensed.ttf dejavu sans condensed bold DejaVu Sans Condensed Bold /usr/share/fonts/dejavu/DejaVuSansCondensed-Bold.ttf dejavu sans condensed bold oblique DejaVu Sans Condensed Bold Oblique /usr/share/fonts/dejavu/DejaVuSansCondensed-BoldOblique.ttf dejavu sans condensed oblique DejaVu Sans Condensed Oblique /usr/share/fonts/dejavu/DejaVuSansCondensed-Oblique.ttf dejavu sans extralight DejaVu Sans ExtraLight /usr/share/fonts/dejavu/DejaVuSans-ExtraLight.ttf dejavu sans mono DejaVu Sans Mono /usr/share/fonts/dejavu/DejaVuSansMono.ttf dejavu sans mono bold DejaVu Sans Mono Bold /usr/share/fonts/dejavu/DejaVuSansMono-Bold.ttf dejavu sans mono bold oblique DejaVu Sans Mono Bold Oblique /usr/share/fonts/dejavu/DejaVuSansMono-BoldOblique.ttf dejavu sans mono oblique DejaVu Sans Mono Oblique /usr/share/fonts/dejavu/DejaVuSansMono-Oblique.ttf dejavu sans oblique DejaVu Sans Oblique /usr/share/fonts/dejavu/DejaVuSans-Oblique.ttf dejavu serif DejaVu Serif /usr/share/fonts/dejavu/DejaVuSerif.ttf dejavu serif bold DejaVu Serif Bold /usr/share/fonts/dejavu/DejaVuSerif-Bold.ttf dejavu serif bold italic DejaVu Serif Bold Italic /usr/share/fonts/dejavu/DejaVuSerif-BoldItalic.ttf dejavu serif condensed DejaVu Serif Condensed /usr/share/fonts/dejavu/DejaVuSerifCondensed.ttf dejavu serif condensed bold DejaVu Serif Condensed Bold /usr/share/fonts/dejavu/DejaVuSerifCondensed-Bold.ttf dejavu serif condensed bold italic DejaVu Serif Condensed Bold Italic /usr/share/fonts/dejavu/DejaVuSerifCondensed-BoldItalic.ttf dejavu serif italic DejaVu Serif Italic /usr/share/fonts/dejavu/DejaVuSerif-Italic.ttf dejavu serif italic condensed DejaVu Serif Italic Condensed /usr/share/fonts/dejavu/DejaVuSerifCondensed-Italic.ttf Now the easiest way for you to stop depending on the disk order of directory entries is to sort the list you get from globbing. This will work for bold vs bold italic, but it will probably break at some other name sequence. The only reliable way is avoid clobbering existing entries in the hash in the same --reload run. But this won't work for incremental updates, since you can't tell whether you should drop an old hash entry or not. So if you want to use hashing, you really need a naming scheme that avoids creating conflicts. XeTeX solves this problem by using *only* the ID 16 and ID 17 OpenType values to create a unique name for system fonts. I actually filed a bug about lack of support for the common ID 1/2 names, but Johnathan WONTFIXED it because he really wants the font names to be unambiguous, and using ID 1 and ID 2 values in addition to ID 16/17 doesn't guarantee that. Your situation is worse, because you want to support all sort of legacy fonts in that single hashtable. Anyway, I've wasted enough of my time on this matter. If you sill don't grok it, forget about it. BTW, the Lua 5.1 "reference" manual is a joke. How do you printf a boolean? What's the syntax for their definitely non-standard regexps. No answers in that "reference". On Wed, Aug 13, 2008 at 4:46 PM, Wolfgang Schuster wrote:

...

On Wed, Aug 13, 2008 at 1:47 PM, Vasile Gaburici wrote:

...
On Wed, Aug 13, 2008 at 2:20 PM, Hans Hagen wrote:

...
Vasile Gaburici wrote:

...
As for the missing bold, it seems there's a bug in the naming scheme: Ii the bold italic file gets read from the disk before the bold, then you don't get the right entries. It so happens that most of the fonts in that dir had bold before bold italic, e.g.

fontnames | identifying ttf font /usr/share/fonts/vista/Verdanai.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdana.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdanaz.ttf fontnames | identifying ttf font /usr/share/fonts/vista/Verdanab.ttf

fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Italic.otf fontnames | identifying otf font /usr/share/fonts/vista/C-series/Calibri Bold.otf

So, I've added some extra code (patch attached) to print the names it adds to the hash. As you can see there is a clash: both bold italic and bold want to "own" bold...

how do you define the font; don't use spaces!

??? If your're complaining that Calibri has spaces in the file name, it's a non-issue here. Verdana has the same "bold not listed" problem, even though there are no spaces in the file name...

Where do you got the vista fonts, i know them only in TrueType format and more verbose names.

Wolfgang

Hans Hagen

10:19 a.m.

Vasile Gaburici wrote:

...

Before I get anymore strawman arguments, here's the definitive experiment:

$ ls -U1 /usr/share/fonts/vista/ | grep erda Verdanai.ttf Verdana.ttf Verdanaz.ttf Verdanab.ttf

$ ls -U1 /xp/wtf/ Verdana.ttf Verdanab.ttf Verdanai.ttf Verdanaz.ttf

did you test the latest beta (this afternoon version?)

...

XeTeX solves this problem by using *only* the ID 16 and ID 17 OpenType values to create a unique name for system fonts. I actually filed a bug about lack of support for the common ID 1/2 names, but Johnathan WONTFIXED it because he really wants the font names to be unambiguous, and using ID 1 and ID 2 values in addition to ID 16/17 doesn't guarantee that. Your situation is worse, because you want to support all sort of legacy fonts in that single hashtable.

part of the problem was that the mtx-font lookup (shown by list) differed from the one used in practice (in tex); this is now harmonized (and seems to be ok on taco's and my machine)

...

Anyway, I've wasted enough of my time on this matter. If you sill don't grok it, forget about it.

you don't want to know how much time we spent on fonts so far -)

...

BTW, the Lua 5.1 "reference" manual is a joke. How do you printf a boolean? What's the syntax for their definitely non-standard regexps.

they are not regexps but just expressions; being a lightweight language lua does not have regexp (as the manual states: it would add more code than lua itself; however, there is lpeg (also in luatex) which is not only more poweeful than regexp but also is efficient wrt the implementation Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Taco Hoekwater

11 a.m.

Vasile Gaburici wrote:

...

Before I get anymore strawman arguments, here's the definitive experiment:

As Hans said, should be corrected in the latest beta. Please cut us some slack here, debugging unreproducible problems is hard and timeconsuming.

...

BTW, the Lua 5.1 "reference" manual is a joke. How do you printf a boolean?

This is indeed not in the manual, but lua behaves like most other languages with boolean types: the boolean prints the string "true" or "false" in a string (=debugging) context. You can force conversion to string by calling tostring() on it.

...

What's the syntax for their definitely non-standard regexps. No answers in that "reference".

Section 5.4.1 Patterns Best wishes, Taco

Vasile Gaburici

10:33 p.m.

On Wed, Aug 13, 2008 at 8:00 PM, Taco Hoekwater wrote:

...

Vasile Gaburici wrote:

...
Before I get anymore strawman arguments, here's the definitive experiment:

As Hans said, should be corrected in the latest beta. Please cut us some slack here, debugging unreproducible problems is hard and timeconsuming.

Okay, I've updated to the latest beta. Recursive OSFONTDIR works now for "script --fonts --reload" and for "context", but "script --fonts --list" is broken: no output. The other bug, i.e. embedding bold italic instead of bold for some fonts, is still present.

Vasile Gaburici

11:48 p.m.

If you still haven't figured out how to reproduce it, apply the patched I've attached. It will force the hash entries to be added in sorted order. With the patch applied, if you have some fonts called Calibri Bold Italic.otf Calibri Bold.otf Calibri Italic.otf Calibri.otf the order of hash insertions will always exactly as above, regardless of disk order, e.g.: filename | 49 -> /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf filename | 50 -> /usr/share/fonts/vista/C-series/Calibri Bold.otf filename | 51 -> /usr/share/fonts/vista/C-series/Calibri Italic.otf filename | 52 -> /usr/share/fonts/vista/C-series/Calibri.otf So, you'll get bold italic instead of bold in the PDF. Feel free to fiddle with the sort function if you name fonts differently, but you need to make sure that bold italic gets loaded before bold for the bug to occur. On Thu, Aug 14, 2008 at 7:33 AM, Vasile Gaburici wrote:

...

On Wed, Aug 13, 2008 at 8:00 PM, Taco Hoekwater wrote:

...
Vasile Gaburici wrote:

...
Before I get anymore strawman arguments, here's the definitive experiment:

As Hans said, should be corrected in the latest beta. Please cut us some slack here, debugging unreproducible problems is hard and timeconsuming.

Okay, I've updated to the latest beta. Recursive OSFONTDIR works now for "script --fonts --reload" and for "context", but "script --fonts --list" is broken: no output.

The other bug, i.e. embedding bold italic instead of bold for some fonts, is still present.

Taco Hoekwater

14 Aug 14 Aug

2:33 a.m.

Vasile Gaburici wrote:

...

Feel free to fiddle with the sort function if you name fonts differently, but you need to make sure that bold italic gets loaded before bold for the bug to occur.

Ok, bug found and squashed. Patch is below

...

...
Okay, I've updated to the latest beta. Recursive OSFONTDIR works now for "script --fonts --reload" and for "context", but "script --fonts --list" is broken: no output.

Hans changed the commandline so that "nothing" is no longer the same as "*". This works: $ mtxrun script --fonts --list \* Best wishes, Taco --- font-syn.lua.old 2008-08-13 14:47:44.000000000 +0200 +++ font-syn.lua 2008-08-14 10:25:13.631806083 +0200 @@ -133,7 +133,8 @@ fontname = fontname or result.fontname add(result.fontname, fontname, filename, suffix, is_sub) end - if result.familyname and result.weight then + if result.familyname and result.weight and + result.italicangle == 0 then local madename = result.familyname .. " " .. result.weight fontname = fontname or madename add(madename, fontname, filename, suffix, is_sub)

Hans Hagen

2:48 a.m.

Vasile Gaburici wrote:

...

If you still haven't figured out how to reproduce it, apply the patched I've attached. It will force the hash entries to be added in sorted order. With the patch applied, if you have some fonts called

Calibri Bold Italic.otf Calibri Bold.otf Calibri Italic.otf Calibri.otf

the order of hash insertions will always exactly as above, regardless of disk order, e.g.:

filename | 49 -> /usr/share/fonts/vista/C-series/Calibri Bold Italic.otf filename | 50 -> /usr/share/fonts/vista/C-series/Calibri Bold.otf filename | 51 -> /usr/share/fonts/vista/C-series/Calibri Italic.otf filename | 52 -> /usr/share/fonts/vista/C-series/Calibri.otf

So, you'll get bold italic instead of bold in the PDF.

the order is just one factor. what actually happens is that there is a compensation for buggy font names (as happens often in afm files) so in practice one entry might become three entries; taco noticed that one of the fallbacks create this way will then obscure a following one in your case it might be order on disk (although the current mechanisms do some sorting) but on our machines more likely is that a bugged afm font obscures later otf's (with similar names) anyhow, we'll cook up a patch Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Thomas A. Schmitz

3:06 a.m.

On Aug 14, 2008, at 10:48 AM, Hans Hagen wrote:

...

the order is just one factor. what actually happens is that there is a compensation for buggy font names (as happens often in afm files) so in practice one entry might become three entries; taco noticed that one of the fallbacks create this way will then obscure a following one

in your case it might be order on disk (although the current mechanisms do some sorting) but on our machines more likely is that a bugged afm font obscures later otf's (with similar names)

anyhow, we'll cook up a patch

Hans

Very funny - I was following this thread with interest, yet had never encountered this problem. This morning, I played around with the minimals on my linux eeepc (had always used TeXLive, but saving some space seemed like a good idea) and got exactly the same problem: instead of bold, I get bold italic. If I typeset the same file with my TeXLive installation, I get proper bold. So Vasile is on to something here... Thomas

Taco Hoekwater

13 Aug 13 Aug

6:29 a.m.

Vasile Gaburici wrote:

...

I've switched to the rsync-ed minimals on Linux. There are still some problems with fonts:

1) Bold is still missing from fonts pulled via OSFONTDIR, e.g.:

verdana Verdana /usr/share/fonts/vista/Verdana.ttf verdana bold italic Verdana Bold Italic /usr/share/fonts/vista/Verdanaz.ttf verdana italic Verdana Italic /usr/share/fonts/vista/Verdanai.ttf

This may sound silly, but: does it work or not? To be precise, what is the font used by the pdf result (if any) of \starttext \definedfont[name:VerdanaBold] Hello \stoptext Best wishes, Taco

5826

Age (days ago)

5828

Last active (days ago)

List overview

Download

17 comments

5 participants

participants (5)

Hans Hagen
Taco Hoekwater
Thomas A. Schmitz
Vasile Gaburici
Wolfgang Schuster

Font problems with latest minimals on Linux

tags

participants (5)