Closed Bug 864168 Opened 13 years ago Closed 10 years ago

May Critical Study - Localization

Categories

(Mozilla Localizations :: Other, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Matt_G, Unassigned)

Details

Hello! Following the instructions from L10n Drivers. I've submitted the request and you can find the project page here: https://wiki.mozilla.org/May_Critical_Study These are the markets we are hoping to localize for: Mexico Japan Brazil France India Russia China Spain Turkey Poland Germany Italy The actual survey is in doc format. Please let me know if you'd prefer I attach it here. It has already been sent to L1on Drivers and a few other email lists. Once you've had time to review this project we would appreciate an estimated timeline so that we can share this with our vendor. Thanks again for all the help!
Hey guys. Never got an update here on a timeline. Unfortunately the third party vendor we are working with needs these translations before the 16th. I am going to use a translation service to ensure we meet that deadline. Apologies for that. I'll be sure to get started earlier the next time we do a project like this so that we can use the existing L10n processes. Appreciate the understanding.
(In reply to Matt Grimes, Mozilla SUMO (irc: Matt_G) from comment #1) > Hey guys. Never got an update here on a timeline. Unfortunately the third > party vendor we are working with needs these translations before the 16th. Is this the same survey we talked about in governance and world-ready? I thought it was going to be translated externally and then checked by existing l10n-teams, but I never got updates after Apr 17.
Hey Francesco. Yes, this is the same project. I was asked to hold off on the external translations to see if this could be done internally. As I mentioned, this was my fault for not starting the process sooner. At this point our timeline is forcing my hand. Apologies again for all the confusion.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.