Francisco Vila wrote:
As for the line number syncing between files and their translations, I realize this is not soo important, BUT it is still a very eye-straining task
to keep track of updates when (for instance) the original simply moved a block from a place to another.
How do you do th
notice that. Are actually all untranslated docs also created in all
languages so I should already update the program/internal -links, or
should I do it only when I start translating?
Well, so far the patches for today's updates.
Greetings
Till
>From a96cdc174fc5c85de1b3180f323ea2579753bf71 Mon
Hi,
I won't get "mensurstriche"-barlines anymore with the last few 2.11.x
versions. It used to be, with the command \override BarLine
#'transparent = ##t in the score context, that only the barlines on
staves would be made transparent, not _between_ staves. See example
D.5.1 -- there used to
Joe Neeman wrote:
On Wednesday 05 September 2007 07:58, Graham Percival wrote:
I believe this is
http://code.google.com/p/lilypond/issues/detail?id=377
You could help Joe by creating a minimal example.
Don't bother -- I have a fix in my working copy.
Great, I can wait for that.
Hello,
from what so far has been discussed I catched somewhat the need is to
group the issues more into "single topic" sections of subsections.
For the discussion about the format of the html-docu: I would rather
like to have whole subsections downloading than those tiny pages -- I
also get l
Original-Nachricht
> >
> > Hello,
> >
> >> For instance I could imagine
> >> a chapter "Ancient music", and one on educational subjects. At least I
> >> don't see why Ancient is "instrument specific", so why not put it in 7
> >> from the current suggestion, right after education
Hi,
I would suggest to remove lines 46 to 48 from
Documentation/user/setup.itely.
They are repetition of two lines earlier.
Greetings
Till
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
while translating the running.itely I stumbled on the section 3.2.1 --
invoking lilypond. Why are there .tex files and why should files with
different \scores get output to numbered files? I have not yet heard
about this, couldn't we tell it in a way, that I know what to translate?
To me
Hi John,
here is a patch for the setup.itely file.
Hope the GDP has started smoothly...
Greetings
Till
>From 35ebfdfc3f80c56b9fd612701fd9cdd82566252b Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Tue, 18 Sep 2007 21:55:48 +0300
Subject: [PATCH] Translation of se
Juergen Reuter wrote:
On Tue, 18 Sep 2007, Reinhold Kainhofer wrote:
...
Fortsetzung, die Finger kreuzen
Segmentation fault
By the way, I guess a proper translation of "crossing fingers" into
German would be something like "Daumen druecken"... Till, what do you
think?
Sounds great! I
John Mandereau wrote:
I seems that running.itely has not been revised for ages, so it contains
somewhat outdated info. If you feel comfortable with updating this
section in the English docs, please do it first, then go on translating
this file; otherwise, it may be more productive to give up t
At least for the German translation I had really problems finding a word
for that -- I think it is still untranslated... Is there any real term
for this that could then also be translated easily?
On the other hand -- so far we have this term, so it really should show
up in the glossary if transl
Hallo Henning!
I am also happy to see support for German growing slowly -- I am so far
the only active translator for German, but will be happy about any
comments/help... Posting here in this list should be in English, but
sure we can communicate privately in German -- there is also the
possi
Hi John
saw the typo also in the German file, here a fix.
Further I uncommented the line for BAnd in a Box file converting: the
link is dead. Should we do this to all languages?
Greetings
Till
>From 94d7f8bf2f7393c49e2950f0aaf9f465905a84ac Mon Sep 17 00:00:00 2001
From: Till Rettig <
Hello,
what happened that all regressiontests by Reinhold are automatically
added to the Examples directory (but not being translated)? Is this
intended behaviour or a bug? At least I think for a user looking for
some nice examples it seems really strange to have these files and only
down on
Hello,
I get this error when making web on lilypond/translation branch:
./introduction.texi:1099: pdfTeX error (ext4): \pdfendlink ended up in
differen
t nesting level than \pdfstartlink.
\onepageout ...\ewbot \hfil \ewbot }}\egroup \fi }
}\advan
John Mandereau schrieb:
I've not compiled GDP for one or 2 weeks, so I don't know, but current
master revision compiles fine on my i686 Fedora 7 box, so I updated
lilypond/translation with master. If the compilation still fails for
you, make sure
- you have installed Texinfo 4.11
- you have re
Hi,
updates to the webpage. Please apply!
Greetings
Till
>From 25ef526fc8d18c4a3002004021325a332c316234 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED](none)>
Date: Wed, 14 Nov 2007 18:25:55 +0200
Subject: [PATCH] Updates to German translation
---
de/about/faq.html
John Mandereau schrieb:
Hi Till,
I'm surprised that the new de.po only differs by the revision date, it
contains no new changes. Can you please double-check that
http://translationproject.org/latest/lilypond/de.po really contains your
changes?
Yes, that is strange, but I will figure it ou
Hi Graham,
seems for one time I can help you... :-)
I had the same problem, and it resulted because I had forgotten to
install also the texfiles from texinfo. So there has to be done:
./configure, make, make install and make TEXMF=your/path tex-install.
Check it from the README. After mktexlsr
John Mandereau schrieb:
Hello translators,
There are some doc sections you can start updating:
- doc PO (don't translate titles named "* sections" or "* FIXME" or
"TODO blah", they are temporary).
- documentation index (index.html.in)
- user/*.tely (NOT .itely files)
Good news, I was alrea
Hi John
I am more and more noticing that for really consequent translation work
we really need a glossary of all the tricky words (that is, not only
musical terms, but also those words that we agree on a specific word for
the translation). This is even more important when there are more than
til the new versions will be ready?
Greetings
Till
>From a10dfbe19decdc5e7c921ae884d93d19fc53dbdc Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED](none)>
Date: Wed, 28 Nov 2007 18:44:47 +0200
Subject: [PATCH] Partly update of Documentation de.po
---
Sorry, I try to say it in a way that it might be added to the docs.
In 5.2.1 the @refbugs (line 495 in spacing.itely on master) it states:
"@code{layout-set-staff-size} does not change the distance between the
staff lines."
Could we add a sentence:
"Use instead the pair
fontSize
page layout. It would then also be possible
to refer to that chapter from the LM.
Till
Trevor D
-Original Message-
From: [EMAIL PROTECTED]
[mailto:lilypond-user-bounces+t.daniels=treda.co.u
[EMAIL PROTECTED] Behalf Of
Till Rettig
Sent: 05 December 2007 16:49
To: Graham Perciv
John Mandereau schrieb:
I've committed a dirty change to make outdated titles appear in the POs.
I hope this is temporary (I expect to change it back when GDP is done).
I've also run po-update in Documentation. With this new hack, you
shouldn't translate all entries, translate only entries in
John Mandereau schrieb:
Possible options for storing translation ressources are
- the unofficial wiki, as Jean-Charles proposed,
- a git branch (maybe it would be too confidential),
- a site shared by many translators (the better option I think, but also
the most difficult to organize).
Ok,
Graham Percival schrieb:
Proposal: deprecate \times, use \tuplet instead.
I think it is worth doing this -- it is really confusing as is.
Till
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-
Graham Percival schrieb:
Yes. The new preferred way to get new material in the docs is to
start off with a snippet in LSR. Once that's been approved, we can
link to this in the Snippets section. From there, we might include
the lilypond code directly.
This is a new way of doing things; L
Sorry, I meant to append a file demonstrating the spacing. Here it comes.
Till
\version "2.11.33"
global = {
\key f \major
\time 2/2
\override Staff.TimeSignature #'style = #'neomensural
%\override Voice.NoteHead #'style = #'neomensural
%\override Voice.NoteHead #'style = #'mensural
Graham Percival schrieb:
Are you referring to x11-color, or normal colors? If it's x11, I
really don't think it's worth keeping them in the docs at all. If
you're curious though, search the mailist archives. Trevor Baca made
a .ly file that demonstrates them all; I think this was approxi
Graham Percival schrieb:
Please add a snippet to LSR.
Sorry, one of us doesn't probably understand right. I thought about
enhancing the table that is in the docs. So I would not really make a
feature that would be useful to anybody but just show the colours in the
printed output (html and p
Hi all, who are interested in Ancient notation.
I started now some trial how to improve the spacing of the notes. The
goal is to have an even spacing where each note head regardless of their
length takes up just the same space. Visible signs in the score as
accidentals, clefs and lyrics should
king for!
Till
Reinhold Kainhofer schrieb:
Am Samstag, 8. Dezember 2007 schrieb Till Rettig:
Please have a look at the lilypond example I created using direct post
script commands. It is an ugly hack, I suppose, but might illustrate
what I am after.
Hehe, you know the filled-box funct
Sure, I will do that.
Valentin Villenave schrieb:
2007/12/7, Till Rettig <[EMAIL PROTECTED]>:
Sorry, I meant to append a file demonstrating the spacing. Here it comes.
Hi Till,
thank you very much for all this work; we do need a few people to care
about Ancient notation :)
John Mandereau schrieb:
Le samedi 15 décembre 2007 à 14:38 +0200, Till Rettig a écrit :
Hi John,
here a patch to lilypond/translation for the glossary. I mainly updated
German translations, also two or three Finnish.
Thanks, but could you please send another patch without removing
John Mandereau schrieb
It's an involved task; I wonder whether it's worth doing it, as there
are few translators. Something that could be done in that direction is
formatting TRANSLATION in Texinfo or Wiki, to start a real "translators
guide". IMHO it's not a priority, Lily translators could
e
English translation of the word custos, it would be "Weiser" in German.
Greetings
Till
>From d34f728c109dc8d07369217c0a3536bc1b5b6054 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED](none)>
Date: Sat, 15 Dec 2007 14:34:11 +0200
Subject: [PATCH] Correctio
Sorry, this file doesn't compile on 2.10. I chose the version-specific
but since lsr is running on 2.10 it won't take the file anyways. On 2.11
I don't get any mistakes. Should I just wait until 2.12?
Till
Valentin Villenave schrieb:
2007/12/7, Till Rettig <[EMAIL PROTECT
Hello Juergen,
thanks for the reply! Again, as almost one year ago, your mail is full
of really good hints! I should just know a bit more about programming --
hope I will be able to learn something about it...
[EMAIL PROTECTED] schrieb:
Hi, Till!
Very nice to hear that there are people stil
Graham Percival schrieb:
I think that in a few places I used a FIXME to mark missing
translations.
If anybody wants to maintain the glossary (Till?),
Hmm, I will think about it, actually I thought Kurtis would do this kind
of work.
Well, I will have time only in January, but I will put it on
Hi Graham,
as a reaction to this thread
http://www.nabble.com/creating-Schenkerian-Graphs-in-Lilypond-td14418187.html
on the bug list, I thought you might wellcome some additions to the
convert-ly discussion in the AU (file running.itely).
I would suggest a text like
@subsection Help for Wi
Hi,
nice that there are some people who use this... I have a totally new
idea in mind, which is only to put the incipit as a markup into the
instruments name. That is, you write an identifier like incipitcantus
which looks like:
incipitcantus=\markup{
\score{
{
\set Staff.ins
Stefan Slapeta schrieb:
Juergen Reuter wrote:
Instead, my idea of the ultimate way of incipit creation is to have
an \incipit scheme function that automatically creates an incipit for
a given music expression.
[...]
I think this would be quite complicated as you have a lot more of
conf
Hello,
I am trying to have an incipit as part of the instrument name for each
staff. The example explains how it should look.
This goes to far well if there are no lyrics, the systems get aligned.
But if I add lyrics as in the example, there is obviously
added so much additional vertical space
nment-Y = #0.31
and
\override InstrumentName #'Y-offset = #-1.9
- both not very smart (because hard coded)
Stefan
Till Rettig wrote:
Hello,
I am trying to have an incipit as part of the instrument name for
each staff. The example explains how it should look.
This goes to far wel
Hi documentation editors,
I started translating the tutorial, or updating, as quite a lot can be
still used as I discovered. I had to add the macros notation and warning
to the macros.itely in the language/user directory and clean up the
macros defined for tex compilation down the file. I ment
Hi again,
I just was thinking about the parts of the tutorial that refer to the
terminology in the glossary: Should we keep them, so that somebody who
doesn't know the meaning of some term can look its (English) description
up in the glossary? Or should we delete them in the translated version
Stefan Slapeta schrieb:
With some trial and error I managed in the D.5.1 ancient music template to
move the SystemStartBracket (using #'extra-offset) towards the end of the
incipit so that it is placed at the beginning of the modern notation.
Attached an image. I'm sure with \startStaff and \st
John Mandereau schrieb:
If I understand well the purpose of @notation well (see
Documentation/user/writing-texinfo.txt), this macro is used to mark
phrases from music notation terminology. As this is an identity macro
(it exactly returns its argument), you can of course translate its
contents
Valentin Villenave schrieb:
Hi everybody,
I just wanted to mention that the templates are currently been moved
to the LSR: for instance have a look at
http://lsr.dsi.unimi.it/LSR/Item?id=363
or
http://lsr.dsi.unimi.it/LSR/Item?id=364
If you want to contribute a new template, you're welcome
Hello,
I realized that I did some commits to my local copy of master, but I
don't get the remote revisions to make a patch out of it.
That is how I pull:
git pull git://git.sv.gnu.org/lilypond.git
Obviously I forgot to name my local branch (?) -- when I call git
show-branch, it says: [master]
David Kastrup schrieb:
Till Rettig <[EMAIL PROTECTED]> writes:
How can I refer to the remote branch? If I say: git rev-parse
git://git.sv.gnu.org/lilypond.git
I get only the message that the revision is unknown, the same for
format-patch...
Try
git rebase origin
and then y
Johannes Schindelin schrieb:
Hi,
On Mon, 7 Jan 2008, Till Rettig wrote:
Obviously I forgot to name my local branch (?)
More like the remote branch: a pull will always be into your current
branch.
-- when I call git
show-branch, it says: [master] Merge git://git.sv.gnu.org
Hello,
I realized that there seems to be some strangeness with staccato dots
positioning: in my opion they are too close to beams when setting
polyphonic music with \voiceOne and \voiceTwo.
Also I saw that the spacing gets influenced by accidentals (?). This
matters only when the dots are abov
ave schrieb:
2008/1/12, Till Rettig <[EMAIL PROTECTED]>:
Hello,
I realized that there seems to be some strangeness with staccato dots
positioning: in my opion they are too close to beams when setting
polyphonic music with \voiceOne and \voiceTwo.
I I understand you correctly, this
Hi Valentin,
I tried updating the snippet I posted (about ancient incipit), but I
can't edit it, I don't know what the mistake is.
Then I have another thing here, a "workaround" from the list about one
year ago. It is about marking the notes of spoken parts with a cross on
the stem. It is no
From the user's point of view I am really happy with a change to this
situation.
I would be really fine with tuplet, but also factor seems to me (also
German speaker :-)
a good solution.
In my opinion the best for now would be a alias with changes in the
documention --
change all mention of tim
Werner LEMBERG schrieb:
Folks,
the TeX-Gyre project (financially supported mainly by the German TeX
Users' Group, DANTE) is developing replacements for the set of common
URW fonts. The project isn't finished yet, but already now the glyph
repertoire has almost doubled, compared to the set of
Han-Wen Nienhuys schrieb:
2008/1/28, Werner LEMBERG <[EMAIL PROTECTED]>:
You can insert any UTF-8 character and LilyPond will render it as
long as Pango can find a font installed on your system that includes
a glyph for that symbol. Pango also handles kerning and ligatures
automatically,
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 to be added to the
score and
the ligature bracket engraver removed (which
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
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
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 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
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
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
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
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
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:
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,
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
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
> - 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
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.
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
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
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
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
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
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
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:
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
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
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
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
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
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
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!).
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
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
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
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
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
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
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
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
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
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
101 - 200 of 250 matches
Mail list logo
