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

From translatewiki.net
Jump to navigation Jump to search
 
(Updating to match new version of source page)
 
Line 1: Line 1:
  +
<languages />__NOEDITSECTION__
==Translatewiki.net wants to grow ==
 
  +
== <span lang="en" dir="ltr" class="mw-content-ltr">Translatewiki.net wants to grow</span> ==
__NOEDITSECTION__
 
  +
<span lang="en" dir="ltr" class="mw-content-ltr">We are looking for more projects! Do not hesitate to contact us and discuss how your project can be added to translatewiki.net. We value the work of our volunteer translators, which means we are looking for healthy projects which are actively developed for the foreseeable future. We also emphasize the communication between the translators and developers. Below is a short list highlighting what we are hoping to see in a new project, and which processes need to be managed once accepted.</span>
<languages />
 
We are looking for more projects! Do not hesitate to contact us and discuss how your project can be added to translatewiki.net. We value the work of our volunteer translators, which means we are looking for healthy projects which are actively developed for the foreseeable future. We also emphasize the communication between the translators and developers. Below is a short list highlighting what we are hoping to see in a new project, and which processes need to be managed once accepted.
 
   
<div style="float:left; max-width:46%; padding-right: 2em">
+
<div style="float:left;min-width:24em;max-width:48%;padding:0 1%">
== We require... ==
+
== <span lang="en" dir="ltr" class="mw-content-ltr">We require...</span> ==
{| style="width:95%; background:transparent;" cellpadding="4"
+
{|style="width:100%;background:transparent"
| colspan="2" | '''Openness'''
 
 
|-
 
|-
  +
|colspan="2" style="padding-top:1em"| '''<span lang="en" dir="ltr" class="mw-content-ltr">Openness</span>'''
| [[File:Crystal Clear app ksmiletris.png|64px|Openness|link=]]
 
| valign="top" | We only accept projects which use a free and open source license. We have to make choices in what we want to support directly. Because our origin lies in MediaWiki and Wikimedia, this is a core value to us. If your application is not free, but you would still like to use the same software, see the [[mw:Special:MyLanguage/Help:Extension:Translate|documentation]].
 
 
|-
 
|-
  +
|style="padding-right:4px"| [[File:Crystal Clear app ksmiletris.png|64px|<span lang="en" dir="ltr" class="mw-content-ltr">Openness</span>|link=]]
| &nbsp;
 
  +
|valign="top"| <span lang="en" dir="ltr" class="mw-content-ltr">We only accept projects which use a free and open source license. We have to make choices in what we want to support directly. Because our origin lies in MediaWiki and Wikimedia, this is a core value to us. If your application is not free, but you would still like to use the same software, see the [[mw:Special:MyLanguage/Help:Extension:Translate|documentation]].</span>
 
|-
 
|-
| colspan="2" |'''Development'''
+
|colspan="2" style="padding-top:1em"| '''<span lang="en" dir="ltr" class="mw-content-ltr">Development</span>'''
 
|-
 
|-
|[[File:Crystal Clear app utilities.png|64px|Development|link=]]
+
|style="padding-right:4px"| [[File:Crystal Clear app utilities.png|64px|<span lang="en" dir="ltr" class="mw-content-ltr">Development</span>|link=]]
| 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 minimized. There are multiple ways to get translations into use faster, which can be discussed.
+
|valign="top"| <span lang="en" dir="ltr" class="mw-content-ltr">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 minimized. There are multiple ways to get translations into use faster, which can be discussed.</span>
 
|-
 
|-
  +
|colspan="2" style="padding-top:1em"| '''<span lang="en" dir="ltr" class="mw-content-ltr">Integration</span>'''
| &nbsp;
 
 
|-
 
|-
  +
|style="padding-right:4px"| [[File:Crystal Clear app Startup Wizard.png|64px|<span lang="en" dir="ltr" class="mw-content-ltr">Integration</span>|link=]]
| colspan="2" |'''Integration'''
 
  +
|valign="top"| <span lang="en" dir="ltr" class="mw-content-ltr">Once content for your project has been translated, a translatewiki.net staff member will integrate translation updates into your project. This requires a language addition procedure. Translatewiki.net needs access to push changes into your project (e.g. commit access with direct push or pull requests), or have access to a branch that will be noticed and merged. This ensures that the work of translators are regularly integrated.</span>
|-
 
|[[File:Crystal Clear app Startup Wizard.png|64px|Integration|link=]]
 
| 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 (with direct push) for at least one translatewiki.net staff member, to ensure that the work of translators will actually be integrated. Translatewiki.net staff have a lot of experience of committing to various source control systems.
 
 
|}
 
|}
 
</div>
 
</div>
  +
<div style="float:left;min-width:24em;max-width:48%;padding:0 1%">
 
<div style="float:left; max-width:46%; padding-right: 2em">
 
 
== Ասոնց կը սիրենք... ==
 
