Closed Bug 20296 Opened 26 years ago Closed 26 years ago

platformGlobalOverlay.dtd should exist under some locale like en-US

Categories

(SeaMonkey :: General, defect, P1)

x86
All
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rchen, Assigned: alecf)

Details

The files platformGlobalOverlay.dtd and platformDialogOverlay.dtd should be under some locale (e.g., "en-UD")sub-directories for localization before platform.
QA Contact: claudius → rchen
The problem is in the build tree not in the product. Please add another sub-directory like "en-US" between "locale" and platform like "win", "mac", "unix".
Status: NEW → ASSIGNED
Target Milestone: M14
We need to make this "locale" directory consistant. I am guessing that you really want everything inside of "locale" to be moved inside of "locale/en-US". Setting as M14.
Paul, we need this fixed before beta, a milestone before that, since we will be localizing beta. Can you make it M13, or at least commit to an early M14 day?
Target Milestone: M14 → M13
Moving to M13, I will see if I can get some help on this one.
Target Milestone: M13 → M14
Moving to M14.
Assignee: hangas → alecf
Status: ASSIGNED → NEW
Target Milestone: M14
Alec, this is the bug tracking the issue of moving all of our files & directories that are filed under locale to be under locale/en-US. Since you were going to do the script, I thought it best just to give you the bug. We must have this one for beta.
Status: NEW → ASSIGNED
Priority: P3 → P1
Target Milestone: M14
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
ok, everying in global has moved to en-US. Since this one was for i18n and the skin issue is for the XPToolkit, I'm going to mark this one fixed and open a new one about the skin.
Moving all UE/UI bugs to new component: User Interface: Design Feedback UE/UI component will be deleted.
Component: UE/UI → User Interface: Design Feedback
Verified!
Status: RESOLVED → VERIFIED
Component: User Interface Design → Browser-General
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.