bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond.pot polluted


From: Federico Bruni
Subject: Re: lilypond.pot polluted
Date: Sun, 04 Nov 2012 09:29:03 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.10) Gecko/20121028 Icedove/10.0.10

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]