On Wednesday, 4 August 1999, Karl Eichwalder writes:
> Mats Bengtsson <[EMAIL PROTECTED]> writes:
>
> | Maybe the problem is that Lilypond is still evolving quite quickly
> | and it's hard to keep the .po files up to date.
>
> Yes, but:
>
> . the robot is patient -- submit as many versions as you like ;)
Ok, that's good.
> . at least submit a pot file short before release date.
That'll only work once the initial translations have been made,
I guess.
> BTW, I forgot to say that I'm very pleased about the fact, that
> lilypond has support for native languages (NLS)!
Well that's the biggest problem, imo. Messages, warnings and errors
have not been really standardised; it's a bit of a mess. I'd like to
devise a bit of a standard, and have this cleaned up before we do the
initial submit for translation. Are there any directions available
that could be useful for LilyPond?
> | >From the Lilypond home page, I clicked on "Mailing Lists" and
> | found:
>
> Yes, but nevertheless it's a good idea to add the address to one of
> these famous BUGS, README or INSTALL files.
> Not every user has good or permanent web access.
Good idea.
Jan.
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien/ | http://www.lilypond.org/
