Localization server: translation and plurals UI

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
Gábor Hojtsy's picture

Only local images are allowed.Now I am up to implementing the translation and plural forms user interface. I'd welcome feedback on how would this work best. The idea is to provide a pager list with some number of strings on a page to translate. If the given string needs plural versions, then we display as many input fields as that language requires. Showing the plural formula for guidance in the localization server helper block. (It is advised to click through to the Flickr page, which shows notes on the image).

Making the plural formula comprehensible seems to be a tricky question. I made it wrap nicely in case it gets too long (as in the case of quite a few of the languages we have), but the complex looking expressions do not make it easy to understand. Also, I am still in high need of feedback on my language listing / plural forms cleanup post, but with help from Gerhard, I'll be able to mail the language team maintainers too.

Comments

Great!

brmassa's picture

Gábor,

absolutely great. i use to use rosetta on launchpad but it seems to be better! (im just looking at the image, no testing)

translation interfaces are usually a mess: too much information.

two things should be on the system interface:
1* easy and straight foward navigation: its irritating and confusing navigate thru many links to reach the desired page. "untranlated strings" link and a good search are crucial
2* bloated screen: too much information. as i just said, its looking great. but when we add "suggestions" from other users it might get too much (despite being a fundamental feature). maybe a jQuery/CSS to hide some stuff when the mouse is out would be useful on this.

regards,

massa

simplified UI

Gábor Hojtsy's picture

Yes, my main goal is to make it extremely simple: http://groups.drupal.org/node/5216 I had 'untranslated' and other status tabs planned for the translate page, and those might come back. Now the (on the picture collapsed) 'Filter' fieldset serves as a filter based on string status, software version and a generic search field. The status tabs might be simpler, but might not be more often used then the version of generic search filter, so I am still undecided.

An AJAXy interface to pull detailed information from the server is a good idea to go, I definitely would not like to display lots of information to distract people from translating.

Translations

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: