I guess this means that the snapshot tarball http://git.savannah.gnu.org/cgit/denemo.git/snapshot/denemo-master.tar.gz will now contain an updated denemo.pot, with the xml labels available but also with additional strings that are not present in 1.0.4
On Mon, 2013-06-17 at 13:15 +0200, Éloi Rivard wrote: > The bug about untranslated strings is fixed in master and > stable-1.0.4 > > The bug about special unicode characters is due to libxml that escapes > special chars when saving a XML file, and intltool that seems to not > unescape those special chars when extracting translatable strings. I > look closer Depending on the outcome of this we have to decide what to do, let me know what you find can be done. Richard > > > > 2013/6/16 Éloi Rivard <[email protected]> > I look at this tonight or tomorrow > > Le 16 juin 2013 15:22, "Richard Shann" > <[email protected]> a écrit : > > On Sat, 2013-06-15 at 12:36 +0200, Federico Bruni > wrote: > > The command is there but it's not translated. I > don't know why... I've > > checked and I see that now the .gmo files are > generated during the > > build, so I don't have to do it manually as I used > to do. But still > > this menu item is not translated. > > > > This happens also with older strings which were > already translated > > (see example attached). > > Looking at the .png I think I see the pattern: the > built-in commands > have translated labels, but none of the scripted ones > do. > So this use of libintl to extract strings from xml is > not working to > provide the translations at run time it would seem. > Eloi, can we fix or revert? I don't think we can > release with > translation broken like this. > > Richard > > > > > > -- > Éloi Rivard - [email protected] > > « On perd plus à être indécis qu'à se tromper. » > _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
