-
Notifications
You must be signed in to change notification settings - Fork 344
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-lingual Support? #35
Comments
There is nothing other then the seperation into an en directory. Multilingual support could certainly be added but it would take a really dedicated translator to get that going. I did contact team cf advance about adding CF11 docs and they have helped a bit there. |
I may play with that on a fork. |
Awesome, that would be cool! I don't think it would be terribly complicated, the main thing you would need to do is edit the files in /views to provide a way to show localized strings, instead of just hard coded english. There is not too much translation needed there. I would probably setup subdomains for each language, eg: es.cfdocs.org I think we should use the ISO-639-1 language codes: http://en.wikipedia.org/wiki/ISO_639-1 I don't think getting into dialects (eg en-US, en-GB, en-CA) would be necessary. The big part of the job is creating all the json files, we need to figure out what to do if a doc is there in one language but not another, 302 redirect, or show the english doc using the language's localized view? |
If a doc didn't exist in the user's selected language, we could load the en version with an extra call to action "Help translate this page!" banner. It could link to a github wiki page with details on how to help translate. |
Good idea. |
Going to close this, as there hasn't been much interest in multi-lingual support. |
I see you've got the data under an 'en' directory. Are you setup already to support multiple languages? If so I think Team CF Advance could gather some devs from Brazil, at least, to work on a secondary language. Thoughts?
The text was updated successfully, but these errors were encountered: