Re: How to adjust space between ChordNames and Staff?

2017-01-18 Thread Risto Vääräniemi
On 14 January 2017 at 21:12, Trevor Daniels  wrote:

>
> Thomas Morley wrote Friday, January 13, 2017 9:05 PM
>
>
> > 2017-01-13 17:05 GMT+01:00 Trevor Daniels :
> >>
> >> Risto Vääräniemi wrote Friday, January 13, 2017 3:15 PM
> >>
> >>> On 13 January 2017 at 01:20, Trevor Daniels 
> wrote:
> >>>
> >>>> Interesting.  Does that mean the ChordNames and Lyrics contexts behave
> >>>> differently wrt the vertical spacing controls when these are placed
> within a
> >>>> \with { } block, since Lyrics can be spaced out that way?
> >>>>
> >>>> If so, is this intended for some reason ... or a bug?
> >>>
> >>> Thanks Harm. That did the trick. However, I concur with Trevor about
> the
> >>> confusing difference compared to Lyrics. I assumed that they'd work the
> >>> same way so I did not occur to me to try the \layout block. If it /is/
> an
> >>> intended behaviour, there should probably be a note that the settings
> >>> won't work with \with { }.
> >>
> >> Exactly, but I think we need to understand exactly what the problem is
> before
> >> we can decide (a) whether this _is_ a bug and if so (b) whether it is a
> coding or
> >> a documentation problem.
> >>
> >> Copying to bug list so this doesn't get forgotten.
> >
> > No bug.
> > It's \chords vs \chordmode.
> >
> > \chords (as a shortcut) already created a ChordNames-context, see:
> >
> > chordStuff = \chords { c1 d:m }
> > \void \displayLilyMusic \chordStuff
> >
> > So if you really want to use \chords you need to put overrides, etc
> > into \layout or use
> > \chords \with { ... }
> > at least with newer devel-versions.
> >
> > If you use \chordmode you can do
> > \new ChordNames \with { ... } \chordmode
>
> Excellent explanation!  Many thanks!
>
> So no bug, but we should add a paragraph somewhere in the NR to make this
> clear.  I'll start on that in a day or two.
>
> Trevor
>
>
Thanks for the explanation. And thanks to Trevor for the NR part.

I had to move from \chords to \chordmode anyway because concatenating two
set of chords did not work ( e.g. \new ChordNames { \chordsPartI
\chordsPartII } ). The second part was thrown under the whole system.
However, at that point I had already moved the padding in the \layout block.

The \chords mechanism might also explain why combining did not work—a
second ChordNames was created and ...

-Risto
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Beam disappears with TupletNumber.avoid-slur = #'outside

2016-11-16 Thread Risto Vääräniemi
> Not top posting

Hi,

The beam disappears (squashed to the left edge) if "\override
TupletNumber.avoid-slur = #'outside" is used.

-Risto

---

\version "2.19.49"

\relative c'' {
  \tuplet 3/2 {a8( g a)}
  \override TupletNumber.avoid-slur = #'outside
  \tuplet 3/2 {a8( g a)}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Vertical spacing of Lyrics messed up by system-system-spacing.basic-distance

2015-04-13 Thread Risto Vääräniemi
Hi,

I'm trying to add some space between systems with
system-system-spacing.basic-distance inside the \paper block. In some cases
the basic-distance gives more uniform spacing than the padding.

However, it seems to mess up the vertical spacing of lyrics placed above a
staff. There seems to be too much space between the lyrics and the staff.
That doesn't affect the first staff but the next ones. The minimum-distance
does the same. Setting stretchability to 0 has no effect. I've attached an
image and an example.

If there are lyrics only on top of the staff the issue can be seen even
without modifying the basic-distance. The default value #12 is enough to
trigger this. If it is set to a much smaller value the spacing is OK. I'm
sorry if my example is confusing. I tried to cover both cases—with one and
two lines of lyrics.

Am I just missing something obvious? I tried to search for a similar bug
but found none so far.

BR,
Risto

-


​

-

\version "2.19.18"

\paper {
  ragged-right = ##t
  indent = #0

  % If this is commented out, the top lyrics spacing is OK with lyrics
  % above and below the staff.
  system-system-spacing.basic-distance = #20
}

melody = \relative c' \new Voice = "melody" {
  c4 c c c \break c4 c c c
}

