Apache OpenOffice (AOO) Bugzilla – Issue 1990
font substitution problem for Chinese
Last modified: 2013-08-07 15:00:01 UTC
For a Chinese document which contains Chinese and English content: The Chinese and English characters are typed using fonts in machine A, but those fonts do not exist in machine B, when opening the file in machine B, only the English characters will be shown using a replacement font, but the Chinese characters will not be shown (just empty space).
Created attachment 609 [details] An example file containing Chinese and English, but only English will be shown on loading
DL->HDU: I think it's your task
The document is displayed correctly in StarOffice. The problem with OOo is that we cannot provide our fonts with it. And in general there are no other Unicode fonts available on the distributions. So which font to fall back when none are available? The fs-1.sxw document sets the font for the chinese characters to "Times New Roman". So I guess on a typical linux installation this falls back to "Times". With StarOffice we always can fall back to "Andale", which contains most asian glyphs. Without a fallback font like this we just cannot reliably fall back.
> The problem with OOo is that we cannot provide our > fonts with it. And in general there are no other > Unicode fonts available on the distributions. So > which font to fall back when none are available? > The fs-1.sxw document sets the font for the chinese > characters to "Times New Roman". So I guess on a > typical linux installation this falls back to "Times". > With StarOffice we always can fall back to "Andale", > which contains most asian glyphs. Without a fallback > font like this we just cannot reliably fall back. Thanks for your information. But can we set our own fall back font? Can we simply change the configuration in the option menu or is there any way to change the source code in order to do this? I think it would be very very useful.
So, OpenOffice won't be able to find out a suitable font (containing the glyph) available from the system?
Yes, we plan to make the font and glyph fallback more flexible. Since this will be much easier in the complex text layout framework we are currently working on that problem will be attacked there.
What's the current status? I really want to see the latest update, thank you for all the great works!
Glyph fallback will work in OOo1.1, but only for static fallback lists. Dynamic fallback lists are not planned yet, so this much more general case is not 100% covered if the distribution developers don't add their fonts to the fallback lists.
Problem persists in 644.
Which 644? 1.1beta?
from the tag: cws_srx644_ooo11beta thanks.
Because of limited resources this task have to re-targeted to target 'OOo Later'. If somebody can be found, who cna implement this task, it can be re-targeted to OOo 2.0.
Is there any reason why OOo can not ship with the fonts that are shipped with Linux distributions. Configure those fonts as the "fallback" fonts for non-western languages.
This issue has become obsolete since the mechanism to define fallback fonts in VCL.xcu has been introduced. If the VCL.xcu configuration file needs to be extended for specific fonts please file individual patches against this file. Changing status to reflect the situation for most commonly used fonts.
Closing issue.