Issue 98833 - font name localization with OO's own option
Summary: font name localization with OO's own option
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2009-02-04 03:31 UTC by kiwon
Modified: 2014-04-04 08:40 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: 4.1.0-dev
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description kiwon 2009-02-04 03:31:51 UTC
This issue is not only for the word processor, but also all other OOs.

Each font has its own localized name, e.g "ì€ ë°”íƒ•" for Korean and "UnBatang"
for English. In OOs, these distinctions work only with LANG setting in the
system. But many people like me are using a different locale such as
LANG='en_US.UTF-8' setting due to some problems with their own locale. Sometimes
this face produces some artifacts when we use OOs among different systems.

Those problems might be solved with an explicit locale setting hack, LANG='...',
before executing OOs. But this may not be a good solution.

So I suggest that the locale of font name follows the setting of OOs' own
language setting, "Menu->Tools->Options->Language Settings->Languages..."

We may need some discussions. :)
Comment 1 eric.savary 2009-02-04 10:17:15 UTC
Comment 2 Edwin Sharp 2014-04-04 08:40:20 UTC
Confirmed with
AOO410m15(Build:9761)  -  Rev. 1583666
2014-04-01 13:50 - Linux x86_64

PS similar request for function names exists.
Tools - Options... - Language Settings - Languages - Language of User interface should split to: Main UI, Fonts, Functions