Difference between revisions of "Translating:New project/fi"

From translatewiki.net
Jump to navigation Jump to search
Line 9: Line 9:
 
| colspan="2" | '''Avoimuutta'''
 
| colspan="2" | '''Avoimuutta'''
 
|-
 
|-
| [[File:Crystal Clear app ksmiletris.png|64px|Avoimuutta|link=]]
+
| [[File:Crystal Clear app ksmiletris.png|64px|Avoimuutta]]
 
| valign="top" | Hyväksymme vain projekteja, jotka käyttävät avoimen lähdekoodin lisenssiä. Meidän täytyy valita mitä haluemme tukea suoraan. Koska alkuperämme on MediaWiki ja Wikimedia, avoimuus on yksi ydinarvoistamme. Jos sovelluksesi ei ole avoin, mutta haluat silti käyttää samaa ohjelmistoa, katso  [[Special:MyLanguage/Translating:Documentation|ohjelmiston dokumentaatiota]].
 
| valign="top" | Hyväksymme vain projekteja, jotka käyttävät avoimen lähdekoodin lisenssiä. Meidän täytyy valita mitä haluemme tukea suoraan. Koska alkuperämme on MediaWiki ja Wikimedia, avoimuus on yksi ydinarvoistamme. Jos sovelluksesi ei ole avoin, mutta haluat silti käyttää samaa ohjelmistoa, katso  [[Special:MyLanguage/Translating:Documentation|ohjelmiston dokumentaatiota]].
 
|-
 
|-
Line 16: Line 16:
 
| colspan="2" |'''Kehitystä'''
 
| colspan="2" |'''Kehitystä'''
 
|-
 
|-
|[[File:Crystal Clear app utilities.png|64px|Kehitystä|link=]]
+
|[[File:Crystal Clear app utilities.png|64px|Kehitystä]]
 
| valign="top" | The new project should be in active development and using a version control system. We are already familiar with CVS, Subversion and Git. The project should have periodic releases or another way to update translations. Time to get translation into use (TIU) should be minimised. There are multiple ways to get translations into use faster, which can be discussed.
 
| valign="top" | The new project should be in active development and using a version control system. We are already familiar with CVS, Subversion and Git. The project should have periodic releases or another way to update translations. Time to get translation into use (TIU) should be minimised. There are multiple ways to get translations into use faster, which can be discussed.
 
|-
 
|-
Line 23: Line 23:
 
| colspan="2" |'''Integraatiota'''
 
| colspan="2" |'''Integraatiota'''
 
|-
 
|-
|[[File:Crystal Clear app Startup Wizard.png|64px|Integraatiota|link=]]
+
|[[File:Crystal Clear app Startup Wizard.png|64px|Integraatiota]]
 
| valign="top" | Once content for your project has been translated at translatewiki.net, ideally translatewiki.net staff is able to integrate the changes back into your product. This requires a language addition procedure and commit access for at least one translatewiki.net staff member. This ensures that the work of translators will actually be integrated. Translatewiki.net staff have a lot of experience of committing to various source control systems.
 
| valign="top" | Once content for your project has been translated at translatewiki.net, ideally translatewiki.net staff is able to integrate the changes back into your product. This requires a language addition procedure and commit access for at least one translatewiki.net staff member. This ensures that the work of translators will actually be integrated. Translatewiki.net staff have a lot of experience of committing to various source control systems.
 
|}
 
|}
Line 31: Line 31:
 
== Arvostamme... ==
 
== Arvostamme... ==
 
