John Hendy <jw.he...@gmail.com> writes: > I use this, or at least things like this. For example: > > * task > :PROPERTIES: > :start: 2014-11-03-08:00 > :task_id: task_d > :depends: task_a task_b task_c > :duration: 30min > :END: > > Not multi-line, but currently I can feed any property that matches a > tj3 attribute (e.g. "task_id") and Org will "do the right thing."
This usage is perfectly fine and will continue to work. There are some very obscure attributes that taskjuggler (and the exporter) support, such as note and journalentry. These can span multiple lines. They can be used to add notes or more structured "journal" entries. A journalentry has several subparts (headline, summary, etc) but I don't think we need to support this. IMHO the best "resolution" to this is to simply take the two attributes note and journalentry out of the list of exported attributes. Or maybe better yet, add a note to the docstring. Maybe I'll just do that. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
