Re: Super and sub

[David Kastrup]

John Gourlay  writes:

> I was thinking that text produced by LilyPond would likely be about
> music, with references, for example, to chords with superscripts in
> their names. It would appear odd if the chord names in text appeared
> differently than in the music itself.

Currently we have different subscript heights in pretty much every
national chord format (probably because the localizers thought that the
defaults sucked).  So unifying this would be some kind of work.  Some of
the differences may also be intentional.

-- 
David Kastrup

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

Re: Super and sub

[David Kastrup]

John Gourlay  writes:

> Joram,
>
> As you say, LaTeX is for producing beautiful mathematics and LilyPond
> is for producing beautiful music. It’s possible that the conventions
> in the two different kinds of typography differ in their placement of
> sub and superscripts, and so LaTeX and LilyPond should differ in their
> behavior. This seems like the first question that should be answered
> before asking whether LilyPond is making the best placement
> choices. I’ll let people with more experience in music notation weigh
> in.

Super- and subscript heights and sizes are usually chosen in connection
with the default font heights and x-heights and baselineskip.  So
I don't see that blind adoption of LaTeX's defaults (which are a
massaged version of plain TeX's defaults, with plain TeX being rather
firmly written serving the aesthetics of the Computer Modern font
family) will automatically lead to best results.

Of course, where the current situation is "this looks awful", getting
one's start values from LaTeX for comparison is a possible first step.
It's also reasonable to look for visual compatibility of music and text
footnotes for lilypond-book.  Of course, let's hope that Texinfo and
LaTeX have made somewhat similar choices, and that HTML does not dictate
something else yet again...

-- 
David Kastrup

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

Re: Super and sub

[Simon Albrecht]

On 07.02.2016 11:39, David Kastrup wrote:

>(Preferably with LilyPonds own accidentals and perhaps the BC-font.)

Well, what you put in there is up to you.


You can also experiment along the lines of

