With this major glossary interface update, users with glossarist permission
can not only see the each term, but also edit them online.
Project Creation Permission
A popular request, was to grant project creation permissions to a specific set of users. This allows Zanata admins more control over the projects that can be created on their instance.
This has to be enabled by admins and will not affect any of the Zanata teams currently maintained instances.
Project Team Management
Project maintainers can now manage their own team of translators.
If you have your own trusted translators or reviewers, they no longer need to join a global language team.
Go to the People tab in project view, click Add Someone. On top of maintainers, you can now add translators, reviewers or translation maintainers (who can also add translator and reviewers).
Search User in Main Search Bar
The main search bar seen on the top of the page can now be used to search users.
When you find the user you are looking for , you will be able to see a few more details and their recent translation/revieer contributions.
More Feature Details
1213630 - Webhook header needs to include cryptographic signature in header for identification
1214502 - RFE: Grant project creation permission to certain sets of users
1224912 - Filter “Last modified by translators other than <user>”
1233524 - Update project search page to include user
From October 7th to October 28th 2015 we put out a survey to the Fedora community and received over 40 responses.
First, we’d like to say thank you to everyone who took the time to complete the survey. We have lots of great feedback to help us understand the needs of the Fedora l10n community and improve Zanata to meet these needs.
In this post I’ll cover some overall statistics around the multiple choice questions and then summarise some of the more specific feedback and how it affects Zanata.
The migration from Transifex to Zanata
Mailing lists were by far (61%) the most common place you heard about the Migration to Zanata, with the Magazine (15%) and Wiki (10%) coming distant runners-up. It seems like the mailing lists remain the best place to get news out to the l10n team.
93% of you thought the migration to Zanata went either very well (29%), well (17%), or OK (46%). There is still room to improve here and I’ll cover some specific feedback later. 91% were either very happy, happy or neutral with responses to your queries and doubts. To the 4 of you that were not satisfied, we’d love to hear from you about what went wrong, if we haven’t already.
Some more specific feedback we received about the Migration was:
Some would have liked a copy of the Transifex history for reference
Some projects were not moved to Zanata. I’m not sure of the reason for this.
More updates on the status of each project’s move to Zanata and when it was ready for translation
The Zanata team has taken this feedback on board and will use it to improve communications about the maintenance and operations of the Zanata instance.
We are happy to hear that over 50% of you have used Zanata more than 10 times (56%). And others are not too far behind. The majority (86%) of your experiences with Zanata have been either positive or OK. With 6 of you having negative experiences. This is still something we would love to improve, and we are grateful to have received lots of specific feedback to help us do just that.
We’ve sorted the feedback to give us some clarity about where we need to focus. I’ll start with the most common feedback we received.
Language Teams / Project Management
By far the most common feedback we received was related to better language team/project management features. In this category we included:
Language-specific project list
These features are one of the major aspects of Zanata that we want to improve and it is great to have the Fedora community confirm their importance.
Team activity feedback is mainly related to being able to see what other members of your language team are working on, and helping each of you decide where your effort is best applied.
Statistics should allow users to see who is contributing to the team and in what capacity. There should be more statistics available for projects, teams and groups.
Project status features could relate to a specific “project” in Zanata or potentially groups. These would include things like minimum translation acceptance percentage & project/team/group milestones.
Language-specific project list was requested a lot, and at least easily seeing your own language without having to select it each time. We can achieve part of this with groups, but it is still less than ideal and still requires you to find your language. We are exploring some solutions for this problem, and will reach out when we have some concrete proposals.
Translation memory was noted as the most critical feature needed. Translation memory is something we still have a focus on and we hope to improve it in some upcoming releases. You can keep track of any translation memory related issues on our JIRA.
Something that we have been planning and discussing for a while is how best to implement notifications. We’ve known they are needed and hopefully the extra feedback we’ve received here will give us the push to start working on them.
To get started as a translator in the Fedora Zanata, we know there are quite a few steps involved. This is made longer again if you don’t already have a Fedora account. We have a change in the next version of Zanata that will make joining a language team easier for both translators and team co-ordinators.
In the future, we may also look into simplifying account activations as well. Other than this, a lot of what is involved may come down to how the Fedora community runs. This is something we can work on as a community to improve.
Fast, Reliable Servers
The problems that were identified are login failures, short authentication expiry and general slowness.
Login failures have been tricky to work out the source, as the only way to use the Fedora Zanata is through Fedora authentication. We will continue to look into this and we hope it will only get better.
Short authentication expiry has been a problem for a while and we will improve this in the next version of Zanata.
We are currently doing some fairly large changes under the hood of Zanata that should make a difference in an upcoming release.
The download size, installation process and general experience of using the command line client is something that needs to improve. There has been some more work on the Python client recently, and we hope to bring this back to feature parity with the Java client.
We recently make the client available to install with 0install which simplifies the install process and shrinks the download size.
At the same time we are still adding new options to the CLI, so if there is something specific you would like to see, we’d love more feedback.
Right to Left Language Support
This isn’t really excusable. We will have this implemented once we have a beta release of the new editor and then we will integrate it into the rest of the interface.
Clearer handling of versions
Translation context enhancements
Multiple translation file downloads
Make comparing translations easier
Current editor needs improvement on small screens (This works in the alpha editor)
Better special character handling in editor
Better plural support
A way to translate, download, and upload entire groups, not just by project
Possibly regular meetings with Zanata team to handle community questions (Monthly/Bi-monthly)
Update/Newsletter style email to community about changes, improvements & fixes
Better status updates on existing bugs/feedback in JIRA
What is working
It was nice to get some positive feedback too. Here is some of the things you liked about Zanata:
This was the most common feedback we received. There are some that disagree with this too, but the good news is, we hope the only change to this is to improve it. So we only plan on making the UI more friendly, clean, and usable.
This was expected, especially from a great open source community like Fedora. Thankfully, this won’t be changing.
This is an area we have always focused on and worked closely with translators to improve. Filtering, project-wide search and replace, and collaborative editing were some specifically mentioned features. There was some positive feedback about the new alpha editor too. If you want to see where the editor in Zanata is heading, have a look for yourself. It doesn’t have all the features yet, but the more feedback the better.
Other positive feedback
Access to TM
Versions/branches in project
Credit references are updated when changing profile info
If you have anything you think we missed, you always report an issue or ask a question over on our JIRA. You can find all our existing issues there too. If you see an existing issue you think needs more attention, vote it up or add any other comments you have.
We’d like to thank you all for helping us improve Zanata and therefore the Fedora translation community. As you can see we’ve taken on all this feedback and are working through it as best we can.
We look forward to working closely with you all in the future.
With over 500 bugs, feature requests and other general feedback, it’s been a challenge to make sure we’re keeping track of everything in Bugzilla, even more so for members of the community that were looking at Zanata for the first time.
It is for this reason (and many others) that we have now moved all our bugs/feedback to JIRA.
We are hoping this will minimise planning time, but also give us greater awareness of our communities issues. We also hope this will give community members greater insight into what we are currently working on and what our future plans may hold.
Here are some of the benefits we hope the community gets out of this move:
Easier to find information on current bugs or feedback and provide their own perspective or experiences
The ability to vote on bugs or feedback that is important to you, which will allow us to see the things that matter most to the community
The ability to see our current sprint activity and backlog priorities (and hopefully in the future, a basic roadmap for upcoming releases)
An easier way to log bugs/feedback from within Zanata itself (Hopefully in an upcoming release)
A better place to ask questions than IRC, where you can ask any time of day and answers will be persistent and searchable by other community members
We've received some great feedback in the previous release that has helped us create or improve this releases features. We hope you find them useful. As always, we'd love to hear how these features affect you and if there is anything we can do better.
You can now upload multiple source documents at once through the web interface.
1066694 - As a project maintainer I would like to upload multiple source files simultaneously
Guided Project Set-up for CLI Users
Command line user can now setup their projects from the CLI quickly with a new command, zanata-cli init. Check out the guide on initialising a project and start saving time on the command line.
1110627 - As a command line user I would like to be guided in setting up a project
Redesigned Account Merge
If you’ve ever had problems with multiple accounts you may have lost track of (this can happen if an extra open id account is not attached properly to your primary account), it should now be easier to merge your accounts.
Project search has now moved into the navigation bar. This should provide a more convenient and consistent location for searching for projects across Zanata.
Adding to this move, is the addition of auto-complete to the search. You can now see results after just a few letters have been typed and navigate directly to that project by hitting enter/return or clicking directly on that result. The last item will give you access to the traditional search results page.
We hope to expand on the features of this search in the future.
New Support for HTML and roff
Translation of .html and .htm files are now supported. This is possible from both the CLI client and the web interface.
Note: Ensure you are using the project type “File” to allow translation of .html and .htm files.
Generally used for UNIX manual pages, roff pages can now be translated and output by the CLI Client. Users who wish to push .roff file can use a command hook to invoke external tool (po4a) before push to convert .roff into .pot. Invoke po4a again after pull to convert translated .po into .roff.
1067253 - RFE:/Tech Debt - Propagate translation done by upload and copyTrans to editor
Prior to this implementation, editor will not receive translation updates done by CopyTrans or REST, i.e. upload translation file though web UI or push from client. Now translation done by any of the above will be broadcast to any open editors. This includes latest translation and statistics.
1002378 - RFE: Introduce a modular translation structure, and gwt generate the *Messages.properties files
Now Zanata editor is ready to be translated. See [[Localize Zanata]] for detail.
Now requires (i.e. is tested on) JBoss EAP 6.2.0 instead of 6.1.1
981071 - Register account still available when logged in
1023227 - Add language member request email contains string jsf.email.joinrequest.RoleRequested
1035057 - Group “Add Language” field should be limited to something sensible
1037925 - Search Projects field not character limited
1039776 - Email template link to zanata log broken
Very soon, translate.zanata.org will be upgraded to version 3. Zanata version 3 adds some major features and improvements over the currently deployed version 2.2.2.
Here is a preview of what is on the way in the new version:
The most immediately noticeable improvement is the new visual style: we have changed our logo and colour scheme to improve readability of the site, and have started improvements to the layout to make Zanata easier to navigate.
Use the menu at the top right to get back to the user dashboard (see below), change your settings, or log out. The rest of the menus and screens should already be familiar.
Finding the content you care about is now much faster with the addition of the user dashboard. The dashboard shows your projects and shows your recent activity, so you can get straight back to anything you have been recently working on. For more, see User Dashboard.
For projects that need an extra level of checking, we have added a translation review workflow. Review can be turned on for a project, allowing reviewers (nominated by translation team coordinators) to mark translated strings as approved, or provide a message indicating what work is still required. See Review Workflow for more information.
Translation Memory Import and Export
It is now possible to export the translation memory for a project or project-version. This will produce a file in TMX format. TMX generated in other systems can be imported to Zanata and will show translation memory matches in the editor. TMX import is currently restricted to administrators since it affects all users, so use the Contact Admin link in the ‘Help’ section
Version 3 comes with more changes the help to improve performance and stability, such as updating to a faster server platform. For more information, see the Zanata Changelog
The spiffy new version of the
Translation Management system is now ready and has been released.
Besides a new look with Zanata’s purple theme, this version packs in a punch with loads of exciting new features in the translation editor interface and several important bug fixes. Translators can now use status filters on the strings
, run validation checks
and get more out of the
improved Translation Memory system
with more efficient
. Package Maintainers can now choose to deprecate projects and iterations that are no longer relevant. Significant improvements have been made to the Zanata Python and Maven clients. The latter now allows projects with multiple modules to share a configuration file. A complete list of the new features and known issues in this release is available in the
The two Zanata instances have also been upgraded to the new version.
A list of all the projects hosted on these two instances can be seen by clicking on Project
Translators and other users can subscribe to the
Zanata-Users mailing list
to communicate with the team and also visit the Zanata Home page for updated information. Bugs can be filed through the Red Hat Bugzilla and if you think that you’d like to help fix it as well feel free to
Project Maintainers have the choice to use two different clients for Zanata – the python client and the maven client, to access the project contents. This video will help with quickly setting up the configuration in the Zanata Python client.