Closed
Bug 107515
Opened 23 years ago
Closed 23 years ago
On Unix, font familyname aliases should be configured with pref or a configuration file
Categories
(Core :: Layout, enhancement, P5)
Tracking
()
Future
People
(Reporter: shom, Assigned: attinasi)
Details
(Whiteboard: [bae:20011030])
0.9.5 on Linux. problem: In MANY pages in Japan, <font face="?? ???"> are used very often, but ignored on Unix. cause: Mozilla searches -*-<family-name>-*, but XLFD is not allow -*-?? ???-*. solution: Now, familyname aliases are hardcoded in nsFontMetricsGTK.cpp. ex) arial = helvetica, courie new = courier, times new roman = times They should be configurable to read prefs or configuration files, so many distributors can modify fontfamily.aliases to match their system font configurations.
Reporter | ||
Comment 1•23 years ago
|
||
"face" above is "MS P Mincho" in Japanese. U+ff2d U+ff33 U+3000 U+ff30 U+660e U+671d.
confirming. any thoughts on the implementation of this? (Unicode config file? prefs.js? GUI?)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 3•23 years ago
|
||
I think a configuration file in UTF-8 (or capable with Unicode escape) is enough. GUI is not necessary. configuration file is very simple. It only can generate gFamilyNameTable[] in nsFontMetricsGTK.cpp on startup, or read in InitGlobals() and add key-value(original-alias) to gAliases. If .properties allows UTF-8 (or Unicode escaped string) as key, res/unixfontaliases.properties is good choice :). Or XML <fontalias name="[UTF8str]" xname="[XLFD family"> ?
Comment 4•23 years ago
|
||
placing enhancement request into future bucket
Priority: -- → P5
Whiteboard: [bae:20011030]
Target Milestone: --- → Future
Comment 5•23 years ago
|
||
this looks like a dup of 80687
duplicate, 80687 already had some discussion on this *** This bug has been marked as a duplicate of 80687 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Oh, and just to make sure, most web designers using: a) SJIS b) "?? ???" as an actual font name should be shot anyway.
You need to log in
before you can comment on or make changes to this bug.
Description
•