Closed Bug 42432 Opened 25 years ago Closed 25 years ago

Need localized autofill tables

Categories

(Toolkit :: Form Manager, defect, P3)

Product:
Toolkit
Component:
Form Manager
Type:
defect

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: dveditz, Assigned: rchen)

References

Details

We need data for foreign-language sites around the world. Would this info be added to the existing tables in the client and on the server side? Do we need to ship *different* tables with different localizations, and if so do these localizations need to point at different server-hosted URLs? This fundamental question needs to be answered because if it's not the same tables there may be additional client work needed to support that and it should be tracked in a separate bug.
Clearly Steve is the wrong owner for this one. Who on the Netcenter or localization side would create these tables?
Blocks: 41128
Keywords: netcenter, nsbeta2
This refers to the FieldSchema table only. The URLFieldSchema table is specific to each url and uses the field names found on that url. For the FieldSchema table, there would be only one. Otherwise a person browsing and prefilling english sites could not go to a french site and expect to have it prefilled. So the same table that has the mapping: firstname -> Name.First would also have the mapping prenom -> Name.First as well as other entries for other languages.
Putting on [nsbeta2-] radar. If this is a beta2 requirement for i18n, let us know.
Whiteboard: [nsbeta2-]
Status: NEW → ASSIGNED
Target Milestone: --- → M18
QA Contact: sairuh → teruko
Pushing this post beta2
Target Milestone: M18 → M20
Isn't this something the l10n folks would have to provide? Since msanz and roberts are out (sabbatical and maternity leave respectively) I'll reassign to tao so he can figure out who it belongs to. Note that unlike most localization efforts, instead of creating translated replacement files for this one instead needs to have the info added to the shared wallet tables that live (will live) at Netcenter. Steve, if you'd rather still own this one accept my apologies and feel free to switch it back
Assignee: morse → tao
Status: ASSIGNED → NEW
No, I'm glad not to own it. Although I'm sure I'll have to assist with whomever is going to do this work and am more than willing to help.
HI, Ray: I remember you owne Wallet's l12y issue. Any idea who should provide the localized tabel? What was the l12y solution at that time?
Assignee: tao → rchen
Localization team will provide the localized table. Steve, please let me know which files need localization.
Status: NEW → ASSIGNED
I think the table is under extensions/wallet/src/*.tbl Steve- can you provide documentation about how can we localized them ? Are they stored in UTF-8 ? What is the file format ? Which file we need to localize ?
Whiteboard: [nsbeta2-] → [nsbeta2-] eng
Steve, I have a question about interview URL. In 2000-07-27 M17 US all platform, when I select menu Task|Form Manager->Interview, it will go to http://home.netscape.com/bookmark/6_0b1/wallet3.html and "Not Found" page will show up. Is this the right URL?
It is. We were forced to put the URL into the browser before they had the page ready on the server so that we could make the m17 branch. Netcenter tells me they are going to push the pages onto the server by tonight. BTW, I'm sorry for not responding sooner to all the questions that the i18n folks have been asking bug report. It's just that the localization here is not the typical ones that you are accustomed to. Give me a call and I'll explain in more detail what has to be done.
Steve, there are four tbl under wallet. We suppose to localize them. If I remember correctly, we need to localize them in UTF-8, right? Is there any webside we can verify our Japanese tables?
Keywords: netcenter, nsbeta2
Whiteboard: [nsbeta2-] eng
Jaime, Bob, what do you want to do this bug?
Localize them does not mean translating the entries that are there but rather to add additional entries. I'll probably have to work on it together with you when the time comes to do this. Yes, it would have to be in utf-8. Sorry, I don't know where the japanese e-commerce websites are. In answer to your final question (in a private e-mail to me), the blank lines are significant.
Steve, what day what time will be good for you to work together with me?
We discussed this issue today. I think we will turn off Form Manager. Jaime, please put what we decided.
Teruko, Steve, Bob and I have been conducting a review of Form Manager, with the following options in mind: * Leave Form Manager as is (Do not translate, do not change functionality) * Localize Form Manager and utilize the available pref to turn off Tasks | Privacy and Security | Form Manager User can still access View Stored Data (Form Manager editor) and View Sites from Advanced Preferences menu Problem: Tabs for View Sites are also turned OFF, when this pref is enabled Fix: Comment out or remove block of code - - lines 51 through 70, in extensions/wallett/signonviewer/signonviewer.js Essentially, making the pref exhibit the behavior we want it to (i.e. Remove the US-Centric UI Form Manager menu) If we can get the above fix, our plan would be to localize everything, including the table. (Note: If the table wasn't loaclizable, or if we didn't have time, I think we could live with that for 6.0). To answer Dan's question, there is not enough time to build different localizations tables for every region of the world. Hence, I think we use the same tables here, and try and work some server-side magic.
signonviewer.js is not in the locale packages. In order for us to make any change to it, it has to be in the package (en_US.jar)
Ray - I understand. This is a change Bob or Ftang (as Steve does not have the time) will have to make, so that the Pref you enable works as we would like it to work (i.e. Only turn off the Form Manager menu under Tasks, and NOT the tabs in View Sites dialogue).
Steve - Ray believed that the he need to localize the table, because Form Manager keys off the displayed text. I explianed that Form Manager keys off the <Input Value>, not the displayed text. Please correct me, if I am wrong. (Note: We did discuss Internationalizing the main table, but that is a future project).
According to Steve Morse, we don't need to localize autofill tables. I mark it Invalid.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Verified as Invalid.
Status: RESOLVED → VERIFIED
Product: Core → Toolkit
QA Contact: teruko → form.manager
You need to log in before you can comment on or make changes to this bug.