pref-colors.dtd: positioning is l10n incompatible

RESOLVED INCOMPLETE

Status

SeaMonkey
Preferences
RESOLVED INCOMPLETE
18 years ago
5 years ago

People

(Reporter: Robert Kaiser, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [2012 Fall Equinox])

(Reporter)

Description

18 years ago
Doing l10n work (M13 de-AT), I encountered the following problems with
chrome/pref/.../pref-colors.dtd:

Try those values from my German Language Pack:
<!ENTITY  useWinColorsCheck.label "Windows-Farben verwenden">
<!ENTITY  underLinksCheck.label "Links unterstreichen">
<!ENTITY  links "Links">
<!ENTITY  unvisit "Nicht besuchte Links:">
<!ENTITY  visit "Besuchte Links:">

Looks awful. OTOH, the same options are in chrome/pref/.../pref-composer.dtd are
are l10n compatible and better-looking there. Shouldn't panles showing the same
kind of options be similar? Would also solve this problem if you take the
Composer Panel's version...

Comment 1

18 years ago
Reassigned to Fergus.
Assignee: rchen → fergus

Updated

18 years ago
Status: NEW → ASSIGNED

Comment 2

18 years ago
Mozilla.org localizer points out that the browser's color prefrences and 
composer's color preferences should look more alike.  Currently the UI of each 
is very different to the other.  He uses the German example, but it's equally 
true for English.

He suggests that pref-composer.dtd is the better-designed of the two.

Assigning to matt as he seems to be the owner of the preferences dialogs 
(unless it's brade or rgoodger/ben?)  Changing component to PrefUI.
Assignee: fergus → matt
Status: ASSIGNED → NEW
Component: Localization → Pref UI

Comment 3

18 years ago
We can change the UI.
The UI was duplicated from the
UI of 4.0.
Status: NEW → ASSIGNED
Target Milestone: M15

Comment 4

18 years ago
Bulk move of all Pref UI component bugs to new Preferences component.  Pref UI 
component will be deleted.
Component: Pref UI → Preferences

Comment 5

18 years ago
Move to M16 for now ...
Target Milestone: M15 → M16

Comment 6

18 years ago
M18 ...
Assignee: matt → mcafee
Status: ASSIGNED → NEW
Target Milestone: M16 → M18

Comment 7

18 years ago
Move to M21 target milestone.
Target Milestone: M18 → M21

Comment 8

17 years ago
Changed QA contact to andreasb@netscape.com.
QA Contact: teruko → andreasb

Comment 9

17 years ago
qa=jonrubin@netscape.com
QA Contact: andreasb → jonrubin

Updated

17 years ago
Target Milestone: --- → mozilla1.0

Comment 10

17 years ago
over to vishy for an owner
Assignee: mcafee → vishy
I dont really understand this bug. Is this still a problem? Why can't the German 
l10n team just set whatever colors they want? 

Please reply, otherwise we shd mark this bug as wfm now. 

Comment 12

16 years ago
i think the question amounts to why the composer and navigator color pref 
panels are so different when they expose the same number of choices.

Comment 13

16 years ago
Concerning browser dialog layout: it looks like navigator's could be improved by 
putting the "Link colors" group box under the "Text and Background" to 
accomodate longer German words.
Concerning differences with Composer: We needed more features in our primary color
picker than the simple Navigator version, so we also used that picker in our
preference panel for consistency within Composer.
I will be working on making Composer color picker more like
a menupopup (bug 90670), so we should try to unify navigator and composer versions
in the process. There's already a bug on that as well: bug 39784.
(Reporter)

Comment 14

16 years ago
vishy:
This was originally reported about M13, and the L12y situation got much better
until now (who wonders?) as pref dialog generally got wider, and dialog width is
now localizeable.
But, as timeless states, the dialog layout differences between the Navigator and
Composer color pref settings are hard to understand, and make pref panels
inconsistent. IMO, the composer panel, which also has a preview area, is much
easier to understand for users.

cmanske:
I think the color picker problem is an additional problem to the dialog layout
problem here (the layout can be made more consitent though it may still use the
current colorpicker) - though it's also important to get addressed.

I know that both layouts are somehow inherited from 4.x but I still think we can
get better in consistency than 4.x was.

Comment 15

16 years ago
mass change, switching qa contact from jonrubin to ruixu.
QA Contact: jonrubin → ruixu

Comment 16

16 years ago
->future
Target Milestone: mozilla1.0 → Future

Comment 17

16 years ago
Reassigning to a real person.
Assignee: vishy → ben
QA Contact: ruixu → sairuh
Product: Browser → Seamonkey
Assignee: bugs → prefs
QA Contact: bugzilla
(Filter "spam" on 'prefs-nobody-20080612'.)
Assignee: prefs → nobody
QA Contact: prefs
Priority: P3 → --
Target Milestone: Future → ---

Comment 19

5 years ago
Is this problem still actual?
Whiteboard: [2012 Fall Equinox][CLOSEME 2012-11-01 INVA/WONT?]

Comment 20

5 years ago
Resolved per whiteboard
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [2012 Fall Equinox][CLOSEME 2012-11-01 INVA/WONT?] → [2012 Fall Equinox]
You need to log in before you can comment on or make changes to this bug.