Localization: Localize the extension to {insert language here}

[shana]

Imported from https://github.com/github/VisualStudioInternal/issues/35

[shana]

Depends on #17

[elbaloo]

I can help with es-MX but I'm not following the implementation... I'm looking at this.

[shana]

@elbaloo There are several resx files in the solution which contain strings. Adding translations is a matter of editing the resx files, adding a new language and the translated strings. There's an extension for Visual Studio called Resx Manager (http://resxresourcemanager.codeplex.com/) that makes this easier.

[austingreendev]

@shana is this issue available? I can use the resxresourcemanager listed above (which if I remember correctly just uses Bing Translate if you ask it to translate as well as read). I am also currently at a University and know several native speakers of the bigger languages so I can double check with them.

What are your target languages?

[haacked]

What are your target languages?

ALL OF THEM! 😛

In all seriousness, we'll take all the languages people are willing to contribute as long as we can reasonably ensure the translations are of good quality.

[austingreendev]

The languages provided in the Microsoft Visual Studio 2015 Language Pack are:

• Chinese (Simplified) - known native speaker
• Chinese (Traditional) - possibly known native speaker
• Czech
• English - I hope this one is right
• French - known native speaker
• German - known native speaker
• Italian - known native speaker
• Japanese
• Korean
• Polish
• Portuguese (Brazil)
• Russian - known native speaker
• Spanish - known native speaker
• Turkish

This should be a good start since most people using VS will be stuck with these.

Also, randomly heard your DotNetRocks podcast the other day. It was a good talk!

[shana]

is this issue available?

All issues are available 😄

Software translation should probably not be done with Bing, though 😉

Microsoft has excellent resources for translation at https://www.microsoft.com/Language/en-US/Default.aspx, including style guides and terminology collections.

[haacked]

Software translation should probably not be done with Bing, though

It's probably fine to use automated translation (such as Bing or Google) to get started as long as the translation is checked and corrected by a native speaker, which is what I think @Austin94 suggested. 😄

Also, randomly heard your DotNetRocks podcast the other day. It was a good talk!

Thanks! ✨

[austingreendev]

Here is a google spreadsheet of all the resx keys that I found along with Translations: https://docs.google.com/spreadsheets/d/1zE-KmrVhSQy3bgJ0Fmaxid-5ImGtEyQzFGaLZZwQ-cI/edit?usp=sharing

So far I have only used Google Translate for Chinese (Simplified), Czech, and German. I hope to have all of these languages double checked by native speakers by the end of this weekend before I move on to others.

One questions on branding though. For the phrase 'GitHub Enterprise' would you prefer that to be left in English for branding? Or would 'GitHub translation' work?

[shana]

@Austin94 Brand names need to be double-checked internally, so leave them as is.

[austingreendev]

I have a completed translation from a native Korean speaker so I will be bringing that in soon. From what he described Google Translate got pretty close, but he gave some grammatical fixes and added some git terminology that it struggled with. Also, the string lengths are pretty close across all of the phrases so we shouldn't have much of an issue with under-over flow of text.

[maikebing]

@shana I am Chinese! So can i translate it?

[austingreendev]

@maikebing Unfortunately, I never completed updating the locale files. I am no longer implementing this feature, but I will leave the google sheet up and give you write access if you still want to translate.

We can leave it here if anyone eventually wants to finish.

[GabPar5]

I am italian, I can translate it if you want :)