1 -*-outline-layout:(2 (-1 -1 0 :) 0);outline-stylish-prefixes:nil -*-
4 Features you cannot find in the documentation as working, should be
5 mentioned here. This is an assorted collection of stuff that will be
6 done, might be done, or is an idea that we want to think about.
8 Most of the items are marked in the code as well
9 Grep -i for TODO, FIXME and ugh/ugr/urg.
12 . * don't take Dimension_cache::offset in Dimension_cache::extent
13 . * Break_req handling is silly (break_forbid () + \break fucks up.)
14 . * redo all --help messages.
15 . * HaraKiriStaffContext removes bar lines and doesn't remove
16 staff margin text on removed staff lines.
19 - I would like to avoid that ties across line breaks run _through_ the
22 - I would like the possibility of forcing clef- and key- changes to be
23 printed _after_ the new bar line
25 - I would like an option to define the number of systems on which the
26 score must be distributed. As it is now it seems that I may only
27 influence that indirectly through the gourlay_maxmeasures property.
29 - if I change the property minVerticalAlign in a multi staff score with
30 lyrics the change affects the lyrics too. I would like the change to
33 - I would like to be able to influence the sloping of xtuplet brackets
35 - for one of my test scores containing a modern edition of an early
36 17'th century composition I have a leading measure containing the
37 orginal clefs and note values of the original composition. I use the
38 "harmonic" and "diamond" note head styles for that measure and would
39 like to have the stems of these notes _centered_ on the notehead as in
40 the mensural music notation.
42 - after the leading measure in the above mentioned score I want a double
43 bar line fully drawn across the staves and after that keep to the
44 ChoirStaff bar line types in the rest of the scores
46 - I would like to be able to define invisible melismatic slurs in order
47 to avoid printing slurs conflicting with an original ms of printing. Of
48 course I can achieve that by just inserting empty syllables in the
49 lyrics. But this facility implemented in the MusiXTeX preprocessor M-tx
52 - if I explicitly beam notes in a staff with auto beaming disabled I
53 would like to have these beams also to be melismatic.
55 - do I need to get warnings on 'No one to print a repeat brace' when I
56 issue a '\repeat fold 2 \alternative' statement with an empty leading
57 text item in a \lyrics context in order to achieve multiple lyrics lines
58 in a _section_ of a score ?
59 . * make all Feta (including dynamics) available to the user in
60 textual scripts. Examples: "D.S. al \coda", "\mf espress.".
62 . * ? -Q, --find-old-relative show all changes in relative syntax
63 What's old about absolute to relative conversion? Could maybe use for
67 . * \$ and $ identifier syntax in examples.
68 . * Junk ghost positioning objects eg, Script leans on Staffside
72 . * center option (??)
73 . * make mudela-book understand usepackage{geometry}
74 . * check that linewidth set in \paper is not wider than actual linewidth?
75 . * the following fails because mudelabook doesn't care that the
76 last } after \end{mudela} finishes the marginpar:
81 . * force-verbatim is maybe not that useful since latex fails with footnotes,
84 . * Key_engraver, Local_key_item
85 . * Think of comprehensive solution for "if (grace_b == self_grace_b_)"
86 . * String[String.length] doesn't trap.
87 . * y dimension units: staffspace vs. Point
90 . * Rhythmic_column and interaction stem/rhythmic_column/note_head/dots.
94 . * Lookup::text -> needs to be TeX independent.
95 . * junk Music_iterator::first_b_
99 . * [c8. c16 c16 c16] in 6/8 timesig.
100 . * staffside spanner (crescendo!) along with staffswitch.
101 . * --- 2, margin notes don't work correctly for the pianostaff (in the
102 following example, i expect the "piano" string to be centered
103 vertically between the two staves):
106 \notes \context PianoStaff <
107 \property PianoStaff.instrument = "Piano"
108 \context Staff = treble {
111 \context Staff = bass {
117 \translator { \StaffContext \consists "Staff_margin_engraver"; }
118 \translator { \PianoStaffContext \consists "Staff_margin_engraver"; }
126 . * sort out breve shapes.
127 . * \time forces keysig?
130 . * We need feta-din*.mf files for more sizes than 10.
132 - It's clumsy to have to set Staff.instr = " " to get instrument name
133 on only the first line.
135 - The syntax for chords looks clumsy with two different meanings of
136 '-' and different syntax for separating modifiers from the tonic
137 and from other modifiers. Why not use for example ':' between
138 tonic and modifier and between the different modifiers?
140 - Rests and beams don't work too well together. Example:
141 [ r8 g''16 des'] [r8 c16 a]
143 - The stemLength property should affect also beamed stems.
145 . * align left edge of broken (de)cresc/slur/tie/tuplet/volta
146 . * fix dynamics decently, ie. use kerning & ligatures.
147 . * key restorations & repeats
148 . * paperXX.ly \quartwidth, font setting not up to date. (Should read from AFM?)
149 . * * auto melismaBusy for beams.
150 . *In Caro Mio Ben, bar 8, there's a syllable that starts on a note, and
151 ends on a pair of grace notes. Standard practice is to mark this with
152 a slur starting on the main note and ending on the grace note, so a
153 singer knows where to break the words.
155 In bar 27, there's a crescendo that's supposed to start at the start
156 of the grace notes and extend to the note after the grace notes.
157 . * 5. Sometimes lyrics extend past the right end of the staff. I guess that
158 this is a similar problem (if not another symptom of the same problem) as
159 one of the spacing bugs mentioned in the TODO.
160 . * 4. Lyrics and grace sections don't go too well together.
161 The words are aligned with the main note, not the start of the
162 grace note. This is usually wrong, but is sometimes right.
163 . * decimal point in \paper {}
165 . * repeats and partial measures.
166 . * rhythmic staff & accidentals.
167 . * use melismaBusy in Lyric context to typeset melismata correctly.
168 . * ly2dvi/lilypond logfile.
170 . * hang Item on Spanner
171 . * do --safe for PS output?
173 . * collision of lyrics with span_bars. See star-spangled.
174 . * Auto_beam debugging output (waarom/wanneer heb jij die weggehaald?)
175 . * It is impossible to typeset two textual scripts that are stacked
176 on top of eachother and avoids note collisions and at the same
177 time are typeset with different textStyle. I tried to move around
178 the text_engraver and other engravers between Voice and Thread
179 but the granularity is not fine enough, the scripts have to
180 share the same engraver in order to be get correct vertical
181 position but than they cannot have different style.
182 In my opinion, all scripts that share the same staff, should
183 be stacked vertically, avoiding collisions with the notes
186 . * break priority setting from SCM.
188 . * don't shorten stems/staffs closer to each other.
189 . * accidentals closer to note head
190 . * to space the staffs/staffgroups contained in the score.
193 . * tuplets that are written as "number : note", for example
194 "3 : [image of a half note here]". possible?
195 . * a note with a circle after it, meaning:
197 note + circle = note + 1/4 of its length
199 the circle is like a dot that's not filled in. for example, on
200 page three, the c-sharp on the second line should be a quarter with
201 a circle, not a quarter tied to a sixteenth. is this at all
203 . * scm-ify \property values.
204 . * make dependencies () a virtual function.
205 . * deprecate hangOnClef.
206 . * Abstraction for engravers:
207 . * make "in-between" engraver (Tie)
208 . * make wide_spanner_engraver (line_group_spanner, staff_symbol)
209 . * store req -> element, element -> element causes for warnings
210 . * compulsory hshift
211 . * My wish list for lyrics. I dream of a time when I will have enough time to
212 become familiar enough with the source code to be able to implement some of
213 these myself, but I don't know when that will be, so I thought I'd "publish"
214 my suggestions in case someone else is in a position to give them some
215 priority. Otherwise, perhaps they could go on the todo list?
217 If any of these are already implemented, please let me what the syntax is to
220 1. Stanza numbering. Numbering at the beginning of a song with the number
221 set to the left of the first note. It would also be nice (but not as
222 important) to be able to have some form of automatic numbering at the
223 beginning of each new line. This would make it easier to follow songs with a
224 large number of stanzas.
226 3. Notes centred above/below lyrics rather than left-aligned.
228 4. It would be very nice to be able to build some kind of phrasing into the
229 lyrics of hymns, etc, so that the first words of a phrase are left aligned
230 with each other, the last words are right aligned, and the words in between
233 5. In a song, with (say) four stanzas and a chorus, it would be nice to be
234 able to vertically align the chorus midway between the staves.
236 6. It would be nice to be able to put vertical brackets either side of a
237 repeated section with different words for each repeat.
239 . * Give # lines in linebreaking.
241 . * rewrite context defs using Scheme
242 . * junk TeX specifics from internal code.
243 . * \selectmusic to cut pieces from music.
244 . * formatting of input stuff.
246 . * TODO: merge atom & molecule; make tree from molecule.
247 . * Align_element::padding ?
248 . * typo checks on property names?
249 . * use streambufs and iostream
250 to provide IO handling for TeX stream, mudela stream, data-file.
251 . * seriously buffer TeX output (do profile of writing .5 mb TeX file.)
252 . * strip EXEs before installing
253 . * zip target for binary windows dist (JBR)
254 . * fix partial measures in meaningful way.
255 . * uniformise recent feta contributions.
256 . * bigger and fatter 4/4 C
257 . * relative mode for midi2ly
258 . * junking \skip req in lyrics
259 . * midi2ly empty staffs.
260 . * use Fourier transformation for rhythmic quantisation.
261 . * horizontal centering of dynamics
262 . * $DEPENDENCIES_OUTPUT support
263 . * turn slope-damping on/off
264 . * sort out directory stuff.
266 . * -I option per filetype?
268 . * fix vertical alignment and stafflines
269 . * declaring Performers
270 . * *.yo: fix pod manpage layout legacy
271 . * text-items clash with stems/beams
272 . * --include, -I option for ly2dvi (pass on to lily)
273 . * fix placement of beam-less abbrev
275 <{\voiceone cis4. cis8 cis4 | cis4 cis cis | r1 }
276 {\voicetwo cis,4 r r | r2. | r1 }> |
278 . * Musical_pitch (analogous to Duration and Rhythmic_req)
279 think about, analogous to pitch:
280 * { a4 a16 } c <-- duration of c?
281 * < a4 b8 > c <-- duration of c?
283 . * make sure all ex's have a mudela-version
284 . * do rest-collisions for Multi_measure_rests as well.
285 . * split error/warning in error/warning/non_fatal_error
286 . * add a Duration_convert member to Duration_iter to set parameters.
287 Junk global duration settings.
288 . * en-,discouraged linebreaking:
289 . * handle DISALLOW < penalty > FORCE
290 . * discourage breaking of slurs
291 . * fix variable define/lookup parser global<->paper
292 . * fix title/instrument placements; see input/test/title.ly
293 . * <\voiceone c4. \voicetwo c4>
294 . * I'd like to change the \repetitions command to Jan's suggested
295 syntax: \repeat "repeatsymbol" 2 {...}, but I'm not sure that
296 I understand the implementation of repeats well enough.
297 . * add full cello suites to web site (kom op, Maarten!)
298 . * rename 'staff_line_leading' (who is being lead where?) to
299 staff_space, interline; (or other meaningful name) and use throughout
302 [-> leading are the lead strips between the sticks (lines) of
303 typeface. ie. leading is vertical space --hwn]
304 . * add mudela-book-doc source to webstie.
305 . * Rethink Time_description
306 \cadenza , \meter, should all be \properties
307 . * fix singleStaffBracket
309 . * partial -> anacrouse
310 . * move paper vars into engraver properties
311 . * add new glyphs to font.ly
312 . * check for groff / troff/ nroff et
313 . * more intelligent file searching
314 . * disable spaces in TeX stuff
315 . * handle ^C for tmp/file creation.
316 . * make LilyPond RPM fully relocatable
317 . * better hshift (dots, distance, head dependent)
318 . * didot / big point.
319 . * clefs (AG): The "8" should appear closer to the actual clef,
321 . * put errorlevel in Input class
322 . * junk nesting slurs
323 . * distinguish between unset and empty properties.
326 . * the bracket is ugly (wings are too parabolic, should be more circular)
327 . * versioning for Feta
328 . * rewrite dynamic signs. They're kind of spaghetti now.
329 . * The `3' in the meter key is a one or two pixels too thin (at 600dpi)
331 . * design macro for penstroke with rounded endings
332 . * timesig C: fat yet less curved. Check out relations.
333 . * design decent macro for bulbed endings
334 . * printer dependencies.
337 . * work out sizes of character fonts.
339 . * piano pedals: Ped/*
341 . * coda signs: Segno, O+
342 . * glissando, arpeggio
344 . * include important spacing dims in fetalog
345 . * scalability: use blot_diameter everywhere, make font chubbier for
349 . * UMR: Uninitialized memory read
350 This is occurring while in:
353 Keyword_table::Keyword_table(Keyword_ent*) [keyword.cc:28]
354 My_lily_lexer::My_lily_lexer() [my-lily-lexer.cc:78]
355 My_lily_parser::parse_file(String,String) [my-lily-parser.cc:54]
356 do_one_file(String,String) [scores.cc:124]
357 Reading 4 bytes from 0xefffeca8 on the stack.
358 Address 0xefffeca8 is 728 bytes below frame pointer in function
359 . * GNU diff 2.7: diff -rN does not see a new directory with empty file
360 . * patch: don't touch timestamp if all patches fail.
361 . * MetaPost: should not generate setgray for unfill
362 . * mfplain.ini not in tetex 0.9
363 . * mf-to-table -> add space 'before ; in AFM output. (-> check AFM
364 spec. Is this a bug in afm2tfm?)
365 . * check out GCC signatures?
367 f = fopen ("/dev/null", "r")
369 . * tetex: mfplain.mem
373 . * stack scripts in chords:
374 % fingering: footing:
375 < a-4 c-2 g-1 > < c-\ltoe e-\lheel >
377 . * slur parts as a script
378 . * stack parameterised scripts for fingering and footing:
381 . * automatically add a \version if not present.
384 . * convert-mudela -e empty.ly
386 . * emacs mudela-mode
387 . * should handle block comments too.
388 . * handle lexer modes (\header, \melodic, \lyric) etc.
391 . * fontlock: \melodic \melodic
393 . * use properties for:
399 . * optimal pagebreaking.
401 . * internationalisation for input.
402 . * Unicode support? -> man 7 unicode
403 . * (The explanation below is mostly intended for Han-Wen and Jan)
404 > Before, the font was changed with macros declared separately for
405 > pure TeX and LaTeX, but now all the fonts are declared directly in
406 > the generated code using the low-level TeX commands. This circumvents
407 > the fontencoding mechanism of LaTeX and is a potential source of
408 > problems also for us users of the Latin-1 character set.
409 > I think it still works since the inputencoding latin1 is
410 > declared by ly2dvi, but it still means that e.g. an o with
411 > umlaut is typeset as a combination of the two symbols 'o' and
412 > 'umlaut' instead of as a single character, as would be the case
413 > if fontencoding OT1 had been used. This shouldn't give any
414 > difference in layout, though. One of the main argument for using
415 > fontencoding OT1 is for the hyphenation mechanism to work, an
416 > argument that's clearly irrelevant in our application. Yet we
417 > see the problem for August.
420 . * output header info to MIDI too.
422 . * a musical dictionary. See Documentation/vocabulary-*, other
432 . * guitar chords (fret diagrams)
433 . * other chord name styles (american(?) style)
438 . * derive lily_stream, Dstream, texstream from ostream?
439 . * indentable stream as baseclass for TeX stream, lily stream, Dstream.
440 . * use dstream feature in midi2ly
441 . * integrate IO checking into stream class
448 . * add to MIDI output:
449 . * sharp / flat on trills (in MIDI ??)
450 . * ornaments (and trills?)
454 > Would it be hard to add support for proper dynamics in MIDI output? I
455 > would really like to have this feature...
457 Concretely spoken, for dynamics you have to write a performer
458 (Dynamics_performer), that will take the input requests. If I
459 understand correctly, every MIDI note played must have its dynamic
460 strength set separately. That means the the Dynamics_performer must
461 set the strength of every Audio_note it finds. This means that one
462 has to modify existing Audio items. The best way of doing this is
463 with a broadcast/acknowledge process.
465 So the best way of handling this, is
467 1 supporting dynamic settings in Audio_note
469 2 Write a Dynamics_performer that will modify
470 any notes it finds to set appropriate strengths.
472 I'd say that the work involved is not hard, but you have to be fluent
473 with C++ and need some insight into the working of Notation Contexts
474 and friends. I guess I could do it in a day or so, but if you are not
475 so fluent with the inner workings of LilyPond, it could take you some
476 more time (A few more days?).
478 Please note, that I am *not* going to code this myself: my days are
479 valuable, and I think I have more interesting things to do than fixing
480 the MIDI output (I don't even have a soundcard). But I *do* want to help
481 you or other people with implementing this, so if you need help, don't
483 . * account for rhythmic position in measure
487 . * Output class, handles : (smallish)
488 . * help text /(c) notice?
490 . * warning /errors/progress
491 . * abort on error/warning; exit status
492 . * quiet/ignore-version options
496 . * speed up PS code.
497 . * PS lines to .eps files
498 . * write custom prolog
503 . * remove links to non-free SW.
504 . * internal documentation
507 . * left/rightbeamcount
508 . * various other new properties.
513 . * Doc (C) stuff of sheet music
514 . * a better format? SGML? TeX? Info?
515 . * a better tutorial
517 . * more spanners (smallish)
521 . * Rewrite Stem, Beam (hairy)
522 . * general shaving on Beam and Stem
523 . * use plet grouping
527 . * Ledger lines, should be separate item: Ledger_lines
528 . * set different line sizes / thicknesses
529 . * beam stem showthrough, inter beam sizes (french vs german style)
532 . * left/right note balls should be handled by Collision:
533 < \multi 2; { \stem 1; <b c> } { <f as b> } >
536 . * merge key{item} & localkey{item}?
537 . * spacing, national styles?
540 . * redo Notehead to allow digits as heads
541 . * add a \tablature {} lexer mode for easy entering
543 . * should adjust stemlength for flag number.
546 . * caching breakpoints
548 . * specify number of lines
551 . * convention for slurs vs. phrasing marks.
555 . * \bla {} vs \bla ;
556 . * mix engraver hacking with music ?
557 . * \once\property KEY = VAL
559 . * abstract grammar.
560 . * Figure out semicolons.
571 . * configure pitch_byte
572 . * rest name configurable
577 . * fix confusing naming in Engraver vs Engraver_group_engraver (context)
579 . * A range for context errors (eg. mark both { and }. )
581 . * lyric in staff (sharpsharp in staff, text below)
583 . * write Dynamic_line (to group dynamics horizontally)
585 . * use Real for all y positions.
587 . * half-sharps, half-flats
589 . * adaptive accidental spacing.
591 . * handle EOF graciously in error messages.
593 . * midi esp.: use I32 iso int where 32 bits are needed (or assumed...)
597 . * % toe to bheel four to five
603 (where "to" is a tiny bow)
605 . * auxilliary file for caching info.
609 . * Output data structures of Mudela in XML/SGML.
610 . * create libmudela, or liblily_frontend
611 . * move MIDI stuff (including Quantization) to a ANSI C libmidi library.
612 . * Spacing_request for manually adjusting spacing
613 . * caching breakpoints
614 . * used fixedpoint arithmetic for min. energy.
619 (defvar outline-font-lock-keywords
620 '(;; Highlight headings according to the level.
621 ;; must change this to allout node layout
622 ;;("^\\(\\*+\\)[ \t]*\\(.+\\)?[ \t]*$"
623 ("^\\([.]*[ ]*[*]\\)[ \t]*\\(.*\\)$"
624 (1 font-lock-string-face)
625 (2 (let ((len (- (match-end 1) (match-beginning 1))))
626 (or (cdr (assq len '((1 . font-lock-function-name-face)
627 (2 . font-lock-keyword-face)
628 (3 . font-lock-comment-face))))
629 font-lock-variable-name-face))
631 ;; Highlight citations of the form [1] and [Mar94].
632 ("\\[\\([A-Z][A-Za-z]+\\)*[0-9]+\\]" . font-lock-type-face))
633 "Additional expressions to highlight in Outline mode.")
635 (add-hook 'outline-mode-hook
637 (setq font-lock-maximum-decoration t)
638 (setq font-lock-maximum-decoration t)
639 (make-local-variable 'font-lock-defaults)
640 (setq font-lock-defaults '(outline-font-lock-keywords t))
641 (font-lock-mode global-font-lock-mode)