Closed Bug 10248 Opened 25 years ago Closed 25 years ago

[BLOCKER] *.xul: non-localizable XUL file

Categories

(Core Graveyard :: Profile: BackEnd, defect, P3)

Product:
Core Graveyard
Component:
Profile: BackEnd
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 12689

People

(Reporter: tao, Assigned: gayatrib)

References

(
URL
)

Details

./res/profile/content1.xul
./res/profile/content2.xul
./res/profile/content3.xul
./res/profile/content4.xul


Please refer to the "XUL Coding Style Guidelines" in the URL above
for how to make XUL localizable. The target deadline is M9.

Thanks!
QA Contact: gbush → tao
Assignee: waterson → gayatrib
reassign to gayatrib, who owns this.
Target Milestone: M9
TFV=M9
Blocks: 10597
Status: NEW → ASSIGNED
The new profile manager UI has a main file pm.xul.
This has all the DTDs in place. There are some more UI
changes to be made that will betaken care of in the beginning
of M10. Once this is done, all DTDs will be in place. Could not
complete all the new UI by M9 due to external dependencies.
So moving the target milestone to M10.
Target Milestone: M9 → M10
P3s aren't going to make it in M10.  Bulk moving to M11.
Hi, Gayatri:

Net developers have started to localize Mozilla client. L10n group also starts
a 2nd Pseudo localization process. Would you please raise the priority of this
bug so that we can at least finish them by M10? We had identified several
crashing bugs in our product in the localization process.

If resource allocation is a problem, please escalate it to your manager. Thanks!
Target Milestone: M11 → M10
Moving target fix date to M10
Severity: critical → blocker
Summary: *.xul: non-localizable XUL file → [BLOCKER] *.xul: non-localizable XUL file
Marking blocker for M10 since L10n has a dependency on it.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Marking this as a dup for bug #12689, the new profile UI tracking bug.

*** This bug has been marked as a duplicate of 12689 ***
Status: RESOLVED → VERIFIED
Component: Profile Manager → Profile Manager BackEnd
Moving all Profile Manager bugs to new Profile Manager Backend component.
Profile Manager component to be deleted.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.