Is there any mechanism for reporting bugs on the LP web pages? Or do the LP
team read these emails?
The link to the LSR on the "Snippets" page has a typo: http://lsr.dsi.unimi.it/
instead of http://lsr.di.unimi.it
Regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
Hi Peter
This was fixed in January, but only the 2.19 version has the correct
link:
http://lilypond.org/doc/v2.19/Documentation/snippets/index.html
I don't know if we have a proper and easy way to backport it to 2.18
Il giorno sab 17 dic 2016 alle 10:45, Peter Toye
ha scritto:
Is there any
Federico,
Thank you very much. At the moment I'm still on 2.18 so I'm using those manual
pages. I can't download 2.19 until Kaspersky have fixed their false positive
bug. Also, it's not a stable release, and I'm fed up with debugging other
people's software - I spent far too much of my professi
On 17.12.2016 10:45, Peter Toye wrote:
Is there any mechanism for reporting bugs on the LP web pages? Or do
the LP team read these emails?
It’s very likely that the Bug Squad people also follow the -user list,
though the proper proceeding is to report to bug-lilyp...@gnu.org, both
for program
Hello Peter,
Although 2.18 is the nominal stable release, I have found from experience
that the development releases are remarkably clean and stable. I engrave
massively complex modernist scores with a large amount of Scheme
customization and only once in several years have I encountered a bug tha
Andrew,
Thanks for these comments. I take your point about the stable releases, but
I've had my fingers badly burned in the past (not by Lilypond) from using
development-stage software. It's taken a lot of correspondence with the vendor
and wasted a lot of time. Sometimes, it's even a full rele
I have again been trying to build up a sensible files-and-variables
structure for more complex scores (e.g. orchestral pieces with several
movements), and I seem once again to have run into the limitation that
'book' and 'bookpart' have no scope for variables.
So I thought I would try Jan-Peter's p
I have never worked with TeX and its relatives, so my only experience is in
plain LY files.
For those not familiar with lyluatex, the way I'm using it works as follows:
1) Inside a the TeX file there is a pointer to the lilypond source file
of the snippet I want to include.
2) When LuaTeX pr
http://lsr.di.unimi.it/LSR/Snippet?id=197 using pure English alphabet it
complies
I try to compile the above LSR using English and UTF-8 as file name, I got the
error below:Starting lilypond-windows.exe 2.18.2 [filename_名字.ly]...Processing
`C:/Users/user/Google
Drive/CHOIR_2016/filename_��
On 17.12.2016 17:02, MING TSANG wrote:
UTF-8 as file name
It does not come as a surprise that non-ASCII file names cause trouble
on windows. Simply don’t do that.
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.o
sorry I hit the wrong key before I complete the email.Here is the other email
message intended to send.I attached a small snippet contains UTF-8 in file name
if compile fine with pdf file name contains the UTF-8.However the log file
cannot display UTF-8 file name (see red text below).Starting
l
As Simon says - if you know that UTF-8 characters in filenames cause problems,
why do you use them? Stick to ASCII.
--
Phil Holmes
- Original Message -
From: MING TSANG
To: Lilypond-usermailinglist ; Andrew Bernard ; Thomas Morley ; David Kastrup
; David Wright
Sent: Saturd
Simon,Thank you for your quick response.Window 10 has no problem use UTF-8 .ly
file. after compile through Frecobaldi .pdf and .mid files are created. It
seems that internal working of lilypond and its associated programs not
handling it. I was wondering there is a work-around?Immanuel,Ming.
Further to my earllier message, I have realized that the problem I am
getting has nothing to do with variable scope (at least, I don't think
it does), so I was asking the wrong question.
But the problem still exists.
My abbreviated file now looks like this:
%
\version "2.19.48"
\language "engli
On 17.12.2016 17:41, MING TSANG wrote:
Window 10 has no problem use UTF-8 .ly file. after compile through
Frecobaldi .pdf and .mid files are created.
It seems that internal working of lilypond and its associated programs
not handling it. I was wondering there is a work-around?
Well, you were
Hello all,
Is there a way to make LilyPond ignore collisions or spacing issues between
a markup text and other staves or grobs? For instance, consider this example
below:
\version "2.19.37"
\new PianoStaff <<
\new Staff {
des''4
f''
e'_\markup{
\hspace #-1.5
\center-c
On 17.12.2016 19:17, Gilberto Agostinho wrote:
Is there a way to make LilyPond ignore collisions or spacing issues between
a markup text and other staves or grobs?
Hi Gilberto,
try wrapping the markup in
\markup {
\with-dimensions-from \null {
% insert your markup here
}
HTH, Simon
_
Hi Simon,
Simon Albrecht-2 wrote
> try wrapping the markup in
> \markup {
>\with-dimensions-from \null {
>% insert your markup here
> }
Thanks for your reply, that's exactly what I was looking for! I really
appreciate your help.
Cheers,
Gilberto
--
View this message in context:
http
On Sat 17 Dec 2016 at 16:31:33 (+), MING TSANG wrote:
> sorry I hit the wrong key before I complete the email.Here is the other email
> message intended to send.I attached a small snippet contains UTF-8 in file
> name if compile fine with pdf file name contains the UTF-8.However the log
> fi
On Sat 17 Dec 2016 at 18:38:59 (+0100), Simon Albrecht wrote:
> On 17.12.2016 17:41, MING TSANG wrote:
> >Window 10 has no problem use UTF-8 .ly file. after compile
> >through Frecobaldi .pdf and .mid files are created.
> >It seems that internal working of lilypond and its associated
> >programs n
David,Thank you for showing that LSR-197 compiles fine with utf-8 characters on
Debian. I think under window 10, this should be the same.Lilypond has no
problem reading and display (output) utf-8 characters. On window 10 llilypond
produces utf-8.pdf utf-8.mid; utf-8 _header (title, subtitle,
On 2016-12-17 02:53 AM, Federico Bruni wrote:
Hi Peter
This was fixed in January, but only the 2.19 version has the correct
link:
http://lilypond.org/doc/v2.19/Documentation/snippets/index.html
I don't know if we have a proper and easy way to backport it to 2.18
I'm not sure what the bug m
How would I define a bar line such that the top is in the middle of the
top staff space and the bottom in the middle of the bottom staff space
(i.e. what would be called a divisio minor if I was typesetting
Gregorian chant, except on a modern 5-line staff).
Also, is there a way to make the tic
Hi Samuel,
LSR 104 I believe.
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Simon,David & Phil:
It seems that UTF-8_filename.ly is not working on LSR-197.I am using the
following snippet to hard-code the file information (ie UTF-8_filename.ly) and
put it in header-copyright. Though, it only displays on first page. I was
hopping LSR-197 will provide file information
On Thu 15 Dec 2016 at 20:32:47 (+0100), Jean Brefort wrote:
> Le jeudi 15 décembre 2016 à 19:16 +, Peter Toye a écrit :
> > As far as I can tell, all I did was move a few files into different
> > directories. And I am now getting this message when it tries to
> > convert the PS file to PDF. The
For those interested,
I made some improvements to the solution for this. It now accounts for whether
the stems are up or down, so as to match what is commonly done in modern
tablature.
I intend to make a tablature template incorporating this solution here also,
http://lists.gnu.org/archive/h
Il giorno dom 18 dic 2016 alle 1:58, Colin Campbell ha
scritto:
Hi Peter
This was fixed in January, but only the 2.19 version has the correct
link:
http://lilypond.org/doc/v2.19/Documentation/snippets/index.html
I don't know if we have a proper and easy way to backport it to 2.18
I'm not
28 matches
Mail list logo
