[tex-live] Palatino / figbas - ligatures for baroque music corrupting web pages(?!)

[Norbert Preining]

Simple answer:

On Mo, 10 Jan 2011, andrew cooke wrote:
> I originally reported this as a bug to OpenSuse, who have replied saying that I 
> need to take it "upstream", which I think means you guys.

That is a bug in openSuSE, not TeX Live ....

> When I viewed web pages with Palatino fonts (in any web browser) I was seeing 
> strange versions of the digits 2, 4, 5, 6 and 9.  I eventually traced this to 
> the file /usr/share/texmf/fonts/type1/public/figbas/plrj.pfb - deleting that 
> file and rebuilding the font cache fixed the issue.

That is probably because the packagers of TeX Live for SuSE have
blindly made *ALL* fonts from TeX Live available to the X server
or fontconfig or whatever they are using, without providing
enough tagging for the fonts and information.

The web browser (your bug report is btw so incredible unclear, you 
did *nowhere* say which OS, which version of TeX Live, which browser,
... all I do is as usual reading from my Crystal Ball ...) uses
probably libfontconfig to get fonts.

You can use 
	fc-cache
and
	fc-list
to search for "Palatino" and see what is spit out (no I don't explain
the detials, I don't know them myself, agian, all Crystal Sphere).

And yes, it is a bug in SuSE, the font should probably not be made
available to fontconfig.

> There's a lot of information here - https://www.quora.com/Typefaces/Why-is-
> Palatino-displaying-2-with-a-vertical-line-that-makes-it-look-like-4 (please 
> expand the "more" under the question link to see everything).  That includes 
> images of the problem.

BTW, please provide links that are useable, and not broken across lines.

And as I saw ... the page you mentioned shows that fontconfig is
using that font. That is not good. So it should not be procided to
fontconfig.

> The OpenSuse bug report is here - https://bugzilla.novell.com/show_bug.cgi?
> id=662159

And here I see that Werner Fink said you should contact us.
Well, we are not upstream, the author of the font itself has to fix
the (maybe wrong - I don't know) fontname.

The whole point is that not blindly all fonts in texlive should
be made available to fontconfig, this is my opinion, and this is
what I (putting Debian hat on) do when packaging TeX Live for Debian.

> If this still is not the correct place to report this, please can you tell me 
> who to talk to?  I realise that it looks a little like one of those annoying 

The author of the original font.

But he will probably tell you: This is a font for TeX, NOT for the X
Window System of fontconfig, why on earth are you using it there?

Enough for today.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
SNITTERFIELD (n.)
Office noticeboard on which snitters (q.v.), cards saying 'You don't
have to be mad to work here, but if you are it helps !!!' and slightly
smutty postcards from Ibiza get pinned up by snitterbies (q.v.)
			--- Douglas Adams, The Meaning of Liff