Update Official:Translation Howto on the wiki

[luzpaz]

Wiki is not working ATM so I'll post here:

• https://wiki.scribus.net/canvas/Translation_workflow
• https://wiki.scribus.net/canvas/Official_talk:Translation_Howto
• https://wiki.scribus.net/canvas/Official:Translation_Howto

[luzpaz]

@gyuris please check my revision at https://wiki.scribus.net/canvas/Official_talk:Translation_Howto

[gyuris]

Excellent, I accept! Thanks.

[luzpaz]

Thanks 👍
Now we need to add a Transifex section:
https://wiki.scribus.net/canvas/Official_talk:Translation_Howto#Add_Transifex_section_--_Kunda_.28talk.29_22:07.2C_2_November_2016_.28CET.29

[gyuris]

Yup, than I understand this: https://bugs.scribus.net/view.php?id=13860#c42288

[gyuris]

These are your previous screenshots: scribusproject/scribus#15 (comment)

[gyuris]

3. Screenshots of the process

Transifex has a very good own documentation with screenshots for translators and about the web editor, about roles, for coordinators about managing collaborators and about reviewing, and more also about offline translating. I think we don't need to duplicate this. Just point translators to the official help.

4. Guidelines for Language Coordinators
5. Guidelines for Language Translators

Yes, they are necessary.

[luzpaz]

Can you identify what strings in the Qt framework specifically impact the issue you were running in to when you filed the bug for issue [13860[(https://bugs.scribus.net/view.php?id=13860) ? We can then tell the other translators to translate those strings.

[luzpaz]

@gyuris updated https://wiki.scribus.net/canvas/Official:Translation_Howto please check and provide feedback. Thanks!

[gyuris]

Related to 13860: These strings were: "OK", "Cancel", "Close"... Nothing more difficult. Therefore wondered I why must we translate whole Qt framework. But we did it.

At first sight on Wiki:

1. The link "check the list of languages that..." is broken. I can't edit "Official" pages, I can't fix it.
2. Why exists this very similar and official wiki page: https://wiki.scribus.net/canvas/Official:Translation_Update

To be continued...

[gyuris]

@luzpaz, this is my 1st proposal for guidelines for coordinators and translators. I know, linguistically isn't the prettiest. What do you think about?

Guidelines for language coordinators

• Create your team. We recommend using Transifex for teamwork. Teamwork is good for load balancing and pinpointing errors. Start blogging about Scribus translation, give news about your work on forums and social networking sites.
• Watch for join requests on Transifex. Accept or decline them.
• Don't let your volunteers wait. Volunteers are motivated by fast and visible results. If they don't see results or you don't address their work, most likely they will move on or become passive.
• Prevent intentional abuse by using Transifex's review system. The reviewed translations can't be modified by those who are designated in the role of 'Translator'. Basically translators can only add suggestions, beyond that they are limited.
• Check new contributions from your team on a regular basis. Use the review system. If you (or a user designated as a 'Reviewer') are OK with the translation then mark it as 'Reviewed'.
• Translate the Scribus terminology dictionary in the Transifex glossary this way translation strings will be uniform across the language.
• If you start from scratch: organize translation dates, times, essentially translation sprints for your team. It's always good for motivation and morale. Motivation and good morale produce results.
• Once you've reached 100%, please follow announcements about the Scribus project schedule on Transifex.

Guidelines for reviewers

• Check new contributions from your team on a regular basis. Use the review system. If you are OK with the translation then mark it as 'Reviewed'.
• Help the language 'Coordinator' when possible.

Guidelines for translators

• Look for the given language translator free software community and know the translation guidelines, practice, common mistakes, terminology.
• Use Scribus. If you don't use it, you don't know it, and you can't translate it.
• Get to know the DTP terms. Translations of commercial DTP software (eg. InDesign) provide much help in this. Use glossary in Transifex (see Transifex glossary).
• If you don't understand something and you can't translate, find the sting in the program user interface or in the source code.
• If you come across a Translation that is incorrect or not clear enough please open an issue for it using the builtin reporting

[luzpaz]

@gyuris looks great

[luzpaz]

@MrB74 Please take a look and if possible give the OK for us to add this to the official Translation page. Thanks

[luzpaz]

I updated the content in #5 (comment)
How does it look?

[gyuris]

@luzpaz, thanks! It's better!