%%%
\version "2.19.36"
#(define-markup-command (number-stack layout props args) (markup-list?)
   (interpret-markup layout props
 #{ \markup \tiny \raise #0.5 \vcenter
\override #'(baseline-skip . 2) \right-column \number #args #}))

\markup {
  Would be a
  \number-stack {6 5 3}
  on the
  \hspace #5
  harmonized as
  \number-stack { 7 \concat \vcenter { \sharp 3 } }
  →
  \number-stack { 7 5 }
}
%%%

Unfortunately, the \sharp takes a lot of vertical space, which I somehow 
couldn’t amend by \with-dimensions.

HTH, Simon


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

Re: Super and sub

[Noeck]

Thanks Simon, I'll do that.

Best, Joram

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

Re: Super and sub

[Simon Albrecht]

On 07.02.2016 14:50, Phil Holmes wrote:

I wasn't aware that git-cl "always fails".  Could you describe the problem


I thought it was a known issue? It’s the case for which you recently 
added more helpful messages. Here’s the command line in- and output:


$ git cl upload origin/master
 Documentation/changes.tely | 18 ++
 scm/define-markup-commands.scm | 10 ++
 2 files changed, 28 insertions(+)
Upload server: codereview.appspot.com (change with -s/--server)
Your browser has been opened to visit:

https://codereview.appspot.com/get-access-token?port=8001

If your browser is on a different machine then exit and re-run
upload.py with the command-line parameter

  --no_oauth2_webbrowser

Issue created. URL: http://codereview.appspot.com/281710043
Uploading base file for Documentation/changes.tely
Uploading base file for scm/define-markup-commands.scm
We were not able to associate this patch with a tracker issue.
Please enter a valid tracker issue number
(or enter nothing to create a new issue):
Error code 403
Failed URL was http://sourceforge.net/rest/p/testlilyissues/issues//new
Failed data was 
ticket_form.summary=Add+%5Cwith-dimensions-from+markup+command_form.custom_fields._patch=new_form.custom_fields._type=Enhancement_form.description=Add+%5Cwith-dimensions-from+markup+command%0A%0AThis+command+acts+as+a+front-end+to+%5Cwith-dimensions%2C%0Ataking+the+new+dimensions+from+a+markup+object+instead+of%0Ahaving+them+explicitly+given.%0AAlso+provides+a+Changes+entry.%0AI+didn%E2%80%99t+think+a+regtest+was+necessary%2C+since+the+functionality%0Aisn%E2%80%99t+new.%0A%0Ahttp%3A%2F%2Fcodereview.appspot.com%2F281710043_token=8f1c33f1a44226b74411_form.status=Started



and provide a traceback?

I everyone having the same problem? 


IIRC, it has been reported by others, and Urs already posted a traceback 
– somewhere…


HTH, Simon

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

Re: Super and sub

[Robert Blackstone]

Dear All,

Just as I was trying to formulate a request for some additional feature related 
to Super and Sub  I saw Joram's mail, the first of this thread, with which I 
very much agree.

So maybe I can use this thread to ask for the following:

In comments accompanying some scores I feel a need for BC figures, as shown in 
these screenshot:. (typeset with ConTeXt, Im not sure this feature exists in 
LaTeX)

 and 

Would this be doable in LilyPond ? A sort of unattached Super-Sub couple (and 
triple)
If not, could it somehow be added to its immense reservoir of features? 
(Preferably with LilyPonds own accidentals and perhaps the BC-font.)
 
Best regards,

Robert Blackstone


On 6 Feb 2016, at 20:58 , Noeck  wrote:

> Dear all,
> 
> in a recent question on this list [1] about \super in markup text, all
> three replies suggested to tweak the vertical position of superscripts
> by hand because the default is obviously too high.
> 
> I compared the Lilypond result of \super and \sub to the equivalents in
> LaTeX (because who would doubt that LaTeX is wrong in such a question)
> and indeed LaTeX makes a different choice when using \textsuperscript
> and \textsubscript.
> 
> Of course LilyPond's emphasis is on beautiful music notation, but I
> think also text parts of scores should look good. Therefore, I would
> like to propose the following change to scm/define-markup-commands.scm:
> 
> - raise the superscript by 0.8 instead of 1.0
> - lower the subscript by -0.4 instead of -0.75
> 
> The result can be seen in the attached figures:
> - latex.png shows how LaTeX would format it
> - lily.png shows the LilyPond default (Lilypond) and the above proposal
> 
> If you agree and there are chances to get this into LilyPond, I would
> prepare a patch.
> 
> Best,
> Joram
> 
> 
> [1]: https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00113.html
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

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

Re: Super and sub

[David Kastrup]

Robert Blackstone  writes:

> Dear David,
>
> Thank you very much. Perfect. This is what I had hoped for.
>
> I needed some time to find out how to insert "real" LilyPond
> accidentals instead of your "♯" but I think I can manage that now.
> (Just curious: What is ♯? Not the normal #.)

It's a text sharp.  On my (X11) terminal, I can enter it with the
Compose key as Compose # #, a flat with Compose # b and a natural with
Compose # f.

It's some standard Unicode char from the code pages for musical symbols.

-- 
David Kastrup

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

Re: Super and sub

[Urs Liska]

Am 07.02.2016 um 15:07 schrieb Simon Albrecht:
> On 07.02.2016 14:50, Phil Holmes wrote:
>> I wasn't aware that git-cl "always fails".  Could you describe the
>> problem
> 
> I thought it was a known issue? It’s the case for which you recently
> added more helpful messages. Here’s the command line in- and output:
> 
> $ git cl upload origin/master
>  Documentation/changes.tely | 18 ++
>  scm/define-markup-commands.scm | 10 ++
>  2 files changed, 28 insertions(+)
> Upload server: codereview.appspot.com (change with -s/--server)
> Your browser has been opened to visit:
> 
> https://codereview.appspot.com/get-access-token?port=8001
> 
> If your browser is on a different machine then exit and re-run
> upload.py with the command-line parameter
> 
>   --no_oauth2_webbrowser
> 
> Issue created. URL: http://codereview.appspot.com/281710043
> Uploading base file for Documentation/changes.tely
> Uploading base file for scm/define-markup-commands.scm
> We were not able to associate this patch with a tracker issue.
> Please enter a valid tracker issue number
> (or enter nothing to create a new issue):
> Error code 403
> Failed URL was http://sourceforge.net/rest/p/testlilyissues/issues//new
> Failed data was
> ticket_form.summary=Add+%5Cwith-dimensions-from+markup+command_form.custom_fields._patch=new_form.custom_fields._type=Enhancement_form.description=Add+%5Cwith-dimensions-from+markup+command%0A%0AThis+command+acts+as+a+front-end+to+%5Cwith-dimensions%2C%0Ataking+the+new+dimensions+from+a+markup+object+instead+of%0Ahaving+them+explicitly+given.%0AAlso+provides+a+Changes+entry.%0AI+didn%E2%80%99t+think+a+regtest+was+necessary%2C+since+the+functionality%0Aisn%E2%80%99t+new.%0A%0Ahttp%3A%2F%2Fcodereview.appspot.com%2F281710043_token=8f1c33f1a44226b74411_form.status=Started
> 
> 
>> and provide a traceback?
>>
>> I everyone having the same problem? 
> 
> IIRC, it has been reported by others, and Urs already posted a traceback
> – somewhere…

I definitely don't have *that* problem, and the traceback I posted was
surely something different. While I had network issues the connection
timed out, and git-cl didn't gracefully catch that exception.

Urs

> 
> HTH, Simon
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


-- 
Urs Liska
www.openlilylib.org

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

Re: Super and sub

[David Kastrup]

Robert Blackstone  writes:

> Dear All,
>
> Just as I was trying to formulate a request for some additional feature 
> related to
> Super and Sub I saw Joram's mail, the first of this thread, with which I very
> much agree.
>
> So maybe I can use this thread to ask for the following:
>
> In comments accompanying some scores I feel a need for BC figures, as shown
> in these screenshot:. (typeset with ConTeXt, Im not sure this feature exists 
> in
> LaTeX)
>
> *
> and 
> *
>
> Would this be doable in LilyPond ? A sort of unattached Super-Sub couple (and
> triple)
> If not, could it somehow be added to its immense reservoir of features?

#(define-markup-command (stack layout props args) (markup-list?)
  (interpret-markup layout props
   #{ \markup \tiny \raise #0.5 \general-align #Y #CENTER
  \override #'(baseline-skip . 2) \right-column #args #}))

\markup { Would be a \stack {6 5 3} on the 
	  harmonized as \stack { 7 ♯3 } → \stack { 7 5 }, }


> (Preferably with LilyPonds own accidentals and perhaps the BC-font.)

Well, what you put in there is up to you.

-- 
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Noeck]

Hi,

from the replies, I conclude:
- The changes to super and sub script positions are considered an
  improvement
- There might be yet unknown cases where something more sophisticated
  is needed for a perfect look
- Superscripts in chords are very inconsistent, for instance
  \chords {
\powerChords
c:7 c:1.5 c:sus4
  }
  but also for different languages. Although related, that is a
  different issue.

So I would like to upload a patch, further discussion can then be done
in the issue. Could someone guide me a bit, how to upload the patch?
Should the issue 3619 [1] be continued or a new one created?
It is probably faster if someone did it for me, but I would like to
learn the procedure for future contributions.

Cheers,
Joram


[1]: http://sourceforge.net/p/testlilyissues/issues/3619/

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

Re: Super and sub

[Simon Albrecht]

On 07.02.2016 14:27, Noeck wrote:

Could someone guide me a bit, how to upload the patch?
Should the issue 3619 [1] be continued or a new one created?


It’ll be better to create a new one.
The procedure to submit patches is explained in the CG, see especially 
. 
Basically, if everything is set up, you do the following:

– Create a new local branch, make your changes and commit them.
– Run ‘git cl upload origin/master’. This will create a Rietveld issue 
and try to create an Allura tracker issue as well, which currently 
always fails.
– So you create an issue manually (if you don’t have permission, just 
ask on the devel list), linking to the Rietveld issue, with 
Status:Started and Patch:new.
And then review cycle begins. When the issue is set to Patch:push and 
you don’t have push access, you should send patches (created via ‘git 
format-patch HEAD~n’, where n is the number of commits) to James.

For further questions, just ask on the devel list.

Best, Simon

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

Re: Super and sub

[Noeck]

Dear Robert,

in a text environment, Davids solution is probably better. But if you
want to use the full bass figure syntax, you can also insert scores into
markup like this:

\paper {
  indent = 0
}

\layout {
  \override FiguredBass.BassFigure.font-size = -1
}


\markup \line {
  would be a
  \raise #3.2 \score { \figures { < 6 5 3> } }
  on the first line and
  \raise #3.2 \score { \figures { < 6 4+ 3> } }
  on the ...
  harmonized as
  \raise #2.4 \score { \figures { < 7 3+> } }
  →
  \raise #2.4 \score { \figures { < 7 5> } }
}

Yet another way of using music glyphs in text is the LilyGlyphs LaTeX
package: http://www.openlilylib.org/lilyglyphs/

HTH,
Joram

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

Re: Super and sub

[Phil Holmes]

I wasn't aware that git-cl "always fails".  Could you describe the problem 
and provide a traceback?


I everyone having the same problem?

--
Phil Holmes



- Original Message - 
From: "Simon Albrecht" <simon.albre...@mail.de>

To: "Noeck" <noeck.marb...@gmx.de>; <lilypond-user@gnu.org>
Sent: Sunday, February 07, 2016 1:45 PM
Subject: Re: Super and sub


On 07.02.2016 14:27, Noeck wrote:

Could someone guide me a bit, how to upload the patch?
Should the issue 3619 [1] be continued or a new one created?


It’ll be better to create a new one.
The procedure to submit patches is explained in the CG, see especially
<http://lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl>.
Basically, if everything is set up, you do the following:
– Create a new local branch, make your changes and commit them.
– Run ‘git cl upload origin/master’. This will create a Rietveld issue
and try to create an Allura tracker issue as well, which currently
always fails.
– So you create an issue manually (if you don’t have permission, just
ask on the devel list), linking to the Rietveld issue, with
Status:Started and Patch:new.
And then review cycle begins. When the issue is set to Patch:push and
you don’t have push access, you should send patches (created via ‘git
format-patch HEAD~n’, where n is the number of commits) to James.
For further questions, just ask on the devel list.

Best, Simon

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


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

Re: Super and sub

[Noeck]

Dear Robert,

are you aware of bass figures in LilyPond?
http://www.lilypond.org/doc/v2.19/Documentation/notation/figured-bass

I think that's the way to go here instead of using markup.

Cheers,
Joram

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

Re: Super and sub

[Robert Blackstone]

Dear David,

Thank you very much. Perfect. This is what I had hoped for.

I needed some time to find out how to insert "real" LilyPond accidentals 
instead of your "♯" but I think I can manage that now.
(Just curious: What is ♯? Not the normal #.)


Best regards,
Robert Blackstone

On 7 Feb 2016, at 11:39 , David Kastrup  wrote:

> Robert Blackstone  writes:
> 
>> Dear All,
>> 
>> Just as I was trying to formulate a request for some additional feature 
>> related to
>> Super and Sub I saw Joram's mail, the first of this thread, with which I very
>> much agree.
>> 
>> So maybe I can use this thread to ask for the following:
>> 
>> In comments accompanying some scores I feel a need for BC figures, as shown
>> in these screenshot:. (typeset with ConTeXt, Im not sure this feature exists 
>> in
>> LaTeX)
>> 
>> *
>> and 
>> *
>> 
>> Would this be doable in LilyPond ? A sort of unattached Super-Sub couple (and
>> triple)
>> If not, could it somehow be added to its immense reservoir of features?
> 
> #(define-markup-command (stack layout props args) (markup-list?)
>  (interpret-markup layout props
>   #{ \markup \tiny \raise #0.5 \general-align #Y #CENTER
>  \override #'(baseline-skip . 2) \right-column #args #}))
> 
> \markup { Would be a \stack {6 5 3} on the 
> harmonized as \stack { 7 ♯3 } → \stack { 7 5 }, }
> 
> 
>> (Preferably with LilyPonds own accidentals and perhaps the BC-font.)
> 
> Well, what you put in there is up to you.
> 
> -- 
> David Kastrup


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

Re: Super and sub

[Kieren MacMillan]

Hi all,

> Of course, where the current situation is "this looks awful", getting
> one's start values from LaTeX for comparison is a possible first step.

There seems to be a reasonably good starting point at 
.
Not sure if we should include all four types they’ve identified.

Cheers,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: Super and sub

[Thomas Morley]

2016-02-07 14:50 GMT+01:00 Phil Holmes <m...@philholmes.net>:
> I wasn't aware that git-cl "always fails".  Could you describe the problem
> and provide a traceback?
>
> I everyone having the same problem?

Well, maybe I confuse something, but I thought we don't use Allura at
all, but sourceforge.net.

Nevertheless, for me it _always_ creates a new entry there (if I enter
nothing when asked for an issue-number)

Cheers,
  Harm

>
> --
> Phil Holmes
>
>
>
> - Original Message - From: "Simon Albrecht" <simon.albre...@mail.de>
> To: "Noeck" <noeck.marb...@gmx.de>; <lilypond-user@gnu.org>
> Sent: Sunday, February 07, 2016 1:45 PM
> Subject: Re: Super and sub
>
>
>
> On 07.02.2016 14:27, Noeck wrote:
>>
>> Could someone guide me a bit, how to upload the patch?
>> Should the issue 3619 [1] be continued or a new one created?
>
>
> It’ll be better to create a new one.
> The procedure to submit patches is explained in the CG, see especially
> <http://lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl>.
> Basically, if everything is set up, you do the following:
> – Create a new local branch, make your changes and commit them.
> – Run ‘git cl upload origin/master’. This will create a Rietveld issue
> and try to create an Allura tracker issue as well, which currently
> always fails.
> – So you create an issue manually (if you don’t have permission, just
> ask on the devel list), linking to the Rietveld issue, with
> Status:Started and Patch:new.
> And then review cycle begins. When the issue is set to Patch:push and
> you don’t have push access, you should send patches (created via ‘git
> format-patch HEAD~n’, where n is the number of commits) to James.
> For further questions, just ask on the devel list.
>
> Best, Simon
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

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

Re: Super and sub

[Phil Holmes]

We use an Allura server hosted on sourceforge.

--
Phil Holmes


- Original Message - 
From: "Thomas Morley" <thomasmorle...@gmail.com>

To: "Phil Holmes" <m...@philholmes.net>
Cc: "lilypond-user" <lilypond-user@gnu.org>; "Simon Albrecht" 
<simon.albre...@mail.de>

Sent: Sunday, February 07, 2016 2:15 PM
Subject: Re: Super and sub


2016-02-07 14:50 GMT+01:00 Phil Holmes <m...@philholmes.net>:

I wasn't aware that git-cl "always fails".  Could you describe the problem
and provide a traceback?

I everyone having the same problem?


Well, maybe I confuse something, but I thought we don't use Allura at
all, but sourceforge.net.

Nevertheless, for me it _always_ creates a new entry there (if I enter
nothing when asked for an issue-number)

Cheers,
 Harm



--
Phil Holmes



- Original Message - From: "Simon Albrecht" 
<simon.albre...@mail.de>

To: "Noeck" <noeck.marb...@gmx.de>; <lilypond-user@gnu.org>
Sent: Sunday, February 07, 2016 1:45 PM
Subject: Re: Super and sub



On 07.02.2016 14:27, Noeck wrote:


Could someone guide me a bit, how to upload the patch?
Should the issue 3619 [1] be continued or a new one created?



It’ll be better to create a new one.
The procedure to submit patches is explained in the CG, see especially
<http://lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl>.
Basically, if everything is set up, you do the following:
– Create a new local branch, make your changes and commit them.
– Run ‘git cl upload origin/master’. This will create a Rietveld issue
and try to create an Allura tracker issue as well, which currently
always fails.
– So you create an issue manually (if you don’t have permission, just
ask on the devel list), linking to the Rietveld issue, with
Status:Started and Patch:new.
And then review cycle begins. When the issue is set to Patch:push and
you don’t have push access, you should send patches (created via ‘git
format-patch HEAD~n’, where n is the number of commits) to James.
For further questions, just ask on the devel list.

Best, Simon

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


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



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

Re: Super and sub

[Paul Morris]

> On Feb 7, 2016, at 8:50 AM, Phil Holmes  wrote:
> 
> I wasn't aware that git-cl "always fails".  Could you describe the problem 
> and provide a traceback?
> 
> Is everyone having the same problem?

It has been working fine for me.  (I think I remember once where it didn’t 
create or update the Allura issue?)

-Paul
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Pierre Perol-Schneider]

Hi all,
Please be so kind to attached objective examples including publishers' name.
What you "imagine", what's "possible" or "seems like" won't help much
here...
Cheers,
Pierre

2016-02-06 22:24 GMT+01:00 John Gourlay :

> Joram,
>
> As you say, LaTeX is for producing beautiful mathematics and LilyPond is
> for producing beautiful music. It’s possible that the conventions in the
> two different kinds of typography differ in their placement of sub and
> superscripts, and so LaTeX and LilyPond should differ in their behavior.
> This seems like the first question that should be answered before asking
> whether LilyPond is making the best placement choices. I’ll let people with
> more experience in music notation weigh in.
>
> John Gourlay
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Urs Liska]

Am 6. Februar 2016 22:24:41 MEZ, schrieb John Gourlay 
:
>Joram,
>
>As you say, LaTeX is for producing beautiful mathematics and LilyPond
>is for producing beautiful music. It’s possible that the conventions in
>the two different kinds of typography differ in their placement of sub
>and superscripts, and so LaTeX and LilyPond should differ in their
>behavior. 

I'm sure Joram is not speaking of formulas but of superscript in plain text 
paragraphs. And I don't see why we shouldn't take LaTeX with its decades of 
typesetting experience as a model for the plain text parts of LilyPond scores.

If LilyPond scores contain text areas they should of course look good,  and 
there is much room for improvement here.

My 2 Ct.
Urs

>This seems like the first question that should be answered
>before asking whether LilyPond is making the best placement choices.
>I’ll let people with more experience in music notation weigh in.
>
>John Gourlay
>
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

Re: Super and sub

[Trevor Daniels]

Kieren MacMillan wrote Saturday, February 06, 2016 8:03 PM

>> - raise the superscript by 0.8 instead of 1.0
>> - lower the subscript by -0.4 instead of -0.75
> 
> In my opinion, these are both improvements on the current default.

I agree.

Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Werner LEMBERG]

>> I compared the Lilypond result of \super and \sub to the
>> equivalents in LaTeX (because who would doubt that LaTeX is wrong
>> in such a question)

Please have a look at other, non-CM fonts also, since CM is sometimes
a bit peculiar :-)

