> Yes, but I can exactly see that one of the few places
> Japanese/Chinese emphasis dots may be used is in lyrics, which I
> guess is the OP's intent.
Also having a (minor) Sinology background, I've never seen emphasis
dots in scores from Taiwan, including music using the jiǎnpǔ notation.
I guess
Yes, but I can exactly see that one of the few places Japanese/Chinese
emphasis dots may be used is in lyrics, which I guess is the OP's
intent.
I was going to make the same point however, that lilypond is not
really the right tool to be attempting complex and extensive CJK
typesetting. Not in any
> I would like to request an implementation for text emphasis points
> native to East Asian scripts.
Please give an example how this is used. And with “example” I mean a
real-word example like existing scores.
Note also that LilyPond is *not* suited for large textual works.
Support for text is
Gosh, a very LARGE can of wriggling worms, and very interesting worms
indeed. A question, say you restrict yourself to emphasis dots for
simplicity, does OpenType support this at the moment? I am unaware of
that. Else, adding that to lilypond seems like a big project.
I am a serious student of Chi
Hello,
I would like to request an implementation for text emphasis points native
to East Asian scripts.
Please refer to the following:
https://en.wikipedia.org/wiki/Emphasis_point
https://www.w3.org/TR/jlreq/#composition_of_emphasis_dots
^ specific to Japanese usage
I understand that this is a
On 2020-09-28 1:13 pm, David Kastrup wrote:
David Rogers writes:
Hello all
I certainly remember having this same question or confusion. The fact
that there is a specific \cresc led me to believe that there ought to
be a specific \rit as well. May I suggest that a new Subsection 1.3.4
"Other e
David Rogers writes:
> Hello all
>
> I certainly remember having this same question or confusion. The fact
> that there is a specific \cresc led me to believe that there ought to
> be a specific \rit as well. May I suggest that a new Subsection 1.3.4
> "Other expressive marks" be added to the Not
Hello all
I certainly remember having this same question or confusion. The
fact that there is a specific \cresc led me to believe that there
ought to be a specific \rit as well. May I suggest that a new
Subsection 1.3.4 "Other expressive marks" be added to the Notation
manual, simply explaini
>
> Even if, as suggested later in the thread, you have ossia-above and
> ossia-below, I don't think that should affect this ordering. Any
> analogy with the << { } \\ { } >> construction is probably unwise,
> as that's something which appears not always to be understood anyway.
>
On a second thou
On Sun 27 Sep 2020 at 23:32:08 (-0700), Aaron Hill wrote:
> On 2020-09-27 7:35 pm, David Wright wrote:
> > I'm not sure that it does produce clarity (as opposed to merely
> > explaining the unreliability in perception). Would it not be
> > clearer to put the ossia music inside a \relative{}, so tha
Il giorno lun 28 set 2020 alle 12:02, N. Andrew Walsh
ha scritto:
Hi Aaron,
On Mon, Sep 28, 2020 at 11:34 AM Aaron Hill
wrote:
See [1] and [2]. It's \compressEmptyMeasures now.
That was it! Thank you. I wonder why that doesn't show up in the
auto-complete popup.
In Frescobaldi
Dear community,
I've recently and successfully installed lyp, which seems to be a great
thing.
When I use the lilypond command, I normally use a bash alias, that allows
my to automatically include a folder, in which I have some templates.
I would like to integrate this path in lyp, but I've no idea
Hi Aaron,
On Mon, Sep 28, 2020 at 11:34 AM Aaron Hill
wrote:
>
> See [1] and [2]. It's \compressEmptyMeasures now.
That was it! Thank you. I wonder why that doesn't show up in the
auto-complete popup.
Cheers,
A
On 2020-09-28 2:22 am, N. Andrew Walsh wrote:
Hi Francesco,
On Mon, Sep 28, 2020 at 11:20 AM Francesco Intrieri <
francesco.intrieri...@gmail.com> wrote:
Hi Andrew !
Is it possible that you forgot to write \compressFullBarRests before
R2*12
?
When I do that, I get an error about an "unre
I'm stuck with 2.20.0, I leave the thread in the hands of more expert and
up to date users. Good luck !
Le lun. 28 sept. 2020 à 11:22, N. Andrew Walsh a
écrit :
> Hi Francesco,
>
> On Mon, Sep 28, 2020 at 11:20 AM Francesco Intrieri <
> francesco.intrieri...@gmail.com> wrote:
>
>> Hi Andrew !
>>
Hi Francesco,
On Mon, Sep 28, 2020 at 11:20 AM Francesco Intrieri <
francesco.intrieri...@gmail.com> wrote:
> Hi Andrew !
>
> Is it possible that you forgot to write \compressFullBarRests before R2*12
> ?
>
When I do that, I get an error about an "unrecognized escape string" (even
though it come
Hi List,
I have a general question. Has compression of full-bar rests been somehow
disabled? I have the following score:
\version "2.21.1"
global= {
\time 4/8
}
%% (and whatever other settings I want)
oDAMusic = \relative c'' {
\key f \minor
R2*12
| %13
r4 bes
}
\score {
\n
Thank you David for this example. I agree with Aaron that ossia notes
should be first when the ossia measure goes above the music. That way you
have a similar "feeling" of the \relative effect as when using << {
%abovemusic} \\ {%belowmusic} >>. However, I went ahead, and, for the sake
of completen
18 matches
Mail list logo
