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

Multilingual? #65

Closed
odie2 opened this issue May 24, 2015 · 10 comments
Closed

Multilingual? #65

odie2 opened this issue May 24, 2015 · 10 comments

Comments

@odie2
Copy link

odie2 commented May 24, 2015

Hello,

Is multilingual possible?

Would translate it to Polish, to complete full Polish Git Extensions' localization. It would be nice way to spread git around Poles.

Greetings

@KindDragon
Copy link

Hi.

First step done https://www.transifex.com/projects/p/git-extensions-manual/, but I don't know how to publish translation ATM :-)

@odie2
Copy link
Author

odie2 commented May 26, 2015

Is it possible to create glossary page in Documentation like Transifex's?

It would be useful for non-English languages to find source English operation's name if user would search for more about this.

@odie2
Copy link
Author

odie2 commented May 26, 2015

but I don't know how to publish translation ATM :-)

Check: Internationalization

@KindDragon
Copy link

s it possible to create glossary page in Documentation like Transifex's?

it's already exist https://www.transifex.com/projects/p/git-extensions-manual/glossary/l/pl/

Check: Internationalization

I know. I only found way though creating manual repository fork https://docs.readthedocs.org/en/latest/localization.html#project-with-multiple-translations

So if you create fork and setup readthedocs project with polish translation we can add it to our RTD project as subproject

@jbialobr
Copy link
Member

I doubt there is such a need, nowadays everyone knows English, especially in IT.

@odie2
Copy link
Author

odie2 commented May 27, 2015

it's already exist https://www.transifex.com/projects/p/git-extensions-manual/glossary/l/pl/

I mean move those phrases to https://git-extensions-documentation.readthedocs.org/en/latest/

So if you create fork and setup readthedocs project with polish translation we can add it to our RTD project as subproject

Will check later

@jbialobr Not exactly. I know many growing programmers who although know English, Git's "slang" makes them headache.
Also programs becomes localization-able to use beautiful of every language and point to more people, who should understand it easier than after long time of work with it.
Additionaly, take a look that earlier or later, someone will do it for learn completely "greens", even in business, how use it to get less works himself. So better is do it before and professionally.
So as Git Extensions is fully Polish supporting, there should be also full manual to even better describe functions.

For curiosity: I already learned three folks how use Git basic with Git Extensions in Polish and saved much work myself, so I could do more programming or translating. If someday they would get know more about it, even with poor English skills, they just will be able to read brief note about it in manual.

@jbialobr
Copy link
Member

I know many growing programmers who although know English, Git's "slang" makes them headache.

Here is a room for improvement and here we should direct our effort towards: to eliminate
complexity, use a simple, easy to understand language and add more examples.

My opinion stems from my point of view about how we should learn a foreign language.
We should surround ourselves with that language as much as possible.

I don't mind creating a translation of manual, but you should note that the current version of manual is stale and uncompleted. It would be better to put in the effort to make it completed and up-to-date.

@odie2
Copy link
Author

odie2 commented May 27, 2015

It would be better to put in the effort to make it completed and up-to-date.

I don't like creating documentations and prefer programming and translating only.
KindDragon is also freelancer that does what he want at the moment. What he prefers, I don't know.

I saw that documentation is little outdated, but there are no problem to translate it and then update on Transifex with little changes. Most of description doesn't need updates or eventually, could be just expanded.

We should surround ourselves with that language as much as possible.

Yes, but it also depens on person. There are two main groups: people who learn foreign language very easy and second group, where people have hardness in even basic grammar or even words.
I sometimes play games or reading articles in English, but when larger story or with specialistic vocabulary, I just scrolling down text for keywords due time limit or that I am poor psychical state to read foreign language intuitively as native.

No one said that you couldn't just switch back to English.
Also, for people who are visualizers and worked with foreign UI before - it's the best way to learn when just switch to native language. They (including me) just remember what were in "that place" and pairing it and here we are - earned excellent knowledge.

@KindDragon
Copy link

I mean move those phrases to https://git-extensions-documentation.readthedocs.org/en/latest/

We accept pull requests :-)

@gerhardol
Copy link
Member

Closing old issues
The documentation need to be updated, then translations could be reconsidered

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