== Ասոնց կը սիրենք... ==
{| style="width:95%; background:transparent;" cellpadding="4"
+
{|style="width:100%;background:transparent"
| colspan="2" |'''i18n support'''
 
 
|-
 
|-
  +
|colspan="2" style="padding-top:1em"| '''<span lang="en" dir="ltr" class="mw-content-ltr">i18n support</span>'''
| [[File:Crystal_Clear_action_apply.png|64px|i18n support|link=]]
 
| valign="top" | We only support the UTF-8 character encoding. 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. This area is often where most problems and delays come from; try and check our [[Translating:Localisation for developers|Localisation for developers]] tips to avoid them.
 
 
|-
 
|-
  +
|style="padding-right:4px"| [[File:Crystal Clear action apply.png|64px|<span lang="en" dir="ltr" class="mw-content-ltr">i18n support</span>|link=]]
| &nbsp;
 
  +
|valign="top"| <span lang="en" dir="ltr" class="mw-content-ltr">We only support the UTF-8 character encoding. 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. This area is often where most problems and delays come from; try and check our [[Translating:Localisation for developers|Localisation for developers]] tips to avoid them.</span>
 
|-
 
|-
| colspan="2" |'''Communication'''
+
|colspan="2" style="padding-top:1em"| '''<span lang="en" dir="ltr" class="mw-content-ltr">Communication</span>'''
 
|-
 
|-
| [[File:Crystal Clear app Community Help.png|64px|Communication|link=]]
+
|style="padding-right:4px"| [[File:Crystal Clear app Community Help.png|64px|<span lang="en" dir="ltr" class="mw-content-ltr">Communication</span>|link=]]
| 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" | <span lang="en" dir="ltr" class="mw-content-ltr">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.</span>
 
|-
 
|-
  +
|colspan="2" style="padding-top:1em"|'''<span lang="en" dir="ltr" class="mw-content-ltr">File formats</span>'''
| &nbsp;
 
 
|-
 
|-
  +
|style="padding-right:4px"| [[File:Crystal Clear action view multicolumn.png|64px|<span lang="en" dir="ltr" class="mw-content-ltr">File formats</span>|link=]]
| colspan="2" |'''File formats'''
 
  +
|valign="top"| <span lang="en" dir="ltr" class="mw-content-ltr">The translatewiki.net system is [[mw:Special:MyLanguage/Help:Extension:Translate/File format support|based on translation files]]. Use of key-based file formats is preferred, like JSON, Java properties, or Ruby-style YAML. Other supported file formats include Gettext, Android and iOS. Let us know if you have a different format in mind; in our experience, support for a file format is relatively easy to add, if you're proficient in PHP.</span>
|-
 
| [[File:Crystal_Clear_action_view_multicolumn.png|64px|File formats|link=]]
 
| valign="top" | The translatewiki.net system is [[mw:Help:Extension:Translate/File format support|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, support for a file format is relatively easy for you to add, if you're proficient in PHP.
 
 
|}
 
|}
 
</div>
 
</div>
  +
<div style="clear:both"></div>
   
  +
<span lang="en" dir="ltr" class="mw-content-ltr">Still interested? Good. You can contact us via,</span>
<br clear="all" />
 
  +
  +
* <span lang="en" dir="ltr" class="mw-content-ltr">Our [[Support|support page]]. First, [[Special:MainPage|create an account as a developer]] (using the ''Can't submit some translations right now?'' option) on the homepage, wait for your account to be approved and then [https://translatewiki.net/w/i.php?title=Support&lqt_method=talkpage_new_thread create a support ticket].</span>
  +
* <span lang="en" dir="ltr" class="mw-content-ltr">Our issue tracker - [https://phabricator.wikimedia.org/ Phabricator]. Fill out the {{Phabricator New Project|project information section on this task template}}.</span>
  +
  +
<span lang="en" dir="ltr" class="mw-content-ltr">If you want to explore some more first, then try the [[Translating:Localisation for developers|localisation for developers]] page.</span>
   
Still interested? Good. Please contact us, on our IRC channel [[Special:WebChat|#mediawiki-i18n at freenode]], by e-mail, or at our [[Support|support page]]. Though, nothing beats good real-time chat to solve any possible issues and to get things going. If you want to explore some more first, then try the [[Translating:Localisation for developers|localisation for developers]] page.
 
 
 
[[Category:Help{{Langcat|New project}}]]
 
[[Category:Help{{Langcat|New project}}]]
[[Category:Projects]]
+
[[Category:Projects{{Langcat|New project}}]]

Latest revision as of 09:20, 20 January 2021

Translatewiki.net wants to grow

We are looking for more projects! Do not hesitate to contact us and discuss how your project can be added to translatewiki.net. We value the work of our volunteer translators, which means we are looking for healthy projects which are actively developed for the foreseeable future. We also emphasize the communication between the translators and developers. Below is a short list highlighting what we are hoping to see in a new project, and which processes need to be managed once accepted.

We require...

Openness
Openness We only accept projects which use a free and open source license. We have to make choices in what we want to support directly. Because our origin lies in MediaWiki and Wikimedia, this is a core value to us. If your application is not free, but you would still like to use the same software, see the documentation.
Development
Development 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 minimized. There are multiple ways to get translations into use faster, which can be discussed.
Integration
Integration Once content for your project has been translated, a translatewiki.net staff member will integrate translation updates into your project. This requires a language addition procedure. Translatewiki.net needs access to push changes into your project (e.g. commit access with direct push or pull requests), or have access to a branch that will be noticed and merged. This ensures that the work of translators are regularly integrated.

Ասոնց կը սիրենք...

i18n support
i18n support We only support the UTF-8 character encoding. 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. This area is often where most problems and delays come from; try and check our Localisation for developers tips to avoid them.
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 JSON, Java properties, or Ruby-style YAML. Other supported file formats include Gettext, Android and iOS. Let us know if you have a different format in mind; in our experience, support for a file format is relatively easy to add, if you're proficient in PHP.

Still interested? Good. You can contact us via,

If you want to explore some more first, then try the localisation for developers page.