Apache OpenOffice (AOO) Bugzilla – Issue 4467
Specific TrueType font doesn't display or print
Last modified: 2003-01-24 14:02:18 UTC
The attached TrueType font does not work at all in Open Office, yet works in every other Windows app. I can find.
Created attachment 1547 [details] Truetype font that is the base of this issue
I have determined the cause of the problem: Any font with a double name separated by a comma (in my instance, "Hall, Gilliam") causes OO to look for the font Hall followed by the font Gilliam . The Help file states that a semi-colon should be the separator, not a comma. So, in theory, the font "Hall, Gilliam" should have worked. Recommendation: Ensure future versions insist on a ";" as the separator.
In short: the fontname is "Hall, Gilliam". vcl treats this as "either Hall or Gilliam". This is a feature since you can type a fontlist in the font list box and you get whatever member is available. Changing "," to ";" does not really change the issue as it will break "Hall; Gilliam". If we want to fix this we need to change our UI to provide defaults. We may also run into problems with old documents that contain such fontlists. CP->CJ: the impact of this bug goes far beyond vcl. Is this a feature we want to have ?
Is not there a different way figure out the font? But back to your question. I could live with a font list separated by ";". We could go for example this way: When users create a font list they can use spaces, commas or a semicolon for separating. After applying the list we convert the list to a semicolon separated one. Old font list will work, too - they will only be displayed in the new way.
Hi Christian, the point is that we must not have any separator in the font list. Neither "," nor ";" nor ":" nor anything else. How would you distinguish the single font "Hall; Gilliam" from the two fonts "Hall"; "Gilliam" ? You can play this game with any separator. A truetype font name is not limited to any character set, potentially it can be ";,:-_ +*+()/&%$§$". If we really want to support this then we need a different UI for entering fonts/lists of fonts.
OK, in my opinion we shouldn't fix that issue, because of too many changes. If TTF-names can include every kind of character it is for us not possible to create a fontlist. For example if a question mark is the separetor for the font list - your font will work, but than some one creates a font with question mark in the name we will have the problem again. A only work around I see is to rename the font.
I close this issue.