#587319 ttf-arphic-ukai: Font priority configuration (Unicode crash issue)

#587319#5
Date:
2010-06-27 12:57:48 UTC
From:
To:
Due to Unicode design, some code points are shared among different
locales.

Problem happens if one want to use Chinese font in mostly Japanese
working environment.

。、are at the corner in Japanese while Chinese fonts uses center
location.

There are many cases of font diffrerences.

Currently, installing any of these arphic fonts override all Japanse
font in priority.  I understand thee are more Chinese user but it will
be nice if this is confgurable.  As far as fontconfig is concerned, this
is possible.  But arphic fonts install data to override Japaese ones.

Can anyone come up with amicable configuration?

#587319#10
Date:
2010-08-22 10:04:44 UTC
From:
To:
zh_CN has ,。、at the left lower corner and zh_TW has them in the
middle. I am not sure which is chosen for ja, but zh_CN users really
feel uncomfortable when they see ,。、are in the middle.

As for LaTeX problem in #593916 I think I am not able to help since I
don't know about LaTeX.

#587319#15
Date:
2010-08-22 11:35:12 UTC
From:
To:
Hi,

On Sun, Aug 22, 2010 at 06:04:44PM +0800, Aron Xu wrote:
...

You have a very good point.  That font comes from zh_TW.  I was assuming
all zh using people share the same feeling without no reason.  Excuse
me.  I should have known better.

I know there are many differences in preferences between ja_JP, zh_CN,
zh_TW, ...  (Also my late grandfather had a very different spelling
preference over what modern Japanese government chose and forces us to
use ...).  That is why we need a technical solution to accomodate any
user preferences easily and respectfully.

Let's wait ...

Osamu

#587319#20
Date:
2011-08-29 05:49:30 UTC
From:
To:
Hi,

I'm not really sure why this bug report has been filed against the
ttf-arphic-ukai package. This package installs the
75-ttf-arphic-ukai-select.conf file, which prevents fontconfig from ever
choosing this font.
Your criticism may be true for the ttf-arphic-uming package, but
shouldn't be for this one. :)

Can you please confirm. if indeed the UKai font is the culprit?

Thanks a lot.
Arne