Template:Tscore/doc

&#160;DRAFT

This template/module is under construction. It may be used for merging multiple parts of score-based music from Page namespace into a single music page in main namespace as well as for manual setting of staff width.

Parameters

 * (optional): unique identifier for merging multiple pages with Tscore template, used on first page of music; if set, also should be set.
 * (optional): same identifier as for, used on subsequent pages.
 * (optional): name of the next page in Page namespace that music from current page is continued on; the "Page:" prefix may be omitted. It is required if is set.
 * (required): score code; note that vertical lines | shold be replaced by &lcub;&lcub;!&rcub;&rcub;. Extra variables containing music (s-variables) or lyrics (l-variables) can be used as  and  ; see below.
 * {optional): staff line width (in milimeters); defaults to 180 as in standard &lt;score>. Note, that for Page namespace width is now limited to 120.
 * {optional): extra layout settings for &lt;score>; you may need to set  here to avoid first line indentation that is default in Lilypond.
 * {optional): set it to 1 to dump the code provided to lilypond; used only for debugging
 * (where variable is an arbitrary sequence of letters) (optional): arbitrary variables used for merging multiple parts of lyrics across pages; values of the same are concatenated across subsequent pages, when generating music in main namespace. Number of variables is not limitted, The values must be set in all subsequent pages that are merged (even if empty on some of them)
 * (where variable is an arbitrary sequence of letters) (optional): arbitrary variables used for merging multiple parts of music (notes) across pages; values of the same are concatenated across subsequent pages, when generating music in main namespace. Number of variables is not limitted, The values must be set in all subsequent pages that are merged (even if empty on some of them)

Remarks

 * 1) You may not use vertical lines   in music code when using this template; use &lcub;&lcub;!&rcub;&rcub; instead
 * 2) You may not use other templates in music / lyrics code on all pages but first (wikicode of subsequent pages is parsed using LUA parser that may be mislead by such templates)
 * 3) You may not use pairs of unseparated brackets: ,   in Lilypond code; separate them with a space:  ,.
 * 4) When displaying in main (or another except Page) namespace, the whole (merged) music is displayed as it is on first page (the one with  parameter). Templates from subsequent pages displays as empty (this is similar to hws / hwe behaviour).
 * 5) You should use the   Lilypond clause carefully; otherwise the results of merged music code may be shofted of one or move octaves. The safast is to set the base for   on next page to the absolute value of last note at the previous page in each context (each ) or not use this clause at all.
 * 6) The midi music generation and vorbis player are always set on

Merging
The following split code is equivalent to the above example:
 * page #1


 * page #2


 * Note: different code for on page #2: especially different base for