Confluence module should do something with non-doxia formatting

The strikethrough and underline ones are duplicates of DOXIA-163 and DOXIA-164

Strictly speaking I wouls argue that is not the case, since DOXIA-163 and DOXIA-164 are Sink API issues. I meant that the Confluence module should recognise those annotations even if it can't render them properly because of limitations in another API.

Could you specify what you mean with 'do something' and 'recognize'? If the confluence parser can't emit an event to a sink, then what's the point in recognizing it? What else do you want to do with it?

I think it should render to something that is readable. In the case of citation and underline, the intention of the author was to highlight the text, so citation->italic, underline->italic/bold makes sense. Strikethrough is difficult because the intention of the author is to show something that is visible but can be ignored. Maybe a special bracket construct like [ignore]...[/ignore]? Superscript and subscript could be rendered as ^(...) and _(...).

I imagine they are not lost as things are, but they also won't come out in HTML anything like the author intended. They will come out with the formatting characters from confluence, which might mean something to the author, but will be nonsense to the reader.

OK, thanks for the clarification. I have scheduled this for a later release for now, but if anyone attaches a patch (hint!) we can incorporate this easily.

Just bear in mind that the parser events should be consumable by any type of sink, eg I think citation->italic, underline->bold makes perfect sense, however inserting special markup might lead to trouble later, so just output plain text would be enough IMO.

strikethrough, underlined, superscript and subscript are now supported via SinkEventAttributes, see DOXIA-163. The confluence parser just needs to be adapted to emit the correct attributes.

Writing to confluence markup is fixed in r1465304

Reading from confluence markup is fixed in r1465353