I am not sure how any of this stuff works. :( Jeremiah
Sent from my Samsung smartphone on AT&T Richard Shann <[email protected]> wrote: >Jeremiah, > >I generated an en_GB.po file using poedit, and managed to build it so >the translations are working, including the non-ascii characters. >I am not sure how the corresponding en_GB.mo file was generated (by >Denemo's make system or by poedit?), but I had to rename it en_GB.gmo >for Denemo's install to find it (so I suspect poedit created it). >Anyway, after building this, the translated strings appear when it is >run. >When you are able to get to it, can you let me know if other >translations are working, or whether we have to tell gettext to use the >utf8 codeset? I am still far from clear how you set about doing a >translation. >I'll work on making the built-ins generate translatable labels now (I >thing they did this until the introduction of the non-ascii musical >symbols). > >Richard > > > >On Mon, 2012-07-16 at 11:32 +0100, Richard Shann wrote: >> I have been looking into the problem of non-ascii chars (the musical >> symbols) in our labels for translation. It seems the with the option >> --from-code=utf8 and with choosing UTF-8 as the charset for translations >> we should be able to use these without problem. >> But I haven't figured out the answer to my question (below)... >> On Sun, 2012-07-15 at 18:01 +0100, Richard Shann wrote: >> > Jeremiah - I have been looking at Poedit for creating a British English >> > translation of Denemo. It is able to generate a new catalog but warns >> > that many projects generate their own via the make system. Do you happen >> > to know if Denemo does this? >> > >> > Richard >> >> Richard >> > > > >_______________________________________________ >Denemo-devel mailing list >[email protected] >https://lists.gnu.org/mailman/listinfo/denemo-devel _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
