LilyIssues / Issues / #1189 Create Texinfo @multitable entries for the articulations.Appendix

Google Importer - 2010-07-17

Originally posted by: percival.music.ca@gmail.com

(No comment was entered for this change.)

Labels: -Priority-Medium Priority-Low

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2011-11-23

Originally posted by: pkx1...@gmail.com

(No comment was entered for this change.)

Labels: -Priority-Low

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2013-11-13

Originally posted by: haydenpi...@gmail.com

Notation A.13 similarly requires more logical restructure within the reference. More appropriate may be a definition table with headings "name" "articulation" "shortcut" producing an example such as: "Staccato" "\staccato" "\." or something along these lines.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2013-11-13

Originally posted by: dak@gnu.org

script-chart.ly does not reference LilyPond internals to get at the articulations as far as I can see. A brutishly boring rendition as, indeed, verbatim code seems like a feasible replacement. That would not require expertise with Scheme. It should also not take 5 hours.

It also does not look significantly more maintenance intensive after changes than generated code would be.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2013-12-24

Originally posted by: pkx1...@gmail.com

The layout for the appendix is quite elegant though, so I wondered if there as a way to set more context settings inside the @lilypond[...] macro (?).

I.e. currently I can see that A.13 uses

   \context {
    \RhythmicStaff
    \remove "Time_signature_engraver"
    \hide BarLine
    \override Stem.direction = #down
}

Is there a way to do this in the macro without having to explicitly state it verbatim - not that that matters but it would look better in the resulting verbatim code - I think anyway.

Summary: articulation-generating script needs verbatim @lilypond (A10 and A13 Appendices of NR)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-02-22

Originally posted by: PhilEHol...@googlemail.com

Just to add some clarity: A10 and A13 are the same, but from different versions of the NR. The appendix being referred to is "List of articulations".

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-02-22

Originally posted by: PhilEHol...@googlemail.com

To follow up: in my PDF reader, the text under each script is rendered as text, not image data. I can copy and paste it and search for it in the reader. I would have thought it would therefore be readable by blind users?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-02-23

Originally posted by: pkx1...@gmail.com

I think the point of this was to use @lilypond[verbatim] examples than what it is at the moment - scripts calling the scheme code to draw the notes and articulations - so that a blind user could read what the lilypond code would be. It actually has more use than just for blind users (i.e. see my work for http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=2fbb7b60302656648646817959da1f2c4f5f74de )

I know now how to modify the @lilypond[...] options see mistaken (and subsequently reverted) checkin

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=188b925d9b2b1c98331dc2d99c6f48f455d380b7

