Closed Bug 26057 Opened 20 years ago Closed 20 years ago

pref-diskspace.dtd: component order needs to be changeable

Categories

(SeaMonkey :: Preferences, defect, P3)

x86
Other
defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: kairo, Assigned: mcafee)

References

Details

(Whiteboard: [nsbeta2+][5/16][pdt-])

Doing l10n work (M13 de-AT), I encountered problems in
chrome/messenger/.../pref-diskspace.dtd

The construct around days.label is not l10n compatible. There are two lines in
the dialog affected by this label:

"Keep messages which have arrived within the past XXX days"
(keepMsgs.label + Input Box + days.label)
"Remove message bodies only older than XXX days"
(removeMsg.label + Input Box + days.label)

In German, the lines should look like this:
"Nachrichten behalten, die in den letzten XXX Tagen eingetroffen sind"
"Nachrichtentexte loeschen, die aelter sind als XXX Tage"

You see, those line endings are not the same anymore. That's not possible with
current files...
Reassigned to Fergus.
Assignee: rchen → fergus
Status: NEW → ASSIGNED
Need to fix this by beta1.

The problem here is that we're combining several distinct elements to make one 
sentence.  When we localize, we need to retain the the meaning, but we need to 
change the order of verb, object, etc.  I can emulate a simpler example from the 
MacOS find file function which shows the problem quite well:
  "Search [popup listing all your mounted drives] for [input box for filename]"
In German, Japanese and other languages, this word order might change to
  "[popup listing all your mounted drives] for [input box for filename] search"

That's what we need to do, right now I don't know HOW to do it, but we will need 
a fix.  Adding an assortment of L10n/I18n folks to the cclist.
Keywords: beta1
Summary: pref-diskspace.dtd: days.label is hard to localise → pref-diskspace.dtd: component order needs to be changeable
pdt says not necessary for beta1, feature likely to go away 
Whiteboard: [pdt-]
removing beta1 keyword
Keywords: beta1
Can we confirm this dialog is going to go away?  If so, I'd like to close this 
bug.
Dropping priority to 4 for reasons listed above.
Priority: P3 → P4
Blocks: 12394
Priority: P4 → P3
Moving to M16
Target Milestone: --- → M16
need to have localizability bugs fixed by beta2
Keywords: nsbeta2
Matt, can you confirm whether or not this dtd is to be redesigned and/or 
removed?
Assignee: fergus → rchen
Status: ASSIGNED → NEW
changing component to preferences, not L10n.
Assignee: rchen → matt
Component: Localization → Preferences
QA Contact: teruko → sairuh
M18 ...
Assignee: matt → mcafee
Target Milestone: M16 → M18
Putting on [nsbeta2+][5/16] radar.  This is a feature MUST complete work by 
05/16 or we may pull this feature for PR2.
QA Contact: sairuh → teruko
Whiteboard: [pdt-] → [nsbeta2+][5/16][pdt-]
Move to M19 target milestone.
Target Milestone: M18 → M19
the feature this pref is used for has been yanked for 6.0.
depends on 17211, marking invalid.
Status: NEW → RESOLVED
Closed: 20 years ago
Depends on: 17211
Resolution: --- → INVALID
Verified as Invalid.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.