>> - raise the superscript by 0.8 instead of 1.0
>> - lower the subscript by -0.4 instead of -0.75
> 
> In my opinion, these are both improvements on the current default.

I could imagine to have values that vertically position the subscript
and superscript glyphs a tiny bit more away from the center.


Werner

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

Re: Super and sub

[Kieren MacMillan]

Hi Joram,

> I compared the Lilypond result of \super and \sub to the equivalents in
> LaTeX (because who would doubt that LaTeX is wrong in such a question)

=)

> Of course LilyPond's emphasis is on beautiful music notation,
> but I think also text parts of scores should look good.

Agreed!

> - raise the superscript by 0.8 instead of 1.0
> - lower the subscript by -0.4 instead of -0.75

In my opinion, these are both improvements on the current default.

Thanks!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: Super and sub

[Pierre Perol-Schneider]

+1
See the wish I had in 2013:
http://lilypond.1069038.n5.nabble.com/WISH-about-super-and-sub-td152384.html

Pierre

2016-02-06 21:34 GMT+01:00 Trevor Daniels :

>
> Kieren MacMillan wrote Saturday, February 06, 2016 8:03 PM
>
> >> - raise the superscript by 0.8 instead of 1.0
> >> - lower the subscript by -0.4 instead of -0.75
> >
> > In my opinion, these are both improvements on the current default.
>
> I agree.
>
> Trevor
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[John Gourlay]

Joram,

As you say, LaTeX is for producing beautiful mathematics and LilyPond is for 
producing beautiful music. It’s possible that the conventions in the two 
different kinds of typography differ in their placement of sub and 
superscripts, and so LaTeX and LilyPond should differ in their behavior. This 
seems like the first question that should be answered before asking whether 
LilyPond is making the best placement choices. I’ll let people with more 
experience in music notation weigh in.

John Gourlay


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

Re: Super and sub

[John Gourlay]

I was thinking that text produced by LilyPond would likely be about music, with 
references, for example, to chords with superscripts in their names. It would 
appear odd if the chord names in text appeared differently than in the music 
itself.

John
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user