<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - lang attribute support for family tag"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68377#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - lang attribute support for family tag"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68377">bug 68377</a>
from <span class="vcard"><a class="email" href="mailto:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> <span class="fn">Akira TAGOH</span></a>
</span></b>
<pre>I was thinking of improving 65-nonlatin.conf say, particularly to address
selecting unexpected font against the order of the fonts. I'm expecting that
applications gives the certain language in FcPattern though, it even breaks
with/without the language in FcPattern if the order of the font is totally
broken.
As you say finding better font against langauge is matcher's job right. but
this way won't affect too much IMHO because it's hard to find one out without
the lang in FcPattern and it should perfectly works if one gives the certain
lang in FcPattern then.
what I implemented to modify the langset in target="scan" was a workaround
IMHO... indeed it's capable to address this issue though, keeping "broken"
default configuration isn't a good idea. this sort of issues should be fixed
upstream so that most distros more or less has managed fonts in similar way. in
other words they know it's broken without it.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>