search

betterangels / buoy

:sos: A community-based crisis response system. Because friends don't let friends call the cops. :fire::police_car::fire:
https://betterangels.github.io/buoy/
GNU General Public License v3.0
72 stars 23 forks source link

Write documentation for translators (a "translator instructions" page) #67

Open fabacab opened 8 years ago

fabacab commented 8 years ago

When someone joins the project as a translator, we currently hope they will figure out Transifex for themselves. This isn't exactly difficult, but it would be even better to have some documentation about the translation process that we are using on a wiki page (such as, perhaps, "Translator instructions") ready to go. I've already linked to that page from our Transifex project's overview so that it's available whenever such a page exists and becomes useful.

This would also be a great way for someone who wants to know more about the localization process to learn how this works and then document their understanding in such a way as to help others figure it out.

fabacab commented 8 years ago

Another consideration is that WordPress.org now has a built-in translation system for plugins distributed via their plugin directory, and it's become the recommended way to do i18n for plugins. So we should maybe migrate off Transifex and begin using the WordPress-native system, in part because this also means we can avoid maintaining the .po files ourselves.

Not entirely sure what to do with the wiki docs around this topic, yet, though.

CC: @thepunkgeek

hurtstotouchfire commented 7 years ago

@trancos11 @tambait Is this issue mostly resolved? Can we tidy up that wiki page and close this?

trancos11 commented 7 years ago

I think we are close. I would advise an actual light style sheet to enhance consistency. I'd like to discuss this a bit more with @tambait. Things like using formal va informal, avoiding gendered terms when possible, expected level of technical understanding for the user, etc. other thoughts @tambait ?