Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internationalization #21

Closed
tweakimp opened this issue Apr 22, 2017 · 16 comments
Closed

Internationalization #21

tweakimp opened this issue Apr 22, 2017 · 16 comments

Comments

@tweakimp
Copy link
Contributor

Are you planning to add other languages? I could write and maintain the german language file, maybe with poedit

@t-mullen
Copy link
Member

t-mullen commented Apr 22, 2017

I have no plans for translation, but any PRs that add it are welcome.

There's not much text, so I don't think it would be too difficult to do manually.

@t-mullen
Copy link
Member

t-mullen commented Apr 22, 2017

Going to backlog this until the VSCode and Atom versions are finished. If we're going to add localization, we should do it correctly and consistently.

Any temporary language PRs for this version are still welcome, just make them easy-ish to revert if needed.

Of course, you can fork the project and change the strings to German as a quick fix.

@tweakimp
Copy link
Contributor Author

Ok.
I like how you are saying "we" while you do all the work :)
Prioritizing is important,of course, but it's also a question of where are you want to go with this plugin. Do you want it to be the ultimate pair progtamming tool or to just do what it does now: synchronized coding?

@t-mullen t-mullen removed the backlog label Apr 22, 2017
@t-mullen
Copy link
Member

t-mullen commented Apr 22, 2017

This will be important for the initial release, but I'm more focused on the core featureset for all the editors right now :)

@tweakimp
Copy link
Contributor Author

ok :) just summon me and ill translate everything to german

@t-mullen t-mullen changed the title Add other languages Internationalization Apr 27, 2017
@t-mullen t-mullen added the BETA label Apr 27, 2017
@Worie
Copy link
Collaborator

Worie commented Apr 29, 2017

Feel free to mention me for Polish

@AonoZan
Copy link
Contributor

AonoZan commented May 1, 2017

Simple menu items wont be much of a problem for anyone to translate I guess. But if you ever run into need for translating help file, tool-tips etc. you have me for Bosnian. :)

@t-mullen t-mullen removed the BETA label May 1, 2017
@t-mullen
Copy link
Member

t-mullen commented May 8, 2017

I've never tried to internationalize software before, so please let me know if this approach won't work:

A json file for each language with this format:
en.json

{
   "disconnect": "Your connection to \"{{nickname}}\" has been lost.",
   "id_prompt": "Enter the ID of the room you want to join.",
   ... and so on
}

Each language file would just swap out these values, while keeping the keys and tags the same (like id_prompt and {{nickname}}). Any objections?

@tweakimp
Copy link
Contributor Author

tweakimp commented May 8, 2017

Please add a comment to each translation. It's helpful to know where it belongs to.

@tweakimp tweakimp closed this as completed May 8, 2017
@tweakimp tweakimp reopened this May 8, 2017
@tweakimp
Copy link
Contributor Author

tweakimp commented May 8, 2017

Little missclick :)

@t-mullen
Copy link
Member

t-mullen commented May 8, 2017

Ok, I pushed a translation file. Please add the 2-letter language code and all of the necessary translations. I think they are pretty straightforward, but if anything is unclear, let me know.

There's about 44 different words/phrases that need translation.

@t-mullen
Copy link
Member

t-mullen commented May 8, 2017

@t-mullen
Copy link
Member

t-mullen commented May 8, 2017

@Worie @AonoZan Mentioning for additional translations, when you get the time :)

@tweakimp
Copy link
Contributor Author

tweakimp commented May 8, 2017

I mixed formal and informal adress of the User. I would like to clean that up. Which one do I use?

@Worie
Copy link
Collaborator

Worie commented May 8, 2017

Lets split the translations to separate files (de.json, pl.json and so on).

Itll prevent a lot of conflicts and be easier to manage. Ill sit to pl translations when im back from jsconf

@t-mullen
Copy link
Member

t-mullen commented Jun 8, 2017

I'd say the solution implemented is adequate for now. Closing as completed.

Splitting up files means determining the language at load time, something I haven't figured out yet (besides simply loading every file). Maybe I'll revisit that, but it should be OK as is.

@t-mullen t-mullen closed this as completed Jun 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants