Skip to content
This repository was archived by the owner on Jun 21, 2023. It is now read-only.
This repository was archived by the owner on Jun 21, 2023. It is now read-only.

Localization: Localize the extension to {insert language here} #18

Closed

Description

@shana

Activity

  1. shana commented on Jul 29, 2015

    @shana
    ContributorAuthor

    Depends on #17

  2. elbaloo commented on Oct 9, 2015

    @elbaloo

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

  3. shana commented on Oct 9, 2015

    @shana
    ContributorAuthor

    @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.

  4. austingreendev commented on Mar 2, 2016

    @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?

  5. haacked commented on Mar 2, 2016

    @haacked
    Contributor

    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.

  6. austingreendev commented on Mar 2, 2016

    @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!

  7. shana commented on Mar 2, 2016

    @shana
    ContributorAuthor

    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.

  8. haacked commented on Mar 2, 2016

    @haacked
    Contributor

    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! ✨

  9. austingreendev commented on Mar 3, 2016

    @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?

  10. shana commented on Mar 4, 2016

    @shana
    ContributorAuthor

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

  11. austingreendev commented on Mar 21, 2016

    @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.

  12. maikebing commented on Feb 24, 2017

    @maikebing
    Contributor

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

  13. austingreendev commented on Feb 24, 2017

    @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.

  14. GabPar5 commented on Aug 25, 2017

    @GabPar5

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

  15. austingreendev commented on Aug 25, 2017

    @austingreendev
  16. wenz commented on May 31, 2018

    @wenz

    Who is maintaining this? I have a set of German translations ready to be used ;)

  17. maikebing commented on Jun 1, 2018

    @maikebing
    Contributor

    I started to do this thing. I hope everyone will support it.

  18. wenz commented on Jun 1, 2018

    @wenz

    @maikebing could you set up the Google Doc (or something similar) again, so that I can dump the German translations?

  19. maikebing commented on Jun 2, 2018

    @maikebing
    Contributor

    @wenz OK, I will have all the statements extracted after the completion, sent to everyone.

  20. maikebing commented on Jun 4, 2018

    @maikebing
    Contributor

    I suggest using Bing translation, then manual proofreading, Bing Chinese translation is very good, so you might try it.

  21. wenz commented on Jun 4, 2018

    @wenz

    shoud we put it up on Google Sheets or something similar, so that we can edit simultaneously?

  22. maikebing commented on Jun 4, 2018

    @maikebing
    Contributor
  23. meaghanlewis commented on Jun 6, 2018

    @meaghanlewis
    Contributor

    @maikebing this crowdin page is great, thanks! It's really nice to visualize the progress of the localizations by language

  24. maikebing commented on Jul 19, 2018

    @maikebing
    Contributor

    Looking forward to other language translators, anyone?
    click here to join HTTPS://CRWD.IN/GITHUBVS

  25. meaghanlewis commented on Feb 25, 2019

    @meaghanlewis
    Contributor

    Closing out since this work was completed in #1968

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions