Open
Bug 231257
Opened 22 years ago
Updated 18 years ago
'allow documents to use other fonts' : confusing : change it to 'always use my fonts'
Categories
(SeaMonkey :: Preferences, enhancement)
SeaMonkey
Preferences
Tracking
(Not tracked)
NEW
People
(Reporter: jshin1987, Unassigned)
Details
About a month ago, on the Linux-utf8 mailing list, I found that a person pretty
knowledgable with font and I18N got completely wrong the meaning of 'allows
documents to use other fonts'. Today, I found that Korean localized version of
Mozilla got it wrong in a similar manner. Then, I realized that Firebird has
'always use my fonts' in place of 'allow documents to use other fonts' (the
meaning is the opposite, needless to say). I guess we have to make a similar
change in Mozilla suite. Some possibilities inclue:
1. Ignore fonts specified in documents
2. Use fonts specified in document (opposite of the above, but the same as
'allows documents to use other fonts')
3. Always use my fonts
4. Always respect my font specficiation
What do you think?
See also bug 79074.
Comment 2•22 years ago
|
||
I quite like the idea of [x] Ignore fonts requested by web pages
Alternatively, if we have room, we could go for a radiogroup:
+- When a web page requests specific fonts: ---------+
| ( ) Always use the fonts specified by the web page |
| (o) Use my fonts, ignoring the fonts specified |
+----------------------------------------------------+
Comment 3•22 years ago
|
||
> 1. Ignore fonts specified in documents
> [x] Ignore fonts requested by web pages
So why would we let pages specify monospace, and (if bug 79074 is fixed) other CSS
generics? (Maybe bug 79074 is too complex, but monospace would still be a problem.)
> 2. Use fonts specified in document
Human thinks: "This is turned on, so what's the point of the other options? Why
aren't they disabled?"
> 3. Always use my fonts
> 4. Always respect my font specficiation
Human thinks: "Always as opposed to what? Sometimes? Rarely? During a full moon?"
> ( ) Always use the fonts specified by the web page
That doesn't work if a page specifies Smegalicious Gothic, coz you don't have it.
> (o) Use my fonts, ignoring the fonts specified
See "1." above.
I could see the text being changed as much as, say, "Let pages use other fonts too".
But the word "other" is key: that's what explains how the prefs work together.
| Reporter | ||
Comment 4•22 years ago
|
||
(In reply to comment #3)
> I could see the text being changed as much as, say, "Let pages use other fonts
too".
> But the word "other" is key: that's what explains how the prefs work together.
That wouldn't work. That's almost identical to what we have now, which is
confusing. The keypoint of this bug is that the meaning of 'other' is far from
clear. Besides, adding 'too' makes it even worse because that gives an
impression that fonts specified in the document are the last resort.
>> ( ) Always use the fonts specified by the web page
> That doesn't work if a page specifies Smegalicious Gothic, coz you don't have
> it.
What's wrong with that? Even a dummy would know that.
Comment 5•22 years ago
|
||
OK, so how about:
( ) Only allow web pages to use these fonts
(o) Allow web pages to use any installed font
Updated•21 years ago
|
Product: Browser → Seamonkey
| Reporter | ||
Comment 6•21 years ago
|
||
(In reply to comment #5)
> OK, so how about:
> ( ) Only allow web pages to use these fonts
> (o) Allow web pages to use any installed font
Neither of the above is what Gfx does. Firefox has 'Always use my fonts'. I
think just a single checkbox with either that or 'Ignore fonts requested by web
pages' is about right.
Comment 7•21 years ago
|
||
(In reply to comment #6)
>(In reply to comment #5)
>>OK, so how about:
>>( ) Only allow web pages to use these fonts
>>(o) Allow web pages to use any installed font
>Neither of the above is what Gfx does.
Which is?
>'Always use my fonts'
Well, that's confusing too... that suggests to ignore dynamic fonts.
>'Ignore fonts requested by web pages'
Ah, but they can still request the five basic fonts...
Comment 8•18 years ago
|
||
(Filter "spam" on 'prefs-nobody-20080612'.)
Assignee: prefs → nobody
QA Contact: prefs
You need to log in
before you can comment on or make changes to this bug.
Description
•