Hi John,
first time I consulted the contributor's guide. It's now much easier to
read than the old text file. Some things made me stumbel upon, though:
in 3.7.2 Documentation translation details you have different starting
points for the individual files: mostly you start from LL-directory, bu
Carl D. Sorensen schrieb:
On 5/22/09 2:55 PM, "John Mandereau" wrote:
Carl D. Sorensen a écrit :
I would recommend that it either be left in english, or translated manually
for now. That is a temporary hack until the great website redesign, which
will be accomplished starting in two
Carl D. Sorensen schrieb:
On 5/22/09 1:13 PM, "Till Rettig" wrote:
Hi John,
I just realized that on the web page there is now an addition for the
windos download entry about lilypond being a command line programm and
so on. This is nowhere translated. I guess it should be in th
John Mandereau schrieb:
Francisco Vila a écrit :
Well, it seems that we can ignore all the diff lines that do not touch
texidoc= or doctitle= fields on files in lsr/ ; so it's not that bad.
Is this right?
It is. This will remain as much cumbersome until LSR snippets (and the
associated data
John Mandereau schrieb:
Till Rettig a écrit :
This translation interface is getting more and more tricky it seems
(I mean technically)
Speaking of, my next task on the translation infrastructure is
simplyfing it a little, i.e. translating node names and titles in
Texinfo sources, which will
Hi John,
I just realized that on the web page there is now an addition for the
windos download entry about lilypond being a command line programm and
so on. This is nowhere translated. I guess it should be in the po.s. Do
we have to add it manually there?
Greetings
Till
Hi John,
somehow the section names don't get translated in the pdfs that are
produced by "make doc". I can see they are translated on the compiled
version on the web, but why don't I get them? :(
Another question is: can I update snippets only for one language? and
how to do a po-update (is
Francisco Vila schrieb:
2009/5/18 John Mandereau :
Francisco Vila a écrit :
Permission to bulk fix it into the last version, in all languages.
...I'm doing my best to update the script and fix committishes
with regexp substitution before next week.
Well, I was really
Francisco Vila schrieb:
2009/2/14 Frédéric Bron :
This link has been broken for a few days:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond-big-page
OK I am sorry, I did not read the message of Firefox. It says there is
an encoding problem:
In French:
"Erreur d'encodage d
John Mandereau schrieb:
Hi Till!
Till Rettig a écrit :
Was there already discussion on translating also the NEWS part of the
documentation? It might not be really used by many people when 2.12
has become normality but for the moment it might be interesting since
it also has a direct link from
Hi,
adding to this old thread:
Was there already discussion on translating also the NEWS part of the
documentation? It might not be really used by many people when 2.12 has
become normality but for the moment it might be interesting since it
also has a direct link from the news entry on lilyp
Patrick McCarty schrieb:
I have considered keeping the soft blue for the links, but here are my
two main reasons for changing to the more "pure" blue:
- The current blue (#3465a4) does not pass the WCAG 1.0 against a
white background. Based on experience, the new blue definitely
increases reada
Patrick McCarty schrieb:
Hello,
This patch features many of the same changes as my previous patches,
but I have changed fewer colors this time. One notable color that is
not present is the `soft blue' currently being used for links. I hope
to reintegrate this color in the future.
Hi,
I lik
Hi John,
could you create new po files for the binary and upload them to the Translation
Project?
Thanks
Till
--
Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
http://www.gmx.net/de/go/multimessenger
___
lilypond-devel mail
Han-Wen Nienhuys schrieb:
On Sat, Dec 6, 2008 at 8:24 PM, Till Rettig wrote:
Thanks I know. Actually I just discovered that Century Schoolbook is to
blame: indeed it doesn't include small caps. Didn't check how pango/lilypond
handles a font that includes them.
It w
Trevor Daniels schrieb:
Reinhold, you wrote Sunday, December 14, 2008 1:46 PM
Where in the docs do the flag styles belong?
There is a selected snippet in 1.2.4 Beams entitled
"Flat flags and beam nibs" which shows flags derived
from beamlets. A new snippet showing straight flags in the two
Hi,
thanks for report, I didn't check on it. What if we use for this particular
case @c KEEP LY and put the
up and down there. So other instantiations with the same name get translated
correctly, where it doesn*t harm.
till
Original-Nachricht
Datum: Tue, 9 Dec 2008 11:08:05 +0
Hi John!
can I just start translating the new helping web page? Do you need first
to adjust the building scripts so the new menu or can I already put the
file into the de folder?
Greetings
Till
___
lilypond-devel mailing list
lilypond-devel@gnu.or
Maximilian Albert schrieb:
P.S.: In case this gets approved in one form or the other, what would
be necessary to document it properly? Add a LSR example, a regression
test, something else? Anything I need to keep in mind when writing
these?
This is great news, I remember I have a piece where t
[EMAIL PROTECTED] schrieb:
On Sat, Dec 6, 2008, Till Rettig <[EMAIL PROTECTED]> said:
(I guess you were just suggesting this in the second part of the message)
I make fonts and understand understand the issue of line weight, 40%
reduced majiscules differ from proper smallcaps.
Danalute schrieb:
Till wrote:
I would like to have *REAL* small caps when the font has them
and not this faked stuff, it really hurts my eyes. (maybe pango indeed
can be configured to do so?)
Unicode provides encodings for SMALL CAPITALS, unfortunatly they are
scattered and saddled
John Mandereau schrieb:
Hi,
texi2html from current CVS no longer crashes on one of French big page
manuals, so I pushed changes that make all big page manuals be generated
in all languages.
Great, I just wanted to ask you to enable it also for the German AU,
which is now fully translated. Ho
Werner LEMBERG schrieb:
I wonder how we are going to get high-quality typesetting within
lilypond. This is a fundamental question: I think we shouldn't extend
lilypond so that it is contains a complete typesetting engine;
instead, we should rather look for alternatives.
I see two possibilities.
was you could just write this actual content code, maybe with a
table or something --
but actually already the plain text with links would be something that
could be easily turned into a web page.
Till
Carl
On 11/27/08 12:46 PM, "Till Rettig" <[EMAIL PROTECTED]> wrote:
Carl
Carl D. Sorensen schrieb:
The Getting Help page would have:
1) A statement saying that "LilyPond does not have a graphical interface",
and an embedded link to the crash course.
2) A statement saying that "The first thing you should do is read the
Learning Manual", with an embedded link to the t
Trevor Daniels schrieb:
Notation Reference Section 1.6 Staff notation has now been reviewed
twice and is ready to be released for translation, although I see Till
and Francisco have already translated it to German and Spanish pretty
well completely!
Thanks anyway, it will be time for an update
to the translation branch, but I can do this if it is ok.
Till
>From 79df5e106ed772b72e79b8bd760dbb8335428d0d Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sun, 23 Nov 2008 11:59:58 +0200
Subject: [PATCH] Add dashed and dotted phrasing slurs
*Add definitions to property-init.ly
*Add regression test
Hi,
just saw that the examples page doesn't have yet the new layout. It
would be nice if there would also a contents where it would be much
easier to see what examples are available. I hope this is no big work.
Also it appeared to me that it would be nice to have some examples of
ancient mus
00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sat, 22 Nov 2008 18:31:45 +0200
Subject: [PATCH] Add dashed and dotted phrasing slurs
*Add dashed and dotted phrasing slur definitions to property-init.ly
*Add regression test file
*Mention dashed and dotted phrasing slurs in the
Hi,
nice work! I like the new green navigation bar! But again, I prefer ther warmer
beige of the old contents box. :-)
Greetings
Till
Original-Nachricht
> Datum: Wed, 19 Nov 2008 17:08:08 -0800
> Von: Patrick McCarty <[EMAIL PROTECTED]>
> An: lilypond-devel
> Betreff: [PATCH] D
Trevor Daniels schrieb:
I think it is even ok to insert them everywhere -- we have also
@ignore and @end ignore.
I'm not opposed to this in principle, but you'll have
to find someone else to go through all the .itely files
and insert them. I don't even have enough time at the
moment to comple
Trevor Daniels schrieb:
Werner LEMBERG wrote Wednesday, November 19, 2008 2:48 PM
There are only a couple of instances where this looks particularly
bad. Could we instead change just those instances so each of
predefined commands is on a separate line? Is this possible? It
would certainly
Original-Nachricht
> Datum: Thu, 13 Nov 2008 16:54:52 -0800
> Von: "Patrick McCarty" <[EMAIL PROTECTED]>
> An: "till Rettig" <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED], lilypond-devel@gnu.org
> Betreff: Re: New patch for style
Hi Patrick,
it's a nice design as far as I can see, I didn't investigate, though. Do you
still have the brown for warning boxes? I somehow liked it that the pages are
not only with green and neutral (whitish) colors.
But it's my personal taste...
Greetings
Till
Original-Nachricht
John Mandereau schrieb:
On 2008/11/09 22:39 +0200, Till Rettig wrote:
is this a known bug that with firefox2 I can see navigation buttons on
top and bottom of the main window at kainhofer.com, but they are missing
on lilypond.org? That is when using the docs from lilypond.org there it
is
Hi,
is this a known bug that with firefox2 I can see navigation buttons on
top and bottom of the main window at kainhofer.com, but they are missing
on lilypond.org? That is when using the docs from lilypond.org there it
is only possible to navigate via the contents window.
Is somebody else al
Hi
here come my comments: line numbers always refer to the itely file
a general note for mensural notation: I had some experiments with
reducing the spaces between notes with long durations -- ideally the
notes should have the same spacing all over. Han-Wen wrote me in Februry
this year:
Thi
Trevor Daniels schrieb:
Eyolf
More comments on Ancient now seem unlikely. T
Oops, I totally forgot about it. I would like to review this, but I am
not really fast at the moment. I might just start next week, or would it
be better to wait for the next version?
Greetings
Till
__
Original-Nachricht
> Datum: Thu, 30 Oct 2008 12:29:12 +0200
> Von: "Risto Vääräniemi" <[EMAIL PROTECTED]>
> An: "Trevor Daniels" <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED], LilyPond Development , Mats
> Bengtsson <[EMAIL PROTECTED]>
> Betreff: Re: What to do when \\> and \\< pr
John Mandereau schrieb:
On 2008/10/25 23:02 +0200, Francisco Vila wrote:
Is there a way to list the changes made to LSR snippets from last time
that they were translated?
Yeah, but not before Thursday ;-)
Success!
I'm thinking on something along the lines
of the make check-t
Tue, 28 Oct 2008 23:42:49 +0100
> Von: Reinhold Kainhofer <[EMAIL PROTECTED]>
> An: lilypond-devel@gnu.org
> CC: Till Rettig <[EMAIL PROTECTED]>, John Mandereau <[EMAIL PROTECTED]>
> Betreff: Re: Release notes in German
> -BEGIN PGP SIGNED MESSAGE-
>
Original-Nachricht
> Datum: Tue, 28 Oct 2008 12:05:29 +0100
> Von: John Mandereau <[EMAIL PROTECTED]>
> An: till Rettig <[EMAIL PROTECTED]>
> CC: lilypond-devel@gnu.org
> Betreff: Re: Release notes in German
> On 2008/10/28 07:44 +0100, till Retti
Original-Nachricht
> Datum: Mon, 27 Oct 2008 22:44:27 +0100
> Von: John Mandereau <[EMAIL PROTECTED]>
> An: Till Rettig <[EMAIL PROTECTED]>
> CC: lilypond-devel@gnu.org
> Betreff: Re: Release notes in German
> > How did you mean to include t
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 translated str
Hi John
maybe my last mail ended up in your spam folder, so here another try:
I translated a first version of the release notes, at the moment at
http://marginalis.de/lilypond/release-notes.txt
Feel free to put it to the wiki yourself, or try to add me again, ( I
never got any message from th
John Mandereau schrieb:
Hi Francisco, hi Till,
On 2008/10/23 20:10 +0200, Francisco Vila wrote:
Also Spanish Internals and Program Usage are now complete in git (or
they were a few days ago). Please add them to this wishlist.
You mean the Notation Reference, not the Internals??
I adde
Hi John
are there now big html pages automatically created? The German
lilypond-learning it fully translated and it would be nice to have it
also as a big page. As I saw the Spanish link shows already to the
Spanish big page, so can I just change it also for German?
Greetings
Till
Francisco Vila schrieb:
Hello all,
As for the Vocal headword: I have prettyfied the code. Here are my two
proposals, the one Valentin liked best (ending) and the one Till liked
best (first systems).
Just vote for one if no other better proposal comes out.
PDFs are on
http://www.paconet.org/oy
Valentin Villenave schrieb:
2008/10/17 Francisco Vila <[EMAIL PROTECTED]>:
If you think it could serve, please select a few measures of your
interest, maybe the last ones?
It's beautiful! The only downside is that the last measures do not
show the funny birdy-lyrics; but that's hardly
John Mandereau schrieb:
On 2008/10/13 06:05 +0200, Werner LEMBERG wrote:
the CVS version of texinfo now supports non-English hyphenation!
It's certainly a good thing you added txi-LL.tex files, as people who
build the docs may not have the latest versions of these files.
It's re
Thanks, it is corrected in the next version (that is in the current development
version and the next stable, 2.12).
Till
Original-Nachricht
> Datum: Thu, 9 Oct 2008 11:54:31 + (UTC)
> Von: Sebastian <[EMAIL PROTECTED]>
> An: lilypond-devel@gnu.org
> Betreff: translation of "
Francisco Vila schrieb:
Hello, John and translators,
When running make translation-status I obtain 'bad object' warnings on
these files:
fr/user/macros.itexi
de/user/macros.itexi
fr/user/lilypond.tely
ok, so this is the thing that cases the bad objects? I will update my
macros since they
it should also be mentioned on this page:
http://lilypond.org/web/about/faq
till
Original-Nachricht
> Datum: Wed, 8 Oct 2008 16:35:57 +0300
> Von: "Risto Vääräniemi" <[EMAIL PROTECTED]>
> An: "Graham Percival" <[EMAIL PROTECTED]>
> CC: Nils Gey <[EMAIL PROTECTED]>, lilypond-deve
John Mandereau schrieb:
On 2008/09/30 23:34 +0200, Francisco Vila wrote:
2008/9/30 Valentin Villenave <[EMAIL PROTECTED]>:
2008/9/30 Francisco Vila <[EMAIL PROTECTED]>:
As headword, woult it serve a fragment of Janequin's Le Chant des
Oyseaux? It is onomatopoeic and funny look
Valentin Villenave schrieb:
2008/9/29 John Mandereau <[EMAIL PROTECTED]>:
Many users overlook the link to the docball in the download page, so
they do not know about it; a user suggested on the French list that we
could add a link to the docball from the documentation index. How does
the
Original-Nachricht
> Datum: Thu, 25 Sep 2008 13:18:59 +0200
> Von: "Eyolf Østrem" <[EMAIL PROTECTED]>
> An: lilypond-devel
> Betreff: Re: Three questions for ancient.itely
> On 25.09.2008 (04:09), Graham Percival wrote:
> >
> > Remember that nobody is maintaining the code for
I would also translate the text, is the wiki a good place for that? Will
this text be also in the news items?
John, could you create an account in the wiki for me?
Thanks
Till
Francisco Vila schrieb:
I'd like to translate the release notes into Spanish, as soon as a
final version exists. This
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thursday 18 September 2008 22:20:12 Till Rettig wrote:
> > Is there no way to make "hidden" links without all the words around? I
> > would prefer something
> > like a clickable word only, that is,
Hi,
I would like to include a link to the Glossary for German users, but not
to a specific section, but in general to the whole document. So far I
tried both
@rglos{Musik Glossary}
and
@ref{Music Glossary,,,music-glossary,Musikglossar}
which links to the top node of the document. I am not
Johannes Schindelin schrieb:
Hi,
On Thu, 4 Sep 2008, till Rettig wrote:
- -) "git checkout filename" -- discards all non-committed changes to the
file.
I thought that works only if you remove the file before?
No, it works also with dirty files, i.e. files that
Hi,
thanks for this comprehensive list! Many things are now also clearer to me!
Original-Nachricht
> Datum: Thu, 4 Sep 2008 01:08:53 +0200
> Von: Reinhold Kainhofer <[EMAIL PROTECTED]>
> An: "Jean-Charles Malahieude" <[EMAIL PROTECTED]>
> CC: lilypond-devel
> Betreff: Re: git un
Francisco Vila schrieb:
This is a git question, or a diff question, or a translation
maintenance scripts question.
When I run make check-translation, if I try to redirect its output,
which is nicely coloured on screen, the resulting file has ugly
escaped codes in it. I have tried to edit the c
Bertalan Fodor schrieb:
I think in this way this is a bad practice
Well, it is also not really logical/good practice to have the major be
the main function
(with no modifier)
and the minor then with a modifier. It is always a bit difficult to
explain people that their
habits are bad and the
Hi,
there has been complaints on the German lilypond forum about the stems
of half notes in tabulatures: half notes and quarter notes look the same
in pure tabulatur notation, if there is no traditional note line above
specifying the rythms. A user posted a picture of a tabulatur featuring
a
Hi,
there has been every once and a while questions about German chord names
on the German lilypond forum.
The users would like to be able to make a minor chord print the chord
name as a small letter, and a big letter for the major chord, e.g.
C maj would be C and C min would be c.
This has so
Looks good,
please apply. I am also not satisfied with the section about compilation
from sources. Maybe there can be a comment stating that understanding of
English is necessary to do the compilation and a link to the English
section. At least it would be really strange to have this section in
Graham Percival schrieb:
There's two months left in GDP. I'd like to reserve one month for
final clean-up and whatnot, so that leaves one month for the bulk
of the work.
Here's my list of what I'm hoping people to finish in July. If you
don't think you can accomplish it, let me know; I shoul
Hi,
Reinhold Kainhofer schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 24. Juni 2008 schrieben Sie:
I don't know about that one, or about how it was before. My Gardner
Notation (did I recall the name correctly) said it should always be aligned
with the middle of the key
Hi
Original-Nachricht
> Datum: Mon, 23 Jun 2008 18:24:21 +0200
> Von: Reinhold Kainhofer <[EMAIL PROTECTED]>
> An: LilyPond Development , Lilypond bug <[EMAIL
> PROTECTED]>
> Betreff: Alignment of metronome marks
> I have now commited my patch that allows text to be included dir
this rearranging work in July, so you can freely start with the file
you like. I guess anyway that translation for this chapter won't start
before August, and there will be enough translation work to do for NR1
and the LM.
Greetings
Till
Francisco Vila schrieb:
2008/6/3 Till Rett
John Mandereau schrieb:
unfretted-strings.itely
fretted-strings.itely
chords.itely
So these are left to me? I'm fine, if it has time until the end of this
month.
Till
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.o
Graham Percival schrieb:
On Thu, 29 May 2008 01:15:12 +0200
"Francisco Vila" <[EMAIL PROTECTED]> wrote:
2008/5/28 John Mandereau <[EMAIL PROTECTED]>:
Till, Francisco,
would you like to do a part of this work?
Count on me, but my GDP contributions will slow down (even more!).
Francisco Vila schrieb:
2008/5/28 John Mandereau <[EMAIL PROTECTED]>:
Till, Francisco,
would you like to do a part of this work?
Count on me, but my GDP contributions will slow down (even more!).
Graham will complain. This month is terrible for me, and summer is
always uncertain. Ple
e but
before I push something wrong could you quickly review the patch and apply?
Thanks
Till
>From 011929280319007861a31a699f55975b12faf251 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Mon, 5 May 2008 19:25:33 +0300
Subject: [PATCH] Update of Document
Hi John
I needed immediately to try the new command line option with xelatex,
and there are some smaller issues that might be interesting: for some
reason xelatex when called by lilypond-book dosn't find the font index,
so it has to build it every time anew itself, or just looks for the
fonts
relevant to that section.
section.
Cheers,
- Graham
On Thu, 24 Apr 2008 08:19:13 +0300
Till Rettig <[EMAIL PROTECTED]> wrote:
I'm fine with this -- the @lilypondfile is a much more powerful
feature that does almost the same.
Till
Graham Percival schrieb:
Does anybody really w
I'm fine with this -- the @lilypondfile is a much more powerful feature
that does almost the same.
Till
Graham Percival schrieb:
Does anybody really want to keep @lsr{} (in addition to
@lsrdir{})? It isn't used in any finished GDP sections, and I'm
90% certain it isn't worth keeping.
@lsrdir
John Mandereau schrieb:
Marcos di Silva wrote:
John Mandereau,
I'm finishing translating Lilypond program messages to pt_BR. I missed
some messages like "syntax error, unexpected %s" [parser.cc] in .pot
file: http://translationproject.org/POT-files/lilypond-2.11.39.pot
How do I translate t
Original-Nachricht
> Datum: Mon, 21 Apr 2008 22:52:37 -0700
> Von: Graham Percival <[EMAIL PROTECTED]>
> An: Till Rettig <[EMAIL PROTECTED]>
> CC: John Mandereau <[EMAIL PROTECTED]>, lily-devel
> Betreff: Re: GDP: translations and code comment
John Mandereau schrieb:
Done. FWIW the script that collects strings to be gettextized found 120
non-unique names of variable definitions and 183 comments in
Documentation/user/*.itely (only snippets with verbatim option are
scanned). input/ is not scanned for now; Francisco, Till, just let me
Marcos di Silva schrieb:
John Mandereau,
I'm finishing translating Lilypond program messages to pt_BR. I missed
some messages like "syntax error, unexpected %s" [parser.cc] in .pot
file: http://translationproject.org/POT-files/lilypond-2.11.39.pot
How do I translate them?
What do you mean w
Francisco Vila schrieb:
2008/4/19, Graham Percival <[EMAIL PROTECTED]>
> Variable names: already translated in @examples, helps clarifying. It
> would be nice to have them translated in verbatim- and non-verbatim-
> snippets. Again, in verbatim mode the translated version could show
> and t
Graham Percival schrieb:
On Sat, 12 Apr 2008 09:33:51 +0300
Till Rettig <[EMAIL PROTECTED]> wrote:
Graham Percival schrieb:
Oh yeah, I remember now. OK guys, here's the problem: we've run
out of headings. Texinfo supports
We need one more. In NR 1+2, we need it
Graham Percival schrieb:
Oh yeah, I remember now. OK guys, here's the problem: we've run
out of headings. Texinfo supports
@heading - used for sections
@subheading - used for subsections
@subsubheading - used for subsubsections
We need one more. In NR 1+2, we need it for the portions of
Reinhold Kainhofer schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 7. April 2008 schrieben Sie:
No, this is not what I meant: If you go into the piano section you see that
the @unnumberedsubsection or how the nodes are created are not translated
in the text, e.g. Automati
Reinhold Kainhofer schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, I didn't check that patch, I thought it was applied already?
No, since the German translation is your responsibility, it's also your task
to approve patches... I can also simply apply it, if you like.
> - Ursprüngliche Nachricht -
> Von: Reinhold Kainhofer
> Gesendet: 07.04.08 02:04 Uhr
> An: Till Rettig, lily-devel
> Betreff: Re: texi2html build system
>
> Am Sonntag, 6. April 2008 schrieben Sie:
> > I guess you are aware that while translated nodes are p
John Mandereau schrieb:
Le dimanche 06 avril 2008 à 08:24 +0200, Reinhold Kainhofer a écrit :
I now made everything build just fine and installed the branch also on
kainhofer.com:
http://kainhofer.com/~lilypond/texi2html-out/Documentation/index.html
There, everything is built with texi2
Hi,
could somebody explain me how ledger-line-thickness behaves? The IR states that
it should be a pair:
"ledger-line-thickness (pair of numbers)
The thickness of ledger lines. It is the sum of 2 numbers: The first is the
factor for line thickness, and the second for staff space. Both contr
Reinhold Kainhofer schrieb:
This gave me an idea:
I've now checked all .itely files in the user manual using ispell with the
american dictionary. Patch is attached, but please double-check all changes
before applying.
Several typos found, also lots of inconsistent British vs. American spel
Hi,
I tried using lilypond-book with other flavours of tex. I don't know how
the context team does it, but with eg. XeLaTeX you have to use a
\ifxetex environment so Latex/PdfLatex will not find any unknown
commands. So I would which some kind of switch with which I could just
tell lilypond-b
Reinhold Kainhofer schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 27. Februar 2008 schrieben Sie:
This is just one of many situations, where you need to explicitly
create the Voice context yourself:
[...]
This is a consequence of the way LilyPond creates new
Mats Bengtsson schrieb:
till wrote:
Paco Vila wrote:
Hello all,
In the tutorial, under @subsubheading Windows, at the end of 2nd
paragraph (line 148) it says
Double-click the
icon to type in your LilyPond source code as before.
Am I wrong, or this makes to process the file rather than
Juergen Reuter schrieb:
Hi all,
as far as I understand, all problems with incipits boil down to the
following two major issues:
(1) horizontal spacing, and
(2) the system start delimiter.
Karl's solution unfortunately leaves horizontal space between the
incipit and the actual score;
Robert Memering schrieb:
Am Montag, 11. Februar 2008 16:36 schrieb Juergen Reuter:
IIRC, the spacing engine maintains a variable that keeps track of shortest
available duration in a peace in computes the ideal distance of larger
note values in a logarithmic scale based on the shortest durat
important.
>From 2d998a6fc1b761b475a3b38d95b5a6abc6a5bdc0 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED](none)>
Date: Thu, 7 Feb 2008 16:40:10 +0200
Subject: [PATCH] Add warning about translation status
---
Documentation/de/index.html.in |6 ++
1 files changed, 6 i
Nicolas Sceaux schrieb:
Le 7 févr. 08 à 02:49, Han-Wen Nienhuys a écrit :
Since the incipit is a completely
different piece of notation (eg. whose spacing and beat counting
should not influence the main music), this should be implemented
similiar to the hack with a \score inside the instrume
John Mandereau schrieb:
Hi,
As I'm responsible for LilyPond translations, I'd like to mark more
message strings to be translated, especially in musicxml2ly and
convert-ly.
As for convert-ly, I've already marked messages that end "not smart
enough to convert...", and I wonder whether it's impo
Nicolas Sceaux schrieb:
Le 3 févr. 08 à 21:07, Till Rettig a écrit :
Whow, this is really great. I guess from that base it is somehow
simple to have also
changing of notehead/flags etc styles possible -- and not to forget:
for most socres
of renaissance music the ligature-engraver will have
Mats Bengtsson schrieb:
Robert Memering wrote:
I think the most important drawback in the instrument name
approach is that the horizontal spacing is very awkward,
e.g. long rests (several longae) or ligatures plus single
notes have unwanted space in between. If only one could
"turn off" spa
1 - 100 of 250 matches
Mail list logo
