On 05/08/2011 07:12 AM, Qianqian Fang wrote:
> Making language-selector-zh-* Chinese specific will leave 65-nonlatin
> the only one active to set CJK font proprieties under non-CJK locales
> (such as en_US etc).
Yep, and one more thing:
language tagging only works if the text which is displayed is _also_
tagged with the correct language code.
In an ideal world every application and every text would be tagged with
the correct language code and the rendering engine would choose the
correct font for every language.
Configuring fontconfig to do so is only one part of the story. The next
step would be to hunt down every application which does not support
language tagging and does not have proper fontconfig integration. And
this includes content management systems which are used on the web. And
then you would need to check all kind of websites if they use proper
language tagging or not, and report to the webmaster if they don't. (And
then hope that they will fix it, which they probably won't.)
The fontconfig configuration can (and probably should) be fixed in each
distribution (we can coordinate this if upstream doesn't bother). But
this doesn't mean that CJK rendering will automatically be improved.
For hunting down applications which don't comply, filing bugs upstream
and maybe sending patches, we would need some volunteers (probably a
team) to do that efficiently... and some coordination of course. Anyone?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 05/08/2011 07:12 AM, Qianqian Fang wrote: selector- zh-* Chinese specific will leave 65-nonlatin
> Making language-
> the only one active to set CJK font proprieties under non-CJK locales
> (such as en_US etc).
Yep, and one more thing:
language tagging only works if the text which is displayed is _also_
tagged with the correct language code.
In an ideal world every application and every text would be tagged with
the correct language code and the rendering engine would choose the
correct font for every language.
Configuring fontconfig to do so is only one part of the story. The next
step would be to hunt down every application which does not support
language tagging and does not have proper fontconfig integration. And
this includes content management systems which are used on the web. And
then you would need to check all kind of websites if they use proper
language tagging or not, and report to the webmaster if they don't. (And
then hope that they will fix it, which they probably won't.)
The fontconfig configuration can (and probably should) be fixed in each
distribution (we can coordinate this if upstream doesn't bother). But
this doesn't mean that CJK rendering will automatically be improved.
For hunting down applications which don't comply, filing bugs upstream enigmail. mozdev. org/
and maybe sending patches, we would need some volunteers (probably a
team) to do that efficiently... and some coordination of course. Anyone?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iQIcBAEBCAAGBQJ NxdnxAAoJENiwmJ tstTzscIUQALcdO iSjMw0u60i3QRjJ mXi2 /cpNEgohJrffMw/ /Gz5VxatBJG00v8 lT6tIy+ 9jBOpUOWdDaB 28xm3FeDXl4b61I NneqaTFCUB8aldj TEySsW+ i2XYfXw5MCcI jFc+ZcMnf/ vImZ8HN3f4FJsCD Weag+iaWbXrPF9R jSwyAzQ5c bHWt3ayQyAbPEEQ 5aMEqHgP2inKCJW ztrRaSQluoOJw+ QU9wv lKufMyLgxGh2B6g 4iGua3yoD6Wj13L UG3l4F+ OP2S23wPQloK H5nTUKt5jJltiEq km2Jwbjy5E5anTH 5AqHgbfv6vZOcRD m6imnsgj2 SiRKt5yXsGlwKPG xb0WONYMG2eNB68 8rpvKhCoy4vZtOS T1iO vBkhDd1jPpiu7iP m22bxFnBwynG0iJ sqpQCaxI2m+ 8zRDQ2BIu7Lvc kGiEWm9EzJDVpFW fJk6dEyDO8jCVka IJcWQOoIt6IFiQ8 GJsp bM6ckOXl4Z4HlYc AToOPo5igRoG3uL 6MkrIi+ QkkBzmICNT2p 0ZPtu
TbJWkGbIOeJStpY
+cGt9jrmNZ5GhbK
LJzM7LzbF81p1VG
NW15ZdqPTcWOTh3
EzrYbR7oc2MJ8jF
wQIRXXw3a/
+f0pT9fW8Uc7sy6
dd0oPDej0+
C4yLPvBIBImpGsO
EWIDI8LIlRiXe7E
pefCmQwCpApfNBS
=DFj1
-----END PGP SIGNATURE-----