Re: lilypond.pot polluted

2012-11-04 Thread Federico Bruni 

Il 03/11/2012 19:04, Jean-Charles Malahieude ha scritto:

Hi John and all,

I just noticed that, because the out of tree build, lilypond.pot gets
polluted by personal path, what does not happen with an in tree build.

e.g. we get, when out of tree :

#: parser.yy:174 parser.yy:188 /home/jcharles/GIT/Mentor/lily/parser.yy:174
#: /home/jcharles/GIT/Mentor/lily/parser.yy:188
msgid Too much lookahead
msgstr 

#: parser.yy:466 parser.yy:736 parser.yy:803
#: /home/jcharles/GIT/Mentor/lily/parser.yy:466
#: /home/jcharles/GIT/Mentor/lily/parser.yy:736
#: /home/jcharles/GIT/Mentor/lily/parser.yy:803
msgid bad expression type
msgstr 


instead of just :

#: parser.yy:174 parser.yy:188
msgid Too much lookahead
msgstr 

#: parser.yy:466 parser.yy:736 parser.yy:803
msgid bad expression type
msgstr 




The full paths are obviously wrong, but relative paths (either to po/ or 
root tree) would be a benefit for translators, because po editors 
provide buttons which open the source file:line for each string.

Now the paths are missing and the editor can't find the file.

Translators are not developers, but sometimes looking at the context can 
help.  When I submitted my translation to the italian proofreader list, 
I received complaints about that.


Other projects I've contributed to use relative paths, so this should be 
possible.

--
Federico

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

lilypond.pot polluted

2012-11-03 Thread Jean-Charles Malahieude 

Hi John and all,

I just noticed that, because the out of tree build, lilypond.pot gets
polluted by personal path, what does not happen with an in tree build.

e.g. we get, when out of tree :

#: parser.yy:174 parser.yy:188 /home/jcharles/GIT/Mentor/lily/parser.yy:174
#: /home/jcharles/GIT/Mentor/lily/parser.yy:188
msgid Too much lookahead
msgstr 

#: parser.yy:466 parser.yy:736 parser.yy:803
#: /home/jcharles/GIT/Mentor/lily/parser.yy:466
#: /home/jcharles/GIT/Mentor/lily/parser.yy:736
#: /home/jcharles/GIT/Mentor/lily/parser.yy:803
msgid bad expression type
msgstr 


instead of just :

#: parser.yy:174 parser.yy:188
msgid Too much lookahead
msgstr 

#: parser.yy:466 parser.yy:736 parser.yy:803
msgid bad expression type
msgstr 


As a matter of fact, only lily/lexer.ll and lily/parser.yy are concerned 
with the duplication. I suspect it comes from ALL_PO_SOURCES which gets 
defined in stepmake/stepmake/po-targets.make, but am not sure how to fix 
it.  Once again, this does not occur when NOT building out of tree 
(you know I prefer a local clone).


Cheers,
Jean-Charles




___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond