Translations

[researchtool]

Hi everyone 👋, I use tenzing on a regular basis, and would like to compliment you on this great tool! I'm truly impressed by the work being done here!

I noticed that translations for the output (and perhaps even the interface) could expand the accessibility of this wonderful project to even more users around the world.

I have some experience in this area and already translated the casrai contributions a while ago casrai-credit-german. I would provide German translations if you like the idea.

Best wishes, timo

[alexholcombe]

Thank you for the compliment, getting this kind of feedback is quite heartening, and also can help with grant applications. About translation, thank you for this excellent idea and generous offer of help. This would be great to do. We actually don't know how translations work in the context of a NISO standard; perhaps they have some kind of process that would eventually incorporate a translation/localization into a revised version of the standard. We should check on that first, so I have now written to some people in touch with NISO and once they answer, I will follow up with you. Thanks again!

[alexholcombe]

Nettie of NISO got back to me (below). @researchtool & @marton-balazs-kovacs , should we schedule a call to discuss a plan? I suppose that separately from tenzing or any other package, your translation should be posted somewhere as a stand-alone document maybe, which NISO can then link to.

"we indeed have a process as we’ve had other ANSI/NISO standards that have been translated to French, Italian, Chinese, etc. over the years. But they are not viewed as official standards - only the ANSI/NISO version is. These translations do, however, make the material more easily accessible for various audiences and of course we’d like to support this.

In past efforts we have prepared simple MOUs to document the permission.

The translation must not be presented or referred to as an American National Standard (ANS). The ANS logo and the words “an American National Standard” should not be on the translated document as the English language version is the only one that was approved as an ANS.

In order to maintain control over the document (to prevent potential forking and confusion), NISO requires that the copyright in the translation be jointly held by NISO and the translating entity. We also request that the original English-language version be referenced with its full title and a link to the original document on the NISO website and a note about the copyright."

[researchtool]

I appreciate your diligence in getting this information, and it looks like we're in a good position to create a stand-alone document for the translation, following the specifics outlined by NISO. This approach will enable us to meet their requirements regarding copyright and reference to the original English version. I'll be ooo for some time, so we could either schedule it within the next week or mid-September. I'm in the Vienna/Berlin time zone. But early mornings and late evenings often work for me. Best, timo

[marton-balazs-kovacs]

Thanks, Timo, for the compliments, I am glad to hear that you like the app. Also, the translations sound like a great idea.

I was wondering whether it would make sense to create a translation template document first in a standalone repository. It could be under the tenzing-contrib org if you all agree. We could also propose a translation hackathon at the next Big Team Science conference as I imagine a lot of people with a wide array of native languages will be present. Creating the first draft of the translation for the 14 roles shouldn't take too long. The deadline is extended until the 14th of August: https://bigteamscienceconference.github.io/submissions/#sessions

[researchtool]

Great idea!

[marton-balazs-kovacs]

Also, we can translate the tenzing Shiny app navigations too. We can implement the translations with i18n on the published version.