Closed Bug 44207 Opened 26 years ago Closed 19 years ago

MT4 miss to check DONT_TRANSLATE

Categories

(Mozilla Localizations Graveyard :: MozillaTranslator, defect, P3)

x86
All

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: oliver, Assigned: rpmdisguise-nave)

Details

(Whiteboard: target=later)

In perf/pref-fonts.dtd, there is LOCALIZATION NOTE as follows. <!-- LOCALIZATION NOTE (size1.option): DONT_TRANSLATE --> <!ENTITY size.label "Size:"> MT4 check DONT_TRANLATE box on size.label. This is MT4's miss? or, pref/pref-fonts.dtd is wrong?
As it is now, MT4 doesn't check to see if the key's match ( size1.option versus size.label ), but allways asumes that the comment is places just before the key that it is meant for. I'll look into doing some better check on the scope, but it wont be until after my vacation (which is the next 3 weeks)
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
version 5.00 does not support the localization note feature because of the switch to a real xml parser. it might come back later
Whiteboard: target=later
The MozillaTranslator component is moving to the Mozilla Localisations product.
Product: Browser → Mozilla Localizations
Version: other → unspecified
Reassigning every MT bug to me.
Assignee: henrik → rpmdisguise-otros
Status: ASSIGNED → NEW
I think it would be better to close this bug (which actually talks about MT 4 and not MT 5) and open another one to implement parsing of localization notes. Any comments on this?
(In reply to comment #5) > I think it would be better to close this bug (which actually talks about MT 4 > and not MT 5) and open another one to implement parsing of localization notes. > Any comments on this? > I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=363691 to bring back localization notes parsing into MT 5.1x, so I'm closing this bug. Marking as WONTFIX since it doesn't apply to MT 5.x, but MT 4.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Product: Mozilla Localizations → Mozilla Localizations Graveyard
You need to log in before you can comment on or make changes to this bug.