Request to put khmer (Cambodia) language on www.ruby-lang.org

[Bunlong]

Dear all,

My name is Bunlong Van, I am a Rubyist living in Phnom Penh Cambodia.
I would like to request you to put khmer (Cambodia) language in www.ruby-lange.org.

I look forward to hearing from you soon.

Thank you!!!

[makimoto]

Hi, Bunlong. Thank you for your issue.
I'm makimoto from the editorial team of www.ruby-lang.org.

We can make a new language version of w.r-l.o if there are enough maintainers for it.
Firstly, could you translate some articles (top page, about page, latest news and so on) into khmer and give us pull-requests?

Thanks.

[stomar]

@Bunlong, @makimoto

It must be certain before any PRs that there are enough maintainers/translators.
Abandoned and out-of-date translations are worse than having none at all. And with a single responsible person this happens very easily.

Adding a new translation involves a lot of work, both in preparation and afterwards:

• all static content must be translated before the site goes live,
• later on all new posts about vulnerabilities and new releases must be translated, and the content needs to be kept up-to-date with the original en site.

See also the milestones for #214 to get an impression of the work involved during the initial translation process.

This may sound a little discouraging, but please keep in mind that a new translation causes a lot of work for us maintainers, too. (I have already coordinated the ru and vi translations and I should know.)

As soon as it is sure that there is a team of at least say 3 persons who will show that kind of commitment, we can discuss the details on how to best proceed.

Please do not provide any PRs right now.

[makimoto]

@stomar i'm sorry for my premature reaction... 🙇

@Bunlong
As @stomar says, a new language version requires active long-run maintainers.
Could you find enough people who can become maintainers of the Khmer version?

[Bunlong]

@makimoto, @stomar Yes, sure. I have enough people who can become maintainers of the Khmer version already. When can I start? and What is the precess? Could you details more?

Thank you

[stomar]

Great! Please let them post a short comment here.

[trodeth]

hi @stomar @makimoto @Bunlong nice to meet you. i'm really excited to be a part of this project.

[sarath-c-sandwich]

Greeting from Cambodia,

I am the Rubyist from Phnom Penh, Cambodia. I would like to join for localizing Khmer language in Ruby docs. I used to join in translating Khmer docs for Google with another people, and this should be another chance.

[sophenpho]

We are in Cambodia. We would like to start localizing Khmer language in Ruby docs.

[Bunlong]

@stomar, @makimoto They are the team member, they can handle on maintain and translation. We can do it. Thank

[SokhomRatanak]

I would be good if we have Khmer language in www.ruby-lange.org
It is going to be cool 👍

[stomar]

@hsbt, @chikamichi, @postmodern, @makimoto, @sorah, @zzak

Any opinion on adding km?

[sorah]

I have no objection.

By the way, I'm worrying to abandoned translations -- please don't give up silently.

Looking forward to your work ✨

[sarath-c-sandwich]

We are now connecting to InSTEDD lab, and another Rubyists in Cambodia to participate.

[Bunlong]

@stomar , @chikamichi , @postmodern , @makimoto , @sorah , @zzak , @makimoto : We are working on this. Thank you all for your support...

[stomar]

I prepared a km-translation branch, but I want to fix a few problems before pushing it to the repo (e.g. failing builds). That will be the branch from which you will have to fork feature branches for PRs. So wait with PRs.

But of course you can already start with translations now. A few hints:

• Keep the formatting (paragraphs, markdown, code examples, ...) like it's done in en, so diffs between km and en are easier to read.
• Use lines with max 80 characters (unless your language has no whitespace between words), avoid trailing whitespace.
• Agree on who starts with which section.
• Agree on how you want to handle code examples: I suggest to only translate comments, not the code itself (I find non-English class and variable names a little strange).
• Remember to adjust the YAML headers (lang: km) and links (/en/downloads/page -> /km/downloads/page).
• Do not start with news posts; the current news will be old news when the site goes live.

[stomar]

I pushed the km-translation branch. Please fork feature branches from km-translation for PRs.
Let's start slow with single PRs, so you can get feedback and needless extra work is avoided.

I also opened an issue for the milestones, see #699.

[Bunlong]

@stomar ok, I got it. Thank you!!!

[stomar]

Sadly not a single PR after the work I put in the setup of this.
I'm closing the issue since I don't except anything to happen here.