Re: Problem with german umlauts and with mapping text to notes

On 10/1/2019 4:44 PM, Frank Steinmetzger wrote: There is no guile-1 anymore in the tree to roll back to. The archives also have instructions for compiling Guile 1.8 from source. This is for Debian Stretch, and I don't

Re: Problem with german umlauts and with mapping text to notes

On Sun, Jan 13, 2019 at 05:43:55PM +0100, Klaus Ethgen wrote: > Hi, > > Am So den 13. Jan 2019 um 17:02 schrieb David Kastrup: Sorry for reviving an ancient thread, but I just encountered the exact same problem as Klaus (after many months of absence). And since there was no solution given at the

Re: Problem with german umlauts and with mapping text to notes

Klaus Ethgen writes: > Hi, > > Am So den 13. Jan 2019 um 18:13 schrieb David Kastrup: >> Yeah. Somebody considered a good idea to override the defaults and >> enable experimental Guile-2 support. > > Grml, that overwrite was necessary as other systems pulled in that > guile2. And it seems to be

Re: Problem with german umlauts and with mapping text to notes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi David, I was able to downgrade. It fixed the problem. Many thanks. (The other tool was autogen that pulled this experimental version.) Am So den 13. Jan 2019 um 18:13 schrieb David Kastrup: > Instead of having the touted 10% speed advantage of

Re: Problem with german umlauts and with mapping text to notes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am So den 13. Jan 2019 um 18:13 schrieb David Kastrup: > Yeah. Somebody considered a good idea to override the defaults and > enable experimental Guile-2 support. Grml, that overwrite was necessary as other systems pulled in that guile2. And

Re: Problem with german umlauts and with mapping text to notes

Am So., 13. Jan. 2019 um 17:48 Uhr schrieb Klaus Ethgen : > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi Thomas, > > Am So den 13. Jan 2019 um 16:10 schrieb Thomas Morley: > > Please enter in terminal: > > lilypond scheme-sandbox > > > > A guile-prompt will open, then do there: > >

Re: Problem with german umlauts and with mapping text to notes

Klaus Ethgen writes: > Hi Thomas, > > Am So den 13. Jan 2019 um 16:10 schrieb Thomas Morley: >> Please enter in terminal: >> lilypond scheme-sandbox >> >> A guile-prompt will open, then do there: >> (version) >> >> Please post what you get. > >> lilypond scheme-sandbox > >GNU LilyPond

Re: Problem with german umlauts and with mapping text to notes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Thomas, Am So den 13. Jan 2019 um 16:10 schrieb Thomas Morley: > Please enter in terminal: > lilypond scheme-sandbox > > A guile-prompt will open, then do there: > (version) > > Please post what you get. > lilypond scheme-sandbox GNU

Re: Problem with german umlauts and with mapping text to notes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am So den 13. Jan 2019 um 17:02 schrieb David Kastrup: > For stuff like encoding problems it is _absolutely_ necessary that you > specify the operating system you use, the LilyPond version you use, and > whether you used the distributed

Re: Problem with german umlauts and with mapping text to notes

Klaus Ethgen writes: > Hi, > > I like the lilypond package and I decided to dive into for my guitar > playing book. > > Unfortunately I stumble over two problems which can be seen in the > example attached. > > - First there is the German umlauts. As you can see in the example, it > is correct

Re: Problem with german umlauts and with mapping text to notes

Sending this again, because google or firefox or whatever buggy program messed up the mail-adress Am So., 13. Jan. 2019 um 16:10 Uhr schrieb Thomas Morley : > > Am So., 13. Jan. 2019 um 15:41 Uhr schrieb Klaus Ethgen see: > : > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > >

Re: Problem with german umlauts and with mapping text to notes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Andrew, Am So den 13. Jan 2019 um 14:57 schrieb N. Andrew Walsh: > On Sun, Jan 13, 2019 at 2:50 PM Klaus Ethgen > wrote: > > - First there is the German umlauts. As you can see in the example, it > > is correct encoded in UTF-8 but the

Re: Problem with german umlauts and with mapping text to notes

Am So., 13. Jan. 2019 um 15:41 Uhr schrieb Klaus Ethgen : > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi Lukas, > > Am So den 13. Jan 2019 um 15:01 schrieb Lukas-Fabian Moser: > [Charset problem] > > This is strange, because I can't reproduce the problem here. On my (Linux > > Mint)

Re: Problem with german umlauts and with mapping text to notes

Hi Klaus, Note that \lyricsto implicitly starts \lyricmode. (Also I'd recommend writing Mond __ if the note with the syllable "Mond" has a tie.) That one is a bit tricky. It is a half and a quarter note that should sound like a dotted half note. But the "Mond" should be sung only on the half

Re: Problem with german umlauts and with mapping text to notes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Lukas, Am So den 13. Jan 2019 um 15:01 schrieb Lukas-Fabian Moser: [Charset problem] > This is strange, because I can't reproduce the problem here. On my (Linux > Mint) machine, the German umlauts are displayed fine without any change in > your

Re: Problem with german umlauts and with mapping text to notes

Am 13.01.19 um 13:42 schrieb Klaus Ethgen: - First there is the German umlauts. As you can see in the example, it is correct encoded in UTF-8 but the umlauts are encoded as "??". I did already try to use no bomb or even in latin1 encoding. But nothing helped. Cannot reproduce.

Re: Problem with german umlauts and with mapping text to notes

Hi Klaus, Am 13.01.19 um 13:42 schrieb Klaus Ethgen: - First there is the German umlauts. As you can see in the example, it is correct encoded in UTF-8 but the umlauts are encoded as "??". I did already try to use no bomb or even in latin1 encoding. But nothing helped. This is

Re: Problem with german umlauts and with mapping text to notes

Hi Klaus, On Sun, Jan 13, 2019 at 2:50 PM Klaus Ethgen wrote: > > - First there is the German umlauts. As you can see in the example, it > is correct encoded in UTF-8 but the umlauts are encoded as "??". > I did already try to use no bomb or even in latin1 encoding. But > nothing helped.

Problem with german umlauts and with mapping text to notes

Hi, I like the lilypond package and I decided to dive into for my guitar playing book. Unfortunately I stumble over two problems which can be seen in the example attached. - First there is the German umlauts. As you can see in the example, it is correct encoded in UTF-8 but the umlauts are