Translations?

[DiogoAndre]

I'm interested in starting a translation effort for the git-scm website. Are there any current plans or efforts?

cheers

[DiogoAndre]

So... I did a static translation of the site in pt-br. Most of the static files are translated, and the book links will point to the pt-br version as default. I've deployed it to Heroku just to have some public facing site for review: http://facetious-earth-6314.herokuapp.com/

Any thoughts @bry4n @schacon ?

I'm not sure if it would be wise to mantain a fork of the site in another language. The ideal would perhaps be a full internatinalization of the site, but not sure what would be the best strategy for that.

[codingisacopingstrategy]

+1 Was surprised to not see translation support, quite important for making Git accessible to French and Spanish speaking communities that I know of… Would gladly contribute to a French translation. If it’s a Ruby on Rails site, I’m sure Rail has some internal mechanism for facilitating i18n no?

cheers,

[codingisacopingstrategy]

Also open: #195

[schacon]

This is a great idea. I'll look into using the Rails i18n tools to help facilitate this for people. Or if someone wants to start on it I would be happy to review and merge it in and add notes to the README for future translators.

/cc @bry4n - you thinking maybe this or something else?

[DiogoAndre]

This is something I would certainly enjoy working on.

I had a experience before with Rails default i18n, and while it works just fine, there might be some gems worth exploring.

haml-i18n-extractor is something that can ease the pain of the boring string extraction. Haven't tested it, though.

ps: I disabled the example site I mention above just a day before @codingisacopingstrategy made his comment and revived this thread. It was basically a static translation of the site, with a couple of tweaks...

[AnneTheAgile]

Would translations need to go through the email patching process as well? It seems like for patches to the regular 'git help' , the email list is the only approved method, https://github.com/git/git/blob/master/Documentation/SubmittingPatches (I was trying to figure out how to get git help checkout's synopsis to include --track.)

[DiogoAndre]

Good question! Even though the man pages - that's what you get when you type git help add for example - are included on this website, they are not an integral part of the git-scm.com code base. The man pages you get when accessing http://git-scm.com/docs/ are generated at deploy time by exporting from the local system's git. You can check how it is done in local_index.rake.

So, this translation effort does not include the man pages, and no patch to the Git man pages can be done from this repository. Contributing to the git-scm.com website does not (as far as I know) requires the same process that is required when contributing to the core Git codebase.

Kind of a long answer, I hope it made sense :)

[AnneTheAgile]

Yes @DiogoAndre , that helps so much, thank you!

[sxlijin]

This no longer seems to be an issue and should be closed.

[codingisacopingstrategy]

@sxlijin Could you give some explanation on why this is no longer an issue?

Thanks,

[peff]

There are three main content sources:

1. Content original to the site itself (e.g., the landing page).

2. Content imported from the Git manpages.

3. Content imported from the Pro Git book.

The third one already has a translation effort ongoing. The second one is outside the scope of this repository (but if a translation project starts, we'd do some work to import them).

I do think the first is within the scope of this repo. However, it's a big project that nobody has moved on at all in the past 3 years since this issue was opened. So it's definitely not "already fixed", and I'm not quite sure it's "won't fix", but it does seem like a stale request.

[sxlijin]

Ah, yeah, I was commenting more specifically along the lines of "there are existing translation efforts" - although I didn't realize that the man pages didn't have any translation efforts.