Spanish Viewer Localization Project - Revision history

Ramzi Linden: fix a typo

2009-07-06T18:57:48Z

fix a typo

← Older revision		Revision as of 11:57, 6 July 2009
Line 35:		Line 35:
	* you know English well		* you know English well
	* and would like to help in localization efforts!		* and would like to help in localization efforts!
	In Viewer 1.23.4, we ~~publish~~ 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.		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.
	</div>		</div>
	\|-		\|-
Line 163:		Line 163:
	'''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.		'''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 '~~_edt~~'''' 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.		'''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!!!! :)		'''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!!!! :)

Ramzi Linden: add a status section

2009-07-06T18:39:25Z

add a status section

Show changes

Danica Linden: /* Editing */

2009-02-07T02:39:02Z

Editing

← Older revision		Revision as of 19:39, 6 February 2009
Line 129:		Line 129:
	<div style="padding:10px; text-align: justify;">		<div style="padding:10px; text-align: justify;">

	*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, ~~send~~ me ~~a note in SL or an e-mail at danica@lindenlab~~.~~com~~		*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. OR, just contact me and I will advise you of what to do.

	*You'll notice that terms in the glossary do not start with a capital letter. It is done on purpose as it makes things easier for working with translation tools.
	~~In the Spanish SL version, all UI elements (menu, buttons...) will start with a cap letter (the first word only).~~
	~~'''Example:''' Pour voler, cliquez sur le bouton Voler. Pour parler, cliquez sur Dire.~~

	*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 back should be translated. The variables (red content into brackets) shouldn't be translated or messed with.		*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 back should be translated. The variables (red content into brackets) shouldn't be translated or messed with.

Danica Linden: /* Editing */

2009-02-07T02:32:40Z

Editing

← Older revision		Revision as of 19:32, 6 February 2009
Line 138:		Line 138:

	'''A Few Spanish Specifics:'''		'''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 :		*Always use this quotation mark: ' . Please, do not use curly quotes or double quotes. Also use a non breaking space before colons :
Line 146:		Line 148:

	*Use this format: L$ not this format L $.		*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...		*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...

Danica Linden: Spanish Viewer Loclization Project moved to Spanish Viewer Localization Project

2009-02-07T02:26:25Z

Spanish Viewer Loclization Project moved to Spanish Viewer Localization Project

← Older revision	Revision as of 19:26, 6 February 2009
(No difference)

Danica Linden at 02:26, 7 February 2009

2009-02-07T02:26:10Z

← Older revision		Revision as of 19:26, 6 February 2009
Line 60:		Line 60:
	'''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.'''		'''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 .~~rtf~~ files. Strings that need translation will be well highlighted and hard to miss (the English '''text which needs translation will be in black font'''~~, while the markups and old strings will be~~ in ~~gray font~~).		'''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).


Line 84:		Line 84:


	'''8.''' Please, '''translate inside the .xml file'''. 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.		'''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 ~~with~~ the ~~same~~ name ~~but add BR at the end~~.''' Before attaching it to the JIRA ticket, you may want to zip it (JIRA is sometimes known to corrupt high ascii encodings).		'''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.''' ~~Once you have translated the strings, attach~~ the translation to your 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''').		'''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''').

	[[Image:Pjira2.png]]		[[Image:Pjira2.png]]
Line 96:		Line 96:
	===Editing===		===Editing===
	</div>		</div>
	'''12.''' Subtask set to "Translated" will be a signal to another translator to come in and edit! '''Editor''' needs to '''Click the Workflow Action - Editing.''' Then, '''download the translation~~'''~~ and the English original text and make edits to the translation.		'''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 ~~selection particularly~~ as ~~it needs to~~ be ~~matched to the translations in~~ the ~~client~~ and any issues with moved xml markings.		'''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 '''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.		'''14.''' After making edits to the translation, the editor will '''save the edited translation by adding '_edt'''' 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.''' ~~After~~ our quick QA, your translation subtask status will change to Published and you will see your translation live in one of the upcoming RC's for 1.22!!!! :)		'''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!!!! :)

