On Mon, Dec 5, 2011 at 11:16 AM, Dag Wieers <[email protected]> wrote: > On Sun, 4 Dec 2011, Stuart Rackham wrote: > >> On 04/12/11 03:16, Dag Wieers wrote: >> >>> I am now implementing comments in ODF using annotations. This works >>> well, >>> but multi-line comments are considered by AsciiDoc to be separate >>> comments, even when trailing th line with a plus (+). > > > -snip- > >>> Also, ODF annotations keep track of the author and a timestamp. Would it >>> be possible to e.g. map the content of the comment to something that >>> can be used ? >> >> >> The single line comments are implemented as block macros which are not >> multi-line. The easiest solution would be to define a delimited comment >> block that generates output. The current delimited comment block does not >> generate output, which is very useful, but not what you want. > > > I feared this was the case, however I clearly see a benefit of having normal > multi-line comments be processed in blocks. > > >> For example, it would be easy to implement a 'comment' style listing >> block: >> >> [comment,dag,2011-12-03] >> --------------------------------------------------------- >> FIXME: Insert the various features from the Release Notes >> include the information from the presentations >> --------------------------------------------------------- > > > It would be very useful to have this, not just for the ODF plugin. Because > if we only add stuff to AsciiDoc for the ODF backend, then I think we all > loose :-/
Hi Dag, I have to disagree about this, comment blocks are meant to not generate output, we should not change that in a backward incompatible way. Using the same markup in different ways in different backends is a "bad thing" (tm). However adding a new block output type as Stuart suggested should be ok. But the terminology needs to be clear. It should be easy to make it clear that you are talking about a comment block which doesn't produce output or comment xxx that does. It looks to me to be another form of annotation with author and date options. So long as you can suggest backends for html and docbook that generate the same look as ODT then it should be ok to be added to standard asciidoc. A comment annotation should be sufficiently different from a comment block to be easy to distinguish. Cheers Lex > > However I would prefer to see multiline comments handled better, as this is > what most people would expect and integrates well with eg. color > highlighting in vim. The comment style listing block looks much more as if > it is part of the content. > > > -- > -- dag wieers, [email protected], http://dag.wieers.com/ > -- dagit linux solutions, [email protected], http://dagit.net/ > > [Any errors in spelling, tact or fact are transmission errors] > > -- > You received this message because you are subscribed to the Google Groups > "asciidoc" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/asciidoc?hl=en. > -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
