Community
Participate
Working Groups
The Confluence language parser should handle table attributes in a way so that end result tables can be rendered similar to how it's done in Confluence itself. Basically we want a "1px solid #ddd border" around each cell and a #f0f0f0 background on table headers. Future implementations may improve on this and handle customised rendering of the tables. The parser does not understand the markup for subscript and superscript. Nor is there support in Attributes for these text effects and consequently the XSL:FO/HTML generators cannot output the required code. See bug 336904. Lastly escaped characters are not properly handled. Sometimes you can for instance see @\-@ in the generated XSL:FO. This markup should be handled as a plain dash character.
(In reply to comment #0) > The parser does not understand the markup for subscript and superscript. Nor is > there support in Attributes for these text effects and consequently the > XSL:FO/HTML generators cannot output the required code. See bug 336904. On further inspection I found that the parser does indeed support these two glyph types so there appears to be no need to handle it further in ConfluenceLanguage.
Thanks for the bug. For the table attributes, please provide an example of Confluence markup and the desired output. Please file a separate bug for character escaping.
Hi David. I do have a small patch for that sets the table attributes as Confluence would. It depends on bug 336813.
Great, feel free to attach the patch!
Created attachment 191162 [details] Patch for handling table attributes Oh... I was about to do that and apparently got distracted. Patch attached. Note that it also contains required changes from bug 336813.
The patch looks good, but it's hard to verify without some JUnit tests. Can you please provide some test cases? Feel free to add methods to one of the existing @XslfoDocumentBuilderTest@ classes (see attached context).
Created attachment 194968 [details] mylyn/context/zip
(In reply to comment #6) > The patch looks good, but it's hard to verify without some JUnit tests. Can you > please provide some test cases? Feel free to add methods to one of the existing > @XslfoDocumentBuilderTest@ classes (see attached context). Sure. Will do.
With Atlassian removing the wiki markup format in their Confluence 4.0 release I think continuing supporting Confluence is a waste of time. I'm resolving this as WONTFIX. http://blogs.atlassian.com/2011/11/why-we-removed-wiki-markup-editor-in-confluence-4/
Reopening as this came up again.
Looks like a duplicate. I'm taking a look at the original issue. *** This bug has been marked as a duplicate of bug 310611 ***