Spanish Viewer Localization Project

CURRENT STATUS:

• 2009-June-30: We have finished all submissions for Viewer 1.23. The next time we make changes/updates for translations in the viewer will be August 2009.

• BUT, we are still keeping track of any bad translations or language bugs that you find!
  • Please report any translation bugs of the viewer in this document.
  • For more information , please contact: Ramzi Linden

This Project     This may be the project for you if you are a Resident who: whose native language is Spanish, you know English well and would like to help in localization efforts! In Viewer 1.23.4, we published a whole new and complete translation into Castilian Spanish. If you would like to join the project for the next version of the Viewer, please read the information below and then sign up! You will be contacted when you are given access to the project. There will be a lot of teamwork among translators. Feel free to use the contact email below for any questions too. 6px

Tips     Familiarize yourself with the Glossary first. It is quite different from the one you're used to and many terms have changed. Please follow what's in it. If you have suggestions or things you really disagree with, do not incorporate them in your translations. Rather, contact our wonderful Spanish Translators who worked on the Glossary: eva Nowicka, Irene Muni, Des Plante, Asghard Igaly, and others. The attached files are prepared to be used with a translation memory tool (we use Trados). The format is rtf. The text in light grey is not translatable, only the text in black should be translated. Any variables (things in [BRACKETS]) shouldn't be translated or messed with. A Few Spanish Specifics: Castilian Spanish is the current Spanish of the viewer. At some later date, we may be able to have more flavors of Spanish. For now, we need to be consistently Castilian. Always use this quotation mark: ' . Please, do not use curly quotes or double quotes. Also use a non breaking space before colons : In English, UI elements often use caps, but in Spanish, only the first world of the UI will be capitalized. In English, there is a double space after a period. In Spanish, a single space will be used. Use this format: L$ not this format L $. Adapt every number, date, timeformat to Spanish when possible. Unfortunately, we still have internationalization issues with some of these and they are not yet editable. We are working on it and this will change soon. The style of the viewer should be "business casual". For Spanish that means that whenever you are translating commands or English 2nd person address, you will use the formal address with the 3rd person singular (and not 2nd person singular or plural). Finally, whenever you see long, unclear sentences in English, try to make the Spanish simpler and clearer. Convey the meaning, but not the poor style... 6px

What To Do     1. Log into Pjira with your Second Life name and password. If you are reading this prior to signing up for the project: In order for you to be added to the access list for this Pjira project you need to have signed into Pjira at least once. Please remember to do that prior to signing up for the project: Sign up for the project HERE You will also need to agree to the Terms and Conditions located HERE during the sign up process. 2. Once you are signed up for the project, and are notified that you have been added, you can > CLICK THIS LINK TO SEE AVAILABLE SUBTASKS in the Community Translations Project in Pjira. 3. Click the subtask link of the set of strings you would like to translate. 4. On the left side of the page under "Available Workflow Actions" you will see Assign this issue > Click on to me. Now that subtask is in your name. 5. On the left side of the page where it says Translation in Progress" - Click that link. You will see the Status at the top change to: Translation in Progress 6. Near the top part of the subtask page you will see an attachment. This is the English string document available for translation. Download this attachment by clicking the download link. 7. Text for translation will be available to you in .xml files. We STRONGLY recommend that you open the files in Komodo - by far the best .xml file reader (you can download it for free). Strings that need translation will be well highlighted and hard to miss (the English text which needs translation will be in black font in Komodo). Here is a sample of a string <delta id="forgot_password_text"> <p1> Forgot your name or password? </p1> </delta> </file> <file name="floater_hud.xml"> <delta id=".[title]"> You guessed it: you will need to input your translation between <p1> and above </p1> and the only translatable text is: "Forgot your name or password?" 8. Please, translate inside the .xml file using Komodo. If you save it as .txt file, you will lose the formatting and it will be infinitely harder to do it. (you'll be more prone to make a mistake). Please, don't do it! :) Don't save them as a .doc or .rtf in Microsoft Office as it will again disturb formatting and we won't be able to import the strings. 9. Please, DO NOT touch the markup (xml) language. When you are finished with translation, make sure to save the file adding "_es_trans" to the end of the file name. . Before attaching it to the JIRA ticket, you may want to zip it (JIRA is sometimes known to corrupt high ascii encodings). 10. Attach the translation to your JIRA subtask click on Attach File to this issue link on the left side of the page. Follow the onscreen directions to upload your completed translation. The last thing you need to do is change the status from "Translation in Progress" to "Translated." (Remember: status changes are made on the left side of the page under "Available Workflow Actions" click the "Translated" link). Editing 12. Subtask set to "Translated" will be a signal to another translator to come in and edit! It is always important to have at least 2 pairs of eyes on a translation: translator and editor. Editor needs to Click the Workflow Action - Editing. Then, download the translation and the English original text and make edits to the translation. 13. What to look for when you are editing: precision of the translation; terminology consistency and compliance with the community-compiled Second Life glossary; consistency in string translation (e.g. string "Stop flying" should not sometimes be translated as "Discontinue flight"); consistency in style (e.g. strings should always be translated with the polite address - 3rd person singular and not 2nd person singular); any issues with moved xml markings; spelling mistakes. If there are strings that are not translated, translate them. 14. After making edits to the translation, the editor will save the edited translation by adding '_edit' to the end of the translated file name; editor will them upload the edited translation to the PJIRA subtask, click on Edited and leave a comment on the subtask that reads: "Edits Done." This comment should include any pertinent information, if applicable. Please, do not remove the original translation attachment. 15. If a second editor would like to follow afterwards, we encourage that: the more eyes see the file, the better. Otherwise and after our quick QA, your translation subtask status will change to Published and, after 2-4 weeks, you will see your translation live in one of the upcoming RC's for 1.23!!!! :) You are done and have helped in the Second Life localization process! Thank You! Feel free to take another subtask and start the process again. 6px

Questions     If you have questions or need help on this project please send an email to: ctproject@lists.secondlife.com Please include the tag [Spanish] in the subject line of the email 6px