h1. Let's Translate OpenSolaris Documents
Welcome to OpenSolaris document translation activities. Why don't you share the hot OpenSolaris information with your community members in your language ?
[#Current Projects - Files Which Need Translation]
[#Getting Started]
[#How to Translate]
[#How to Review]
[#How to Update Translation]
[#Your Language's Page]
h2. {anchor:Current Projects - Files Which Need Translation}Current projects - Files Which Need Translation
As of today, following combination of language and documents need your contribution. If you are interested, please go through Getting Started and How to Translate sections.
* Translation:
[^ReleaseNotes2008.11.zip]
* Review: Translated files will be uploaded to [Translated Files for Review] as soon as they are ready
To Be Added Here
h2. {anchor:Getting Started}Getting Started
* Translation Editor: If you want to get advantage of Translation Memory (TM), please use the editor supporting TMX 1.4. For example, [OmegaT|http://www.omegat.org/en/omegat.html] (You can get one from [this download site|http://www.omegat.org/en/downloads.html]). If available, Sun will provide TM compatible with TMX 1.4. If you do not use TM, you can use any editor.
* Translation Memory: If the translation is for the updated version, Sun can provide you the file leveraged by the translation memory or memory itself. In that case, Sun will put xx.tmx file in the package of Files for Translation - This is to leverage the fuzzy translation. For detail of TMX, see [LISA web page|http://www.lisa.org/Translation-Memory-e.34.0.html].
* Glossary: [SunGloss|http://g11nportal.sun.com/sungloss/] You can get an account shortly from login link.
** Online search: Select "Solaris" and check "Always Show General Terms". Recommended - Check "Select All Product Lines" option.
** Offline search: You can export the list from Generate Glossary on SunGloss.
*** JA glossary: [All Product Glossary|http://jp.opensolaris.org/all-product-glossary.zip]
* Styleguide: You can download Sun Styleguide for your language from \[ Open Translation web site\|http://developers.sun.com/global/technology/translation/lang-style-guides.html\].
** The latest Japanese styleguide for community is available in two pdf format: [Quick Reference Guide|http://blogs.sun.com/reiko/resource/ja-style-quick.pdf] and [Full Context|http://blogs.sun.com/reiko/resource/ja-style-open.pdf].
h2. {anchor:How to Translate}How to Translate
h3. General Step
# Announce email is sent to your g11n-<lang>-discuss and i18n-discuss mailing lists.
# Reply to that email telling "I will contribute to the translation".
# Submit SCA from [Sun Contributor Agreement page|http://jp.opensolaris.org/os/about/sun_contributor_agreement/]. (SCA number will be informed to you by email)
# Translate English strings into your language.
# Send the file and SCA number to your contact person who sent out the announce email.
# Send email to your g11n-<lang>-discuss@opensolaris.org and i18n-discuss telling "I have completed the translation, so please review and send comments."
h3. If you use Translation Memory
If you use TM-compatible editor, updating the existing translation is much easier. You do not have to compare the old and new sentences one by one visually. If Sun can provide TM and you can use TM-compatible editor, please update that TM and keep it in your community. For example, you can store it to your project archive or upload it to your wiki. Once the files you translated this time are updated again, your TM will be a valuable aid.
If you send your TM compatible with TMX 1.4 to Sun, Sun will import your TM to the database. By this, Sun can provide you the TM or leveraged files for the next translation.
If Sun cannot provide TM or leveraged files, for example, it is a brand new translation and no relevant translation available, still you can use TM-compatible editor to generate a new TM.
h3. If you work on xml, sgml, or xliff
Unlike HTML or text file, XML, SGML, and XLIFF files are the source to be published in another format like PDF or HTML. If the files for translation are either one of them, and no publication tool is available, Sun will generate a final format. So, please send them to your contact person.
h2. {anchor:How to Review}How to Review
Please check [Translated Files for Review] page for instructions and files.
h2. {anchor:How to Update Translation}How to Update Translation
# Confirm the comments posted to your translation.
# Update the translation if you agree with their suggestion.
# Send the updated xliff and tmx files to your contact person.
h2. {anchor:Your Language's Page}Your Language's Page
* [Japanese]
Welcome to OpenSolaris document translation activities. Why don't you share the hot OpenSolaris information with your community members in your language ?
[#Current Projects - Files Which Need Translation]
[#Getting Started]
[#How to Translate]
[#How to Review]
[#How to Update Translation]
[#Your Language's Page]
h2. {anchor:Current Projects - Files Which Need Translation}Current projects - Files Which Need Translation
As of today, following combination of language and documents need your contribution. If you are interested, please go through Getting Started and How to Translate sections.
* Translation:
[^ReleaseNotes2008.11.zip]
* Review: Translated files will be uploaded to [Translated Files for Review] as soon as they are ready
To Be Added Here
h2. {anchor:Getting Started}Getting Started
* Translation Editor: If you want to get advantage of Translation Memory (TM), please use the editor supporting TMX 1.4. For example, [OmegaT|http://www.omegat.org/en/omegat.html] (You can get one from [this download site|http://www.omegat.org/en/downloads.html]). If available, Sun will provide TM compatible with TMX 1.4. If you do not use TM, you can use any editor.
* Translation Memory: If the translation is for the updated version, Sun can provide you the file leveraged by the translation memory or memory itself. In that case, Sun will put xx.tmx file in the package of Files for Translation - This is to leverage the fuzzy translation. For detail of TMX, see [LISA web page|http://www.lisa.org/Translation-Memory-e.34.0.html].
* Glossary: [SunGloss|http://g11nportal.sun.com/sungloss/] You can get an account shortly from login link.
** Online search: Select "Solaris" and check "Always Show General Terms". Recommended - Check "Select All Product Lines" option.
** Offline search: You can export the list from Generate Glossary on SunGloss.
*** JA glossary: [All Product Glossary|http://jp.opensolaris.org/all-product-glossary.zip]
* Styleguide: You can download Sun Styleguide for your language from \[ Open Translation web site\|http://developers.sun.com/global/technology/translation/lang-style-guides.html\].
** The latest Japanese styleguide for community is available in two pdf format: [Quick Reference Guide|http://blogs.sun.com/reiko/resource/ja-style-quick.pdf] and [Full Context|http://blogs.sun.com/reiko/resource/ja-style-open.pdf].
h2. {anchor:How to Translate}How to Translate
h3. General Step
# Announce email is sent to your g11n-<lang>-discuss and i18n-discuss mailing lists.
# Reply to that email telling "I will contribute to the translation".
# Submit SCA from [Sun Contributor Agreement page|http://jp.opensolaris.org/os/about/sun_contributor_agreement/]. (SCA number will be informed to you by email)
# Translate English strings into your language.
# Send the file and SCA number to your contact person who sent out the announce email.
# Send email to your g11n-<lang>-discuss@opensolaris.org and i18n-discuss telling "I have completed the translation, so please review and send comments."
h3. If you use Translation Memory
If you use TM-compatible editor, updating the existing translation is much easier. You do not have to compare the old and new sentences one by one visually. If Sun can provide TM and you can use TM-compatible editor, please update that TM and keep it in your community. For example, you can store it to your project archive or upload it to your wiki. Once the files you translated this time are updated again, your TM will be a valuable aid.
If you send your TM compatible with TMX 1.4 to Sun, Sun will import your TM to the database. By this, Sun can provide you the TM or leveraged files for the next translation.
If Sun cannot provide TM or leveraged files, for example, it is a brand new translation and no relevant translation available, still you can use TM-compatible editor to generate a new TM.
h3. If you work on xml, sgml, or xliff
Unlike HTML or text file, XML, SGML, and XLIFF files are the source to be published in another format like PDF or HTML. If the files for translation are either one of them, and no publication tool is available, Sun will generate a final format. So, please send them to your contact person.
h2. {anchor:How to Review}How to Review
Please check [Translated Files for Review] page for instructions and files.
h2. {anchor:How to Update Translation}How to Update Translation
# Confirm the comments posted to your translation.
# Update the translation if you agree with their suggestion.
# Send the updated xliff and tmx files to your contact person.
h2. {anchor:Your Language's Page}Your Language's Page
* [Japanese]