desktop-packages team mailing list archive

[Launchpad Bug Tracker <953342@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package intltool - 0.51.0-1

---------------
intltool (0.51.0-1) experimental; urgency=medium


  [ Rodney Dawes ]
  * New upstream release.
    - Support Qt Designer UI files (LP: #953342)
    - Do not include full path to source files in template. (LP: #1316777)
    - Support spaces around '=' in key files. (LP: #1395561)
    - Support single quotes in intltool-extract regex. (LP: #1034153)
  * debian/watch:
    - Fix search pattern URL to be https.
  * debian/control.in:
    - Bump standards version.

  [ Iain Lane ]
  * debian/control{,.in}: Update for experimental

 -- Rodney Dawes <rodney.dawes@xxxxxxxxxx>  Mon, 16 Mar 2015 18:17:42
+0000

** Changed in: intltool (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to intltool in Ubuntu.
https://bugs.launchpad.net/bugs/953342

Title:
  [ffe] Add support for Qt Designer UI files

Status in Internationalization Tool Collection:
  Fix Released
Status in intltool package in Ubuntu:
  Fix Released

Bug description:
  Qt Designer files are XML files that describe the UI of a Qt
  application, and are the Glade .ui file equivalent in the Qt world.

  Their format definition can be found here:

  - http://qt-project.org/doc/designer-ui-file-format.html

  While many Qt projects use Qt's own i18n/l10n framework, others rely
  on gettext. Some examples are core Ubuntu applications such as the
  Ubuntu One client and Checkbox, which have started to migrate to Qt-
  based user interfaces while overriding Qt's i18n system and using
  gettext instead.

  These cases need a way to extract translatable messages from Qt's .ui
  files, merge the translations in .pot files and thus integrate with
  the gettext workflow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intltool/+bug/953342/+subscriptions