I am trying to typset a choral piece with half bar-lines in different places
in different voices.
The two approaches I have seen is to use polymetric notation or possibly
subverting the /breathe command to get the desired effect.
I have been trying to cut and paste examples from the manual,
Just to further clarify, this is the problem I am trying to overcome:
/In scores with many staves, a \bar command in one staff is automatically
applied to all staves. The resulting bar lines are connected between
different staves of a StaffGroup, PianoStaff, or GrandStaff./
I am trying to print
2013/6/23 DW jdmusictuit...@gmail.com:
I am trying to typset a choral piece with half bar-lines in different places
in different voices.
The two approaches I have seen is to use polymetric notation or possibly
subverting the /breathe command to get the desired effect.
I have been trying to
Hi. The example in the attachment shows that the current whiteout mechanism is
not perfect. As far as I know, it works by drawing white box in the background
of the text. This solution, however, has one drawback: sometimes bar line isn't
broken in it's full width and that looks ugly. (see
Hi,
2013/6/23 Karol Majewski karo...@wp.pl:
Hi. The example in the attachment shows that the current whiteout mechanism
is not perfect. As far as I know, it works by drawing white box in the
background of the text. This solution, however, has one drawback: sometimes
bar line isn't broken
Hi Janek. Here's a similar example:
upper = \relative c'' {
\clef treble
\key c \major
\time 4/4
a4 b c d
a b c d
}
lower = \relative c {
\clef bass
\key c \major
\time 4/4
a4 b c d^w..
a b c d
}
\score {
\new PianoStaff
\set PianoStaff.instrumentName =
Ah, thanks. I was using the latest stable version which is 12.16.2, updating
to the unstable version did the trick.
Thanks again
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147287.html
Sent from the User mailing list
Am 23.06.2013 15:59, schrieb DW:
Ah, thanks. I was using the latest stable version which is 12.16.2, updating
to the unstable version did the trick.
It is a really common source of problems that people use examples from
manuals not matching their LilyPond version ...
Urs
Thanks again
--
Urs Liska u...@openlilylib.org writes:
Am 23.06.2013 15:59, schrieb DW:
Ah, thanks. I was using the latest stable version which is 12.16.2, updating
to the unstable version did the trick.
It is a really common source of problems that people use examples from
manuals not matching their
For the manual version problem, this arises largely because the manuals are
laid out in such a way as to force one to do a google search on more obscure
implementations, at that point it is very hard to see where you end up
because you are opening 50 tabs that might lead you in the right
Maybe in 20 years time once the development has slowed down some can go back
and comprehensive comprehensible manual, but as it is one has to rely on
googling increasingly obscure search terms to do some of the less common
things that is required when typesetting.
--
View this message in
Just to clarify: It often seems as if the simple, obvious things are all in
one easily accessible place but the more fine grained stuff is hidden
somewhere completed different.
What would really be helpful is for the manual to be a singular thing where
even detail conceivably related to bar-lines
DW jdmusictuit...@gmail.com writes:
For the manual version problem, this arises largely because the
manuals are laid out in such a way as to force one to do a google
search on more obscure implementations, at that point it is very hard
to see where you end up because you are opening 50 tabs
That's what I'm referring to (if I am understanding you correctly).
If I want information on barlines I should go to BARLINES, not
LearningBarlines or UsageBarlines or NotationBarlines or
SnippetsBarlines. Just BARLINES.
Never mind various manuals for different version numbers added on top of
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-user@gnu.org
Sent: Sunday, June 23, 2013 3:48 PM
Subject: Re: Cut and paste from manual returns errors
DW jdmusictuit...@gmail.com writes:
For the manual version problem, this arises largely because the
manuals are
DW jdmusictuit...@gmail.com writes:
That's what I'm referring to (if I am understanding you correctly).
If I want information on barlines I should go to BARLINES, not
LearningBarlines or UsageBarlines or NotationBarlines or
SnippetsBarlines. Just BARLINES.
If you want extensive information,
I don't want to harp on this point, but it is significant that when I mention
to people that I use Lilypond their faces curl up and frumple. Usually a
little prodding reveals that they have encountered the manuals.
I have invested a little time in trying to figure them out, and I find them
highly
Hello,
most people will do what I did at first, go to the search box on the
lilypond page, type in barlines and proceed to be baffled and confused.
I have literally never used that search box before.
I don't even think it makes sense there — at the very least, it should be next
to the
I also prefer blog.lilypond.org
But lilypondblog.org would be fine, and it looks like the path of least
resistance and the more likely outcome given the previous discussion.
--
View this message in context:
- Original Message -
From: DW jdmusictuit...@gmail.com
To: lilypond-user@gnu.org
Sent: Sunday, June 23, 2013 4:47 PM
Subject: Re: Cut and paste from manual returns errors
I don't want to harp on this point, but it is significant that when I
mention
to people that I use Lilypond their
I am more than happy to volunteer, and I realise that it is easy to point
these things out but much harder to actually fix them.
http://lilypond.org/manuals.html
...is next to useless is you are looking for anything but the simplest
implementations.
The divisions are not really sensible.
I
Kieren MacMillan wrote
Hello,
most people will do what I did at first, go to the search box on the
lilypond page, type in barlines and proceed to be baffled and confused.
I have literally never used that search box before.
I don't even think it makes sense there — at the very least, it
Hi,
How do I get directly from here: http://lilypond.org/manuals.html to where I
need to be in my example in the post above?
There should be a Search v2.16.2 Documentation field — instead of, or in
addition to, the one that's currently in the upper nav bar — which does a
search on the
Yes, that would be a simple solution, maybe even just with a drop down menu
to select version numbers for stable/unstable.
I would venture that would already be an enormous improvement even if it
isn't a complete fix when it comes to the more obscure stuff.
--
View this message in context:
p.s.
I would venture that would already be an enormous improvement even if it
isn't a complete fix when it comes to the more obscure stuff.
For the more obscure stuff, I would imagine a very good — and possibly complete
— solution would simply be a matter of getting volunteers to add index
Hi,
2013/6/23 DW jdmusictuit...@gmail.com:
I am more than happy to volunteer, and I realise that it is easy to point
these things out but much harder to actually fix them.
http://lilypond.org/manuals.html
...is next to useless is you are looking for anything but the simplest
Thanks, I will take you up on that if you don't mind :)
I am more than happy contribute my time and effort to such an indexing
effort, I think something of that nature would help enormously to improve
the general usability of what I consider to be by far the best music editor
available.
While we
2013/6/23 DW jdmusictuit...@gmail.com:
[...]
If I am looking for a way to separate a notehead from its stem, how would I
go about finding this information?
_
First step, according to the advice here is the manual index. But which
manual do I choose?
2013/6/23 DW jdmusictuit...@gmail.com:
While we are on the topic of general improvements. One way I have found that
makes editing a lot easier is to export snippets to .jpg and then using
picture editors for larger scale alignments.
One problem with this approach is, that we've several blind
DW jdmusictuit...@gmail.com writes:
Thanks, I will take you up on that if you don't mind :)
I am more than happy contribute my time and effort to such an indexing
effort, I think something of that nature would help enormously to
improve the general usability of what I consider to be by far
2013/6/23 DW jdmusictuit...@gmail.com:
While we are on the topic of general improvements. One way I have found that
makes editing a lot easier is to export snippets to .jpg and then using
picture editors for larger scale alignments. My problem is that many .pdf to
.jpg converters often leave
Janek Warchoł janek.lilyp...@gmail.com writes:
2013/6/23 DW jdmusictuit...@gmail.com:
While we are on the topic of general improvements. One way I have found that
makes editing a lot easier is to export snippets to .jpg and then using
picture editors for larger scale alignments. My problem is
- Original Message -
From: DW jdmusictuit...@gmail.com
To: lilypond-user@gnu.org
Sent: Sunday, June 23, 2013 8:28 PM
Subject: Re: Cut and paste from manual returns errors
While we are on the topic of general improvements. One way I have found
that
makes editing a lot easier is to
On 24/06/13 01:19, DW wrote:
That's what I'm referring to (if I am understanding you correctly).
If I want information on barlines I should go to BARLINES, not
LearningBarlines or UsageBarlines or NotationBarlines or
SnippetsBarlines. Just BARLINES.
Never mind various manuals for different
Am 23.06.2013 23:14, schrieb Mark Polesky:
Urs,
I missed the big discussion earlier, but has anyone mentioned FreeSerif?
Not that I recall ...
http://www.fontspace.com/gnu-freefont/freeserif
I'm getting some good results with lyrics. I particularly like that it has all
5
of the common
I'm new at this and expect to be drawing from this well, so, at the risk of
providing common knowledge, I'll contribute what I know about this subject
and how I plan to go about preparing .pdf pages for current publishing
project.
As a Quark and InDesign user, I have been very happy with the
How about considering Gentium Plus once the bold and bold italic faces
are available (at the moment Gentium Plus contains only regular and
italic faces). It's released under the SIL open font license
(http://scripts.sil.org/cms/scripts/page.php?site_id=nrsiid=OFL) and
contains virtually all
Urs,
I missed the big discussion earlier, but has anyone mentioned FreeSerif?
http://www.fontspace.com/gnu-freefont/freeserif
I'm getting some good results with lyrics. I particularly like that it has all
5
of the common English ligatures 0xFB00 - 0xFB04 (ff fi fl ffi ffl). Century
Schoolbook
Urs Liska wrote:
http://www.fontspace.com/gnu-freefont/freeserif
...
test sentence with ligatures:
office flight raffle, final offer
test sentence, spelled out completely:
office flight raffle, final offer
I just could only look at the samples on the page you linked, but it
looks quite
On 24/06/13 08:09, ed shaw wrote:
I'm new at this and expect to be drawing from this well, so, at the risk of
providing common knowledge, I'll contribute what I know about this subject
and how I plan to go about preparing .pdf pages for current publishing
project.
As a Quark and InDesign user, I
Am 24.06.2013 00:32, schrieb Nick Payne:
How about considering Gentium Plus once the bold and bold italic faces
are available (at the moment Gentium Plus contains only regular and
italic faces). It's released under the SIL open font license
On 24/06/13 09:58, Urs Liska wrote:
Am 24.06.2013 00:32, schrieb Nick Payne:
How about considering Gentium Plus once the bold and bold italic faces
are available (at the moment Gentium Plus contains only regular and
italic faces). It's released under the SIL open font license
Yeah, DW, I see what you mean. I'm in the process of setting up a MAC. So
far, can't get the
resolution. I'll work on that tomorrow. Looks like crop copy and paste is
not going to be good
enough.
--
View this message in context:
43 matches
Mail list logo
