# comments in the PO files
On 2015-09-28 07:39, Federico Bruni wrote: > Il giorno mer 23 set 2015 alle 9:50, Benno Schulenberg > <be...@vertaalt.nl> ha scritto: >> grep -A3 "# FIXME" lilypond-2.19.26.nl.po | grep -v "#:" >> # FIXME: trailing space? > > This is strange, it's only in the dutch PO file. No, it's not strange: I put those comments there. :) (Comments that start with "# " are made by translators themselves, ones that start with "#." are extracted from the source by xgettext -- and most of these shouldn't be in the POT file as they are not addressed to the translators.) > cd lilypond-git > grep -A3 "# FIXME" po/*.po | grep -v "#:" Then my PO file still has not been imported into git. > Perhaps a wrong import from pot template? > You can fix it manually? No need to fix anything. My "# " comments are hints for the maintainers to improve something. Regards, Benno ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: # comments in the PO files
On 2015-09-28 13:00, Federico Bruni wrote:
> Il giorno lun 28 set 2015 alle 12:19, Benno Schulenberg
> <be...@vertaalt.nl> ha scritto:
>> No, it's not strange: I put those comments there. :)
>
> That's what I thought (you or Jan), but then I don't understand why
> you opened this thread :)
Well, you started the thread; I just hijacked it. :)
For the reason, see below.
>> My "# " comments are hints for the
>> maintainers to improve something.
>
> for the translation maintainers.. ok
No, for the Lilypond maintainers. They could improve the source.
For example:
# FIXME: this and next two should be one
msgid "Use the `alignment-offsets' sub-property of\n"
msgid "NonMusicalPaperColumn #'line-break-system-details\n"
msgid "to set fixed distances between staves.\n"
This means, the above three msgids should be a single msgid, one string.
So, in the source it should not say:
stderr_write (_ ("Use the `alignment-offsets' sub-property of\n"))
stderr_write (_ ("NonMusicalPaperColumn #'line-break-system-details\n"))
stderr_write (_ ("to set fixed distances between staves.\n"))
but:
stderr_write (_ ("Use the `alignment-offsets' sub-property of\n"
"NonMusicalPaperColumn #'line-break-system-details\n"
"to set fixed distances between staves.\n"))
And maybe dropping the first \n too.
Benno
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: verkeert is wrong
On 2015-09-22 23:09, Federico Bruni wrote: > I'm not a developer and don't know what they really mean. > Anyway, you mean this: [...] No, I mean the ones in the Dutch PO file, nl.po: grep -A3 "# FIXME" lilypond-2.19.26.nl.po | grep -v "#:" # FIXME: trailing space? #, python-format msgid "Processing `%s'... " -- # FIXME: command line ==> standard input # that is: use the existing standard phrase instead -- # FIXME: this and next two should be one msgid "Use the `alignment-offsets' sub-property of\n" msgstr "" -- # FIXME: this and next should be one msgid "Use \\override ... #'style = #'line for solid lines and\n"msgid "" -- # FIXME: uncapitalize Standard msgid "Reading MusicXML from Standard input ..." msgstr "Lezen van MusicXML van standaardinvoer..." -- # FIXME: trailing space? #, scheme-format msgid "Unknown octaveness type: ~S " -- # FIXME: stray apostrophe msgid "Defaulting to 'any-octave." msgstr "" -- # FIXME: what does accidental mean? #, fuzzy, scheme-format msgid "unknown accidental style: ~S" -- # FIXME: capitalize Unicode msgid "Glyph must have a unicode value" msgstr "Glief moet een Unicode-waarde hebben" Benno ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: verkeert is wrong
Hello Federico, On 2015-09-22 11:24, Federico Bruni wrote: > Benno, can you fix this error (see below) and send it to the robot? Done. By the way, in the Dutch PO file there are some FIXME remarks. They comment on some strangeness in the corresponding msgid. Could you have a look at them and maybe fix some of them in the source? Second by the way: some msgids are identical save for a terminating \n. Is this distinction necessary or could those strings be equalized? Regards, Benno ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