testLyrics = \lyricmode {
  Aa aa aa aa. Aa aa aa aa.
}

<<
  \new Staff = "SI" <<
\melody
  >>
  \new Lyrics \with {alignAboveContext = "SI"} \lyricsto "melody"
\testLyrics
  % If this is commented out, the default value is enough to trigger the
spacing issue.
  \new Lyrics \lyricsto "melody" \testLyrics
>>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: (Bug?) Hidden staves take space if there are lyrics

2009-02-20 Thread Risto Vääräniemi
Hi all,

Has anyone else encountered this issue? The feature / bug still exists
in 2.12.2.

-Risto

2008/9/1 Risto Vääräniemi :
> Hi,
>
> It seems that if I remove the empty staves using
> RemoveEmptyStaffContext everything is usually OK if there are not
> lyrics. There's equal amount of space between the staves. However, if
> I throw in some lyrics the spacing is messed up and the invisible
> staves start taking some space. If there are lyrics you can see the
> difference when you compare the space between the first and the second
> system and between the second and the third. If there's no lyrics the
> spacing is normal (between 3rd and 4th staves).
>
> Is this a known feature / issue or a new bug? Is there a workaround
> for it? I tried to search the bug repository but could not find
> anything similar.
>
> -Risto
>
>

%%%
\version "2.11.56"

\paper {
   ragged-right = ##t
   indent = 0\mm
   between-system-padding = 0\mm
}

\score {
   <<
   \new Staff {
   c'1 c' \break
   c' c' \break
   c' c' \break
   c' c'
   }
   \addlyrics { foo bar foo bar  }
   \new Staff {
   c'1 c'
   s s
   s s
   c' c'
   }
   \addlyrics { foo bar }
   >>

   \layout {
   \context {
   \RemoveEmptyStaffContext
   }
   }
}
%%%
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: lyric tie usage makes for a huge (50Mb) postscript file

2008-11-11 Thread Risto Vääräniemi
2008/11/11 Peter Riegel <[EMAIL PROTECTED]>:

> % this creates a .ps file of 49,967,248 bytes
> % the .pdf is more reasonably sized at 108,361 bytes
> % the problem stems from use of the lyric tie

As Werner said, it's the included font that's causing the size. On
Windows the font containing the undertie is Arial-Unicode and its size
is whopping 28 MB. If you'd like to get the PS files smaller you could
try installing a smaller Unicode font e.g. DejaVuGSCSans. The same
small test file created a PS file of just 1,2 MB. You probably have to
uninstall the ArialUNI.ttf first and then remove the LP font cache
folder in your home / profile folder to make LP recognise the new
font.

-Risto


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Lyrics ignore ties and slurs when applied to a Devnull context.

2008-11-05 Thread Risto Vääräniemi
2008/11/4 Mats Bengtsson <[EMAIL PROTECTED]>:
> At least we should have a feature request that
> it somehow is possible to place the lyrics according to a Voice
> that's not typeset. Erik's proposal was a response to such a
> request to be able to typeset the lyrics of a song over a guitar
> accompaniment, without typesetting the song itself.

One more use for this invisible context springs to mind – \partcombine
and lyrics. One could combine voices with \partcombine and use an
invisible context (possibly one of the original voices) where the
lyrics could be attached.

-Risto


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Windows V2.11.62 and V2.11.63 report version number as V2.11.61

2008-11-03 Thread Risto Vääräniemi
Hi Ian,

2008/11/1 Ian Hulin <[EMAIL PROTECTED]>:

> The last kits for Windows I installed for 2.11.62
> and 2.11.63 say they are
> 2.11.61 when

Do you have also 2.11.61 installed on your system but on a different
path? I have the same situation every time I install a new version. If
you install a new version to a different location LP installer does
not remove the previous versions from the path and you have to
manually fix it i.e. remove the old one.

BTW: My 2.11.63 reports the version number correctly.

