Apache OpenOffice (AOO) Bugzilla – Issue 30431
Check box for suppression of Bitmap glyph
Last modified: 2013-02-07 22:34:08 UTC
Do you have a chance to add a new option for suppression of Bitmap glyph in Tools > Options > ProductName > View near an option Screen font antialiasing? A need of controlling whether use of Bitmap glyph embedded in a TrueType font file or not is increasing. Nowadays, many users are using high-quality computers. In such case, no Bitmap glyph is required any more. It has a poorer quality than that of vector glyph on high resolution, high depth in color display. Bitmap glyph, however, is still needed on old computers. So Adding a new check box in the Tools > Options window and controlling use of Bitmap would be a good strategy to make OOo/SO/SS more competitive.
Created attachment 15971 [details] Depicts comparison between Bitmap and vector glyph on high quality display.
Created attachment 15972 [details] Is a bug doc.
To take Bitmap glyph away, 1. mkdir work 2. cd work 3. perl ../ttfar -xvf ../xxx.ttf 4. rm EB* 5. perl ../ttfar -cvf ../xxx-Bitmap-removed.ttf
Created attachment 15973 [details] A hand-made tool that extracts and assembles internal tables of TureType font file.
Oops, Correction: 5. perl ../ttfar -cvf ../xxx-Bitmap-removed.ttf *
cp->mmp: maybe you ? ;-) adding a checkbox is easy, however currently we would require to restart the Office, and it's not just TrueType but X11 bitmap fonts in general. I'd like to address font related issues in the next major after 2.0.
This looks like your G11n area, Falko.
forgot to assign it to you. It still looks like G11n.
FT: I agree with CP. Since we have more than enough on our schedule for 2.0 I postpone thisissues to OO.o Later
JA: this can be set via environment variable: SAL_EMBEDDED_BITMAP_PRIORITY to 0 In this case it's just a decision if we implement and where we implement a checkbox to deactivate the suppression of bitmap glyphs if they're availble within a font. In my opinion it's a "no brainer" to get this into 2.0 JA->FT: please think again about your decision
I have changed my position from adding new options to removing similar ones. Relationship_between_OOo_and_Desktop.png illustrates a relationship between OOo and Desktop properties. OOo Windows version does not have such options that control appearance of fonts since Windows itself does it. Similarly, recent Gnome has a feature to control appearance of fonts. OOo could use the properties that a user can specifies through Gnome Desktop interface. Now, I don't think it would be a good idea for additional options that I proposed before as long as we have another option - an environment variable, SAL_EMBEDDED_BITMAP_PRIORITY -. However, the addition of new options could be acceptable until most Linux distributions employ a way of controlling font properties. I would like to leave a decision to Falko.
Created attachment 16426 [details] Illustrates relationship between OOo and font properties of Desktop
Created attachment 16427 [details] The same one in Draw.
FT: Re-assigned to requirement default user