Re: New argument types (Was: Constructive Criticism and a Question)

2007-01-09 Thread Erik Sandberg 
[moving to -devel]

On Monday 08 January 2007 09:30, Mats Bengtsson wrote:
> [EMAIL PROTECTED] wrote:
> > Increasing the number of different argument types for music functions
> > would almost certainly be extremely useful for users, who, judging from
> > this mailing list, seem to have an unlimited imagination when it comes to
> > wanting to be able to extend LP syntax.
>
> I doubt that the number of argument types is any major problem. The

I disagree: I think it would be useful to have more argument types; this would 
make it possible to soft-code more of the commands that now are hard-coded in 
the parser.

Also, more argument types would make it possible to implement some functions 
more cleanly, which makes the lily<->scheme connection easier to understand 
(it is not very clean to say \myFunction s2. if you mean \myFunction 2., 
IMHO)

I have been thinking; I see two ways to make durations work as function 
arguments:
- Forbid space between pitch and duration in notes; create separate token 
PITCH_AND_DURATION (it's unclean in a sense, and requires a small hack in the 
lexer, but might be worth it). It shouldn't be too hard to write a convert-ly 
rule for this, but in any case it could be wise to postpone this change to 
v3.0
- Only allow durations as the first few parameters of music functions (so 
(duration? music?) is allowed, but not (music? duration?)). I think this is a 
dangerous path, as the rules for which signatures to allow can grow complex 
if we find more argument types with similar problems.

Han-Wen?

-- 
Erik


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Styles [Was Re: Barline scans]

2007-01-09 Thread Karl Hammar 
[EMAIL PROTECTED]:
> Karl Hammar wrote:
> > [moving this from bug-lilypond]
> > 
> > [EMAIL PROTECTED]:
> >> Karl Hammar wrote:
> >>> Maybe we should have a "my style" section in the doc.
> >> Like section 4.3 Style sheets ?
> > 
> > There you tell us how to do it. But perhaps more like the snippet
> > respository, examples of different styles. Right now we "only" have
> > one style, the default one. Plus "tweaks", where the tweaks are more
> > something you do when lilypond don't cope with it, not a different 
> > style.
> 
> I have no objection to this; see
> http://lilypond.org/web/devel/participating/documentation-adding

I guess it would go to 9.4 Style examples.

Before I can present any "new" style I have to make one though.

Regards
/Karl




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

fr.po updatae on master branch

2007-01-09 Thread Jean-Charles 

Hi all!

Here is an update for the lilypond fr.po according to this evening's git 
origin.  Please apply.



Jean-Charles
From 8a1bd1b5cc6263f5671900d2021d3f3d5a37a8c4 Mon Sep 17 00:00:00 2001
From: Jean-Charles <[EMAIL PROTECTED]>
Date: Tue, 9 Jan 2007 22:04:59 +0100
Subject: [PATCH] fr.po update

---
 po/fr.po |  263 +-
 1 files changed, 88 insertions(+), 175 deletions(-)

diff --git a/po/fr.po b/po/fr.po
index fd9eca0..035ffc8 100644
--- a/po/fr.po
+++ b/po/fr.po
@@ -10,8 +10,8 @@ msgstr ""
 "Project-Id-Version: fr\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2006-12-24 10:40+0100\n"
-"PO-Revision-Date: 2006-10-22 11:13+0200\n"
-"Last-Translator: John Mandereau <[EMAIL PROTECTED]>\n"
+"PO-Revision-Date: 2007-01-09 21:53+0100\n"
+"Last-Translator: Jean-Charles Malahieude <[EMAIL PROTECTED]>\n"
 "Language-Team: Français <[EMAIL PROTECTED]>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -77,23 +77,23 @@ msgid "Running %s..."
 msgstr "Exécution de %s..."
 
 #: lilylib.py:203
-#, fuzzy, python-format
+#, python-format
 msgid "Usage: %s"
-msgstr "Utilisation : %s\n"
+msgstr "Utilisation : %s"
 
 #: abc2ly.py:1349 convert-ly.py:80 lilypond-book.py:125 midi2ly.py:869
-#, fuzzy, python-format
+#, python-format
 msgid "%s [OPTION]... FILE"
-msgstr "Utilisation : %s [OPTIONS]... FICHIER..."
+msgstr "%s [OPTIONS]... FICHIER"
 
 #: abc2ly.py:1351
-#, fuzzy, python-format
+#, python-format
 msgid ""
 "abc2ly converts ABC music files (see\n"
 "%s) to LilyPond input."
 msgstr ""
-"Ce programme convertit les fichiers musicaux ABC (voir\n"
-"http://www.gre.ac.uk/~c.walshaw/abc2mtex/abc.txt) vers le format LilyPond."
+"Le script abc2ly convertit les fichiers musicaux ABC (voir\n"
+"%s) en fichier source LilyPond."
 
 #: abc2ly.py:1355 etf2ly.py:1200 midi2ly.py:885
 msgid "write output to FILE"
@@ -109,29 +109,21 @@ msgstr "préserver la notion de lien de croches d'ABC"
 
 #: abc2ly.py:1361 convert-ly.py:112 etf2ly.py:1208 lilypond-book.py:168
 #: midi2ly.py:911 musicxml2ly.py:505
-#, fuzzy
 msgid "Report bugs via"
-msgstr "Rapporter toute anomalie à %s"
+msgstr "Rapporter toute anomalie à"
 
 #: convert-ly.py:41
