[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Musicxml2ly and convert-ly localization
From: |
John Mandereau |
Subject: |
Re: Musicxml2ly and convert-ly localization |
Date: |
Sun, 10 Feb 2008 11:44:30 +0100 |
Le vendredi 08 février 2008 à 17:30 +0100, Reinhold Kainhofer a écrit :
> Am Montag, 4. Februar 2008 schrieb John Mandereau:
> > Reinhold, are Musixml2ly messages stable enough so they can be marked
> > for translation?
>
> I don't think they'll rapidly change.
> However, I have never really bothered about i18n-able messages, so some
> error/warning messages might currently not really suited for translation...
> Also, some messages are not really userfriendly (i.e. hard to understand...).
If I understand correctly, such messages seem to happen in weird cases,
and users who simply use MusicXML as a software-generated exchange
format and don't know about the format spec in detail probably won't
have a clue about the problem, whatever meaningful the error message is.
> So, in short, I don't think that most of the messages will change in the near
> future, but feel free to improve the messages to make them more targeted at
> end users (rather than simply describing a technical problem).
I tried to "improve" some messages, but I'm not sure at all I succeeded;
the problem is, I don't know MusicXML at all, so I'm not aware of
possible problems. Feel free to revert messages strings I changed :-)
> Another thing: The musicxml2ly
> (http://kainhofer.com/~lilypond/Documentation/user/lilypond-program/Invoking-musicxml2ly.html#Invoking-musicxml2ly)
>
> web page describes only a subset of options available with musicxml2ly.
If nobody else updates this, I'll do it when you have removed --relative
and added --absolute ;-) (I'm all for this change too).
Cheers,
John