Original Message -
From: Graham Percival gra...@percival-music.ca
To: Federico Bruni fedel...@gmail.com
Currently, makelsr.py adds different amounts of blank lines to
some .ly files depending on whether you run it as a full import
vs. when you run it locally. It would be nice if that
Il 25/04/2012 12:04, Graham Percival ha scritto:
[..]
I'm trying to learn Python and I'd like to contribute to some frog
tasks requiring python (I've starred some frog issues in the tracker).
Probably this is too much difficult for a newbie.
Actually, I've got a good suggestion on how you
Le 04/05/2012 17:34, Francisco Vila disait :
2012/5/4 Phil Holmesm...@philholmes.net:
I think the way to do this would be to have makelsr.py extract the texidoc
and doctitle strings from the snippets and to put them into
Documentation/texidoc/. In principle it would delete them from the
On Sat, May 05, 2012 at 10:35:02AM +0200, Federico Bruni wrote:
Il 25/04/2012 12:04, Graham Percival ha scritto:
[..]
I'm trying to learn Python and I'd like to contribute to some frog
tasks requiring python (I've starred some frog issues in the tracker).
Probably this is too much
- Original Message -
From: Federico Bruni fedel...@gmail.com
To: Phil Holmes m...@philholmes.net
Cc: lilypond-devel@gnu.org
Sent: Tuesday, April 24, 2012 1:29 PM
Subject: Re: Regarding LSR translation work
2012/4/24 Phil Holmes m...@philholmes.net:
1) I don't understand what say
2012/5/4 Phil Holmes m...@philholmes.net:
I think the way to do this would be to have makelsr.py extract the texidoc
and doctitle strings from the snippets and to put them into
Documentation/texidoc/. In principle it would delete them from the snippet,
and then put them back in again, as I
On Tue, Apr 24, 2012 at 02:28:21PM +0200, Federico Bruni wrote:
2012/4/24 Graham Percival gra...@percival-music.ca:
2) ask the LSR author to add the possibility to insert translated
titles and descriptions (the website itself could benefit from this,
since it may enable language
- Original Message -
From: Federico Bruni fedel...@gmail.com
To: lilypond-devel@gnu.org
Sent: Monday, April 23, 2012 11:04 PM
Subject: Re: Regarding LSR translation work
Il 21/04/2012 13:09, Graham Percival ha scritto:
From a very basic-no-progamming skill perspective, why can't we
On Tue, Apr 24, 2012 at 07:52:55AM +0100, Phil Holmes wrote:
3) Graham is wrong when he says writing snippets is not a good
introduction to lilypond. I started by doing a fair few that
documented undocumented features shown in the regtests.
Sorry, I came on too strong there. I didn't mean to
I _am_ topposting. Let me explain a copule of things.
Ciao is Italian for hello and also for goodbye, so if you
untranslate and then translate back, all becomes clear, at least for
me.
The problem is not LSR itself. Yes, the docs will look the same after,
but it's not how the docs look like,
2012/4/24 Francisco Vila paconet@gmail.com:
I _am_ topposting. Let me explain a copule of things.
Ouch!
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
2012/4/24 Graham Percival gra...@percival-music.ca:
On Tue, Apr 24, 2012 at 12:04:57AM +0200, Federico Bruni wrote:
1) manage all the docs snippets in Git and say hello to LSR (see
bottom of my email)
Do you mean goodbye instead of hello ?
sorry, yes of course I meant goodbye
2) ask the
2012/4/24 Carl Sorensen c_soren...@byu.edu:
Let's manage all the doc snippets in Git and say hello to LSR import!
Which are the arguments against this change?
It involves work. In particular, horrible build system work,
which always takes an order of magnitude longer than you might
expect.
2012/4/24 Phil Holmes m...@philholmes.net:
1) I don't understand what say hello to LSR means.
sorry, I meant goodbye to LSR
2) I don't really understand how LSR snippets are translated, so can't
comment knowledgably
See CG, 5.8.3, Updating translation committishes (last two paragraphs).
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: Phil Holmes m...@philholmes.net
Cc: Federico Bruni fedel...@gmail.com; lilypond-devel@gnu.org
Sent: Tuesday, April 24, 2012 8:42 AM
Subject: Re: Regarding LSR translation work
[1] of course there was some recent
- Original Message -
From: Francisco Vila paconet@gmail.com
To: Graham Percival gra...@percival-music.ca
Cc: Phil Holmes m...@philholmes.net; lilypond-devel@gnu.org
Sent: Tuesday, April 24, 2012 9:10 AM
Subject: Re: Regarding LSR translation work
The problem is not LSR itself. Yes
- Original Message -
From: Federico Bruni fedel...@gmail.com
To: Graham Percival gra...@percival-music.ca
Cc: lilypond-devel@gnu.org
Sent: Tuesday, April 24, 2012 1:28 PM
Subject: Re: Regarding LSR translation work
2) ask the LSR author to add the possibility to insert translated
On 4/24/12 7:56 AM, Phil Holmes m...@philholmes.net wrote:
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: Phil Holmes m...@philholmes.net
Cc: Federico Bruni fedel...@gmail.com; lilypond-devel@gnu.org
Sent: Tuesday, April 24, 2012 8:42 AM
Subject: Re: Regarding LSR
Il 24/04/2012 16:00, Phil Holmes ha scritto:
I'd be happy to make this a summer project, if you and Federico want to
collaborate. Can't start until the end of this year of college, though.
Thanks Phil, that would be great.
Let us know when you start, I'll try to help as much as I can.
2012/4/24 Federico Bruni fedel...@gmail.com:
Il 24/04/2012 16:00, Phil Holmes ha scritto:
I'd be happy to make this a summer project, if you and Federico want to
collaborate. Can't start until the end of this year of college, though.
Thanks Phil, that would be great.
Let us know when you
Il 21/04/2012 13:09, Graham Percival ha scritto:
From a very basic-no-progamming skill perspective, why can't we just
have an extra texidoc entry in the snippet itself and add the
translation manually, like we would for any updated snippet?
Because then it would be overwritten whenever
On Tue, Apr 24, 2012 at 12:04:57AM +0200, Federico Bruni wrote:
Il 21/04/2012 13:09, Graham Percival ha scritto:
Because snippets come from LSR, and that needs a texidoc to
display some text for the snippet.
So it seems that there are only two possible solutions (I'm just
daydreaming):
On 4/23/12 6:25 PM, Graham Percival gra...@percival-music.ca wrote:
On Tue, Apr 24, 2012 at 12:04:57AM +0200, Federico Bruni wrote:
Personally, I'm a bit worried about going on with translating NR
when I know that keeping it up-to-date will be an hassle.
Let's manage all the doc snippets in
Il 17/04/2012 23:40, Francisco Vila ha scritto:
2012/4/17 Federico Brunifedel...@gmail.com:
Another solution could be keeping the current structure and changing only
check-translation.py so that, when looking at the files in
Documentation/snippets, it should check only the changes inside
Le 21/04/2012 10:57, Federico Bruni disait :
Il 17/04/2012 23:40, Francisco Vila ha scritto:
2012/4/17 Federico Brunifedel...@gmail.com:
Another solution could be keeping the current structure and
changing only
check-translation.py so that, when looking at the files in
Hello,
On 21 April 2012 10:13, Jean-Charles Malahieude lily...@orange.fr wrote:
...
This makes me believe it would be a good opportunity to have the English
version follow the same rule as translations.
Err.. not sure what you mean by that technically but it's complicated
enough with snippets
On Sat, Apr 21, 2012 at 11:33:49AM +0100, James wrote:
Err.. not sure what you mean by that technically but it's complicated
enough with snippets as it is, to follow the translation method adds
even more complexity (if the CG is anything to go by).
+1
We want to encourage contributors not
Le 21/04/2012 12:33, James disait :
Hello,
On 21 April 2012 10:13, Jean-Charles Malahieudelily...@orange.fr wrote:
...
This makes me believe it would be a good opportunity to have the English
version follow the same rule as translations.
Err.. not sure what you mean by that technically but
Hello all,
As you know, we translators are constantly aware of how much pendant
work we have, thanks to 'make check-translation'. For example, right
now
cd Documentation
make ISOLANG=es check-translation | wc -l
gives ten thousand lines as result, most of them from
Documentation/snippets/.
Le 17/04/2012 11:46, Francisco Vila disait :
Hello all,
As you know, we translators are constantly aware of how much pendant
work we have, thanks to 'make check-translation'. For example, right
now
cd Documentation
make ISOLANG=es check-translation | wc -l
gives ten thousand lines as
Hi Francisco,
thanks for bringing this to the attention of developers!
Il 17/04/2012 11:46, Francisco Vila ha scritto:
Hello all,
As you know, we translators are constantly aware of how much pendant
work we have, thanks to 'make check-translation'. For example, right
now
cd Documentation
2012/4/17 Federico Bruni fedel...@gmail.com:
Another solution could be keeping the current structure and changing only
check-translation.py so that, when looking at the files in
Documentation/snippets, it should check only the changes inside texidoc =
and doctitle = strings.
Yes, I intially
32 matches
Mail list logo
