Muse2ps feature requests and bug reports - Revision history

Craig: /* Tilde and newline conflict in =C option */

2011-11-06T20:50:33Z

Tilde and newline conflict in =C option

← Older revision		Revision as of 20:50, 6 November 2011
Line 226:		Line 226:
	===Tilde and newline conflict in <nowiki>=C</nowiki> option===		===Tilde and newline conflict in <nowiki>=C</nowiki> option===

	When a n-tilde is needed in the ~~Compser~~'s name, the escape sequence "\n1" is ~~neede~~ for creating the character ñ. However, the escape sequence "\n" marks a newline for a secondary line underneath the composer (used for an opus number, for example). Therefore, some other method of indicating a newline is needed to replace "\n".		When a n-tilde is needed in the Composer's name, the escape sequence "\n1" is needed for creating the character ñ. However, the escape sequence "\n" marks a newline for a secondary line underneath the composer (used for an opus number, for example). Therefore, some other method of indicating a newline is needed to replace "\n"; probably identifying any special characters which start with <tt>\n<tt> first, and then applying the newline substitution for <tt>\n</tt>. Alternatively, add a digit to create a new special character after the <tt>\n<tt> sequence to indicate a newline. In addition, allowing multiple <tt>\n</tt> newlines is desirable (only one allowed currently).

	===Spacing of dummy time signatures ===		===Spacing of dummy time signatures ===

Craig: /* Bugs */

2011-08-16T02:04:25Z

Bugs

← Older revision		Revision as of 02:04, 16 August 2011
Line 4:		Line 4:

	== Bugs ==		== Bugs ==

			===Tuplet brackets and rests ===

			Unusual behavior for tuplet brackets when a rest is involved (or the following data is incorrect?). The following data produces the notation:

			[[image:MuseData_tupletbracket.png]]

			<pre>
			Header Record 1: optional copyright notice
			Header Record 2: optional file identification
			TIMESTAMP: AUG/15/2011 []
			08/15/2011 C. Sapp
			WK#:1 MV#:1
			Header Record 6: source
			Header Record 7: work title
			Header Record 8: movement title

			Header Record 10
			Group memberships: score
			score: part 1 of 1
			$ Q:3 T:2/4 C:4
			P C0:t2
			C4 2 1 q 3 *
			P C32::
			D4 2 1 q 3
			E4 2 1 q 3 !
			measure
			rest 6 1
			measure
			rest 2 1 q 3 *
			rest 2 1 q 3
			rest 2 1 q 3 !
			measure
			rest 6 1
			measure
			rest 2 1 q 3 *
			C4 2 1 q 3
			D4 2 1 q 3 !
			measure
			rest 6 1
			measure
			D4 2 1 q 3 *
			P C32::
			C4 2 1 q 3
			rest 2 1 q 3 !
			mheavy2
			/END
			/eof
			//
			</pre>

	===Text starting with a digit ===		===Text starting with a digit ===

Craig: /* Feature Requests */

2011-08-11T20:38:50Z

Feature Requests

← Older revision		Revision as of 20:38, 11 August 2011
Line 196:		Line 196:

	== Feature Requests ==		== Feature Requests ==

			=== Additional mensural time signature ===

			A new mensural time signature "O/3" should be created. The MuseData tempo code for it should be "T:104/0". The visual display of the mensural sign is the letter "O" over the number 3. Use the shape of the mensural sign indicated by "T:11/0" placed above the shape of the mensural sign indicated by "T:102/0".

	=== Echoing initial comment lines with <nowiki>=M</nowiki> ===		=== Echoing initial comment lines with <nowiki>=M</nowiki> ===

Craig: /* Chord text */

2011-04-07T10:38:54Z

Chord text

← Older revision		Revision as of 10:38, 7 April 2011
Line 155:		Line 155:
	</center>		</center>

	<center>		[[Image:muse2ps_chord_text_3.png\|\|center]]
	[[Image:~~muse2ps_chord_text_3~~.png]]
	</center>		===Tuplet bracket/stem directions===

			Tuplet brackets do not keep track of stems very well. It would be useful to adjust the angle and vertical placement of tuplet brackets in particular when the starting and ending notes in the tuplet group have stems in different directions. For example, the tuplet brack slope on the second tuplet in the following example is incorrect:

			[[Image:muse2ps_tuplet.png\|\|center]]

			Source MuseData:
			[[Media:muse2ps_tuplet.md2 \| muse2ps_tuplet.md2]]

			In addition, tuplet brackets on stemless notes do not accommodate the fact that the notes do not have stems, and therefore the brackets are placed too far from the noteheads. In the following example, measures 1 and 4 should visually appear identical, and measures 2 and 3 should as well:


			[[Image:muse2ps_tupletwhotenote.png\|\|center]]

			Source MuseData:
			[[Media:muse2ps_tupletwholenote.md2 \| muse2ps_tupletwhotenote.md2]]

	===Tilde and newline conflict in <nowiki>=C</nowiki> option===		===Tilde and newline conflict in <nowiki>=C</nowiki> option===

Craig: /* Echoing initial comment lines with =M */

2011-04-04T18:26:50Z

Echoing initial comment lines with =M

@@ Line 267: / Line 267: @@
 %=EndMuseData: 1
 </pre>
 === Clef/key/time signature suppression at indented line breaks ===

Craig: /* Spacing of dummy time signatures */

2011-04-04T01:31:44Z

Spacing of dummy time signatures