but have not yet been able to get a 'nice' layout without staff lines (at least involving simple code without a lot of overrides and \removes constructs.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-06-28

Originally posted by: pkx1...@gmail.com

I've now been using a pretty good layout for these Appendixes which, while not 'scripted' (they just use Texinfo @multitable layouts) I think there was some comment that maintenance would be just as much work in a script, where the 'articulations' have to be entered in the 'script' that builds the page, as Texinfo code. At least in this way, it makes it simpler for others that do doc work to be at least keep these tables updated and it also allows for the examples to be manipulated much simpler (I think anyway).

See checkins

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=17fecdfc86780cccffdf8fb91a1394da2980860a

and

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=4cd16b30ea12e67d0c67c3e5663db113ae95db5f

If you are interested.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-06-28

Originally posted by: pkx1...@gmail.com

(No comment was entered for this change.)

Summary: articulation-generating script needs verbatim @lilypond (Appendices of NR)
Owner: pkx1...@gmail.com

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-06-28

Originally posted by: pkx1...@gmail.com

Doc: Appendix A14 List of Articulations

Issue 1189

Create Texinfo @multitable entries for the articulations.Appendix

http://codereview.appspot.com/102700044

Labels: Patch-new
Status: Started

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-06-28

Originally posted by: pkx1...@gmail.com

Still needs work.

Labels: -Patch-new Patch-needs_work

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-09

Originally posted by: pkx1...@gmail.com

(No comment was entered for this change.)

Summary: Create Texinfo @multitable entries for the articulations.Appendix
Labels: -Patch-needs_work

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-09

Originally posted by: pkx1...@gmail.com

Patch has been reduced in size to only cover articulations and ornamentations to aid in the review process. Other entries will be changed in a later patch, assuming this passes.

http://codereview.appspot.com/102700044

Labels: Patch-new

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-09

Originally posted by: pkx1...@gmail.com

Patchy the autobot says: passes make, make check and a full make docs.

Labels: -Patch-new Patch-review

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-09

Originally posted by: pkx1...@gmail.com

Added second example for each script showing the articulation on the low note, some 'scripts' have different glyphs when attached 'down'. Removed the note referenced in the @code and just left the script command 'as is'.

http://codereview.appspot.com/102700044

Labels: -Patch-review Patch-new

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-09

Originally posted by: pkx1...@gmail.com

Patchy the autobot says: passes make, make check and a full make docs. An example of the output can be downloaded here (PDF): https://www.hightail.com/download/ZUcyNWNxeFhwTVZ2Zk1UQw

Labels: -Patch-new Patch-review

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-10

Originally posted by: pkx1...@gmail.com

Patch on countdown for July 15th 2014

Labels: -Patch-review Patch-countdown

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-15

Originally posted by: pkx1...@gmail.com

Patch counted down - please push

Labels: -Patch-countdown Patch-push

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-15

Originally posted by: pkx1...@gmail.com

author    James Lowe <pkx166h@gmail.com>
    Wed, 9 Jul 2014 19:13:24 +0000 (20:13 +0100)
committer    James Lowe <pkx166h@gmail.com>
    Tue, 15 Jul 2014 16:33:12 +0000 (17:33 +0100)
commit    [r85530210e95f55885e6b472e753b7561739fa472]

Note this is only Part 1, more patches to follow.

Labels: -Patch-push Patch-needs_work

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-15

Originally posted by: pkx1...@gmail.com

Doc: Appendix - Articulations and Ornamentation - part 2

Issue 1189

Create Texifo @multitable entries for the
List of Articulations appendix.

As there are a lot of separate scripts being
documented this Issue is going to be split
into multiple, smaller, parts to aid in the
review process. Part 1 was commit 8553021

This is part 2 and covers 'Fermata', 'Instrument
specific', 'Repeat signs' and 'Ancient' scripts.

Also after more consideration I have added an
extra column compared to the previous @multitable
construction and also brought the verbatim script
into the sale column as the @lilypond example
saving a significant of wasted page space.

Also removed unnecessary lilypond-book variables
thus making the texinfo code less noisy.

http://codereview.appspot.com/114840043

Labels: -Patch-needs_work Patch-new

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-15

Originally posted by: pkx1...@gmail.com

Hmm.. fails make. I can build my construction in a raw *.tely file using manual lilypond-book commands but it seems that I am getting complaints about max of 4 columns in multitable (I am trying to use 5 here).

More investigation needed on my part.

Labels: -Patch-new Patch-needs_work

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-16

Originally posted by: pkx1...@gmail.com

Changed from 5 to 4 column @multitable entries to see if this allows make doc

http://codereview.appspot.com/114840043

Labels: -Patch-needs_work Patch-new

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-16

Originally posted by: pkx1...@gmail.com

Patchy the autobot says: passes 'make', 'make check' and a full 'make doc'. includes a full make doc

Labels: -Patch-new Patch-review

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2014-07-18

Originally posted by: pkx1...@gmail.com

(No comment was entered for this change.)

Labels: -Patch-review Patch-needs_work

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Create Texinfo @multitable entries for the articulations.Appendix

Issue Tracker for LilyPond

Searches

Help

#1189 Create Texinfo @multitable entries for the articulations.Appendix

Discussion