On Tue, 2013-06-18 at 14:25 +0200, loi Rivard wrote: > I suppose you can just get the denemo.pot file from the stable-1.0.4 > branch and resend it to translationproject.org
We need to supply a URL for a tarball, I think it may cause confusion or worse if we provide the snapshot tarball (since it has different strings in it). So Jeremiah - can you generate a new tarball from the stable-1.0.4 branch I will then send the URL of that to translationproject.org. Richard > > > > 2013/6/18 Richard Shann <[email protected]> > On Tue, 2013-06-18 at 11:50 +0200, loi Rivard wrote: > > I updated denemo.pot in stable-1.0.4, special chars and the > typo are > > fixed. > > > > However I add to fix a bug in intltool because XML special > entities > > ( < > & … ) seemed to not be decoded by intltool-extract. I > sended a > > patch upstream : > https://bugs.launchpad.net/intltool/+bug/1191978 > > > > Also, maybe we can use the arrow unicode character "→" > instdead of > > "->"… > > > That will be nice, we need to check that they are in the > Denemo.ttf > font, most characters I have used are, but I put in some > and > < > characters in a script (cresc start and end markers) which > turned out to > be Arial and not in Denemo.ttf and I noticed that they didn't > display > properly on a windows box (because no Arial font on that box). > I still > have to fix this. > We can add extract glyphs to Denemo.ttf of course, but it > means doing > battle with fontforge :) > > Tell me what/if I need to do now to get the new denemo.pot > submitted. > > Richard > > > > > > > > > > > 2013/6/17 Federico Bruni <[email protected]> > > If you are going to submit a new pot have a look at > this typo: > > > > > > Prints accidentals accoring to a chosen style > > > > > > > > > > > > 2013/6/17 Richard Shann <[email protected]> > > > On Mon, 2013-06-17 at 17:38 +0200, loi > Rivard wrote: > > > Ok I found out what it is. Actually > unicode > > characters were escaped > > > because XML files were not encoded in > UTF-8. This is > > fixed now in > > > stable-1.0.4 and master, but XML files > still > > contains escaped > > > charcaters, and denemo.pot is still not > clean. I can > > update XML files > > > and regenerate denemo.pot tonight or > tomorrow. > > > > > > That's great news, I was fearing we had hit > a bug in > > libintl. Once > > denemo.pot is built how should we get it > submitted to > > translationproject.org (one way I can think > of is to > > ask Jeremiah to > > generate a new candidate tarball from > stable-1.0.4, > > but perhaps there is > > something simpler?) > > > > Richard > > > > > > > > > > > > > 2013/6/17 Richard Shann > <[email protected]> > > > 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 indcis qu' se > > tromper. > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > loi Rivard - [email protected] > > > > > > On perd plus tre indcis qu' se tromper. > > > > > > > > > > > > > > _______________________________________________ > > Denemo-devel mailing list > > [email protected] > > > https://lists.gnu.org/mailman/listinfo/denemo-devel > > > > > > > > > > > > > > -- > > > loi Rivard - [email protected] > > > > On perd plus tre indcis qu' se tromper. > > > > > > > > -- > loi Rivard - [email protected] > > On perd plus tre indcis qu' se tromper. > _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
