When running make all on OS X 10.6.2, I get the following C++ compilation error:
In file included from /usr/include/c++/4.2.1/vector:70,
from ./include/std-vector.hh:78,
from ./include/file-name.hh:23,
from file-name.cc:21:
/usr/include/c++/4.2.1/bit
On 2009.11.19., at 11:42, Valentin Villenave wrote:
> Can you try and find what exactly in this snippet produces the bug? (I
> strongly suspect that it's the embedded postscript code with the font
> instructions.)
Of course: the lines
/Times-Roman findfont
2.0 scalefont
s
On 2009.11.19., at 9:10, Valentin Villenave wrote:
> 2009/11/9 Harmath Dénes :
>> On OS X 10.5.8 (Linux works well), LilyPond 2.13.7 can't compile
>> Documentation/snippets/bar-chords-notation-for-guitar--with-text-spanner.ly:
>
> Greetings,
>
> this is weird
On OS X 10.5.8 (Linux works well), LilyPond 2.13.7 can't compile
Documentation/snippets/bar-chords-notation-for-guitar--with-text-spanner.ly:
thSoft-MacBook:Temp thsoft$
/Applications/LilyPond-dev.app/Contents/Resources/bin/lilypond
bar-chords-notation-for-guitar--with-text-spanner.ly
GNU LilyPon
h into account, but
correctly counts UTF-8 characters.
thSoft
On 2009.10.30., at 4:07, Patrick McCarty wrote:
On 2009-10-29, Harmath Dénes wrote:
On 2009.10.29., at 22:12, Patrick McCarty wrote:
It *should* have an effect. But if I'm thinking about this
correctly,
there will still be an
On 2009.10.29., at 22:12, Patrick McCarty wrote:
It *should* have an effect. But if I'm thinking about this correctly,
there will still be an off-by-one error in the character/column
counts, because my commit only affects the value of the character
count when non-ASCII characters are found.
I
On Windows platform only (where the default encoding is not UTF-8), non-ASCII
characters in a source line shift the subsequent PDF point-and-click link column
positions in that line by 1.
Example:
%{ á %} { a }
The link of the note 'a' points to the space after the 'a' (column 11), not to
it (col
I found out that they are actually encoded in the system's default encoding
(Cp1250 on Windows, UTF-8 on Unixes) and then escaped with backslash-codes. So
maybe this is the expected behaviour?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://l
The point-and-click links in the PDF file do not work if they link to a file
with a non-ASCII filename or path.
The PDF spec says that the URIs should be encoded as 7-bit ASCII; I couldn't
find out what encoding is actually used.
___
bug-lilypond maili
The recently released 2.13.4 dev version handles all characters perfectly! Thank
you!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
10 matches
Mail list logo
