Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks
Issue 617: X-offset works in a specific way for RehearsalMarks http://code.google.com/p/lilypond/issues/detail?id=617 Comment #4 by v.villenave: Yes indeed; so, that leaves us already with two convenient solutions; many thanks to Neil, Mats and Nicolas. We have to document it as a @knownissue somewhere; let's just find where the most convenient place would be. Issue attribute updates: Summary: X-offset works in a specific way for RehearsalMarks Cc: gpermus Labels: -Type-Enhancement Type-Documentation -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 617 in lilypond: X-offset should take the specified alignment method into account
Issue 617: X-offset should take the specified alignment method into account http://code.google.com/p/lilypond/issues/detail?id=617 Comment #3 by n.puttock: Like Mats says, you could use ly:make-simple-closure to add the extra offset, but wouldn't it be easier just to override the time signature's break-align-anchor-alignment instead? I'm assuming that the idea is effectively to set a position for the rehearsal mark which is equivalent to (left-aligned + one staff space right). Regards, Neil -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: feedback to the latex-program option of lilypond-book
Sorry, I don't know how to set fonts inside of xelatex (there are
examples for plain xetex though on the webpage) without the fontspec
package, but it comes bundled with xetex I think so it is quite a
prerepuisite of the program. My file was derived from the template I
sent sometimes to the list:
\documentclass{article}
%\usepackage{ifxetex}
%\ifxetex
%xetex specific stuff
\usepackage{xunicode,fontspec,xltxtra}
\setmainfont{Gentium}%works
%/setmainfont[Numbers=OldStyle]{Gentium}%this fails
\setsansfont{DejaVu Sans Mono}
%\else
%This can be empty if you are not going to use pdftex
%\usepackage[T1]{fontenc}
%\usepackage[utf8]{inputenc}
%\usepackage{mathptmx}%Times
%\usepackage{helvet}%Helvetica
%\fi
%Here you can insert all packages that pdftex also understands
\usepackage[ngerman,finnish,english]{babel}
\usepackage{graphicx}
\begin{document}
\title{A short document with lilypond and xelatex}
\maketitle
Normal \textbf{font} commands inside the \emph{text} work,
because they \textsf{are supported by \LaTeX{} and XeteX.}
If you want to use specific commands like \verb+\XeTeX+, you
should include them again in a \verb+\ifxetex+ environment.
You can use this to print the \ifxetex \XeTeX{} command \else
XeTeX command \fi which is not known to normal \LaTeX .
In normal text you can easily use lilypond commands, like this:
\begin{lilypond}
{a2 b c'8 c' c' c'16 c'16}
\end{lilypond}
\noindent
and so on.
\end{document}
%%%
The file contains all the ifxetex package stuff, just commented out, the
two relevant lines are the \setmainfont command lines. There are no old
style numbers in Gentium, so you get a warning. I just read in the
fontspec documentation that the package issues quite a lot of warnings
on purpose, but you can switch them off with the [quiet] option for the
package. Didn't try though.
Hope this helps already a bit.
Till
John Mandereau schrieb:
[moved from lilypond-devel to bug-lilypond]
On 2008/04/26, Till Rettig wrote:
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 -- but as a result the compilation takes really a long time. And
then I was somehow astonished about the unforgivingness of
lilypond-book: even if there is only a warning issued by xelatex I get a
"failed" and the compilation is stopped. The warning is issued by the
fontspec package that the font doesn't support a specific font feature I
called.
Does this warning also happen with a full document with the same
specific font feature is directly processed with xelatex?
If xelatex exits with non-zero, it should mean that the warning is to be
considered as an error. Do you know where xelatex exit codes are
documented?
And the last: xelatex gives this message:
Running xelatex...xelatex: /usr/local/lilypond/usr/lib/libpng12.so.0: no
version information available (required by xelatex)
It doesn't harm me so far, but if libpng could give its version
number... :-)
This warning probably happens because lilypond-book GUB wrapper changes
LD_LIBRARY_PATH.
But it works, this is really great. Thank you. You might consider
closing issue 543.
I prefer to sort out problems with running xelatex first, especially the
fact that xelatex doesn't find the font index. Could you send me a real
but not too big lilypond/xelatex sample privately?
Cheers,
John
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 617 in lilypond: X-offset should take the specified alignment method into account
If you want to add a fixed offset to the default layout, you can redefine X-offset, for example to \override RehearsalMark #'X-offset = #(ly:make-simple-closure `(,+ 1.0 ,(ly:make-simple-closure (list ly:break-alignable-interface::self-align-callback)) ,(ly:make-simple-closure (list ly:self-alignment-interface::x-aligned-on-self Which differs from the default setting only in the extra 1.0 that's added (this works since (+ ...) in Scheme can take any number of arguments, not only two). Exactly what kind of enhancement are you looking for that cannot be solved in this way? /Mats [EMAIL PROTECTED] wrote: Issue 617: X-offset should take the specified alignment method into account http://code.google.com/p/lilypond/issues/detail?id=617 Comment #2 by v.villenave: Thanks Neil and Mats. I'm keeping this as an Enhancement though, if no one objects. Issue attribute updates: Summary: X-offset should take the specified alignment method into account Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low -- = Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 617 in lilypond: X-offset should take the specified alignment method into account
Issue 617: X-offset should take the specified alignment method into account http://code.google.com/p/lilypond/issues/detail?id=617 Comment #2 by v.villenave: Thanks Neil and Mats. I'm keeping this as an Enhancement though, if no one objects. Issue attribute updates: Summary: X-offset should take the specified alignment method into account Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 617 in lilypond: self-alignment-X doesn't work when X-offset is overridden
Neil is completely right. The value of self-alignment-X is only taken into account if the setting of X-offset includes a call to the function ly:self-alignment-interface::x-aligned-on-self, which it does by default. /Mats [EMAIL PROTECTED] wrote: Issue 617: self-alignment-X doesn't work when X-offset is overridden http://code.google.com/p/lilypond/issues/detail?id=617 Comment #1 by n.puttock: Hi Valentin, I think this is invalid. Have you tried increasing the X-offset? It's not really centre-aligned, it's just one staff space away from the left edge of the stave. By overriding the RehearsalMark's default X-offset, it no longer gets the result of the alignment callback, thus ignoring break-align-symbols. Regards, Neil -- = Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
