-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add FR translation #1
Comments
…ributors-list Add Valeri Vicneansch to the list of contributors
Would this be achieved via an index_fr.html file or changing the index.html to support a yaml with the content for each language? |
@ajmas I used @sylvaindurand 's https://github.com/sylvaindurand/jekyll-multilingual for https://github.com/bettermtl/bettermtl.github.io - a working implementation, there are other ways to do internationalization as you suggest See how https://github.com/nodeschool/nodeschool.github.io did it differently Montreal is fun because it is multilingual, a barebone setup would probably work best, such that maybe other bilingual+ cities can fork our effort, like we forked nodeschool.io/toronto |
Looks like jekyll-multiple-languages-plugin is a fair bit more maintained than jekyll-multilingual. I wouldn't mind taking care of this feature when I've got some down time. |
BTW It should be noted that Github has a number of whitelisted Jekyll plugins. If we wish to use an extended set, then we should look to using a continuous integration solution, such as Travis (cloud version free for open source): https://github.com/github/pages-gem/blob/master/lib/github-pages/plugins.rb Neither of the two suggested plugins are white-listed for gh-pages, so we may need to look at using a CI solution, or look at another approach. I have added a feature request here: github/pages-gem#401 |
Allow for missing translation strings to show in the secondary language. Montrealers are bilingual
The text was updated successfully, but these errors were encountered: