-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Make the site multi-language #6
Comments
Question:
|
I am collecting some links to Jekyll multi-lingual solutions:
Ruby gems/plug-ins: |
Well due to the new orthographic agreement of the Portuguese language and the political project of unification of the language, I suggest keeping only PT, since technically it is perfectly possible to consolidate the work only in PT. Even knowing that in colloquial language there are several slang that differ between countries. Thus we consolidated the translation efforts. The result will be the same and readable at all, mainly because our intention is a purely technical material. If someone who has mastered the Portuguese language in its original form from Portugal to come to join us wants to express contrary opnion assess the impact and ramificamos, if it is really necessary to have two translation branches, PT and pt_BR. For now I reaffirm that prefer only one, PT. See the example of Stackoverflow Portuguese, it works perfectly for both variants. |
I'm reading the suggested links and liked the first because of the argument that advocates no internal interference in Jekyll even with plugins. I think the proposal to have a code in the layout format the site very attractive bilingual form, but the ideal is to have the url any indication of the language beyond words natively as there could be conflicts, as some terms will not be translated. One way or another, or the path of the url should indicate the language, or the file, I prefer to be the directory to have a proper separation of files in the source. |
ok. so I suggest we have the Portuguese pages marked with I don't think we should translate the urls, they can remain in English; the prefix should be enough to differentiate the pages. |
for start, I would add |
since the actual site structure is explicitly defined by the permalinks, the physical folder structure of this project is not relevant, we can adopt any scheme that suits us and we can change it at any time. for example we can start with minimal changes, by storing the Portuguese manual pages in the same folder as the English ones, and insert this does not require any plug-in, and we can use it immediately. |
Sidebarfor a completely translated site, we should think of translating the sidebar too, but, for the beginning, I think we can live with an |
Well, I agree with everything. I think for the layout (_layout and _Include) of the site and the pages of the site structure, not the content itself, we can use a file in the folder _data for translation, so we will not have problems, also remember to add the charset UTF 8 as standard, but when someone is translating into a language that utf-8 does not meet this may change in the future and adjust the layout to suit every charset. As suggested in https://www.sylvaindurand.org/making-jekyll-multilingual/ |
Please see #9 |
please check http://micro-os-plus.github.io/pt/user-manual/ |
there is a |
yes, we can use this, if necessary. there are many other suggestions in Sylvain's post. if you think they are needed, please suggest punctual changes, the current proposal is very basic. |
I added the language ID to the |
I translated the 'Contents' label used by the TOC generator. the translation is done via a data file ( |
Mãos a Obra! :) |
Two issues anticipated:
The text was updated successfully, but these errors were encountered: