Hi,
1. Zanata is missing terminology control. This is a feature already in Transifex, Pootle and present in most proprietary translation tools out there.
While Zanata does have glossary support that apply across all projects, I do agree we need some sort of granularity and different level of glossary. (please feel free to file a feedback for us @
zanata.atlassian.net)
Whether its project based, individual based, group based, organisational based.
With what you described on your workflow, in Zanata, you can actually see matching glossary term in the editor itself while translating.
And if you prefer to have editing feature, you can open up the glossary screen in new tab as you had done in your workflow and edit it while translating.
2. Language-specific dashboards for Zanata
for each language, from the Language page (eg. https://fedora.zanata.org/language/view/fr ):
- latest changed projects, number of strings for each project and who did them
- a link to a diff-style list with 'before', 'after', 'translator' for the last changed strings
Currently all these information is on individual's dashboard which we find it is more relevant rather than putting in language screen.
I do think we can improve the dashboard by having more information related to your role (e.g language coordinator, project maintainer) or even just have more information of your language team.
That would help a user to see all important information in a single screen.
3. Diff tools for Zanata: a way to inspect the state of the strings in 'before' and 'after' style picking two arbitrary dates, with github-like diff coloring for the changes and authors for each string (or substring) changed.
4. Feature improvement: an option to automatically import strings to a branch from another branch (for example, from 'development' to F24) for identical strings. Maybe an option to import identical translated strings from all other projects.
5. L10n engagement:
- mass-email people who contributed to Fedora from Transifex who have not yet registered for Zanata (not yet joined a language group)
I think this should be handled by l10n coordinator or the language coordinator as Zanata has no information on the users before they are registered.
If you're fedora translator, translator's mailing list should be the default tool used for any sort of communication.
- mass-email translation contributors, even those not yet on the mailing lists about the Fedora schedule and deadlines and maybe another mail about vFAD or translation test day
Yes, I agree it is nice to have Zanata implement mass emailing to language contributors. But as workaround for now, mailing list should be sufficient for these type of communication.
6. Automatic UI testing
I was wondering if it were possible to set up some kind of automation that can:
Walk the UI of a given project and take screenshots progressively of the interface, menus, submenus, windows and contextuals. I understand Gnome already has a web tool where you can manually inspect the menus, but something that generates a flat list of screenshots can help people go through the UI in a faster way. This would be toolkit-specific, but may be worth investigating if possible.
I believe during QA, there a such infrastructure built and used for test. But need to check with QA team for confirmation.