LGTM, thanks!
https://codereview.appspot.com/571950043/diff/545810043/input/regression/auto-beam-exceptions.ly
File input/regression/auto-beam-exceptions.ly (right):
https://codereview.appspot.com/571950043/diff/545810043/input/regression/auto-beam-exceptions.ly#newcode7
input/regression/auto-be
Francisco Vila wrote Friday, August 20, 2010 4:20 PM
2010/8/17 Trevor Daniels :
I've just updated a snippet which contained translated texidoc
strings.
Only the LilyPond code was changed,
not the texidoc strings themselves. I also updated
the committishes in the four texidocs fo
2010/8/17 Trevor Daniels :
> Francisco
>
> I've just updated a snippet which contained translated texidoc strings.
> Only the LilyPond code was changed,
> not the texidoc strings themselves. I also updated
> the committishes in the four texidocs folders.
Francisco
I've just updated a snippet which contained translated
texidoc strings. Only the LilyPond code was changed,
not the texidoc strings themselves. I also updated
the committishes in the four texidocs folders. These
were in commits:
bfc88203ac2572737480e78ef2635ed35b4
On 2008/10/27 20:00 +0100, Francisco Vila wrote:
> I could be wrong, but the actual strings are taken from input/lsr and
> put there by Neil Puttock's LSR updates, that also take into account
> possible updates from the LSR online service.
This is correct.
> I don't know if this process or a par
2008/10/27 Francisco Vila <[EMAIL PROTECTED]>:
Sorry, I mean:
> Talking of, any feedback about my message about how to detect changes
> on these snippets _or_ filtering which ones need to update _since_ last
> translation?
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
2008/10/27 Till Rettig <[EMAIL PROTECTED]>:
> Hi,
> what has to be done to use the texidoc strings for included files if I build
> the documentation myself? I thought this way I could check if everything
> went well and I didn't forget some double quotes or somehting. As I
&
Hi,
what has to be done to use the texidoc strings for included files if I
build the documentation myself? I thought this way I could check if
everything went well and I didn't forget some double quotes or
somehting. As I understand it consists of running some process to add
the trans
t;
> On second thought, maybe you should not spend time in this. As a
> translator, for sure you will find a proper way to translate texidoc
> strings quickly, when the moment arrives.
OK, let's drop this feature request for makelsr.py then. There's still
a bunch of technical
a
translator, for sure you will find a proper way to translate texidoc
strings quickly, when the moment arrives.
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
a
translator, for sure you will find a proper way to translate texidoc
strings quickly, when the moment arrives.
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2008/07/15 23:16 +0200, Francisco Vila wrote:
> 2008/7/15 Graham Percival <[EMAIL PROTECTED]>:
> > This is trickier than you think, because input/lsr/ stuff is
> > automatically junked and updated from LSR. If the snippet in LSR
> > is updated, that new description would need to get put into
>
On Tue, 15 Jul 2008 23:16:28 +0200
"Francisco Vila" <[EMAIL PROTECTED]> wrote:
> Alternatively, given that I am first copying lsr/thesnippet.ly into
> texidocs/thesnippet.texidoc and then overwriting the English string
> with the Spanish translation, I could simply NOT to overwrite it but
> copy i
2008/7/15 Graham Percival <[EMAIL PROTECTED]>:
> This is trickier than you think, because input/lsr/ stuff is
> automatically junked and updated from LSR. If the snippet in LSR
> is updated, that new description would need to get put into
> texidoc/, and the translation infrastructure would need t
On Tue, 15 Jul 2008 20:17:53 +0200
"Francisco Vila" <[EMAIL PROTECTED]> wrote:
> Would it be considered a waste of space if original texidoc/doctitle
> strings were permanently in the texidocs/ files, thus making
> translation much easier (and faster)?
This is trickier than you think, because inp
I've been adding translated texidoc strings for the LSR, and now I
realize that life of translators would be much easier if original
strings were on the same file, untranslated. Otherwise, one has to
retrieve the lsr/*.ly file of the same name and pick the English
string, copy it to the tex
16 matches
Mail list logo
