Skip to content
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

Community Survey Issue: Different Translation Paths #1020

Closed
alsalin opened this issue Sep 20, 2018 · 7 comments
Closed

Community Survey Issue: Different Translation Paths #1020

alsalin opened this issue Sep 20, 2018 · 7 comments

Comments

@alsalin
Copy link
Contributor

alsalin commented Sep 20, 2018

Along the lines of the following comment:
"It would be great, when you could provide the opportunity to translate articles or parts of articles into one’s native language, without having to commit to become a whole kind of “Special Interest Group Language X” and having to tackle the overhead coming along with this (I imagine most people don’t have the time to become a full-blown translation project within PH. Most imho, however, have the time to translate or improve upon a couple of articles)."

Do we want to consider different routes for translation at all? We had interest in the following languages emerge from the survey: German, Portuguese, Japanese.

@drjwbaker
Copy link
Member

drjwbaker commented Sep 21, 2018

Having gone down the route of having an ISSN for each translation project #788, ad-hoc translation no longer fits with our infrastructure.

@acrymble
Copy link

This is something anyone can do because our lessons are published CC-BY. We could address this with a blog post encouraging ad hoc translation.

@amsichani
Copy link
Contributor

This is something anyone can do because our lessons are published CC-BY. We could address this with a blog post encouraging ad hoc translation.

Ad hoc translation of a (part of a ) lesson is a great idea for impact- internationalisation - engagement with PH! I 'd like to contribute to such a blog post!

@drjwbaker
Copy link
Member

drjwbaker commented Oct 2, 2018

Another thought on this (were ad-hoc translations to somehow fall into our infrastructure): who is responsible for keeping an ad-hoc lesson translation up to date? (that is, if the original language lesson needs to change slightly, then so does the translation, but if we don't have the language skills to make the change, who does it?)

@acrymble
Copy link

acrymble commented Oct 2, 2018

Informally, it's whomever makes the English changes is responsible for finding someone to make the other language changes. It's the same issue we have when changing the about page, for example.

@drjwbaker
Copy link
Member

Pulled over from email conversion, there are two actions from this issue.

  1. a blog post:
  • encouraging ad-hoc translation (in sum: lessons are CC-BY so go ahead!)
  • underscoring the effort + commitment + policy it takes to integrate a full translation initiative as justification for why we can’t/won't take all translations in house
  • showcasing examples & uses ad-hoc translation
  • explaining the procedure
  1. assess setting up a workflow / tech reqs for hosting ad-hoc translations

Assigning to @amsichani for now. Anna-Maria: it may be the case that we can close this and set-up two seperate issues for 1 and 2 above, but I'll leave that decision with you 😄

@amsichani
Copy link
Contributor

closed now, as #1037 and a blog post are on their way!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants