Need a way to control what goes in gFamilyNameTable

NEW
Unassigned

Status

()

Core
XUL
17 years ago
9 years ago

People

(Reporter: TVL, Unassigned)

Tracking

Trunk
Future
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
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).

Updated

17 years ago
Blocks: 77421

Updated

17 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 1

17 years ago
Reassigning to XP widgets to gather suggestions on the best way this should be 
done.
Assignee: adamlock → trudelle
Component: Embedding APIs → XP Toolkit/Widgets
QA Contact: mdunn → jrgm

Comment 2

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

Comment 3

17 years ago
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
Assignee: trudelle → ftang

Comment 4

17 years ago
reassign to bstell. I am not sure how high the priority should be. we also need 
to watch start time performance.                                                          
Assignee: ftang → bstell

Updated

17 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → Future

Comment 5

17 years ago
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

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

Comment 7

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

Comment 8

17 years ago
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

17 years ago
>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

16 years ago
--> ftang
Assignee: bstell → ftang
Status: ASSIGNED → NEW

Comment 11

16 years ago
bulk move NEW FUTURE bug to ASSIGN
Status: NEW → ASSIGNED

Comment 12

13 years ago
-> to default owner
Assignee: ftang → jag
Status: ASSIGNED → NEW

Comment 13

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

Updated

9 years ago
Assignee: jag → nobody
You need to log in before you can comment on or make changes to this bug.