Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upDecide how to handle doc/website language translations #1333
Comments
andrewdavidwong
added
the
C: website
label
Oct 14, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Oct 22, 2015
Member
If no one voices any objections in the next week, I'll default to the following scheme:
- Use subdirectories for any new page translations:
https://www.qubes-os.org/intro/(unchanged canonical English version)https://www.qubes-os.org/pl/intro/(new Polish translation)https://www.qubes-os.org/de/intro/(new German translation)
- Use filename language codes for any new source file translations:
_doc/basics/intro.md(unchanged canonical English version)_doc/basics/intro.pl.md(new Polish translation)_doc/basics/intro.de.md(new German translation)
|
If no one voices any objections in the next week, I'll default to the following scheme:
|
andrewdavidwong
added
the
C: doc
label
Oct 22, 2015
andrewdavidwong
changed the title from
Decide how to handle website language translations
to
Decide how to handle doc/website language translations
Oct 22, 2015
added a commit
to QubesOS/qubes-doc
that referenced
this issue
Oct 28, 2015
added a commit
to QubesOS/qubes-doc
that referenced
this issue
Oct 28, 2015
added a commit
to QubesOS/qubesos.github.io
that referenced
this issue
Oct 28, 2015
added a commit
to QubesOS/qubesos.github.io
that referenced
this issue
Oct 28, 2015
andrewdavidwong
closed this
Oct 28, 2015
andrewdavidwong
added
the
localization
label
Jan 27, 2017
andrewdavidwong
referenced this issue
Feb 19, 2017
Open
Create automated workflow for translation of Markdown content #1452
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Feb 25, 2017
Member
can we explore implementing this? there are a couple of full translations for spanish now:
https://www.transifex.com/otf/qubes/language/es/
this is less a priority than changing the markdown conventions in #1452.
|
can we explore implementing this? there are a couple of full translations for spanish now: this is less a priority than changing the markdown conventions in #1452. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Feb 26, 2017
Member
can we explore implementing this? there are a couple of full translations for spanish now:
https://www.transifex.com/otf/qubes/language/es/this is less a priority than changing the markdown conventions in #1452.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Feb 26, 2017
Member
If no one voices any objections in the next week, I'll default to the following scheme:
- Use subdirectories for any new page translations:
https://www.qubes-os.org/intro/(unchanged canonical English version)https://www.qubes-os.org/pl/intro/(new Polish translation)https://www.qubes-os.org/de/intro/(new German translation)- Use filename language codes for any new source file translations:
_doc/basics/intro.md(unchanged canonical English version)_doc/basics/intro.pl.md(new Polish translation)_doc/basics/intro.de.md(new German translation)
Based on internal discussions, we've decided to put all translated files in a separate, untrusted repo (i.e., no signed commits or tags). The main reason is that we can't evaluate content in languages that we can't read, and we don't want to sign content that we haven't evaluated (also see #2652).
This won't affect the URL/subdirectory scheme outlined above, but it may affect the naming scheme for source files. For example, we may just want to retain the same (canonical English) source file name for every language.
Based on internal discussions, we've decided to put all translated files in a separate, untrusted repo (i.e., no signed commits or tags). The main reason is that we can't evaluate content in languages that we can't read, and we don't want to sign content that we haven't evaluated (also see #2652). This won't affect the URL/subdirectory scheme outlined above, but it may affect the naming scheme for source files. For example, we may just want to retain the same (canonical English) source file name for every language. |
andrewdavidwong commentedOct 14, 2015
This issue continues the conversation from comments on #1205. There are two main places where languages might be represented:
Given that the website is currently in English, there are several available approaches to differentiating pages/sites in other languages in URLs:
https://www.qubes-os.org/(unchanged canonical English version)https://pl.qubes-os.org/(new Polish translation)https://de.qubes-os.org/(new German translation)https://www.qubes-os.org/-->https://en.qubes-os.org/https://pl.qubes-os.org/https://de.qubes-os.org/https://www.qubes-os.org/intro/(unchanged canonical English version)https://www.qubes-os.org/pl/intro/(new Polish translation)https://www.qubes-os.org/de/intro/(new German translation)https://www.qubes-os.org/intro/-->https://www.qubes-os.org/en/intro/https://www.qubes-os.org/pl/intro/https://www.qubes-os.org/de/intro/Likewise, there are several possible ways to differentiate source files in different languages:
_doc/basics/intro.md(unchanged canonical English version)_doc/pl/basics/intro.md(new Polish translation)_doc/de/basics/intro.md(new German translation)_doc/basics/intro.md-->_doc/en/basics/intro.md_doc/pl/basics/intro.md_doc/de/basics/intro.md_doc/basics/intro.md(unchanged canonical English version)_doc/basics/intro.pl.md(new Polish translation)_doc/basics/intro.de.md(new German translation)_doc/basics/intro.md-->_doc/basics/intro.en.md_doc/basics/intro.pl.md_doc/basics/intro.de.mdFactors which might influence the decision: