Deckard: a web based Glade Runner

l10n
#1

Hi,

there exists a web-based tool for display of translated glade dialogs:
https://launchpad.net/deckard
gnome dialogs: http://deckard.malizor.org/

It would be really great to have something like that for LO - it would simplify our work and simultaneously improve the quality of translations.

On the launchpad page, it says: "In the long run, it would be cool to have distinct instances for distinct projects like Xfce or LibreOffice."

As I understand it, the runner takes translation from a po file in a repository, converts it and displays the dialog. So, to see the result, it is necessary to upload po file to the repository.

Can we talk to Deckard developers regarding that?

Milos

#2

Added Nicolas, who is the developer.

Top-posted to keep content.

#3

Added Nicolas, who is the developer.

Top-posted to keep content.

Hi,

there exists a web-based tool for display of translated glade dialogs:
https://launchpad.net/deckard
gnome dialogs: http://deckard.malizor.org/

It would be really great to have something like that for LO - it would
simplify our work and simultaneously improve the quality of translations.

On the launchpad page, it says: "In the long run, it would be cool to have
distinct instances for distinct projects like Xfce or LibreOffice."

As I understand it, the runner takes translation from a po file in a
repository, converts it and displays the dialog. So, to see the result, it
is necessary to upload po file to the repository.

Can we talk to Deckard developers regarding that?

Milos

--
-----------------------------------------------------------------------------
Milos Sramek
Gregor Mendel Institute of Molecular Plant Biology,
Dr. Bohr-Gasse 3, 1030 Vienna, Austria
TEL: +43 1 79044 9810 EMAIL: Milos.Sramek@oeaw.ac.at
-----------------------------------------------------------------------------

--
sankarshan mukhopadhyay
<https://twitter.com/#!/sankarshan>

As far as I know the tool is based on GTK3+, so at least we need to wait for the port to .ui dialog system. Nevertheless, even that couldn't mean it'd support LO, but I'm not sure.

+dev list and Caolán McNamara.

Probably Caolán who's converting the dialogs may tell us more.

And yes, it's really really useful tool for localization QA, especially for such huge project as LO. So I'm looking forward to that great feature as well.

#4

Hi,

I would suggest inclusion into open-tran.eu site, which already supports
search in many open souce projects localizations, and even old translations
from OpenOffice.org.

www.open-tran.eu

Lp, m.

#5

Looks great. I think it should basically "just work" for LibreOffice and
the 250+ new .ui elements. Our .uis pretend to be gtk3 ones, with a
handful of custom widgets, mostly previews. We have a glade catalog for
the custom ones to provide stubs for glade. So, what does deckard do
there, does it load the .ui with standard gtk3 code, i.e. expects all
the widgets to be instantiatable, or does it load it the glade way, i.e.
can reuse a glade catalog to handle those ?

There might also be a little bit of tweaking required to stitch the .po
and .ui together because we're not (currently) using gettext natively in
LibreOffice but are using it as an intermediate format so it probably
wouldn't work to just throw a libreoffice .po with translations for a
dialog at the normal gtk3 gettext loader and get it to do the right
thing.

C.

#6

Hi everyone,

On the launchpad page, it says: "In the long run, it would be cool to have
distinct instances for distinct projects like Xfce or LibreOffice."

Yes, I though Deckard could be useful for LO when I read the 4.0
changelog about the new .uis.

As I understand it, the runner takes translation from a po file in a
repository, converts it and displays the dialog. So, to see the result, it
is necessary to upload po file to the repository.

Yes, the runner basically needs a folder containing a .ui and a .mo file.

The layout expected by Deckard is documented in the README file:
http://bazaar.launchpad.net/~malizor/deckard/trunk/view/head:/README#L90

I wrote a script that create such a layout from Gnome git repositories
(which run once a day), so you may just want to write a similar script
for LO.
In fact I was planning to write one at some point, but it would be much
easier for someone familiar with the LO organisation.

Looks great. I think it should basically "just work" for LibreOffice and
the 250+ new .ui elements. Our .uis pretend to be gtk3 ones, with a
handful of custom widgets, mostly previews. We have a glade catalog for
the custom ones to provide stubs for glade. So, what does deckard do
there, does it load the .ui with standard gtk3 code, i.e. expects all
the widgets to be instantiatable, or does it load it the glade way, i.e.
can reuse a glade catalog to handle those ?

It instantiates all widgets. If it encounters an unknown one, it tries
to replace it with a placeholder.
All this magic happens in the "gladerunner.py" file (you can download it
and easily experiment with it in a standalone way).

It may be possible to make it work with a glade catalog, I will try to
have a look at it (though I don't have much free time currently).

There might also be a little bit of tweaking required to stitch the .po
and .ui together because we're not (currently) using gettext natively in
LibreOffice but are using it as an intermediate format so it probably
wouldn't work to just throw a libreoffice .po with translations for a
dialog at the normal gtk3 gettext loader and get it to do the right
thing.

It is true that Deckard is a bit Gnome centric for now, so any
suggestion or patch (better :p) to make Deckard more suitable for other
projects/infrastructures would be very much welcomed.

Cheers,
Nicolas