Closed Bug 85297 Opened 23 years ago Closed 16 years ago

ES: Forms Manager | View Stored Data fields need to be localized

Categories

(Toolkit :: Form Manager, defect, P3)

x86
Windows 98
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: jaimejr, Unassigned)

References

Details

(Keywords: l12y)

We need to localize the fields in the Forms Manager Dialogue for the Spanish 
release by Region (Spain, Mexico, Argentina, Costa Rica, etc.)

Assigning defintion to jaimejr, with hope that we can get it for RTM. If we
can't get it in for RTM, we will have to default to using US-centric version.
Changing QA Contact to Annac. Adding L12Y, nsbeta1 keywords.
Keywords: l12y, nsbeta1
QA Contact: tpreston → annac
Jaime - is there a specification for what the form looks like in the ES locale?
thanks, Vishy
Note: this is a ressurection of bugscape 4800/4802 and there are attachments in 
those bug reports that might apply here.
Status: NEW → ASSIGNED
Setting milestone to 0.9.2 because that is what was in bugscape 4800/4802
Target Milestone: --- → mozilla0.9.2
This is approved work for rtm stoppage. However, lets do risk assessment before
we check in, after getting the patch, r and sr. 
Whiteboard: [pdt+]
Jaime, I do not believe that there is a UI spec for the ES locale yet. Without
that, we cannot implement this bug. Can you attach the relevant files here or
point to a mozilla.org URL that has the spec. Since the m0.9.2 deadline is less
than 5 days away, it is critical to have that in the bug today. thanks, Vishy. 
Vishy - This one might be really tricky because there are over 17 Spanish
speaking countries. Comteplating leaving this one as is (US centric), or just
doing it for Spain. In any case, this one would be of lower priority than UK and
France.

Assinging to danielmc for L10N. Localize ME bebe.

Daneil - Pls provide attach a template specification for ES version of Form
Manager to this bug by 06.15.01, so Morse can build the localize UI.
Priority: -- → P3
nav triage team:

Somebody forgot the nsbeta1+ again.
Keywords: nsbeta1nsbeta1+
as per discussion with Jaime, we can live with the ability to remove panels. 
moving this to m1.0. 
Target Milestone: mozilla0.9.2 → mozilla1.0
Is this still pdt+ now that we've decided to do bug 86181 instead?
Lets leave the pdt+ in there for the record that this is an issue needing to be
solved completely in the long run. But we do not need it for Netscape 6.1, so I
moved it to mozilla1.0. Lets work on this later. 
Agree with Vishy.
If we don't need for shipping, we need to remove the PDT+.
Whiteboard: [pdt+]
Keywords: nsBranch
Blocks: 99227
Propose we nsbranch - this one.

Peter - If you agree, pls minus and remove from your nsbranch metabug list.
Marking nsbranch- as it was decided in the August bug triage that we wouldn't
have enough time in eMojo to fix this.  Let's revisit for MachV.
Keywords: nsbranch-
removing redundant nsbranch keyword
Keywords: nsbranch
No longer blocks: 99227
More realistic milestone since we have the fix in bug 86181.
Target Milestone: mozilla1.0 → Future
Blocks: 107067
Keywords: nsbranch-
dveditz is the new module owner, reassigning.
Assignee: morse → dveditz
Status: ASSIGNED → NEW
Assignee: dveditz → nobody
Filter on "Nobody_NScomTLD_20080620"
QA Contact: annac → form-manager
This UI no longer exists. Closing.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Product: Core → Toolkit
QA Contact: form-manager → form.manager
Target Milestone: Future → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.