Need help to make sure package priority list  is ready to receive
translation during vFAD. I am myself not very clear on what to do in
this activity but this is basically to make sure contributors will have
minimal problems during translations vFAD, so good if someone can check
it prior vFAD days.
Alex i have added your name at  being only Zanata developer ;)
Will be nice if few more members also join this activity :)
I would like to detail some suggestions I had for Zanata improvements,
engagement for translators and testing.
1. Zanata is missing terminology control. This is a feature already in
Transifex, Pootle and present in most proprietary translation tools out
Terminology control means "glossary", but also aspects of something people
call "controlled language".
In Transifex, each project has an attached terminology, with translation
reviewers being able to update the terminology. My workflow there is a
little clunky, but workable:
I keep at the same time two tabs open, one with Terminology definitions,
where I can add or adjust terms, and a second tab with the translation
interface itself. As I translate, especially a new project, I add new terms
to the list. (An improvement may be to be able to adjust terminology and
translation from the same window)
Setting terminology as translation progresses helps maintain consistency
even if there is just one translator working on it. Unlike the automated
translation memory, terminology provides 'intent' and highlights the
As people translate, the terminology words get highlighted, with
suggestions for each one. In Transifex there is inline highlighting
(underlining) and a contextual bubble appears when you hover across the
highlighted term. In Pootle the terminology terms appear to the side in a
separate rectangle, along with their recommended translation and comments.
Other than simply a glossary, terminology control should also highlight
'terminology violations' and have a filter to select only for these strings.
As people add new terms to the terminology, the English variants get all
added to a global list, so if a Japanese reviewer adds a new term, that one
is also available to the French locale (and every other one) -- a good
feature of Transifex. Now, a tool like Pootle only has locale-specific
terms list, so each locale has to figure out their own terminology list. I
prefer the Transifex way.
Something that doesn't exist, but may help: 'hard' and 'soft' terminology.
Hard terms may be those specific to the application or technical terms with
strict interpretation, while 'soft' ones may be regular language which
needs to be kept consistent, but not critical or with a special meaning for
that project. Hard terms may be global, while soft ones may be
more nice things to have:
2. Language-specific dashboards for Zanata
for each language, from the Language page (eg.
- latest changed projects, number of strings for each project and who did
- a link to a diff-style list with 'before', 'after', 'translator' for the
last changed strings
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)
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)
- 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
6. Automatic UI testing
I was wondering if it were possible to set up some kind of automation that
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.
That is all, thanks!
We had good meeting today. Following are minutes.
#fedora-meeting: g11n (l10n focused)
Meeting started by pravins at 08:30:06 UTC. The full logs are available
* agenda and roll call (pravins, 08:30:13)
* LINK: https://fedoraproject.org/wiki/I18N/Meetings/2016-03-09
* Upcoming schedule (pravins, 08:31:35)
* LINK: https://fedoraproject.org/wiki/Releases/24/Schedule
* 2016-03-22 Alpha Release (pravins, 08:32:13)
* 2016-04-05 Software Translation Deadline (pravins, 08:32:13)
* 2016-04-19 Beta Freeze (*) (pravins, 08:32:13)
* 2016-04-19 Change Checkpoint: 100% Code Complete Deadline
* 2016-05-03 Beta Release (pravins, 08:32:13)
* 2016-05-24 Final Freeze (*) (pravins, 08:32:14)
* 2016-06-07 Fedora 24 Final Release (GA) (pravins, 08:32:16)
* Software String Freeze happened on 8th march. (pravins, 08:34:48)
* Fedor 24 L10N test day planning (pravins, 08:34:55)
* LINK: https://fedorahosted.org/G11N/ticket/18 (pravins, 08:35:01)
* LINK: https://fedorahosted.org/fedora-qa/ticket/480 (pravins,
* Jobava has some suggestions on "mission functionality is terminology
control" in Zanata. Later follow up with aeng and team. (pravins,
* vFAD for Translations (pravins, 08:41:57)
* LINK: https://fedorahosted.org/G11N/ticket/5 (pravins, 08:41:57)
* LINK: http://fedoraproject.org/wiki/L10N_GUI (pravins, 08:51:21)
* LINK: http://fedoraproject.org/wiki/Docs_Project_guides_table
* Docs Schedule might not fit with GUI Translation vFAD. (pravins,
* difficult to get vFAD translation in L10N test day image. Since
package owners might not build packages before Translation deadline.
* IDEA: execute vFAD from 21-27 but translation may not get build by
package owners for L10N test day. (pravins, 09:19:25)
* Next meeting time (pravins, 09:22:36)
* Jobava will help to chair next G11N meeting. (pravins, 09:26:01)
* Open Floor (pravins, 09:26:22)
Meeting ended at 09:31:03 UTC.
Action Items, by person
People Present (lines said)
* pravins (118)
* noriko (26)
* jibecfed (23)
* Jobava (20)
* juhp (12)
* zodbot (9)
* fale (9)
* paragan (5)
* mfabian (1)
* tagoh_ (1)
* epico (1)
* fujiwarat (1)
* suanand (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
I am interested in [Community Activity] Fedora 24 Translation Test Day, please add me, thanks
Name: Song Liu
IRC. #ent #eng-china #qa
Glibc locale subpackaging  is critical change for Fedora 24. In last
meeting Jens suggested an idea of having dedicated test day for this change.
Just continuing discussion on that.
1. Change is not available in Fedora 24
2. Other missing things?
Test cases availabiltiy
What is appropriate date? Alpha freeze??
Creating test day page.
One important topic we are discussing from DevConf is vFAD. We have very
less time around, say 2/3 weeks to get things done for vFAD. (Translation
freeze 5th April 2015)
I have created initial Wiki page for vFAD, few more edits from Ani. 
This page is mostly from planning side. Feel free to correct/extend it with
As you can see from Wiki, we have different tasks and different
expertise contribution is required. Please add your name in part you can
help. Then later we can discuss in small group how to execute it.
If we can get small groups by Friday. Next week we can start working on
completing prerequisite list.
Lets collaborate and make it big success :)