80687 - Need a way to control what goes in gFamilyNameTable

Status: NEW

(Core :: XUL, defect)

Description

[TVL]

in nsFontMetricsGTK, the mappings in gFamilyNameTable for arial, courier new. and 
times new roman are all hardcoded.  There needs to be a way that and embeddor can 
provide what these mappings should be (pref, compile time, something).

Comment 1

[Adam Lock]

Reassigning to XP widgets to gather suggestions on the best way this should be 
done.

Comment 2

[rbs]

-> property file (see what I did in bug 73273 for a similar problem).

Comment 3

[Peter Trudelle]

Who owns this stuff?  GFX doesn't have a bugzilla component, and I see lots of
names giving r= in the code, but nobody on my team. ->ftang, cc bstell

Comment 4

[Frank Tang]

reassign to bstell. I am not sure how high the priority should be. we also need 
to watch start time performance.                                                          

Comment 5

[pocemit]

gisburn, let's do this

rbs: how does nsIPersistentProperties deal with unicode property files?
Some CJK font aliases would definitely have to have Unicode names

Comment 6

[pocemit]

*** Bug 107515 has been marked as a duplicate of this bug. ***

Comment 7

[Roland Mainz]

I can implement this (but in 0.9.7, my 0.9.6 ToDo list is far too large now) ...

Comment 8

[pocemit]

There is very nice code dealing with a very similar problem in Win32 gfx/,
using nsIPersistentProperties.
Looks like PersistentProperties will handle unicode properly, using \xxxx escapes.
nsFontMetrics*::TryAliases would have to be adjusted too.

Comment 9

[rbs]

>how does nsIPersistentProperties deal with unicode property files?

&#xNNNN; -> \uNNNN

(e.g., http://lxr.mozilla.org/seamonkey/find?string=mathfont)

Beware: in the "name = value" pair, the name is left as-is, while the value is 
mapped to Unicode. So if you put \uNNNN in the "name" part, it will be kept 
as-is, i.e., the equivalent 6-character ASCII string: '\', 'u', and digits... 
but if you put \uNNNN in the "value" part, it is converted to the single 
corresponding Unicode character.

Comment 10

[kill this account]

--> ftang

Comment 11

[Frank Tang]

bulk move NEW FUTURE bug to ASSIGN

Comment 12

[Adam Hauner]

-> to default owner

Comment 13

[Alexander Sack]

Is this bug still considered valid? jag are you still working on this?