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

Multi Languague #45

Open
pedromorgan opened this issue Dec 28, 2014 · 11 comments
Open

Multi Languague #45

pedromorgan opened this issue Dec 28, 2014 · 11 comments

Comments

@pedromorgan
Copy link
Member

Make it more multilingual also.. (I think in Welsh when i code docs = idiots language)

Also we need chinese and nippongo translations..

@brendensoares
Copy link
Member

@pedromorgan We already have Chinese, Russian and soon Korean translations. I wonder how we can help keep them up to date? @arahansa

@ghost
Copy link

ghost commented Jan 2, 2015

@brendensoares

We already have Chinese, Russian and soon Korean translations. I wonder how we can help keep them up to date? @arahansa

Aaaaand @gorevelru, @goofcc

@pedromorgan
Copy link
Member Author

Not sure we can run "jekyll plugins" on github..

but the other way to do would be with a directory for each lang..
en/, fr/ ru/ etc

There again, we'd need to sync than will all the other "participants".

@pedromorgan pedromorgan reopened this Jan 2, 2015
@pedromorgan pedromorgan changed the title Idiot Proof Multi Languague Jan 2, 2015
@ghost
Copy link

ghost commented Jan 2, 2015

but the other way to do would be with a directory for each lang..
en/, fr/ ru/ etc

@pedromorgan Do you think the translations should be centralized?

Right now docs are kind of federated. Revel Core Team is responsible for English version only. Translations are driven by community. Moreover, there are kind of separate communities around translated versions. They may have their own forums, moderators, etc. And what's important authors of translations can add ADs to their web-site for monetization.

@pedromorgan
Copy link
Member Author

anonx: Do you think the translations should be centralized?

No, i dont think so, and that's from experience with Smarty docs from yonder year, and was complicated by permissions, abandoned users, incorrect translation and hijacking et all

However we could help by maybe linking to the "other langs" on the sire somehow, maybe with a dropdown on the "top nav right side"..

@ghost
Copy link

ghost commented Jan 2, 2015

However we could help by maybe linking to the "other langs" on the site somehow, maybe with a dropdown on the "top nav right side"..

@pedromorgan 👍

@brendensoares
Copy link
Member

@AnonX @pedromorgan I like the idea of having the translations central to this repo and giving other community members access. At the very least, we could use a PR work flow.

@arahansa
Copy link

arahansa commented Jan 3, 2015

@brendensoares Ah, I just see this mention.
http://100coding.com/go/revel
This site is translated Revel site in Korea.. But All of content is not translated.
I translated main page("메인") and tutorial page("튜토리얼") so far.
I was busy last year. sorry.
hm... I added a button called "번역" in all paragraph.
If visitor push a button "번역", they will see the text changed in English or Korean.
Because I respect the original manual.

I am developing web board using Go, Revel, GORP.
(I refer to booking sample a lot. thanks.) It is almost completed. I plan to make video tutorial, blog post, ppt slide and git repository. and share it with facebook group members.
As soon as make the tutorial. I will translate Revel manual into Korean again.

@goofcc
Copy link

goofcc commented Jan 4, 2015

@AnonX , @brendensoares,Chinese manual translation, I would have taken the time to make and keep track of the latest version of Revel. Don't know what the official has rules to follow for translation? At present, Chinese manual has a simple version, I hope to finish the translation when the Revel 1.0 release.

@brendensoares
Copy link
Member

@goofcc @arahansa I am not familiar with translation best practices. What do you recommend as far as defining translation guidelines/rules?

@jniltinho
Copy link

add folder doc to translation pt-BR like https://github.com/beego/beedoc or https://github.com/macaron-contrib/docs.
We would like to contribute to the project

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

5 participants