← Older revision		Revision as of 01:31, 4 April 2011
Line 167:		Line 167:
	When a time signature is not given at the start of the music, the space between the clef and the first note is good. When a dummy time signature is given (such as T:9/0), there is extra space added between the clef and the first note which appears to be the width of a cut-time metrical sign. It would probably be a good idea to set the width of a dummy time signature to 0. Illustration of the extra space and comparing between the various time signature settings:		When a time signature is not given at the start of the music, the space between the clef and the first note is good. When a dummy time signature is given (such as T:9/0), there is extra space added between the clef and the first note which appears to be the width of a cut-time metrical sign. It would probably be a good idea to set the width of a dummy time signature to 0. Illustration of the extra space and comparing between the various time signature settings:

	~~<center>~~		[[Image:muse2ps_features_sanctustimesig.png\|\|center]]
	[[Image:muse2ps_features_sanctustimesig.png]]
	~~</center>~~

	MuseData for example: [[Media:sanctustimesig.md2 \| sanctustimesig.md2]].		MuseData for example: [[Media:sanctustimesig.md2 \| sanctustimesig.md2]].


			===Systembreak interaction with editorial accidentals===

			When an editorial accidental is placed on a note which is tied over a system break, a regular-style cautionary accidental is placed on the tied note on the next system. This cautionary accidental should instead be in the same style as the editorial accidental.

			[[Image:muse2ps_features_editorialbreak.png\|\|center]]

			MuseData for example: [[Media:editorialbreak.md2 \| editorialbreak.md2]].

	== Feature Requests ==		== Feature Requests ==

Craig: /* Spacing of dummy time signatures */

2011-04-04T00:08:51Z

Spacing of dummy time signatures

← Older revision		Revision as of 00:08, 4 April 2011
Line 158:		Line 158:
	[[Image:muse2ps_chord_text_3.png]]		[[Image:muse2ps_chord_text_3.png]]
	</center>		</center>

			===Tilde and newline conflict in <nowiki>=C</nowiki> option===

			When a n-tilde is needed in the Compser's name, the escape sequence "\n1" is neede for creating the character ñ. However, the escape sequence "\n" marks a newline for a secondary line underneath the composer (used for an opus number, for example). Therefore, some other method of indicating a newline is needed to replace "\n".

	===Spacing of dummy time signatures ===		===Spacing of dummy time signatures ===

Craig: /* Chord text */

2011-03-21T21:35:19Z

Chord text

@@ Line 73: / Line 73: @@
 /eof
 //
-</pre>
+</pre></td></tr></table>
 The above MuseData generates the following notation:
@@ Line 79: / Line 80: @@
 <center>
 [[Image:muse2ps_chord_text.png]]
 </center>

Craig: /* Text starting with a digit */

2011-03-21T20:38:07Z

Text starting with a digit

← Older revision		Revision as of 20:38, 21 March 2011
Line 40:		Line 40:

	But it would be preferred that the second note (D4) have a "2" shown below it.		But it would be preferred that the second note (D4) have a "2" shown below it.


			===Chord text===

			Lyric text attached to chords has to be placed on the last note listed in a chord. However, it seems more logical to place the text on the first note of the chord. In any case, the position of the text in the chord data is not specified in the [[Media:Stage2-specs.html\|MuseData stage2 specification]].

			<center><table cellspacing=0 cellpadding=0><tr><td bgcolor=#ffffff>
			<pre>
			Header Record 1: optional copyright notice
			Header Record 2: optional file identification
			TIMESTAMP: MAR/21/2011 [md5sum:0d0a:d26153bf39ade160d1aaeafc54a33b39]
			03/21/2011 C. Sapp
			WK#:1 MV#:1
			Header Record 6: source
			Header Record 7: work title
			Header Record 8: movement title

			Header Record 10
			Group memberships: score
			score: part 1 of 1
			$ Q:1 C:4
			C4 1 1 q a1
			E4 1 1 q a2
			G4 1 1 q a3
			D4 1 1 q b1
			F4 1 1 q b2
			A4 1 1 q b3
			E4 1 1 q c1
			G4 1 1 q c2
			B4 1 1 q c3
			/END
			/eof
			//
			</pre>

			The above MuseData generates the following notation:

			<center>
			[[Image:muse2ps_chord_text.png]]
			</center>

	===Spacing of dummy time signatures ===		===Spacing of dummy time signatures ===

Craig: /* Bugs */

2011-03-19T18:10:01Z

Bugs

← Older revision		Revision as of 18:10, 19 March 2011
Line 4:		Line 4:

	== Bugs ==		== Bugs ==

			===Text starting with a digit ===

			Lyric text cannot start with a digit. It would be useful for displaying analytical data if lyric text can start with a digit. Example data:

			<center><table cellspacing=0 cellpadding=0><tr><td bgcolor=#ffffff>
			<pre>
			Header Record 1: optional copyright notice
			Header Record 2: optional file identification
			TIMESTAMP: MAR/19/2011 [md5sum:0d0a:d18c08728833c68ab4d3dc6687fe95bd]
			03/19/2011 C. Sapp
			WK#:1 MV#:1
			Header Record 6: source
			Header Record 7: work title
			Header Record 8: movement title

			Header Record 10
			Group memberships: score
			score: part 1 of 1
			$ Q:1 C:4
			C4 1 1 q a
			D4 1 1 q 2
			E4 1 1 q c3
			/END
			/eof
			//
			</pre>
			</td></tr></table>
			</center>

			The current output from [[muse2ps]] for this data is:
			<center>
			[[Image:Muse2ps_digits.png]]
			</center>

			But it would be preferred that the second note (D4) have a "2" shown below it.

	===Spacing of dummy time signatures ===		===Spacing of dummy time signatures ===