Closed Bug 789724 Opened 8 years ago Closed 8 years ago

Rename "Other Languages" to "Unicode" on the Fonts pref pane (port TB bug 323747)

Categories

(SeaMonkey :: Preferences, enhancement)

enhancement
Not set

Tracking

(Not tracked)

RESOLVED FIXED
seamonkey2.15

People

(Reporter: InvisibleSmiley, Assigned: InvisibleSmiley)

Details

Attachments

(1 file)

Bug 323747 renamed "Other Languages" to "Unicode" in the "Fonts & Encodings" dialog for TB. I think we should follow suit(e).

It's not very clear what "other languages" means. Technically it evaluates to Unicode. Some localizations, e.g. German, already show "Unicode" instead and I think it makes sense since it describes exactly what it means instead of introducing a term that needs explanation.

When fixing this, we should fix/adapt (en-US) Help in one go.
Overview of how this is translated into other languages (heh):
http://mxr.mozilla.org/l10n-central/search?string=font.langGroup.unicode&find=pref-fonts.dtd
Assignee: nobody → jh
Status: NEW → ASSIGNED
Attachment #659523 - Flags: review?(iann_bugzilla)
Attachment #659523 - Flags: feedback?(neil)
Attachment #659523 - Flags: feedback?(kairo)
> http://mxr.mozilla.org/l10n-central/search?string=font.langGroup.unicode&find=pref-fonts.dtd

In my opinion, some of these translations already use "Unicode". Changing the entity only makes more work for those localisers. Perhaps a post to m.d.a.l10n instead?
Comment on attachment 659523 [details] [diff] [review]
patch [Checkin: Comment 8]

Philip's suggestion is worth considering, kairo probably knows more about l10n than me, r=me either way
Attachment #659523 - Flags: review?(iann_bugzilla) → review+
Comment on attachment 659523 [details] [diff] [review]
patch [Checkin: Comment 8]

I notice that some locales have even translated the Firefox string as Unicode too. (Simply remove the pref- prefix to see strings for all applications.)
Attachment #659523 - Flags: feedback?(neil) → feedback+
I sent a message to mozilla.dev.L10n. Let's see what they think.
(In reply to Philip Chee from comment #6)
> I sent a message to mozilla.dev.L10n. Let's see what they think.

FTR: There was just one reply, suggesting to change the entity name so we make sure that nobody misses the modification. [I'm leaving out the translation statistics provided there because they were for browser/ instead of suite/.] I tend to agree with that (better safe than sorry), so I'll go with my patch as-is.
Attachment #659523 - Flags: feedback?(kairo)
Comment on attachment 659523 [details] [diff] [review]
patch [Checkin: Comment 8]

http://hg.mozilla.org/comm-central/rev/c652d0ae41a7
Attachment #659523 - Attachment description: patch → patch [Checkin: Comment 8]
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.15
(In reply to Jens Hatlak (:InvisibleSmiley) from comment #7)
> FTR: There was just one reply, suggesting to change the entity name so we
> make sure that nobody misses the modification. [I'm leaving out the
> translation statistics provided there because they were for browser/ instead
> of suite/.] I tend to agree with that (better safe than sorry), so I'll go
> with my patch as-is.

Sorry I didn't get to look at it, but my first reaction was the same, I feel better with doing the change of entity name so people actually do look at it.
You need to log in before you can comment on or make changes to this bug.