Translation workflow: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Two ways to add translations to Scribus: # Submitting .ts file via bugs.scribus.net # Via [https://www.transifex.com/scribus/scribus/ Transifex] the online crowdsourced transl...") |
(added link to language Graph) |
||
| Line 19: | Line 19: | ||
What else? | What else? | ||
See [https://github.com/scribusproject/scribus-translations/blob/master/README.md Language Graph] | |||
Latest revision as of 05:39, 22 October 2015
Two ways to add translations to Scribus:
- Submitting .ts file via bugs.scribus.net
- Via Transifex the online crowdsourced translation site
Some of the official translators of their specific languages are going to have their own preferences between option #1 and #2
Challenge: How do we keep Transifex up to date with SVN ?
Because if someone submits directly to SVN:
- How does that specific language .ts file get updated in Transifex?
- What if the translations of that same language have already been translated in Transifex? There is a conflict.
- How can we make it easy for an official designated Scribus translators to incorporate/approve the changes from transifex and non-transifex .ts files ?
Infrastructure issues:
- Transifex exports obsolete .ts xml format that is < /> and needs to be < ></> How do we reconcile this?
- BTW I sent an email to Transifex support for orientation about this. Awaiting response
- Utilizing chhitz's script in http://bugs.scribus.net/view.php?id=13097
- Making sure that the bumped .ts files continue to show the context of where the translation string is in the code (because this was missing in Transifex's previously updated en_US.ts file)
What else? See Language Graph