Created attachment 377539 [details] IT Survey .lang file Mozilla's IT team is investigating the need for a data center in South America and in Asia-Pacific. Specifically, Mozilla is trying to get feedback from users in the following regions on website performance: pt-BR, es-CL, es-AR, ms, ta-IN, ta-LK, th, jp, hi-IN, id The strings for the survey are attached. A screen shot from the survey software is also attached to provide some context. Please submit your translations to this bug by attaching a .txt file. I have set up the file so that it is similar to a .lang file. Please place your translation below the each English string that is prefaced by a semi-colon. We are hoping to launch the survey in June. Can you attach your translations to the bug by June 1, 2009?
the attached lang file is an rtf file, not a UTF8 text/plain file also the ms locale doesn't exist and some of the listed locales above will be first released with 3.5.
Ah, I see on the dashboard that ms is the code for malay and is a new future locale, my bad.
Created attachment 377633 [details] IT Survey .lang file (UTF-8) UTF-8 .lang file in UTF-8
Attachment #377539 - Attachment is obsolete: true
(In reply to comment #2) > the attached lang file is an rtf file, not a UTF8 text/plain file Thanks for checking Pascal. UTF8 attached now.
seth, is jp in the list for japanese ?
Attachment #377633 - Attachment mime type: application/octet-stream → text/plain
(In reply to comment #6) > seth, is jp in the list for japanese ? Yes, my apologies for the typographical error and thank you for catching it. The title of the bug is now correct after my edit. And, the correct list of locale codes is: pt-BR, es-CL, es-AR, ms, ta-IN, ta-LK, th, ja, hi-IN, id
Summary: Translate Mozilla IT Survey for pt-BR, es-AR, es-CL, ms, ta-IN, ta-LK, th, jp, hi-IN, id → Translate Mozilla IT Survey for pt-BR, es-AR, es-CL, ms, ta-IN, ta-LK, th, ja, hi-IN, id
Thank you to the localizers who have completed this survey. For those who have not completed it yet, PLEASE STOP YOUR TRANSLATION WORK. Please wait to hear from us about the next steps in this bug and remove it from your to-do lists for the time being. We learned from the third-party survey provider (Kampyle) that there is a 30 character length on many of the feedback forms. This causes a text clipping problem for all locales, including en-US. Sadly, the provider did not relay this information in our early conversations and has no solution for string lengths longer than 30 characters. We are going to work with them to see what options we have. This will cause the release date in each locale to be delayed until Q3 2009. It is likely that en-US will launch first, once the text clipping from the character length restriction is resolved. Then, we may have to provide a subset of new strings that will fit the allowable length. Apologies to all for this setback and thank you to those who have already finished the translation. As mentioned above, please wait to hear from us about the next steps in this bug and remove it from your to-do lists for the time being. We will get back to you when we have an appropriate solution.
Whiteboard: Q3 2009: pt-BR, es-AR, es-CL, ms, ta-IN, ta-LK, th, ja, hi-IN, id
Closing, re: comment 10.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.