https://issues.apache.org/ooo/show_bug.cgi?id=125483

--- Comment #3 from Alex Taylor <alts...@gmail.com> ---
After some more testing...

The 1993 versions of MSMINCHO.TTF and MSGOTHIC.TTF which are included in OS/2
Japanese (and other DBCS versions) exhibit this problem.  The problem MIGHT be
related to the fact that they include non-Latin Japanese names (MS明朝 and
MSゴシック) which are (only) used on DBCS OS/2 systems.  Since they in fact contain
only Unicode cmaps, this is the only factor I can identify which might explain
the different behaviour on DBCS vs non-DBCS systems.

If newer versions (MSMINCHO.TTC and MSGOTHIC.TTC) from e.g. Windows 7 are
installed instead, those ones seem to work perfectly well. These ones have
English-only names which are used on DBCS and non-DBCS systems alike.

Of the other default Japanese system fonts, Heisei Mincho and Heisei
Kaku-Gothic (both versions) do not work, even though they have English names. 
(However, I have checked the TTFs and they do not have Unicode cmaps.)  

So, the workaround seems to be: avoid the use of all the DBCS outline fonts
included with OS/2.  This is pretty cumbersome, of course, since users are
required to hunt down other DBCS fonts to use in their place.

This is almost certainly (yet another) bug in the Innotek Font Engine. This
really has to be replaced, it is causing too many problems at this point!

-- 
You are receiving this mail because:
You are the assignee for the issue.
You are watching all issue changes.

Reply via email to