-Risto


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: documentation-files / lilypond-homepage

2008-09-30 Thread Risto Vääräniemi
2008/9/12 Patrick McCarty <[EMAIL PROTECTED]>:

>> No they cannot (unless they're already familiar with GNU/Linux).
>> Zip, anyone? :-)
>
> They can, but only with third-party programs, like the (amazing) 7-Zip
> application.  But a zip file is definitely more recognizable in the
> Windows world.

I've been using WinRAR to extract the LP docs quite successfully.

There's one curious thing, though. The program usually complaints
about files with the same name. This happens because Windoze does not
understand a difference between upper and lower cases. I just wonder
why there are two files with basically the same name. In 2.11.60 docs
there was just one:
Documentation\user\lilypond-learning\lilypond_002dbook-templates.de.html and
Documentation\user\lilypond-learning\Lilypond_002dbook-templates.de.html.
Usually there are more.

I normally overwrite the smaller one.

-Risto


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


(Bug?) Hidden staves take space if there are lyrics

2008-09-01 Thread Risto Vääräniemi
Hi,

It seems that if I remove the empty staves using
RemoveEmptyStaffContext everything is usually OK if there are not
lyrics. There's equal amount of space between the staves. However, if
I throw in some lyrics the spacing is messed up and the invisible
staves start taking some space. If there are lyrics you can see the
difference when you compare the space between the first and the second
stave and between the second and the third. If there's no lyrics the
spacing is normal (between 3rd and 4th staves).

Is this a known feature / issue or a new bug? Is there a workaround
for it? I tried to search the bug repository but could not find
anything similar.

-Risto


%%%
\version "2.11.56"

\paper {
ragged-right = ##t
indent = 0\mm
between-system-padding = 0\mm
}

\score {
<<
\new Staff {
c'1 c' \break
c' c' \break
c' c' \break
c' c'
}
\addlyrics { foo bar foo bar  }
\new Staff {
c'1 c'
s s
s s
c' c'
}
\addlyrics { foo bar }
>>

\layout {
\context {
\RemoveEmptyStaffContext
}
}
}
%%%
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Bug? Vertical spacing algorithm changed? (lyrics move notes)

2008-08-22 Thread Risto Vääräniemi
Hi,

I just compiled a piece of music that I created earlier this summer
and I noticed that if I modify the minimum-Y-extent the lyric text
sometimes moves the following notes. I wonder if this is a deliberate
change or a bug?

The behaviour changed between 2.11.52 and 2.11.53.

I have attached two example images and the code (not very minimised
but hopefully understandable).

-Risto

%%
\version "2.11.48"

one = \relative c'
{
  r4 a a a
}

two = \relative c' \new Voice = "vTwo"
{
  c2  c
}

words = \lyricmode
{
  Something...
}

\score
{
  <<
\new Staff = "sOne" { \one }

\new Staff = "sTwo" { \two }

\new Lyrics \with {alignAboveContext = "sTwo"}
  \lyricsto "vTwo" \words
  >>

  \layout
  {
\context
{
  \Lyrics
\override VerticalAxisGroup #'minimum-Y-extent =
  %#'(-0.75 . 2.0) %% default values give normal results
  #'(-0.5 . 0.5) %% custom values don't
}
  }
}
%%
<><>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Broken hairpin placed too high on new line ("collision" with clef/key signature)

2008-07-24 Thread Risto Vääräniemi
On 24/07/2008, Reinhold Kainhofer wrote:

> Note that other spanners (like line spanners) do not exhibit this problem.

Although this might be a different case the same thing happens with
volta brackets. It can be very annoying if you are short of vertical
space.


\version "2.11.53"

#(ly:set-option 'debug-skylines #t)

