To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112739





------- Additional comments from [email protected] Thu Sep 23 13:50:27 +0000 
2010 -------
Some findings to date:

a) The replacement text being the same as the original word in the autocorrect
file makes writer spawn a slow full-document load to see if its a different type
of replacement via properties, we should remove that entry from the stock
autocorrect anyway as even without this bug it causes an extra delay. I'll do
that in issue 114704

b) For me what I see is that dtardon's change is good, but with it in place when
we look up the default CJK font we get a fontname back from fontconfig which
happens to be a CJK name, i.e. not in english one but we're not able to find the
fontname in our list of known fonts because our list is only of the English
names, so we keep looping searching for another one until 

c) In the fontconfig code we pick the best fit localized name for the fontname
to display. We should try in order of "Exact Language", "Close Language",
"English", "First Entry", rather than the current "Exact Language", "Close
Language", "First Entry", see issue 114703 for this

d) The font aliases are being read in truncated, see issue 114702

e) In e.g. Chinese locale only the English names of the font are being
displayed, I'm sure that the Chinese ones were displayed at some stage in the
past, hmm.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to