Re: Required font for simplified Chinese characters?

Thanks to all for the advice. And, now with a little spare time, I checked the font list: $ lilypond -dshow-available-fonts 2>&1 | grep 'CJK SC' family Noto Sans CJK SC Noto Sans CJK SC,Noto Sans CJK SC Bold:style=Bold,Regular ... and many other style variants Unfortunately, the crash

Re: Frescobaldi 3,.0 CRAHES

Hi Andrew, my comments below are based on a very vague understanding of the issue, but maybe they are of help anyway (but please don't let them confuse you). Am 08.12.2017 um 23:52 schrieb Andrew Bernard: Hi Ben and All, I have to run F 3 on Mint because I can't get the dependencies all

Re: Frescobaldi 3,.0 CRAHES

Hi Ben, > I'm not too familiar with Ubuntu's update path, but is it possible for > you to upgrade to 17.04 - maybe the poppler issue has been resolved in > later releases? Just an idea for testing. If you're not wanting to leave > your older-but-stable OS, I totally understand. With 17.04 I had

Re: Frescobaldi 3,.0 CRAHES

On 12/8/2017 5:52 PM, Andrew Bernard wrote: Hi Ben and All, I have to run F 3 on Mint because I can't get the dependencies all lined up for Ubuntu 16.04. It's incredibly difficult, to the point that I had given up and I run a Mint VM just for F 3. Now that others are also having problems,

Re: Frescobaldi 3,.0 CRAHES

Cross reference in this thread: https://lists.gnu.org/archive/html/lilypond-user/2017-12/msg00187.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi 3,.0 CRAHES

Possibly related, I've noticed that the 16.04 repository version of Frescobaldi has been holding back python3-pyqt4 and python3-sip from upgrading for several months. On Fri, Dec 8, 2017 at 2:52 PM, Andrew Bernard wrote: > Hi Ben and All, > > I have to run F 3 on Mint

Re: Frescobaldi 3,.0 CRAHES

Hi Ben and All, I have to run F 3 on Mint because I can't get the dependencies all lined up for Ubuntu 16.04. It's incredibly difficult, to the point that I had given up and I run a Mint VM just for F 3. Now that others are also having problems, perhaps I will look into this again. As to what

Re: Required font for simplified Chinese characters?

Hello Jinsong, I am having trouble seeing how your answer is different to mine, apart from the fact that SimHei is not installed by default on Ubuntu. [Of course, he can pick any font he likes.] Was there something else you wanted to add that we should know about this technique? Andrew

Re: Python dependencies: plea for help

Hi Simon, on which system? And do you need to build it or can you use a deb package? As discussed on Sept 23rd on this list [1], I used this package python3-poppler-qt5_0.24.2-3build1_amd64.deb on my Ubuntu machine. And Jamie found out where it came from: > This one worked for me: >

Re: removing automatically generated natural signs

On 08.12.2017 23:18, Chris Jones wrote: As a matter of fact without being an expert I have great respect for quality typesetting, past and present... paper-oriented or digital. Quality typesetting requires some degree of understanding about what you are typesetting; so if you’re going to do

Re: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 04:40:51PM EST, David Kastrup wrote: > Chris Jones writes: > [..] > > Don't underestinmate the anonymous grease monkeys in printers' shops. Far from my intention I can assure you. As a matter of fact without being an expert I have great respect for

Python dependencies: plea for help

Hello everybody, following the post by Vincenzo I take the liberty of turning to this group for advice, even if it’s OT. It’s such a hassle working with LilyPond without Frescobaldi, and I couldn’t solve the problem described in . So I

Re: Frescobaldi CRASHES

There's not much information in your mail but fwiw: I had the problem of Frescobaldi crashing right away when I opened it (on a Mac). Solved it by completely trashing the preferences. > On 8 Dec 2017, at 19:53, Son_V wrote: > > I'm no more able to open any .ly file

Re: Frescobaldi 3,.0 CRAHES

On 12/8/2017 4:59 PM, Simon Albrecht wrote: Hi Vincenzo, I haven’t been able to get any version of Frescobaldi working under Ubuntu 16.04, sadly. I made several attempts at fixing it, and there’s some information here: Unfortunately,

Re: Frescobaldi 3,.0 CRAHES

On 08.12.2017 20:04, Son_V wrote: It's the second message on the same subject I post, but I don't see the first, in case excuse me... Both arrived, so please check in the online archives (they update about every half hour) before reposting your e-mail. Best, Simon

Re: Frescobaldi 3,.0 CRAHES

Hi Vincenzo, I haven’t been able to get any version of Frescobaldi working under Ubuntu 16.04, sadly. I made several attempts at fixing it, and there’s some information here: Unfortunately, the dependencies seem to be terribly

Re: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 03:30:00PM EST, Simon Albrecht wrote: > On 08.12.2017 20:09, Chris Jones wrote: > > Wouldn't this become rather painful/tedious if the gentleman who wrote > > this particular song had had the bright idea of transposing it to > > a fancier key like... G# major for instance?

Frescobaldi 3,.0 CRAHES

It's the second message on the same subject I post, but I don't see the first, in case excuse me... If I try to open a .ly file in Frescobaldi 3.0 (installed blindly as an update) it (Frescobaldi) crashes in a breath. What can I do? Thanks. -- Sent from:

Frescobaldi CRASHES

I'm no more able to open any .ly file in UbuntuStudio, Frescobaldi crashes in a breath, what can I do? Thanks. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org

Re: removing automatically generated natural signs

Chris Jones writes: > But that is precisely the documentation I have been reading over and > over without being able to quite understand the implications. > > And I think that my problem lies with the last word: "... hear". > > Since I am not a musician but a mere scribe

Re: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 03:23:35PM EST, Noeck wrote: > Hi, > > this isa bad hack I would not recommend, but you *could* revert the key > back to c major without showing it: > > \relative { > \key g \major > c' > \once \omit Staff.KeyCancellation > \key c \major > d e f g a b c > } > >

Re: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 02:22:32PM EST, Ben wrote: > ( > On 12/8/2017 2:09 PM, Chris Jones wrote: [..] > > (from documentation) > "... > > To determine whether to print an *accidental*, LilyPond examines the pitches > and the key signature. The key signature only affects the >

Re: Required font for simplified Chinese characters?

On December 8, 2017 12:33:21 Andrew Bernard wrote: Hi James, What platform are you on? Do you want simplified or traditional characters? Oh right, I forgot the OS. I'm on Ubuntu Studio 16.04. I'm based in mainland China, so, simplified characters. Btw my

Re: removing automatically generated natural signs

On 08.12.2017 20:58, Urs Liska wrote: I think this is a great way to explain this concept. And I also belong to the party of those who want to write down (encode) what it*is* and not what it looks like. However, sometimes in ancient music accidentals are _not_ part of the actual content,

Re: removing automatically generated natural signs

On 08.12.2017 20:09, Chris Jones wrote: Wouldn't this become rather painful/tedious if the gentleman who wrote this particular song had had the bright idea of transposing it to a fancier key like... G# major for instance? If that were the case I would have to add an "is" to just about every

Re: removing automatically generated natural signs

Hi, this isa bad hack I would not recommend, but you *could* revert the key back to c major without showing it: \relative { \key g \major c' \once \omit Staff.KeyCancellation \key c \major d e f g a b c } Midi, transposition etc. will be broken, of course. Cheers, Joram

Re: removing automatically generated natural signs

Am 8. Dezember 2017 21:06:05 MEZ schrieb Ben : >On 12/8/2017 2:58 PM, Urs Liska wrote: >> >>> (from documentation) >>> "... >>> >>> To determine whether to print an *accidental*, LilyPond examines the >>> pitches and the key signature. The key signature only affects

Re: removing automatically generated natural signs

Urs, > But to be fair one should note that there are serious encoding systems out > there that work like the OP expects, for example the MEI encoding format or > the Amadeus notation software. > When I discussed the topic with an Amadeus power user he said that he would > go nuts with all the

Re: removing automatically generated natural signs

On 12/8/2017 2:58 PM, Urs Liska wrote: (from documentation) "... To determine whether to print an *accidental*, LilyPond examines the pitches and the key signature. The key signature only affects the */printed/***accidentals, not the note’s pitch! --> This is a feature that often causes

Re: removing automatically generated natural signs

Am 8. Dezember 2017 20:22:32 MEZ schrieb Ben : >( >On 12/8/2017 2:09 PM, Chris Jones wrote: >> I would need some help removing the autmatically generated natural >signs >> that I see in lilypond's output. >> >> | melody = \relative c { >> | \global >> |

Re: removing automatically generated natural signs

On Fri 08 Dec 2017 at 14:09:31 (-0500), Chris Jones wrote: > I would need some help removing the autmatically generated natural signs > that I see in lilypond's output. > > I coded this: > > | global = { > | \time 4/4 > | \key g \major > | \tempo \markup { \concat {Mouv. \super t}

Re: removing automatically generated natural signs

( On 12/8/2017 2:09 PM, Chris Jones wrote: I would need some help removing the autmatically generated natural signs that I see in lilypond's output. | melody = \relative c { | \global | \partial 16 d'16 \bar "||" | \set melismaBusyProperties = #'() |

Re: removing automatically generated natural signs

On 12/8/2017 2:09 PM, Chris Jones wrote: I would need some help removing the autmatically generated natural signs that I see in lilypond's output. I coded this: | global = { | \time 4/4 | \key g \major | \tempo \markup { \concat {Mouv. \super t} de Marche} | } | |

Re: removing automatically generated natural signs

On 12/8/2017 2:09 PM, Chris Jones wrote: I would need some help removing the autmatically generated natural signs that I see in lilypond's output. I coded this: | global = { | \time 4/4 | \key g \major | \tempo \markup { \concat {Mouv. \super t} de Marche} | } | |

removing automatically generated natural signs

I would need some help removing the autmatically generated natural signs that I see in lilypond's output. I coded this: | global = { | \time 4/4 | \key g \major | \tempo \markup { \concat {Mouv. \super t} de Marche} | } | | #(set-global-staff-size 16.5) | | melody =

Re: lilypond code in (pdf/lua/xe)latex documents

Am 06.12.2017 um 20:40 schrieb Jacques Peron: Here is a modified version, that calls `lilypond` only when needed by computing a md5 hash of the content. A good idea. What about making a package out of that and putting it on CTAN ? It would be more universal than lyluatex, so I think many

Re: Required font for simplified Chinese characters?

On 2017/12/8 14:53, Jinsong Zhao wrote: On 2017/12/6 21:34, James Harkins wrote: I have: \header {    dedication = "为星海音乐学院的电脑乐团，2017年秋天" You may have to set the font that could be used for the  simplified Chinese characters. Something like: dedication = \markup \override #'(font-name .

Re: Required font for simplified Chinese characters?

On 2017/12/6 21:34, James Harkins wrote: I have: \header { dedication = "为星海音乐学院的电脑乐团，2017年秋天" You may have to set the font that could be used for the simplified Chinese characters. Something like: dedication = \markup \override #'(font-name . "SimHei") "为星海音乐学院的电脑乐团，2017年秋天" SimHei

Re: optional measure

Thank you Robin and Karlin for the suggestion!!! Gianmaria ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fontsize ornaments

Am 07.12.2017 um 17:57 schrieb Pieter Terpstra: Do you think this could be made in to a configuration file and store it in the /usr/share/lilypond/$VERSION/ly directory? You could have a “personal/private includes directory” in your home dir, f. e. something like ~/MyLilyIncludes

Re: Required font for simplified Chinese characters?

Hi James, I don't know about the crash, but on Ubuntu you can observe all the Chinese fonts available to lilypond with: $ lilypond -dshow-available-fonts 2>&1 | grep CJK family Noto Sans Mono CJK JP Noto Sans Mono CJK JP,Noto Sans Mono CJK JP Bold:style=Bold,Regular family Noto Sans Mono CJK KR