Christian,<br><br>I agree completely with you and learn a lot from you detail explanation. Next I'd need a bit of advice to fix the bug I've mentioned.<br><br><div class="gmail_quote">On Sun, Feb 6, 2011 at 1:40 AM, Christian Lohmaier <span dir="ltr"><<a href="mailto:lohmaier%2Blibreoffice@googlemail.com">lohmaier+libreoffice@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
> On Sat, Feb 5, 2011 at 9:59 PM, Christian Lohmaier<br>
> <<a href="mailto:lohmaier%2Blibreoffice@googlemail.com">lohmaier+libreoffice@googlemail.com</a>> wrote:<br>
</div>On Sat, Feb 5, 2011 at 6:38 PM, Nguyen Vu Hung <<a href="mailto:vuhung16plus@gmail.com">vuhung16plus@gmail.com</a>> wrote:<br>>>> [VCL.xcu / list of default fonts and fallback]<br>
<div class="im">>> When there are issues "cross-locale", then raise them. It is not that<br>
>> the list didn't change since the beginning of the OOo project.<br>
> If I understand the OP correctly, he wants LibO to<br>
> 1. Handle different languages on different locales.<br>
This is already done.<br></div></blockquote><div><br>I'd like to explain a bit about our (Thai) situation. Thai users may use en_US or th_TH for UI locale to get English menu and translated menu respectively. Normally, en_US are used for most users. The UI font replacement list based on locale seem to assume that for en_US UI locale, only Western characters will be in the UI. However, UI font isn't only used for static text in menu and dialog box. But also for user text in File > Property > Description text boxes, File > Recent Documents filename list, and Calc formula bar. For user/editable text like these, they could be in any languages - Western, CTL, CJK.<br>
<br>So with this (user text) in mind, the higher-priority font in UI font list should have good glyph coverage. For example (I know little about fonts), Tahoma or Microsoft Sans Serif in Windows. So I imagine replacing Andale UI with Tahoma (or better default) in the list. <br>
<br>Having default with good glyph coverage is a good thing. However, LibO itself should display any multi-lingual text correctly if glyph fallback work correctly. But as you can see in the bug we've submitted : <a href="https://bugs.freedesktop.org/show_bug.cgi?id=33090" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=33090</a><br>
Glyph fallback for <b>CTL</b> text in <b>Windows</b> is currently broken but <b>"only"</b> for UI text rendering, not for text in the document. It used to work in older versions. This is the part that we'd like to fix. Can you give as a clue about where should we look in the VCL source?<br>
<br>Thanks.<br><br></div></div>-- <br>_/|\_ Samphan Raruenrom. Open Source Development Co., Ltd.<br>Tel: +66 38 311816, Fax: +66 38 773128, <a href="http://www.osdev.co.th/">http://www.osdev.co.th/</a><br>