Fontconfig - Mar 2010 - Font matching mismatch when font has two language name.

In my ~/.fonts.conf

<match target="font">
	<test
name="family"><string>NanumGothicCoding</string></test>
	<edit
name="autohint"><bool>false</bool></edit>
</match>

It''s Korean fonts. Now let''s test my config.

~$ fc-list | grep NanumGothicCoding
NanumGothicCoding,??????:style=Regular
NanumGothicCoding,??????:style=Bold

~$ fc-list | grep ??????
NanumGothicCoding,??????:style=Regular
NanumGothicCoding,??????:style=Bold

~$ fc-match NanumGothicCoding -v | grep autohint
	autohint: FcFalse(w)                             // What I want

~$ fc-match ?????? -v | grep autohint
	autohint: FcTrue(w)                             // It''s same font.
But didn''t work.

~$ fc-match NanumGothicCoding -v | grep ''family:\|fullname:''
	family: "NanumGothicCoding"(s)
	fullname: "NanumGothicCoding"(s)

~$ fc-match ?????? -v | grep ''family:\|fullname:''
	family: "??????"(s)
	fullname: "NanumGothicCoding"(s)

Is this bad font problem or fontconfig? Should I add two rule for same font?
Or should make rule with ''fullname'' element? I''m
wondering what is right
way.

Thanks for any advice.

Here are my ENV

~$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL
~$ apt policy fontconfig
fontconfig
Installed: 2.6.0-1ubuntu12
Candidate: 2.6.0-1ubuntu12
Version table:
*** 2.6.0-1ubuntu12 0
500 http://kr.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status

~$ fc-match --version
fontconfig version 2.6.0

I''m using linuxmint 8 - It''s Ubuntu 9.10 based

-- 
Mait

On 03/31/2010 12:04 PM, ??(Mait) wrote:
> In my ~/.fonts.conf
> 
> <match target="font">
> 	<test
name="family"><string>NanumGothicCoding</string></test>
> 	<edit
name="autohint"><bool>false</bool></edit>
> </match>
Does it help if you add qual="any" to your test?

behdad

Thanks for quick help, Behdad : )

I got some hint from qual="any".

<match target="font">
	<test name="family" qual="any">
		<string>NanumGothicCoding</string>
		<string>??????</string>     // added
	</test>
	<edit
name="autohint"><bool>false</bool></edit>
</match>

Then now,

~$ fc-match NanumGothicCoding -v | grep autohint
	autohint: FcFalse(w)

~$ fc-match ?????? -v | grep autohint
	autohint: FcFalse(w)                // It works !

It works also without ''qual="any"'' - as I know
It''s default value.
But one question, is this right config for font that has two language
''family''?

Thanks.


2010/4/1 Behdad Esfahbod <behdad at behdad.org>:
> On 03/31/2010 12:04 PM, ??(Mait) wrote:
>> In my ~/.fonts.conf
>>
>> <match target="font">
>> ? ? ? <test
name="family"><string>NanumGothicCoding</string></test>
>> ? ? ? <edit
name="autohint"><bool>false</bool></edit>
>> </match>
>
> Does it help if you add qual="any" to your test?
>
> behdad
>


-- 
Mait

Ok, let me look into this.  Sounds like a bug.

behdad

On 03/31/2010 12:26 PM, ??(Mait) wrote:
> Thanks for quick help, Behdad : )
> 
> I got some hint from qual="any".
> 
> <match target="font">
> 	<test name="family" qual="any">
> 		<string>NanumGothicCoding</string>
> 		<string>??????</string>     // added
> 	</test>
> 	<edit
name="autohint"><bool>false</bool></edit>
> </match>
> 
> Then now,
> 
> ~$ fc-match NanumGothicCoding -v | grep autohint
> 	autohint: FcFalse(w)
> 
> ~$ fc-match ?????? -v | grep autohint
> 	autohint: FcFalse(w)                // It works !
> 
> It works also without ''qual="any"'' - as I know
It''s default value.
> But one question, is this right config for font that has two language
''family''?
> 
> Thanks.
> 
> 
> 2010/4/1 Behdad Esfahbod <behdad at behdad.org>:
>> On 03/31/2010 12:04 PM, ??(Mait) wrote:
>>> In my ~/.fonts.conf
>>>
>>> <match target="font">
>>>       <test
name="family"><string>NanumGothicCoding</string></test>
>>>       <edit
name="autohint"><bool>false</bool></edit>
>>> </match>
>>
>> Does it help if you add qual="any" to your test?
>>
>> behdad
>>
> 
> 
>