forked from carpentries-i18n/i18n
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Guidelines for Translators #13
Comments
Guidelines for TED will be used (as suggested by @kyyonko). These may be adapted for the purposes of Software Carpentry. |
How come I had forgotten about the TED community!!! Thanks for finding it!! :) |
TomKellyGenetics
added a commit
that referenced
this issue
Nov 19, 2018
rikutakei
pushed a commit
to rikutakei/i18n
that referenced
this issue
Nov 19, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Spanish team has clear guidelines for translators to ensure consistent style across different lesson and contributors. They have a dedicated repo for theirs:
https://github.com/Carpentries-ES/board/blob/master/Convenciones_Traduccion.md
I think ours could be included here since we are using a newer system. Many of these are specific to the Spanish language (such as gender, plurals, or pronouns) so are not such an issue with Japanese. Still matters such as the level of formality #10 should be agreed on (and made clear for non-native speakers who may not understand conventions of when to use formal language).
I've set up a
CultureNotes.md
for non-literal translations and cultural considerations but perhaps we need basic guidelines on language style as well. The Spanish version has also been used for translating R and data science books. If anyone has experience with book translations between English and Japanese, we could use similar style to those projects.The text was updated successfully, but these errors were encountered: