From ttrinks at redhat.com Mon Mar 7 06:31:44 2016 From: ttrinks at redhat.com (ttrinks at redhat.com) Date: Mon, 7 Mar 2016 06:31:44 +0000 (UTC) Subject: [zanata-users] Zanata on translate.zanata.org Scheduled Maintenance | 08-Mar-2016 02:00:00 UTC Message-ID: 7ae2794b-7cdc-4dfe-b18a-47fb180af425@support.engineering.redhat.com --------------------------------------------------------- ***// SCHEDULED MAINTENANCE REPORT //*** HostName: translate.zanata.org Priority: Medium Scheduled Date: 08-Mar-2016 02:00:00 UTC Estimated Time Required: 30 minutes Performed By: ttrinks People/Groups Impacted: Users of translate.zanata.org Services/Sites Impacted: Zanata on translate.zanata.org Description: The root context on translate.zanata.org will be made consistent with the other Zanata services. Impact: The translation framework Zanata will not be available during outage. Sign Off: Marc Raaz ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 -------------- next part -------------- A non-text attachment was scrubbed... Name: maintenance.ics Type: text/calendar Size: 1690 bytes Desc: not available URL: From dchen at redhat.com Mon Mar 7 08:53:25 2016 From: dchen at redhat.com (Ding Yi Chen) Date: Mon, 7 Mar 2016 03:53:25 -0500 (EST) Subject: [zanata-users] https://translate.zanata.org/zanata/ will becomes https://translate.zanata.org/ In-Reply-To: <1171475793.34000346.1457339716161.JavaMail.zimbra@redhat.com> Message-ID: <1894318502.34003947.1457340805669.JavaMail.zimbra@redhat.com> After 3:00 UTC, 08 Mar 2016, the URL of our generic open source server https://translate.zanata.org/zanata/ will be shortened as https://translate.zanata.org/ So all of our public servers have consistent URL format. It will be not only easier for users to input, but also for system administrators to manage. Possible impact: Both https://translate.zanata.org/zanata/ and https://translate.zanata.org/ should be working for both WebUI and command line client users. However, for command line clients, URL start with http:// will NOT be automatically redirected. To fixed it, you need to check the URL in both zanata.xml and $HOME/.config/zanata.xml Both URL need to be started as "https://...", NOT "http://...". Should you encounter any problem, please don't hesitate to leave your feedback in https://zanata.atlassian.net/ Regards, -- Ding-Yi Chen Software Engineer Globalization Group DID: +61 7 3514 8239 Email: dchen at redhat.com Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com Red Hat, Inc. Facebook: Red Hat APAC | Red Hat Japan | Red Hat Korea | JBoss APAC Twitter: Red Hat APAC | Red Hat ANZ LinkedIn: Red Hat APAC | JBoss APAC From ttrinks at redhat.com Tue Mar 8 03:41:52 2016 From: ttrinks at redhat.com (ttrinks at redhat.com) Date: Tue, 8 Mar 2016 03:41:52 +0000 (UTC) Subject: [zanata-users] Zanata on translate.zanata.org Scheduled Maintenance | 08-Mar-2016 02:00:00 UTC In-Reply-To: 7ae2794b-7cdc-4dfe-b18a-47fb180af425@support.engineering.redhat.com References: 7ae2794b-7cdc-4dfe-b18a-47fb180af425@support.engineering.redhat.com Message-ID: <203051908.1492.1457408511994.JavaMail.jboss@charnet.host.prod.eng.rdu2.redhat.com> COMPLETED COMMENT ADDED BY ttrinks at 08-Mar-2016 03:41:51 UTC Outage complete. Changes have successfully been implemented. Please report any issues via eng-ops at redhat.com. --------------------------------------------------------- ***// SCHEDULED MAINTENANCE REPORT //*** HostName: translate.zanata.org Priority: Medium Scheduled Date: 08-Mar-2016 02:00:00 UTC Estimated Time Required: 30 minutes Performed By: ttrinks People/Groups Impacted: Users of translate.zanata.org Services/Sites Impacted: Zanata on translate.zanata.org Description: The root context on translate.zanata.org will be made consistent with the other Zanata services. Impact: The translation framework Zanata will not be available during outage. Sign Off: Marc Raaz ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 From dchen at redhat.com Tue Mar 8 05:12:24 2016 From: dchen at redhat.com (Ding Yi Chen) Date: Tue, 8 Mar 2016 00:12:24 -0500 (EST) Subject: [zanata-users] translate.zanata.org/zanata/ has shorten to translate.zanata.org In-Reply-To: <203051908.1492.1457408511994.JavaMail.jboss@charnet.host.prod.eng.rdu2.redhat.com> References: <7ae2794b-7cdc-4dfe-b18a-47fb180af425@support.engineering.redhat.com> <203051908.1492.1457408511994.JavaMail.jboss@charnet.host.prod.eng.rdu2.redhat.com> Message-ID: <147362996.34358781.1457413944783.JavaMail.zimbra@redhat.com> Now https://translate.zanata.org/zanata/ has been shorten to https://translate.zanata.org/. Thanks Timo Trinks for handling the change. For backward compatibility, you can access Zanata through either https://translate.zanata.org/zanata/ or https://translate.zanata.org/ Both our Python client and Java client can work with both URLs as well. Chester Cheng has kindly mentioned following tip: Edit your ${HOME}/.config/zanata.ini and duplicate the translate.zanata.org section like following: translateZanata.url = https://translate.zanata.org/ translateZanata.username = translateZanata.key = translateZanata1.url = https://translate.zanata.org/zanata/ translateZanata1.username = translateZanata1.key = It works with both old and new projects, error message like "Username must be specified" will no longer disturb you. Regards, -- Ding-Yi Chen Software Engineer Globalization Group DID: +61 7 3514 8239 Email: dchen at redhat.com Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com Red Hat, Inc. Facebook: Red Hat APAC | Red Hat Japan | Red Hat Korea | JBoss APAC Twitter: Red Hat APAC | Red Hat ANZ LinkedIn: Red Hat APAC | JBoss APAC From pravin.d.s at gmail.com Wed Mar 9 10:16:57 2016 From: pravin.d.s at gmail.com (pravin.d.s at gmail.com) Date: Wed, 9 Mar 2016 15:46:57 +0530 Subject: [zanata-users] Zanata improvements, L10n engagement and testing In-Reply-To: References: Message-ID: Added Zanata users list as well.. On 9 March 2016 at 15:35, Baadur Jobava wrote: > 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 > there. > > 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 > important terms. > > 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 > locale-specific. > > more nice things to have: > 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 > > 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) > - 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 > 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. > > That is all, thanks! > > Jobava > > > _______________________________________________ > g11n mailing list > g11n at lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/g11n at lists.fedoraproject.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aeng at redhat.com Wed Mar 9 21:38:11 2016 From: aeng at redhat.com (Alex Eng) Date: Thu, 10 Mar 2016 07:38:11 +1000 Subject: [zanata-users] Zanata improvements, L10n engagement and testing In-Reply-To: References: Message-ID: 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. Zanata do have that feature. http://docs.zanata.org/en/release/user-guide/editor/translation-history/ 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. Zanata do have that feature. http://docs.zanata.org/en/release/user-guide/translation-reuse/copy-version/ > 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. --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 Mobile: +614 2335 3457 Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com On Wed, Mar 9, 2016 at 8:05 PM, Baadur Jobava wrote: > 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 > there. > > 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 > important terms. > > 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 > locale-specific. > > more nice things to have: > 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 > > 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) > - 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 > 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. > > That is all, thanks! > > Jobava > > > _______________________________________________ > g11n mailing list > g11n at lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/g11n at lists.fedoraproject.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: