[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Denemo-devel] A problem with ja.po for the Denemo project
From: |
Richard Shann |
Subject: |
Re: [Denemo-devel] A problem with ja.po for the Denemo project |
Date: |
Tue, 08 Nov 2016 17:18:33 +0000 |
On Tue, 2016-11-08 at 09:31 -0600, Jeremiah Benham wrote:
> Richard
> I can look into upgrading gettext.
It's not a high priority - Benno has assured us that deleting the lines
starting # is fine, so I can do that. Right now we should change as
little as possible towards releasing 2.0.14 working on all platforms.
> Wasn't there some other package that needed upgrading but we were
> unable to compile lilypond? Whatever this was, it seems to be fixed. I
> can now compile lilypond from the latest upstream gub.
I'm afraid I don't recall that :( but we should stick to the latest
LilyPond 2.18 (ie stable) build, as there are API changes and we did get
crash reports for certain 2.19.xx versions.
Richard
>
>
> Jeremiah
>
> On Tue, Nov 8, 2016 at 6:37 AM, Benno Schulenberg
> <address@hidden> wrote:
>
> Hello Richard,
>
> On 2016-11-06 13:39, Richard Shann wrote:
> > This problem "#~| msgid "re-surfaced with the latest ja.po
> file.
> > It appeared on just one line and that broke the overnight
> build for a
> > couple of days while we figured out what it was.
> > I deleted the line and the overnight build has now
> succeeded.
> > Is it a matter of our Japanese translator updating his
> software?
>
> No. It is a problem with the software you use to build
> denemo:
> your msgmerge is too old, /or/ it has a bug, because it should
> simply ignore /any/ line that starts with #. Yes, some lines
> that start with # are special to gettext, but if an
> unexpectedly
> formatted comment line breaks your build, this is a bug that
> you
> should report to bug-gettext.
>
> Regards,
>
> Benno
>
>
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/denemo-devel
>
>
>