Danica Linden at 02:10, 7 February 2009

2009-02-07T02:10:52Z

← Older revision		Revision as of 19:10, 6 February 2009
Line 48:		Line 48:
	*<font color=#008000>'''You will also need to agree to the Terms and Conditions located [[Terms and Conditions for Second Life Community Translation Program\|HERE]] during the sign up process.'''</font>		*<font color=#008000>'''You will also need to agree to the Terms and Conditions located [[Terms and Conditions for Second Life Community Translation Program\|HERE]] during the sign up process.'''</font>

	'''2.''' Once you are signed up for the project, and are notified that you have been added, you can [http://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10070&sorter/order=DESC&sorter/field=priority&resolution=-1&component=10267>'''CLICK THIS LINK TO SEE AVAILABLE SUBTASKS'''~~</font>~~] in the [https://jira.secondlife.com/browse/CT Community Translations Project] in Pjira.		'''2.''' Once you are signed up for the project, and are notified that you have been added, you can [http://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10070&sorter/order=DESC&sorter/field=priority&resolution=-1&component=10267>'''CLICK THIS LINK TO SEE AVAILABLE SUBTASKS'''] in the [https://jira.secondlife.com/browse/CT Community Translations Project] in Pjira.

	'''3.''' Click the subtask link of the set of strings you would like to translate.		'''3.''' Click the subtask link of the set of strings you would like to translate.

Danica Linden at 02:09, 7 February 2009

2009-02-07T02:09:14Z

← Older revision		Revision as of 19:09, 6 February 2009
Line 48:		Line 48:
	*<font color=#008000>'''You will also need to agree to the Terms and Conditions located [[Terms and Conditions for Second Life Community Translation Program\|HERE]] during the sign up process.'''</font>		*<font color=#008000>'''You will also need to agree to the Terms and Conditions located [[Terms and Conditions for Second Life Community Translation Program\|HERE]] during the sign up process.'''</font>

	'''2.''' Once you are signed up for the project, and are notified that you have been added, you can [http://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&~~requestId~~=~~11653<font color~~=~~#008000~~>'''CLICK THIS LINK TO SEE AVAILABLE SUBTASKS'''</font>] in the [https://jira.secondlife.com/browse/CT Community Translations Project] in Pjira.		'''2.''' Once you are signed up for the project, and are notified that you have been added, you can [http://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10070&sorter/order=DESC&sorter/field=priority&resolution=-1&component=10267>'''CLICK THIS LINK TO SEE AVAILABLE SUBTASKS'''</font>] in the [https://jira.secondlife.com/browse/CT Community Translations Project] in Pjira.

	'''3.''' Click the subtask link of the set of strings you would like to translate.		'''3.''' Click the subtask link of the set of strings you would like to translate.

Danica Linden at 02:06, 7 February 2009

2009-02-07T02:06:11Z

← Older revision		Revision as of 19:06, 6 February 2009
Line 19:		Line 19:
	<div style="padding:10px; text-align: justify;">		<div style="padding:10px; text-align: justify;">

	If you are a Resident whose native language is ~~Brazilian Portuguese~~, you know English well and would like to help in localization efforts, this may be the project for you! Currently a segment of viewer strings vital to the ~~Brazilian Portuguese~~ Community localization effort are available for translation. If you would like to join the project 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 and help going on among translators. Give it a try and ask questions if you have them! Feel free to use the contact email below for any questions too!		If you are a Resident whose native language is Spanish, you know English well and would like to help in localization efforts, this may be the project for you! Currently a segment of viewer strings vital to the Spanish Community localization effort are available for translation. If you would like to join the project 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 and help going on among translators. Give it a try and ask questions if you have them! Feel free to use the contact email below for any questions too!
	</div>		</div>
	\|-		\|-
Line 132:		Line 132:

	*You'll notice that terms in the glossary do not start with a capital letter. It is done on purpose as it makes things easier for working with translation tools.		*You'll notice that terms in the glossary do not start with a capital letter. It is done on purpose as it makes things easier for working with translation tools.
	In the ~~Brazilian Portuguese~~ SL version, all UI elements (menu, buttons...) will start with a cap letter (the first word only).		In the Spanish SL version, all UI elements (menu, buttons...) will start with a cap letter (the first word only).
	'''Example:''' Pour voler, cliquez sur le bouton Voler. Pour parler, cliquez sur Dire.		'''Example:''' Pour voler, cliquez sur le bouton Voler. Pour parler, cliquez sur Dire.

	*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 back should be translated. The variables (red content into brackets) shouldn't be translated or messed with.		*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 back should be translated. The variables (red content into brackets) shouldn't be translated or messed with.

	'''A Few ~~Brazilian Portuguese~~ Specifics:'''		'''A Few Spanish Specifics:'''

	*Always use this quotation mark: ' . Please, do not use curly quotes or double quotes. Also use a non breaking space before colons :		*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 ~~Brazilian Portuguese~~, only the first world of the UI will be capitalized.		*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 ~~Brazilian Portuguese~~, a single space will be used.		*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 $.		*Use this format: L$ not this format L $.

	*Finally, whenever you see long, unclear sentences in English, try to make the ~~Brazilian Portuguese~~ simpler and clearer. Convey the meaning, but not the poor style...		*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...
	</div>		</div>
	\|-		\|-
Line 171:		Line 171:

	If you have questions or need help on this project please send an email to: ctproject@lists.secondlife.com		If you have questions or need help on this project please send an email to: ctproject@lists.secondlife.com
	*Please include the tag [~~Brazilian Portuguese~~] in the subject line of the email		*Please include the tag [Spanish] in the subject line of the email
	</div>		</div>
	\|-		\|-

Danica Linden: New page: NOTOC
{| cellpadding="1" cellspacing="1" style="width: 100%; background-color: #f9f9f7; vertical-ali...

2009-02-07T02:04:16Z

New page: __NOTOC__ <div style="background-color: #F9f9f7; padding: 6px; border: 2px ridge #ABCDEF;"> {| cellpadding="1" cellspacing="1" style="width: 100%; background-color: #f9f9f7; vertical-ali...

New page

__NOTOC__

<div style="background-color: #F9f9f7; padding: 6px; border: 2px ridge #ABCDEF;">
{| cellpadding="1" cellspacing="1" style="width: 100%; background-color: #f9f9f7; vertical-align: top;"
| colspan="2" style="padding: 0;" |
|-
| style="width: 100%; vertical-align: top;" |
{| border="0" cellspacing="0" cellpadding="0" width="100%"
| style="background-color:#fff;" width="0" |
{| style="width="30%"; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"
| rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#fff; border:2px solid #ABCDEF; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" | [[Image:cartella_blu.jpg|none]] <div style="margin-top:-37px; padding-left:5px">[[Image:Info.png|36px]]</div><div style="padding-left:45px; margin-top:-29px; font-size:130%">'''This Project'''</div>
|}
| style="border-bottom:2px solid #ABCDEF; background:#f9f9f7;" width="8" |  
| style="border-bottom:2px solid #ABCDEF; background:#f9f9f7;" width="100%"|  
|}
{| style="width:100%; margin-bottom:.5em; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"
| rowspan="1" width="100%" colspan="2" valign="top" style="background:#FFF; border:2px solid #ABCDEF; border-bottom:0; border-top:0; padding:0; margin:0" |
<div style="padding:10px; text-align: justify;">

If you are a Resident whose native language is Brazilian Portuguese, you know English well and would like to help in localization efforts, this may be the project for you! Currently a segment of viewer strings vital to the Brazilian Portuguese Community localization effort are available for translation. If you would like to join the project 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 and help going on among translators. Give it a try and ask questions if you have them! Feel free to use the contact email below for any questions too!
</div>
|-
| colspan="2" class="radius_bottom" style="background:#CFF; border:2px solid #ABCDEF" | <div style="font-size:0">[[image:pix.gif|6px]]</div>
|}
|}

{| cellpadding="1" cellspacing="1" style="width: 100%; background-color: #f9f9f7; vertical-align: top;"
| colspan="2" style="padding: 0;" |
|-
| style="width: 100%; vertical-align: top;" |
{| border="0" cellspacing="0" cellpadding="0" width="100%"
| style="background-color:#FFF;" width="0" |
{| style="width="30%"; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"
| rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#FFF; border:2px solid #A3BFB1; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" | [[Image:Green_bk.jpg|none]] <div style="margin-top:-37px; padding-left:5px">[[Image:Edit.png|36px]]</div><div style="padding-left:45px; margin-top:-29px; font-size:130%">'''What To Do'''</div>
|}
| style="border-bottom:2px solid #A3BFB1; background:#f9f9f7;" width="8" |  
| style="border-bottom:2px solid #A3BFB1; background:#f9f9f7;" width="100%"|  
|}
{| style="width:100%; margin-bottom:.5em; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"
| rowspan="1" width="100%" colspan="2" valign="top" style="background:#FFF; border:2px solid #A3BFB1; border-bottom:0; border-top:0; padding:0; margin:0" |
<div style="padding:10px; text-align: justify;">

'''1.''' Log into [http://jira.secondlife.com/secure/Dashboard.jspa 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:

*<font color=#008000>'''Sign up for the project [http://www.surveymonkey.com/s.aspx?sm=rCz4oYbrdLslUgEv2ENO1A_3d_3d HERE]'''</font>
*<font color=#008000>'''You will also need to agree to the Terms and Conditions located [[Terms and Conditions for Second Life Community Translation Program|HERE]] during the sign up process.'''</font>

'''2.''' Once you are signed up for the project, and are notified that you have been added, you can [http://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=11653<font color=#008000>'''CLICK THIS LINK TO SEE AVAILABLE SUBTASKS'''</font>] in the [https://jira.secondlife.com/browse/CT 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.

[[Image:Pjira1.png]]

'''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 .rtf files. Strings that need translation will be well highlighted and hard to miss (the English '''text which needs translation will be in black font''', while the markups and old strings will be in gray font).

===Here is a sample of a string===
<pre>
<delta id="forgot_password_text">

<p1>

Forgot your name or password?

</p1>
</delta>

</file>

<file name="floater_hud.xml">

<delta id=".[title]">
</pre>

*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'''. 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 with the same name but add BR at the end.''' Before attaching it to the JIRA ticket, you may want to zip it (JIRA is sometimes known to corrupt high ascii encodings).

'''10.''' Once you have translated the strings, attach the translation to your 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''').

[[Image:Pjira2.png]]

<div style="background:#CEF2E0">

===Editing===
</div>
'''12.''' Subtask set to "Translated" will be a signal to another translator to come in and edit! '''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 selection particularly as it needs to be matched to the translations in the client and any issues with moved xml markings.

'''14.''' After making edits to the translation, the editor will '''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.''' After our quick QA, your translation subtask status will change to Published and you will see your translation live in one of the upcoming RC's for 1.22!!!! :)

'''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.'''

</div>
|-
| colspan="2" class="radius_bottom" style="background:#CEF2E0; border:2px solid #A3BFB1" | <div style="font-size:0">[[image:pix.gif|6px]]</div>
|}
|}

{| cellpadding="1" cellspacing="1" style="width: 100%; background-color: #f9f9f7; vertical-align: top;"
| colspan="2" style="padding: 0;" |
|-
| style="width: 100%; vertical-align: top;" |
{| border="0" cellspacing="0" cellpadding="0" width="100%"
| style="background-color:#fff;" width="0" |
{| style="width="30%"; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"
| rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#fff; border:2px solid #F26C6C; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" | [[Image:Red_bk.jpg|none]] <div style="margin-top:-37px; padding-left:5px">[[Image:star.png|36px]]</div><div style="padding-left:45px; margin-top:-29px; font-size:130%">'''Tips'''</div>
|}
| style="border-bottom:2px solid #F26C6C; background:#f9f9f7;" width="8" |  
| style="border-bottom:2px solid #F26C6C; background:#f9f9f7;" width="100%"|  
|}
{| style="width:100%; margin-bottom:.5em; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"
| rowspan="1" width="100%" colspan="2" valign="top" style="background:#FFF; border:2px solid #F26C6C; border-bottom:0; border-top:0; padding:0; margin:0" |
<div style="padding:10px; text-align: justify;">

*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, send me a note in SL or an e-mail at danica@lindenlab.com

*You'll notice that terms in the glossary do not start with a capital letter. It is done on purpose as it makes things easier for working with translation tools.
In the Brazilian Portuguese SL version, all UI elements (menu, buttons...) will start with a cap letter (the first word only).
'''Example:''' Pour voler, cliquez sur le bouton Voler. Pour parler, cliquez sur Dire.

*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 back should be translated. The variables (red content into brackets) shouldn't be translated or messed with.

'''A Few Brazilian Portuguese Specifics:'''

*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 Brazilian Portuguese, only the first world of the UI will be capitalized.

*In English, there is a double space after a period. In Brazilian Portuguese, a single space will be used.

*Use this format: L$ not this format L $.

*Finally, whenever you see long, unclear sentences in English, try to make the Brazilian Portuguese simpler and clearer. Convey the meaning, but not the poor style...
</div>
|-
| colspan="2" class="radius_bottom" style="background:#FFD1D1; border:2px solid #F26C6C" | <div style="font-size:0">[[image:pix.gif|6px]]</div>
|}
|}

{| cellpadding="1" cellspacing="1" style="width: 100%; background-color: #f9f9f7; vertical-align: top;"
| colspan="2" style="padding: 0;" |
|-
| style="width: 100%; vertical-align: top;" |
{| border="0" cellspacing="0" cellpadding="0" width="100%"
| style="background-color:#fff;" width="0" |
{| style="width="30%"; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"
| rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#fff; border:2px solid #ABCDEF; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" | [[Image:cartella_blu.jpg|none]] <div style="margin-top:-37px; padding-left:5px">[[Image:QuestionMark.png|36px]]</div><div style="padding-left:45px; margin-top:-29px; font-size:130%">'''Questions'''</div>
|}
| style="border-bottom:2px solid #ABCDEF; background:#f9f9f7;" width="8" |  
| style="border-bottom:2px solid #ABCDEF; background:#f9f9f7;" width="100%"|  
|}
{| style="width:100%; margin-bottom:.5em; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"
| rowspan="1" width="100%" colspan="2" valign="top" style="background:#FFF; border:2px solid #ABCDEF; border-bottom:0; border-top:0; padding:0; margin:0" |
<div style="padding:10px; text-align: justify;">

If you have questions or need help on this project please send an email to: ctproject@lists.secondlife.com
*Please include the tag [Brazilian Portuguese] in the subject line of the email
</div>
|-
| colspan="2" class="radius_bottom" style="background:#CFF; border:2px solid #ABCDEF" | <div style="font-size:0">[[image:pix.gif|6px]]</div>
|}
|}
[[Category:Localization]]

Spanish Viewer Localization Project - Revision history

Ramzi Linden: fix a typo

Ramzi Linden: add a status section

Danica Linden: /* Editing */

Danica Linden: /* Editing */

Danica Linden: Spanish Viewer Loclization Project moved to Spanish Viewer Localization Project

Danica Linden at 02:26, 7 February 2009

Danica Linden at 02:10, 7 February 2009

Danica Linden at 02:09, 7 February 2009

Danica Linden at 02:06, 7 February 2009

Danica Linden: New page: __NOTOC__ {| cellpadding="1" cellspacing="1" style="width: 100%; background-color: #f9f9f7; vertical-ali...

Danica Linden: New page: NOTOC
{| cellpadding="1" cellspacing="1" style="width: 100%; background-color: #f9f9f7; vertical-ali...