Jan Nieuwenhuizen wrote:
Han-Wen Nienhuys writes:
columns TAB is set in the user's editor. Several broken editors allow
setting TAB to a different value than 8.
I can add an "dont-expand-tabs" option. Is that sufficient?
I don't understand, then you can have two PDFs with different locat
Hi,
I noticed that the Swedish translation of 'lilypond' in the glossary is
'liljedamm'. Shouldn't this be 'näckrosdamm', since lily refers to 'water
lily' rather than 'ordinary lily'?
A quick googling reveals that the correct translation of water lily may be
different than proposed in several
Han-Wen Nienhuys writes:
>> columns TAB is set in the user's editor. Several broken editors allow
>> setting TAB to a different value than 8.
>
> I can add an "dont-expand-tabs" option. Is that sufficient?
I don't understand, then you can have two PDFs with different location
encodings? Is that
Jan Nieuwenhuizen wrote:
Han-Wen Nienhuys writes:
Disagree. We're talking about _column_ numbers, not character numbers.
Maybe that's a bad idea, because lilypond cannot know at how many
columns TAB is set in the user's editor. Several broken editors allow
setting TAB to a different value
We're talking about column numbers, but how many columns does one TAB
character in the source make? Eight? Why eight and not four or two? Now
when lilypond finds a TAB, it assumes 8 columns and hard-codes it into
the PDF. That is not correct, because all editors' TAB width can be set
by users.
Han-Wen Nienhuys writes:
> Disagree. We're talking about _column_ numbers, not character numbers.
Maybe that's a bad idea, because lilypond cannot know at how many
columns TAB is set in the user's editor. Several broken editors allow
setting TAB to a different value than 8.
> You could rightly
Am 06.06.05 schrieb Han-WenNienhuys:
> Apparently, there is a incompatibilities RH and Suse in both directions.
> I get.I think I will stop distributing flex output again.
Wait a minute! My flex is not SuSE's original (2.5.4a for SuSE 9.0) but a
self-made one from the latest source tarball (2
Bertalan Fodor wrote:
Sorry, I meant 4:2, if we the first character is indexed 1.
Bert
Disagree. We're talking about _column_ numbers, not character numbers.
You could rightly file a related bugreport for ClickEdit.app, though,
because it doesn't do tab conversion.
--
Han-Wen Nienhuys -
In LilyPond 2.5.27, barlines look far thicker than in previous
versions, and far thicker than is visually appealing. This seems to
be a byproduct of the fix for inconsistent width of barline
connections between staves.
___
bug-lilypond mailing li
(Resent with configuration information...)
In LilyPond 2.5.27, barlines look far thicker than in previous
versions, and far thicker than is visually appealing. This seems to
be a byproduct of the fix for inconsistent width of barline
connections between staves.
Specifically, I'm seeing th
Sorry, I meant 4:2, if we the first character is indexed 1.
Bert
c2 % BEGINS WITH TAB, reported as position 4:8
how should it be reported?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilyp
4:1
c2 % BEGINS WITH TAB, reported as position 4:8
how should it be reported?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Bertalan Fodor wrote:
SYMPTOM: \stopStaff kills the barline at the end of the fragment
\layout { }
\version "2.5.27"
\paper {
raggedright = ##t
}
\relative \new StaffGroup <<
\context Staff = "3" { c1
\new Staff {
\set Staff.alignAboveContext = #"3"
c8 d e f g a b c \stopStaff }
c1 }
fixe
Bertalan Fodor wrote:
%BUG: Point-and-click positions count one TAB character as 8 SPACE
character. Because of this, editors are called with wrong horizontal
position.
\version "2.5.27"
\relative {
c2 % BEGINS WITH TAB, reported as position 4:8
how should it be reported?
d
}
__
Bertalan Fodor wrote:
Two bugs are documented here:
1. \startStaff fails to start ledger lines in some situations:
- when there is a linebreak in the started staff
- when stopped at the beginning of the staff
see CVS.
2. \stopStaff doesn't stop correctly when stopped at the beginning
Werner Scheinast wrote:
Am 03.06.05 schrieb Han-WenNienhuys:
Werner Scheinast wrote:
In fact, when I delete FlexLexer.h and lexer.cc in lily/out/ before the
build, it works with the first attempt. Therefore my question:
Are these files needed for anything?
Yes, they are there for all thos
%BUG: Point-and-click positions count one TAB character as 8 SPACE
character. Because of this, editors are called with wrong horizontal
position.
\version "2.5.27"
\relative {
c2 % BEGINS WITH TAB, reported as position 4:8
d
}
___
17 matches
Mail list logo