\paper { ragged-right = ##t }

{
\repeat volta 2 {
b'2 b' }
\alternative {{b' b' \break
}{
b' b'}}
}


-Risto
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: grace note makes voiceOne go stems down

2008-06-06 Thread Risto Vääräniemi
On 05/06/2008, Mats Bengtsson wrote:

>> Looks like a new bug to me, indeed. Did work in previous versions?
> It's the same in 2.10.33!

I tested it on 2.11.34 (I didn't have any older version installed) and
it happens there, too.

-Risto


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Quoted text (was Re: When is "-" required in articulations?)

2008-05-29 Thread Risto Vääräniemi
2008/5/25 Graham Percival wrote:
> While you're at it, could you update any other properties?
>  cd scm/
>  grep ",string?" *
> shows a bunch of properties that shouldn't be touched (like filename),
> but a few that probably should be markup intead (like ottavation,
> soloText, and... hmm, I'm not seeing a lot of other ones).  Still, a
> detailed examination would be good.

I noticed that the LP front page states that "LilyPond now allows all
text context properties to be markups". This does not yet cover volta
brackets, though. That is Score.repeatCommands, which only accepts
plain text. If you try to enter a markup the volta bracket disappears
completely. I guess this is a bit more difficult to fix/change because
to get some normal text inside volta brackets you have make some
special overrides, i.e., font encoding, font family etc.

I just thought you might be interested...

-Risto

%
\version "2.11.47"

{
\override Score.VoltaBracket #'font-encoding = #'latin1
\override Score.VoltaBracket #'font-family = #'roman

c'1
\set Score.repeatCommands = #'((volta \markup {"markup"} ))
%\set Score.repeatCommands = #'((volta "no markup" ))
c'  \bar ":|" %\break
\set Score.repeatCommands = #'((volta #f))
\set Score.repeatCommands = #'((volta "no markup" ))
c'
\set Score.repeatCommands = #'((volta #f))
\bar "|."
}
%


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: pitchedtrill accidental problem

2008-05-19 Thread Risto Vääräniemi
2008/5/19 Valentin Villenave:

> Actually, I was mainly referring to the installing/uninstalling
> process: on Windows, for instance, such a thing would be practically
> impossible (the installation takes ages, and the uninstall is even
> worse).

I agree. In this case JEdit and LilypondTool prove their handiness.
:-) I have several LP installations and in LPTool I can specify which
version I want to use. Of course, if you launch LP by double clicking,
command prompt etc. it's not that simple.

-Risto


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Bug? - Different horizontal spacing in instrumentName and shortInstrumentName

2008-03-07 Thread Risto Vääräniemi
Hi all,

On 05/03/2008, Risto Vääräniemi  wrote:
>  I noticed that versions 2.11.41 and .40 produce a different "padding" between
>  the instrument name and the staff depending if I use instrumentName or
>  shortInstrumentName.

It seems that the behaviour can be controlled by using setting:
\override Staff.InstrumentName #'self-alignment-X = #

If  is replaced by RIGHT the output is as in .39. If LEFT or
CENTER are used only the shortInstrumentName is moved - the
instrumentName is not affected.

Should the self-alignment affect both? If yes, this might be a bug.
Could this patch have something to do with the issue:
http://lists.gnu.org/archive/html/lilypond-devel/2008-02/msg00055.html

The "gap" only appears if the short instrument name is very short (one
character). If it is longer the alignment works as usual.

Hopefully this helps in tracking down the source of the inconsistency.

-Risto


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Different horizontal spacing in instrumentName and shortInstrumentName

2008-03-05 Thread Risto Vääräniemi
Oops. I used a wrong bug list address. Sorry.

On 05/03/2008, Risto Vääräniemi wrote:
>  I noticed that version 2.11.41 produces a different "padding" between
>  the instrument name and the staff depending if I use instrumentName or
>  shortInstrumentName. The behaviour has changed somewhere after .39
>  where the spacing was still OK. I haven't tested it on .40.

Anyway... I installed the .40 and made a test. The same thing happens
there, too.

-Risto


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: set associatedVoice and disappearing lyrics

2008-01-28 Thread Risto Vääräniemi
I'll try to clarify some more. :-)

On Jan 28, 2008 3:53 PM, Risto Vääräniemi wrote:
> If you have just one note (and syllable) in the alternative voice you
> have to call both the setting and unsetting commands before that
> syllable. Could that confuse LP?
>
> The alternate melodies have stems pointing down.

The NOT syllable should be attached to the first note of the third
measure and the rest of the lyrics should be shifted to the right
accordingly. The OK is attached to the half note and it's OK. :-)

In the previous example the last two measures were there just to show
that if the alternative part has two notes / syllables it works. I
boiled down the example closer to Matti's example.

-Risto

%%% Clip %%%
\version "2.11.37"

\paper{ ragged-right=##t }

<<
\new Voice = "melody"
{
\time 2/4 \stemUp
c'4 c'
<<
\new Voice = "alternate"
   { \stemDown  c'2 }
   { \stemUp c'4 c' }
   >>
   c'4 c'
}

\new Lyrics \lyricsto "melody" \lyricmode
{
one \set associatedVoice = alternate two
\set associatedVoice = melody
OK NOT five
}
>>
%%% END %%%
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: set associatedVoice and disappearing lyrics

2008-01-28 Thread Risto Vääräniemi
Dear Mats and Matti,

On Jan 28, 2008 3:07 PM, Mats Bengtsson wrote:
> However, I'm not sure if it's exactly the same problem that you try to
> illustrate below. I don't have the time to try to decipher exactly what
> is right and wrong in your example. Could you please point out the
> problematic syllables with comments in the code replace the corresponding
> syllable by "HELP!!!" or whatever to clarify what the problem is.

Hopefully this clip is of some help. I didn't dig deeper into your
example but it seems a bit different from this.

If you have just one note (and syllable) in the alternative voice you
have to call both the setting and unsetting commands before that
syllable. Could that confuse LP?

The alternate melodies have stems pointing down.

Another issue... If I try to set e.g. \stemDown at the beginning of
the song, it only affects the first two notes before the <<.
Naturally, it shouldn't affect the second and the fourth measure but
in the 3rd and the 5th the stems are pointing up. Normal?

-Risto

PS. I'm sorry for calling Trevor as Mats in my previous message. It's
usually Mats who posts the first comment. :-)

 Clip 
\version "2.11.37"

\paper{ ragged-right=##t }

<<
\new Voice = "melody"
{
\time 2/4
c'4 c'
<<
\new Voice = "alternate"
   {\voiceTwo \override NoteColumn #'force-hshift = #-3 d'2 }
   {\voiceOne c'4 c' \oneVoice}
   >>
   c'4 c'
   <<
\new Voice = "alternateII"
   {\voiceTwo \override NoteColumn #'force-hshift = #-3 d'4 d' }
   {\voiceOne c'4 c' \oneVoice}
   >>
   c'4 c'
}

\new Lyrics \lyricsto "melody" \lyricmode
{
\set stanza = "mel" one two three four five six seven eight nine ten
}

\new Lyrics  \lyricsto "melody" \lyricmode
{
\set stanza = "alt" one \set associatedVoice = alternate
two \set associatedVoice = melody
OK WRONG five six seven eight nine %ten
}

\new Lyrics \lyricsto "melody" \lyricmode
{
\set stanza = "altII" one two three four five
\set associatedVoice = alternateII six OK
\set associatedVoice = melody OK nine ten
}
>>
 END 
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: set associatedVoice and disappearing lyrics

2008-01-28 Thread Risto Vääräniemi
Terve Matti,

On Jan 27, 2008 11:32 AM, Matti Aaltonen wrote:
> Well, the words show on the page, but it doesn't work correctly
> as you can see from this slightly modified example. The first "yes" of the
> first verse gets associated to a wrong note.

I think Matti has a point here (or alternatively we're both wrong ;-) ).

I tested the example ant it seems the LP gets confused if there's only
one note in the alternate voice. At least to it seems. I tried to set
the associated voice as Mats and the manual instructed – one syllable
early. If there's just one note / syllable I don't get it right.

The first alternative depicts Matti's (modified) example with just one
alternate note. The second one has two notes. I've shifted the
alternative parts so you can see where the lyrics are attached.

-Risto

%%% Clip %%%
\version "2.11.37"

\paper{ ragged-right=##t }

<<
\new Voice = "melody"
{
\time 2/4
e4 e
<<
\new Voice = "alternate"
   {\voiceOne \override NoteColumn #'force-hshift = #-3 d'2 }
   {\voiceTwo a4 a \oneVoice}
   >>
   g4 g
   <<
\new Voice = "alternateII"
   {\voiceOne \override NoteColumn #'force-hshift = #-3 d'4 d' }
   {\voiceTwo a4 a \oneVoice}
   >>
   g4 g
}

\new Lyrics  \lyricsto "melody" \lyricmode
{
one \set associatedVoice = alternate
two \set associatedVoice = melody
three four five six seven eight nine
}

\new Lyrics \lyricsto "melody" \lyricmode
{
one two three four five six seven eight nine ten
}

\new Lyrics \lyricsto "melody" \lyricmode
{
one two three four five
\set associatedVoice = alternateII six seven
\set associatedVoice = melody  eight nine ten
}
>>
%%% END %%%
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: \transposition bug - pitch names in other languages

2008-01-06 Thread Risto Vääräniemi

Dear Rune and all,

Rune Zedeler wrote:
> This is not a bug.
> See my comment in the bug tracker.

Arrgh! Stupid, stupid me. My mind got messed up by all the different pitch
names. With "\transposition b" it works.

Thanks and sorry for the trouble.

-Risto
-- 
View this message in context: 
http://www.nabble.com/%5Ctransposition-bug---pitch-names-in-other-languages-tp14639047p14649014.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: \transposition bug - pitch names in other languages

2008-01-06 Thread Risto Vääräniemi

Hi Valentin,

Valentin Villenave wrote:
> Thank you for the report (took me a few minutes to understand what it
> was all about; as a pianist I don't use the \transposition command
> very often ;)

This is the first time for me too (I normally write choir music). :-) I was
wondering why I cannot get the right tune out of my speakers and when I
removed the \transposition altogether and used the \transpose command in the
MIDI section the revelation came to me.

One small addition to the bug specification... The file won't even compile
if you use \transposition bes with \include "suomi.ly" because "bes" is not
defined in suomi.ly.

-Risto
-- 
View this message in context: 
http://www.nabble.com/%5Ctransposition-bug---pitch-names-in-other-languages-tp14639047p14648013.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


\transposition bug - pitch names in other languages

2008-01-05 Thread Risto Vääräniemi

Dear All,

I was writing a piece of score with transposed instruments and found out
that the \transposition command does not work in all cases. With B-flat
instruments it expects a parameter "bes" which is not present in Finnish
language file "suomi.ly". In Finnish you use either "bb" or "heses" for
b-flat. 

The example below shows the effects. If you comment out the \include line
and use the "bes" option you get a unison sound. If you use either "bb" or
"heses" with the \include you get some exotic tunes. :-)

-Risto

%% Begin %%
\version "2.11.34"
\include "suomi.ly"

\score
{
\new GrandStaff <<
\new Staff  {
g'4 g'4 g'4 g'4
}
\new Staff  {
\key d \major
%\transposition bes  % standard b-flat
\transposition bb% b-flat in Finnish
%\transposition heses % alternative b-flat in Finnish
a'4 a'4 a'4 a'4 
}
>>
\layout {}
\midi {}
}
%%% END %%%


-- 
View this message in context: 
http://www.nabble.com/%5Ctransposition-bug---pitch-names-in-other-languages-tp14639047p14639047.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: layout-set-staff-size strange look: bug or feature?

2008-01-03 Thread Risto Vääräniemi

Dear sdfgsdhdshd, ;-)

"sdfgsdhdshd" wrote:
>As i need to have several scores in the same pdf, each one with its own 
> size, i tried to use layout-set-staff-size as explained in § 5.2.1.
>
> I endup with the code below (reduced to be as minimal as possible).
> -- If i don't write the layout-set-staff-size line (or comment it below), 
>   the result is OK.
> -- If i add the layout-set-staff-size line below, the height of the staves 
>   look like greater than expected, and the items on the staves smaller
> than 
>   expected. ==> proportions problem
>
> What is wrong in this code?
> (XP + lilypond 2.11.36 and 2.11.37)

There's a bug filed for this setting
(http://code.google.com/p/lilypond/issues/detail?id=367) and it's supposed
to be fixed. However, if I try the example code on XP 2.11.36 I get the same
results as presented in the example image.

Has this broken down again?

You have probably tried the global staff option (#(set-global-staff-size
15.0)) already?

-Risto
-- 
View this message in context: 
http://www.nabble.com/layout-set-staff-size-strange-look%3A-bug-or-feature--tp14597530p14598574.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: font error in 2.11.36/5 - workaround (not quite)

2007-12-31 Thread Risto Vääräniemi

I'll continue my monologue. :-)

Risto Vääräniemi wrote:
> I think there are two font bugs after all (they could be interrelated,
> though). 
> One is related to missing accents and the other to substituting all fonts
> with Verdana.
> 
> programming error: FT_Get_Glyph_Name () error: invalid argument
> continuing, cross fingers
> programming error: Glyph has no name, but font supports glyph naming.
> Skipping glyph U+, file C:/WINDOWS/fonts/CenturySchL-Ital.otf
> continuing, cross fingers

The missing accented characters issue is probably not caused by any bug.

I was able to reproduce the behaviour when I created a LP source file with
accents but did not save it as UTF-8. When I converted it to UTF-8 the
accented chars were OK.


-Risto


-- 
View this message in context: 
http://www.nabble.com/font-error--in-2.11.36-tp14313181p14556442.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: font error in 2.11.36/5 - workaround (not quite)

2007-12-24 Thread Risto Vääräniemi

Hi again,

Risto Vääräniemi wrote:
> I made some more tests. On my XP box the effect was similar 
> to Martial-3's observations, i.e., dynamic texts and time 
> signature were converted to sans-serif font but lyrics and 
> markups were fine. I was wondering why I got different results 
> on this computer but I finally remembered that I had copied 
> the Lilypond OTF fonts to the Windoze Fonts directory. 
> When did the same trick on my W2k box I got similar results.
> 
> After that I copied the Type1 Feta fonts to windoze\fonts 
> directory (normal copy & paste doesn't work, but command 
> line copy does). After that LP was able to find the Feta 
> font and the output seemed quite OK.

I think there are two font bugs after all (they could be interrelated,
though). One is related to missing accents and the other to substituting all
fonts with Verdana.

The trick described above only helps if you're suffering the Verdana font
error that was introduced in .36 (cannot find fonts under LP installation
dir). If the accents were missing (in .35) it won't bring them back. :-(

I made a new installation on my mother's computer (XP Personal in Finnish)
and I cannot get accents on the prints even if I copy the OTF and TYPE1
fonts to Windows\Fonts dir. The fonts are restored to normal, though.

On my two other computers (XP Pro and W2k both in English) there were no
accent problems either with .35 or .36. I wonder if there could be a
connection with Windoze language and font (Pango?) errors.

When LP is run with -V option it blurts out errors like this:
(lilypond.exe:712): Pango-CRITICAL **: pango_coverage_get: assertion `index
>= 0' failed

programming error: FT_Get_Glyph_Name () error: invalid argument
continuing, cross fingers
programming error: Glyph has no name, but font supports glyph naming.
Skipping glyph U+, file C:/WINDOWS/fonts/CenturySchL-Ital.otf
continuing, cross fingers

If someone is interested in a full print, let me know.

-Risto

-- 
View this message in context: 
http://www.nabble.com/font-error--in-2.11.36-tp14313181p14491636.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: font error in 2.11.36 - workaround

2007-12-17 Thread Risto Vääräniemi

Dear All,

Risto Vääräniemi wrote:
> It also seems to affect other text features such as lyrics and markup
> (in Win2k).

I made some more tests. On my XP box the effect was similar to Martial-3's
observations, i.e., dynamic texts and time signature were converted to
sans-serif font but lyrics and markups were fine. I was wondering why I got
different results on this computer but I finally remembered that I had
copied the Lilypond OTF fonts to the Windoze Fonts directory. When did the
same trick on my W2k box I got similar results.

Somehow it seems that .36 does not find the fonts in its own directory
structure and cannot use the Feta font from Windows\Fonts directory.

When I ran LP using -V option on .35 and .36 one line caught my eye. LP .36
tries to set:
GS_FONTPATH=C:/Program Files/LilyPond/usr/bin/../share/gs/fonts

The above-mentioned directory does not exist. I tried to copy the fonts
there but nothing really changed. :-(

When printing to PS file started, .35 output a list of fonts that reside in
LP installation path. .36, however, gave a list of fonts in C:\Windows\Fonts
directory. The feta-alphabet20.pfa font was not found and was replaced by
Verdana.ttf, which caused the font weirdness.

After that I copied the Type1 Feta fonts to windoze\fonts directory (normal
copy & paste doesn't work, but command line copy does). After that LP was
able to find the Feta font and the output seemed quite OK.

This is probably not the ultimate solution but now I can use the .36.
Hopefully it is of some help.

-Risto
-- 
View this message in context: 
http://www.nabble.com/font-error--in-2.11.36-tp14313181p14373910.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: font error in 2.11.36 - workaround

2007-12-17 Thread Risto Vääräniemi

Dear All,

Risto Vääräniemi wrote:
> It also seems to affect other text features such as lyrics and markup 
> (in Win2k). 

I made some more tests. On my XP box the effect was similar to Martial-3's
observations, i.e., dynamic texts and time signature is converted to
sans-serif font but lyrics and markups are fine. I was wondering why I got
different results on this computer and I finally remembered that I had
copied the LP fonts to the Windoze Fonts directory. When I copied them also
on my W2k box I got similar results. 

Somehow it seems that LP does not find the fonts in its own directory
structure and cannot use the Emmentaler font from Windows\Fonts directory. 

When I ran LP using -V option on .35 and .36 one line caught my eye. LP .36
tries to set: 
GS_FONTPATH=C:/Program Files/LilyPond/usr/bin/../share/gs/fonts

The above-mentioned directory does not exist. I tried to copy the fonts
there but nothing really changed. :-( 

When printing to PS file starts, .35 prints a list of fonts that reside in
LP installation path. .36, however, prints a list of fonts from
C:\Windows\Fonts directory. When they are compared, the feta-alphabet20.pfa
font is replaced by Verdana.ttf, which causes the font weirdness.

Then I copied also the Type1 Feta fonts to windoze\fonts directory (normal
copy & paste doesn't work, but command line copy does). After that LP can
find the Feta font and the output seems quite OK.

This is probably not the ultimate solution but now I can use the .36.

-Risto
-- 
View this message in context: 
http://www.nabble.com/font-error--in-2.11.36-tp14313181p14372559.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: font error in 2.11.36

2007-12-13 Thread Risto Vääräniemi

Dear All,

Martial-3 wrote:
> Thank for the version 2.11.36
> but there are dysfunction with the fonts
> for dynamics and TimeSignature.

It also seems to affect other text features such as lyrics and markup (in
Win2k). 

Example:  http://www.nabble.com/file/p14314241/fonttivirhe_36.png Font error 

-Risto
-- 
View this message in context: 
http://www.nabble.com/font-error--in-2.11.36-tp14313181p14314241.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Wrong abbreviation - decr.

2007-11-23 Thread Risto Vääräniemi

Hi,

Graham Percival-2 wrote:
> Zoltan Selyem wrote:
> > I think the correct abbreviaton for "decrescendo" is "decresc."
> > and not "decr." as \setTextDecresc writes it.
> 
> Hmm.  Do you have a reference or something?  The only text I can find at 
> the moment is "dim."  I'm honestly not sure if it's supposed to be decr. 
> or decresc.

I made a quick search at the omniscient Google. :-) It seems that in the
definition of decrescendo decresc. is used more often as the abbreviation
than decr. (9650 to 581) *). The decr. is used too, though and I can
understand both. 

However, if crescendo is abbreviated cresc. then it is logical to abbreviate
decrescendo decresc. by just adding a de- in the beginning. I don't have any
music notation hand book close by so this point of view is not based on any
hard facts.

-Risto

*)
decrescendo decresc -> 9650
decrescendo decr -> 581
-- 
View this message in context: 
http://www.nabble.com/Wrong-abbreviation---decr.-tf4849531.html#a13892738
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond