Re: Add backup option to convert-ly (Issue 3572) (issue 14040043)

On 2013/09/29 05:46:39, dak wrote: https://codereview.appspot.com/14040043/diff/6001/scripts/convert-ly.py The name here was chosen to correspond with the numbered backups of Emacs. Emacs will recognize a numbered backup file (joining the backup scheme) only when there is a good match. In

Re: Add backup option to convert-ly (Issue 3572) (issue 14040043)

https://codereview.appspot.com/14040043/diff/6001/scripts/convert-ly.py File scripts/convert-ly.py (right): https://codereview.appspot.com/14040043/diff/6001/scripts/convert-ly.py#newcode243 scripts/convert-ly.py:243: back_up = file + '.~' + str(n) + '~' On 2013/09/29 01:00:49, Ian Hulin (gmail)

Re: Add backup option to convert-ly (Issue 3572) (issue 14040043)

I'd prefer a single tilde to indicate the a backup file after the version string. https://codereview.appspot.com/14040043/diff/6001/scripts/convert-ly.py File scripts/convert-ly.py (right): https://codereview.appspot.com/14040043/diff/6001/scripts/convert-ly.py#newcode243 scripts/convert-ly.py

Re: LSR imports and version numbers?

Phil Holmes writes Saturday, September 28, 2013 2:19 PM > From: "David Kastrup" >> "Phil Holmes" writes: >> >>> There is a question in my mind as to what a) should bump the version >>> to: i) current version; or ii) version that the update related to. >>> Simplest is probably i). >> >> Uh, i)

Re: LSR imports and version numbers?

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: Sent: Saturday, September 28, 2013 1:36 PM Subject: Re: LSR imports and version numbers? "Phil Holmes" writes: The bumping of version numbers is a pain for me, too - it makes it tedious to check what makelsr has _re

Re: LSR imports and version numbers?

"Phil Holmes" writes: > The bumping of version numbers is a pain for me, too - it makes it > tedious to check what makelsr has _really_ done. > > I think we should have 2 alternatives: a) bump the version if the file > is updated, and not if it hasn't or b) bump to the current version > regardles

Re: LSR imports and version numbers?

- Original Message - From: "David Kastrup" To: Sent: Saturday, September 28, 2013 1:25 PM Subject: LSR imports and version numbers? Hi, I've seen the last LSR import do nothing but bump the version number on a large number of files from 2.17.25 to 2.15.27. Now that's consistent wi

LSR imports and version numbers?

Hi, I've seen the last LSR import do nothing but bump the version number on a large number of files from 2.17.25 to 2.15.27. Now that's consistent with the current documentation on convert-ly which states: The following options can be given: -d,--diff-version-update increase the \version

Re: Add backup option to convert-ly (Issue 3572) (issue 14040043)

Please review. https://codereview.appspot.com/14040043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: lilypad is localized?

2013/9/28 Phil Holmes > I believe lilypad for Windows is localised - see > > https://github.com/gperciva/**lilypad/tree/master/windows > > All those .rc files are Windows resource files in different languages. > I've no idea how it works,

Re: lilypad is localized?

- Original Message - From: "Graham Percival" To: "David Kastrup" Cc: "lilypond-devel" Sent: Saturday, September 28, 2013 8:26 AM Subject: Re: lilypad is localized? On Sat, Sep 28, 2013 at 08:24:13AM +0200, David Kastrup wrote: So the real question _if_ it is localized is how you c

Re: lilypad is localized?

On Sat, Sep 28, 2013 at 08:24:13AM +0200, David Kastrup wrote: > > So the real question _if_ it is localized is how you can figure out the > translations used in the localized versions so that you can _copy_ them > into the documentation and/or put better translations in _both_ places. > > Graham