[jira] [Commented] (CB-4461) Globalozation and I18N - Crowdin Proposal Discussion
[ https://issues.apache.org/jira/browse/CB-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727110#comment-13727110 ] Dariusz Mikulski commented on CB-4461: -- Can you add Polish translation? Also i'll ping you on crowdin. > Globalozation and I18N - Crowdin Proposal Discussion > - > > Key: CB-4461 > URL: https://issues.apache.org/jira/browse/CB-4461 > Project: Apache Cordova > Issue Type: Improvement > Components: Docs >Affects Versions: 3.0.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: documentation, globalization, translation, > > I have created a project within Transifex for cordova here: > https://www.transifex.com/projects/p/cordova > The way it works is: > 1.files are upload to the Transifex system. Transifex does not have > markdown files as one of the options for file type to import but they do have > html and plain text. I have chosen plain text for testing and it appears to > work great. I setup a preferences for the resource to be pulled from github > on a daily basis with the latest version of the file. > 2.Users may come in and provide translation or all or part of a file. > 3.A "maintainer" or language expert is assigned to each language and > approves the translations > 4.progress information and status can be shown per file/project. Once > complete, the translated file can be uploaded back into github under the > specific language. This part is a manual process > Other open source projects use Transifex, for example, OpenStack. > I propose we do the following: > Use Transifex for each major release starting with 3.0. If it is relatively > easy to translate for minor releases we can vote to do so with each. > Assign a language "maintainer" for each supported language to monitor > translations. I suggest we start with Spanish and French since those are the > languages our group of committers can best contribute to at this time. (If > we have a consensus to use Transfix, please volunteer if you'd like to be the > maintainer for a specific language). > Once a section of the documentation is approved by the language moderator, we > push the updates to GitHub. > Another thing to think about, Transifex offers automatic translation for > faster translation using google translation services or microsoft's which > require an api key and a paid subscription. I don't know if either of those > companies offer a free key for open source needs. I know we have a few > representatives from those companies that might be able to give us more > information. > Why we should be worried about translation? > Globalization! If we can attract more developers to Cordova and make it > easier for those developers to get up and running with cordova by providing > documentation in their native languages, cordova will continue to grow in > popularity globally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4461) Globalozation and I18N - Crowdin Proposal Discussion
[ https://issues.apache.org/jira/browse/CB-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727117#comment-13727117 ] Michael Brooks commented on CB-4461: Very nice! > Globalozation and I18N - Crowdin Proposal Discussion > - > > Key: CB-4461 > URL: https://issues.apache.org/jira/browse/CB-4461 > Project: Apache Cordova > Issue Type: Improvement > Components: Docs >Affects Versions: 3.0.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: documentation, globalization, translation, > > I have created a project within Transifex for cordova here: > https://www.transifex.com/projects/p/cordova > The way it works is: > 1.files are upload to the Transifex system. Transifex does not have > markdown files as one of the options for file type to import but they do have > html and plain text. I have chosen plain text for testing and it appears to > work great. I setup a preferences for the resource to be pulled from github > on a daily basis with the latest version of the file. > 2.Users may come in and provide translation or all or part of a file. > 3.A "maintainer" or language expert is assigned to each language and > approves the translations > 4.progress information and status can be shown per file/project. Once > complete, the translated file can be uploaded back into github under the > specific language. This part is a manual process > Other open source projects use Transifex, for example, OpenStack. > I propose we do the following: > Use Transifex for each major release starting with 3.0. If it is relatively > easy to translate for minor releases we can vote to do so with each. > Assign a language "maintainer" for each supported language to monitor > translations. I suggest we start with Spanish and French since those are the > languages our group of committers can best contribute to at this time. (If > we have a consensus to use Transfix, please volunteer if you'd like to be the > maintainer for a specific language). > Once a section of the documentation is approved by the language moderator, we > push the updates to GitHub. > Another thing to think about, Transifex offers automatic translation for > faster translation using google translation services or microsoft's which > require an api key and a paid subscription. I don't know if either of those > companies offer a free key for open source needs. I know we have a few > representatives from those companies that might be able to give us more > information. > Why we should be worried about translation? > Globalization! If we can attract more developers to Cordova and make it > easier for those developers to get up and running with cordova by providing > documentation in their native languages, cordova will continue to grow in > popularity globally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
