On Tue, 23 May 2006 19:33:31 +0100, Alex Bligh wrote: > > amb@polonius:~/camelot/XaraLX$ fc-match Arial > n019003l.pfb: "Nimbus Sans L" "Regular" ... > Sure - but we should not expect users to have to do this. I think you've got the issue well-established now. But, to make it completely concrete: The easy, standard way to make this work on fontconfig-based systems is to use a actual standard name for the default font. Charles has been arguing "Arial" based on a de facto Windows standard. Meanwhile, fontconfig-based systems would suggest one use an actual standard such as CSS2: http://www.w3.org/TR/REC-CSS2/fonts.html#generic-font-families This defines five "generic font families" that are defined to exist in all CSS implementations: serif sans-serif cursive fantasy monospace Stick to those and if you hit any operating system that doesn't map any of those to an actual, existing font, then you've found a definite bug in that OS. -Carl
Attachment:
pgpGrxDukPLfj.pgp
Description: PGP signature