Re: [Denemo-devel] Translation

[Richard Shann]

I think I have this sorted now. To make it take note of edits to
po/en_GB.po you do a make dist. Then to test you do a make install and
run the installed denemo. One of the things that was needed was to
manually update the file po/POTFILES.in
This needs to be done after adding any new source code files that need
translation. So I have added e.g. commands.c and scorelayout.c, I think
there may be others, as well as many strings in the sources not enclosed
in _()
I have also finally grokked what N_() is doing, you apply it to
translatable strings in struct initializers (which can't have actual
function calls in them as the are not executed at run time).
I think I have now got everything except strings displayed by scheme
scripts as translatable.
By the way, I guess Americans are just as happy with Bar for Measure? I
think the British use only the latter, certainly they usually talk about
bars not measures. Except when cooking:) But I never heard of a
12-measure blues :) So I guess Americans are happy to use the term Bar?
(I am thinking of my en_GB.po file here).
I'm checking this into git now.

Richard

On Tue, 2012-07-17 at 09:27 -0500, Jeremiah Benham wrote:
> On 07/16/2012 11:14 AM, Richard Shann wrote:
> >> {"WholeNote", NULL, N_("WholeNote"), NULL,N_("Insert
> >> >\xF0\x9D\x85\x9D"),G_CALLBACK (insert_chord_0key_cb)},
> >> >
> >> >The problem is the N_("Insert \xF0\x9D\x85\x9D"). This \xF0\x9D\x85
> >> >\x9D
> >> >is not translatable but it is encapsulated in the N_("") thingy. This
> >> >is
> >> >causing the packager to choke here.
> > so there is something to do to get it to choke. But I don't know what.
> I kind of remember this. It must have given me an error when running 
> make dist. It probably complained that it could translate 
> \xF0\x9D\x85\x9D. I think it produces some files .po or something (not 
> sure) based off of the .pot (not sure). I don't know anything about this 
> really. I don't know how to test the translations either. I spent weeks 
> trying to find a clear tutorial on this stuff because I could not wrap 
> my head around the dry reference manual for some reason. The fact that 
> it did not give me a clear way to test the translation out was the 
> biggest stumbling block for me. I guess I must need the confirmation 
> that I am understanding that stuff. Without being able to test, I had 
> nothing to tell me I was on the correct path.
> 
> Jeremiah
> 
> 
>