Virtaal 0.5.0 released

  • user warning: Table './translatewebsite/blog_friedel_captcha_sessions' is marked as crashed and should be repaired query: INSERT into blog_friedel_captcha_sessions (uid, sid, ip_address, timestamp, form_id, solution, status, attempts) VALUES (0, 'a56ukkiq1rl24c7si4rhtkhal2', '38.107.179.223', 1328777562, 'comment_form', '30cabcaf505a365cae54404c44125c61', 0, 0) in /var/www/vhosts/translate.org.za/httpdocs/blogs/drupal-common/sites/all/modules/captcha/captcha.inc on line 99.
  • user warning: Table './translatewebsite/blog_friedel_captcha_sessions' is marked as crashed and should be repaired query: UPDATE blog_friedel_captcha_sessions SET token='4fda689fc810d19480acf5845de3c976' WHERE csid=60454 in /var/www/vhosts/translate.org.za/httpdocs/blogs/drupal-common/sites/all/modules/captcha/captcha.module on line 216.
  • user warning: Table './translatewebsite/blog_friedel_captcha_sessions' is marked as crashed and should be repaired query: SELECT status FROM blog_friedel_captcha_sessions WHERE csid = 60454 in /var/www/vhosts/translate.org.za/httpdocs/blogs/drupal-common/sites/all/modules/captcha/captcha.inc on line 129.
  • user warning: Table './translatewebsite/blog_friedel_captcha_sessions' is marked as crashed and should be repaired query: SELECT status FROM blog_friedel_captcha_sessions WHERE csid = 60454 in /var/www/vhosts/translate.org.za/httpdocs/blogs/drupal-common/sites/all/modules/captcha/captcha.inc on line 129.
  • user warning: Table './translatewebsite/blog_friedel_captcha_sessions' is marked as crashed and should be repaired query: UPDATE blog_friedel_captcha_sessions SET timestamp=1328777562, solution='foo' WHERE csid=60454 in /var/www/vhosts/translate.org.za/httpdocs/blogs/drupal-common/sites/all/modules/captcha/captcha.inc on line 111.

Yesterday the Translate team released version 0.5.0 of Virtaal. Virtaal is a translation program with powerful features to help translators increase translation quality and have fun. It is available for download from SourceForge and soon your favourite Linux distro.

This release was meant to only add a few small features, but ended up with many other enhancements and nice bugfixes.

Highlighted improvements

  • Autoterm provides terminology files for Virtaal to download and use (even if the internet connection disappears later)
  • Web look-up allows you to look-up some selected text on websites
  • Highlighting of differences in non-100% TM matches
  • New plugins for machine translation with Google and Moses
  • Correctly support Open-Tran.eu for languages with regional modifiers
  • Web requests now accept compressed responses if the server offers it
  • Language identification for easier selection of language pairs
  • New autocorrect files for Luxembourgish and Croatian
  • Updated translations as well as these new ones: Sotho, Northern Sotho, Songhay, Korean, Ukrainian. Contact us to add yours!
  • Several bug fixes

Users of input methods such as ibus should see their issues fixed, but need GTK+ 2.18 (on Linux). Many thanks to Sankarshan Mukhopadhyay, Peng Huang, and Matthias Clasen for helping to resolve these issues. (bugs 1119, 1281)
This release will also benefit from some improvements in new releases of the Translate Toolkit, including support for OmegaT glossary files, and the experimental new PO parser which is much faster.

The Virtaal user manual is an excellent way to learn how Virtaal can help you to be productive.

Comments

Nested elements in XLIFF files

Hi,

from a quick test, the network crawling functionality in this new Virtaal seems to be very powerful.

However I still find Virtaal suboptimal for my use case (XLIFF intermediate format), if i can, my main concerns are:

  • The user interface is still a bit confused
  • Lack of support for nested Translation Units when editing an XLIFF file, see here to see what I am talking about

I find that transolution is very good for my very modest use.

just my 2c.

Regards,
Antonio

Re: Nested elements in XLIFF files

Hi Antonio

When you talk about "nested translation units", do you refer to the g tags in the file you point to? The current versions of Virtaal should support those well, so please say if you have any problems with that. Are you perhaps trying a version before version 0.4? That is when we got support for these inline elements in XLIFF. I just translated the file you linked to, and Virtaal is able to manipulate all the inline elements.

In terms of the user-interface, perhaps you want to send some of your ideas to the mailing list or explain somewhere what you find confusing. We would like to make it very accessible to a wide audience. Since Transolution has been a dead project for many years, I think Virtaal can replace it for you and give you many new features.

Hi Friedel, sorry for the

Hi Friedel,

sorry for the huge delay, just tried Virtaal 0.5.1.

Yes, I was referring to the g elements in english-english.xlf, when I try to translate this file I simply get those elements lost, should I re-enter them by hand in the translated string? Transolution is able to preserve them without retyping them manually.

About the UI usability, well, the only thing that is disturbing me is the auto-translation dropdown menu, how to close it after I chose the translation? Is the only way to hide it to click on another string to translate?

I'll try to find some time for proper bug reports, sorry for abusing this blog post.

Thanks,
Antonio.

XLIFF working well in Virtaal

Hi Antonio

Have you checked how placeables are handled in Virtaal? You should not be entering them by typing at all. See more about placeables here:
http://translate.sourceforge.net/wiki/virtaal/placeables

So just use Alt+Rigth to move to the correct one, and Alt+Down to insert it in your translation. The file you point to works well for me, so hopefully it is only a misunderstanding about how the placeables work. I'm sure you will like it - it makes me very productive during translation.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options