[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Translation string problem
From: |
Francisco Vila |
Subject: |
Re: Translation string problem |
Date: |
Tue, 9 Dec 2008 11:08:05 +0100 |
2008/12/8 Jean-Charles Malahieude <address@hidden>:
> I think a warning would be useful, even for the English users, mentioning
> that this use of the autochange command *needs* the staves to be called "up"
> and "down".
I agree.
> Therefore I also removed the relevant lines in the pot and po files (on my
> working copy of git) in order to have them untranslated.
> #. Documentation/user/keyboards.itely:264 (context id)
> #. Documentation/user/keyboards.itely:273 (context id)
>
> but with no success.
As pot and po files are auto-generated, you'll have to do this
continuously. The only way I see is to warn this in some place and try
to remember it. We could also get rid of the @lilypond block and live
with only an @example which is freely translated on the sources, but
we'll lose the graphical example.
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
- Translation string problem, Jean-Charles Malahieude, 2008/12/08
- Re: Translation string problem,
Francisco Vila <=
- Re: Translation string problem, Trevor Daniels, 2008/12/09
- Re: Translation string problem, till Rettig, 2008/12/09
- Re: Translation string problem, Francisco Vila, 2008/12/09
- Re: Translation string problem, Francisco Vila, 2008/12/09
- Re: Translation string problem, Francisco Vila, 2008/12/09
- Re: Translation string problem, Jean-Charles Malahieude, 2008/12/09
- Re: Translation string problem, Francisco Vila, 2008/12/09
- Re: Translation string problem, John Mandereau, 2008/12/09
- Re: Translation string problem, Carl D. Sorensen, 2008/12/09