Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Fonts in large Type 1 families not recognized correctly | ||
---|---|---|---|
Product: | gsl | Reporter: | wshooper <wsh-openoffice> |
Component: | code | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, niemayer |
Version: | 641 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
Developer Difficulty: | --- | ||
Issue Depends on: | 79878 | ||
Issue Blocks: |
Description
wshooper
2002-01-17 05:02:20 UTC
besides the book-light clash this works as designed: The addstyle name is usually not taken into account. Anyway William has a point here that the presentation of typefaces is very limited. I would be glad if you could evaluate the gimp as this feature is concerned and come up with a RFE. The gimp has a high reputation so it is surely worth a look. Reassigened to Bettina. I think this issue is more severe than it seems from the descriptions here: OO is not only unable to make certain font styles available to the user, but in fact confuses font styles in a way that makes certain well-known fonts unusable under certain conditions. Example: Import the original Adobe Type 1 font "Helvetica" from spadmin. Works fine. Now also import the original Adobe Type 1 font derivative "Helvetica-Fraction" - a special variant that is only meant to create good looking fraction numbers, such as "3/17". Now you cannot choose the "-Fraction" variant, but that is the minor part of the problem. If you're unlucky, depending on the order the fonts appear in your share/psprint/pspfontcache file (as "File:XXXX.pfb ... etc.), you're now unable to use the ordinary "Helvetica" font, because OO confuses the "Helvetica-Fraction" variant with it. If you print a document that shall contain Helvetica letters, you can see the wrongly chosen font when you look through the resulting .ps file. I think the only solution is to teach OO to treat whatever "font-style" may appear that is not known to OO as a different font familily. Of course you could also teach OO about all existing variants, but there are far too many and maybe unknown ones ("-Display", "PhoneticalAlternate", "-UltraHeavy" etc.). This looks more like a fontconfig/freetype2 issue (if OO is using fontconfig). Almost all freetype2-based apps I've used give wrong results for lots of Type 1 fonts (esp. commercial fonts). I'm glad to see this issue is well-documented. I was thinking I would have explain
it in depth.
Pniemayer states:
> I think the only solution is to teach OO to treat whatever
> "font-style" may appear that is not known to OO as a different font
> familily.
I disagree that this is the *only* solution, though it might be a good one. An
alternative might be to keep the fonts in the same family, but provide, probably
in the Format -> Character dialog, a selection list of "Additional
variants"--since there is no universal scheme for classifying unusual font
variants, and different vendors may use different terms for the same thing or
vice versa, the list should probably just give the PostScript name for each
font, with no attempt to interpret that name. I suspect this approach might be
easier to implement and less error-prone than automatically creating new families.
As others have argued, I believe that OpenOffice (or freetype, or whatever
software component is responsible) needs to be more sophisticated in recognizing
font variants, so that the "normal" typefaces will be used by default in most
cases, and that users should have access to all installed variants when creating
documents. On the other hand, I doubt that these measures will be sufficient for
all cases. There should also be an "advanced font management" interface that
allows users to manipulate font classifications when OpenOffice is unable to do
the right thing automatically.
Reasigedn to the owner requirements. |