-#, fuzzy
 msgid ""
 "Update LilyPond input to newer version.  By default, update from the\n"
 "version taken from the \\version command, to the current LilyPond version."
 msgstr ""
 "Mettre à jour le fichier source vers une version plus récente. Par 
défaut,\n"
 "de la version indiquée par la commande \\version vers la version courante\n"
-"de LilyPond.\n"
-"\n"
-"Exemples :\n"
-"\n"
-"  convert-ly -e ancien.ly\\n\n"
-"  convert-ly --from=2.3.28 --to=2.5.21 toto.ly\n"
+"de LilyPond."
 
 #: convert-ly.py:43 lilypond-book.py:73
-#, fuzzy
 msgid "Examples:"
-msgstr "Exemple"
+msgstr "Exemples : "
 
 #: convert-ly.py:56 lilypond-book.py:98 warn.cc:48 input.cc:90
 #, c-format, python-format
@@ -168,7 +160,6 @@ msgid "do not add \\version command if missing"
 msgstr "ne pas ajouter la commande \\version si elle est absente"
 
 #: convert-ly.py:100
-#, fuzzy
 msgid "show rules [default: --from=0, [EMAIL PROTECTED]@]"
 msgstr "afficher les règles [par défaut : --from=0, [EMAIL PROTECTED]@]"
 
@@ -181,13 +172,12 @@ msgid "Applying conversion: "
 msgstr "Conversion en cours : "
 
 #: convert-ly.py:166
-#, fuzzy
 msgid "Error while converting"
-msgstr "erreur lors de la conversion"
+msgstr "Erreur lors de la conversion"
 
 #: convert-ly.py:168
 msgid "Stopping at last succesful rule"
-msgstr ""
+msgstr "Arrêt après la dernière règle appliquée avec succès."
 
 #: convert-ly.py:190
 #, python-format
@@ -200,25 +190,23 @@ msgid "cannot open file: `%s'"
 msgstr "impossible d'ouvrir le fichier : « %s »"
 
 #: convert-ly.py:284
-#, fuzzy, python-format
+#, python-format
 msgid "cannot determine version for `%s'.  Skipping"
-msgstr "impossible de déterminer la version pour « %s ». Au suivant"
+msgstr "impossible de déterminer la version pour « %s ». Au suivant !"
 
 #: etf2ly.py:1196
-#, fuzzy, python-format
+#, python-format
 msgid "%s [OPTION]... ETF-FILE"
-msgstr "Utilisation : %s [OPTIONS]... FICHIER..."
+msgstr "%s [OPTIONS]... FICHIER-ETF"
 
 #: etf2ly.py:1198
-#, fuzzy
 msgid ""
 "Enigma Transport Format is a format used by Coda Music Technology's\n"
 "Finale product.  etf2ly converts a subset of ETF to a ready-to-use LilyPond "
 "file."
 msgstr ""
 "Enigma Transport Format est utilisé par Finale, de Coda Music Technology.\n"
-"Ce programme convertit partiellement un fichier ETF en un fichier LilyPond "
-"exploitable."
+"Le script etf2ly convertit partiellement un fichier ETF en un fichier 
LilyPond exploitable."
 
 #: etf2ly.py:1201 midi2ly.py:886 musicxml2ly.py:498 main.cc:172 main.cc:178
 msgid "FILE"
@@ -232,10 +220,12 @@ msgstr "afficher les notices de garantie et de droit 
d'auteur"
 msgid ""
 "Process LilyPond snippets in hybrid HTML, LaTeX, texinfo or DocBook document."
 msgstr ""
+"Traite des ext

Re: Backporting doc changes to stable/2.10 [was: Re: Docs check-translation]

2007-01-09 Thread John Mandereau 
Han-Wen Nienhuys wrote: 
> Graham Percival escreveu:
> > Jean-Charles wrote:
> >> All the documents that I have read about typography and "good use"
> >> show examples introduced with a colon (:) throughout their content. 
> >> So I think it is normal French typography to do like this.
> > 
> > To be honest, I'm not certain where the no-colon rule came from.  I just
> > checked a few technical books lying around (I'm in a lab) and they
> > sometimes used colons.
> > 
> > Not that I consider blogs to be authoritative, but this article makes
> > sense to me:
> > http://www.megginson.com/blogs/quoderat/2005/12/23/mind-your-colons/

It makes sense to me too, for both French and English.  If Jean-Charles
agrees, it will become an official rule for the French docs.  Besides
that, from now I will ask permission before changing any punctuation
sign in the English docs.


> FWIW, I learned the 'avoid colons' rule both from an editor at GNU press
> and the famous mathematician Paul Halmos. 
> 
> Rules may be different in other languages, of course.

I conclude I shouldn't have changed anything, so unless you complain I'm
going to undo all period replacements I've made in introduction.itely.

Greetings
-- 
John Mandereau <[EMAIL PROTECTED]>



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Spanish translation update

2007-01-09 Thread Daniel Tonda Castillo 
Just in case the translation update got list among the huge threads, I 
resend in bz2 all the patches.


Daniel Tonda C.
--
I'll burn my books. -- Christopher Marlowe


patches-2007-01-09.tar.bz2
Description: application/bzip
begin:vcard
fn:Daniel Tonda Castillo
n:Tonda Castillo;Daniel
email;internet:[EMAIL PROTECTED]
version:2.1
end:vcard

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel