Contributing Bulgarian translation

[Alexander Shopov]

Hello Jenkins developers,

I am Alexander Shopov and I want to update the Bulgarian translation of Jenkins.

I have quite a long experience with translating free and oss in Bulgarian.

Here are my first questions/statements after reading https://wiki.jenkins-ci.org/display/JENKINS/Internationalization and searching on the dev list:

1. The quickest way to get the translation merged is just fork on github and create pull request, right?

2. Is there a list of priorities of messages - which should be translated first, which next, etc? Stats show that there are around 2000 messages and experience tells me batches of 4-5 hundred messages tops work best. This way translation can be prioritized. I hope to be able to do most of this before Nov 22 when Kohsuke should be in Bulgaria. LTS releases come about every 12 weeks which gives high probability that two LTS from now the translation should be done.

3. I see no list of terms for Jenkins - I would expect about 150-200 terms that should be translated the same way throughout all messages for consistency. If such a list does not exist I can contribute the one I generate during the translation.

4. I see no mentions of the way translations should be licensed. Is fixing their license to be the same as the whole Jenkins project OK? Jenkins is MIT licensed (OK by me) is there something special I should be aware of.

5. I will discuss the Bulgarian translation on Bulgarian free and open source software translation list di...@ludost.net. http://ludost.net/cgi-bin/mailman/listinfo/dict

6. Once a translation is in place - can it be updated with the translation plugin?

Kind regards:

al_shopov

[Daniel Beck]

On 13.10.2015, at 09:52, Alexander Shopov <li...@kambanaria.org> wrote:

> 1. The quickest way to get the translation merged is just fork on github and create pull request, right?

Yes! We only occasionally process the Translation Assistance submitted data (and by "occasionally" I mean "almost never").

> 2. Is there a list of priorities of messages - which should be translated first, which next, etc? Stats show that there are around 2000 messages and experience tells me batches of 4-5 hundred messages tops work best. This way translation can be prioritized. I hope to be able to do most of this before Nov 22 when Kohsuke should be in Bulgaria. LTS releases come about every 12 weeks which gives high probability that two LTS from now the translation should be done.

I don't think there's a list, but you can use common sense -- messages that are rarely ever shown (e.g. ones you didn't even know existed) are probably not as important. Of course given the property file format, they often aren't clustered that way. While I'm not sure about how much there is to translate in each of the following buckets, I'd start with Messages.properties files and once they're done, move on other .properties files, as those can probably be prioritized somewhat by looking at the corresponding jelly files -- AbstractProject/main.properties (you see this all the time) is higher priority than HudsonHomeDiskUsageMonitor/index.properties (you've likely never seen this).

> 3. I see no list of terms for Jenkins - I would expect about 150-200 terms that should be translated the same way throughout all messages for consistency. If such a list does not exist I can contribute the one I generate during the translation.

That would be a good idea as a guide for translations into your language. I'm not sure but I think this was only implied in existing translations, and the job of translators to find existing usages of a term and be consistent in translating it.

> 4. I see no mentions of the way translations should be licensed. Is fixing their license to be the same as the whole Jenkins project OK? Jenkins is MIT licensed (OK by me) is there something special I should be aware of.

Anything other than MIT would probably (need to) be rejected.

> 6. Once a translation is in place - can it be updated with the translation plugin?

Not as easily -- I think there's some protection in place because we had some regressions (worse translations or outright vandalism in languages none of the Jenkins team speak), so the more reliable way to change these is through pull requests.

[Alexander Shopov]

Hi,

I have sent my first pull request for merging Bulgarian translation in Jenkins.

https://github.com/kohsuke/hudson/pull/15

I have translated all Messages.properties files as a first step (slightly more than 600 messages).

I have explicitly stated MIT license in every file and claimed copyright only on translation.

Kind regards:

al_shopov

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/a-iAiGtUasQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/A748FEC2-35FF-4DF4-8947-8D06FDDB2254%40beckweb.net.

For more options, visit https://groups.google.com/d/optout.

[Daniel Beck]

On 13.11.2015, at 16:09, Alexander Shopov <a...@kambanaria.org> wrote:

> I have sent my first pull request for merging Bulgarian translation in Jenkins.
> https://github.com/kohsuke/hudson/pull/15
>

We're not using that repository. Please send your PR to jenkinsci/jenkins.

[Alexander Shopov]

> We're not using that repository. Please send your PR to jenkinsci/jenkins.

Ooops, there you go:

https://github.com/jenkinsci/jenkins/pull/1913

Kind regards:

al_shopov