{| style="width:95%; background:transparent;" cellpadding="4"
 
{| style="width:95%; background:transparent;" cellpadding="4"
| colspan="2" |'''i18n support'''
+
| colspan="2" |'''i18n-tukea'''
 
|-
 
|-
| [[File:Crystal_Clear_action_apply.png|64px|i18n support|link=]]
+
| [[File:Crystal_Clear_action_apply.png|64px|i18n support]]
 
| valign="top" | We only support the UTF-8 character set. Support in the i18n framework for applications for variables, multiple different plurals, and Right-to-left languages is preferred. Having support for grammatical forms is something we think should always be considered, and also support for gender of the user where the user is spoken to directly or other users are mentioned in interface texts.
 
| valign="top" | We only support the UTF-8 character set. Support in the i18n framework for applications for variables, multiple different plurals, and Right-to-left languages is preferred. Having support for grammatical forms is something we think should always be considered, and also support for gender of the user where the user is spoken to directly or other users are mentioned in interface texts.
 
|-
 
|-
Line 40: Line 40:
 
| colspan="2" |'''Communication'''
 
| colspan="2" |'''Communication'''
 
|-
 
|-
| [[File:Crystal Clear app Community Help.png|64px|Communication|link=]]
+
| [[File:Crystal Clear app Community Help.png|64px|Communication]]
 
| valign="top" | A developer from the project should be active in translatewiki.net to answer questions, notify about coming releases, coordinate with the project's developer group, etc. Our approach to localisation works best when knowledge flows as freely as possible between developer communities and translator communities. The project liaison plays a very important role in that.
 
| valign="top" | A developer from the project should be active in translatewiki.net to answer questions, notify about coming releases, coordinate with the project's developer group, etc. Our approach to localisation works best when knowledge flows as freely as possible between developer communities and translator communities. The project liaison plays a very important role in that.
 
|-
 
|-
Line 47: Line 47:
 
| colspan="2" |'''File formats'''
 
| colspan="2" |'''File formats'''
 
|-
 
|-
| [[File:Crystal_Clear_action_view_multicolumn.png|64px|File formats|link=]]
+
| [[File:Crystal_Clear_action_view_multicolumn.png|64px|File formats]]
 
| valign="top" | The translatewiki.net system is based on translation files. Use of key-based file formats is preferred, like Java properties and Ruby-style YAML. Other supported file formats are PHP arrays, PHP variables and Gettext. Let us know if you have a different format in mind; in our experience adding file format support is relatively easy for someone proficient in PHP.
 
| valign="top" | The translatewiki.net system is based on translation files. Use of key-based file formats is preferred, like Java properties and Ruby-style YAML. Other supported file formats are PHP arrays, PHP variables and Gettext. Let us know if you have a different format in mind; in our experience adding file format support is relatively easy for someone proficient in PHP.
 
|}
 
|}

Revision as of 07:50, 12 July 2010

Translatewiki.net haluaa kasvaa

Etsimme lisää projekteja! Älä epäröi ottaa yhteyttä ja keskustella siitä, miten projektisi voidaan lisätä translatewiki.netiin. Arvostamme vapaaehtoisten kääntäjien työtä, mikä tarkoittaa, että etsimme terveitä projekteja, joita kehitetään aktiivisesti myös ennustettavissa olevassa tulevaisuudessa. Korostamme myös kääntäjien ja kehittäjien välistä viestintää. Alla on lyhyt lista siitä, mitä toivomme näkevämme uudessa projektissa ja mitä prosesseja projektin hyväksyminen jälkeen pitää hoitaa.

Haluamme...

Avoimuutta
Avoimuutta Hyväksymme vain projekteja, jotka käyttävät avoimen lähdekoodin lisenssiä. Meidän täytyy valita mitä haluemme tukea suoraan. Koska alkuperämme on MediaWiki ja Wikimedia, avoimuus on yksi ydinarvoistamme. Jos sovelluksesi ei ole avoin, mutta haluat silti käyttää samaa ohjelmistoa, katso ohjelmiston dokumentaatiota.
 
Kehitystä
Kehitystä The new project should be in active development and using a version control system. We are already familiar with CVS, Subversion and Git. The project should have periodic releases or another way to update translations. Time to get translation into use (TIU) should be minimised. There are multiple ways to get translations into use faster, which can be discussed.
 
Integraatiota
Integraatiota Once content for your project has been translated at translatewiki.net, ideally translatewiki.net staff is able to integrate the changes back into your product. This requires a language addition procedure and commit access for at least one translatewiki.net staff member. This ensures that the work of translators will actually be integrated. Translatewiki.net staff have a lot of experience of committing to various source control systems.

Arvostamme...

i18n-tukea
i18n support We only support the UTF-8 character set. Support in the i18n framework for applications for variables, multiple different plurals, and Right-to-left languages is preferred. Having support for grammatical forms is something we think should always be considered, and also support for gender of the user where the user is spoken to directly or other users are mentioned in interface texts.
 
Communication
Communication A developer from the project should be active in translatewiki.net to answer questions, notify about coming releases, coordinate with the project's developer group, etc. Our approach to localisation works best when knowledge flows as freely as possible between developer communities and translator communities. The project liaison plays a very important role in that.
 
File formats
File formats The translatewiki.net system is based on translation files. Use of key-based file formats is preferred, like Java properties and Ruby-style YAML. Other supported file formats are PHP arrays, PHP variables and Gettext. Let us know if you have a different format in mind; in our experience adding file format support is relatively easy for someone proficient in PHP.


Still interested? Good. Please contact us, on our IRC channel #mediawiki-i18n at freenode, by e-mail, or at our support page. Though, nothing beats good real-time chat to solve any possible issues and to get things going.