[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LilyPond Odd Jobs
From: |
John Mandereau |
Subject: |
Re: LilyPond Odd Jobs |
Date: |
Mon, 01 Jan 2007 23:00:06 +0100 |
Werner LEMBERG wrote:
> > - So, another thing for the todo list is to do through
> > ly/music-functions-init.ly and add a doc string to every function
> > listed.
>
> I wonder how those strings can be internationalized. The normal
> gettext mechanism might work (and is probably the right approach), but
> how to get the translations from the PO files into the texinfo file?
If the string to be translated can be easily identified (e.g. by a
regexp), there's no need to mark the strings in the Texinfo file, and
regexp substitution with a Python/Gettext combination on the Texinfo
file or output files is a solution. Such a mechanism already exists in
buildscripts/html-gettext for translation of the node names.
(slightly off-topic)
Btw, is there any chance that Texinfo is actively developed to support
internationalization? Would that need sponsoring, or an important number
of contributors?
Happy 2007
--
John Mandereau <address@hidden>
Re: LilyPond Odd Jobs,
John Mandereau <=