Juan Pablo Santos RodrÃguez created JSPWIKI-1180:
----------------------------------------------------
Summary: Plain editor full support of markdown
Key: JSPWIKI-1180
URL: https://issues.apache.org/jira/browse/JSPWIKI-1180
Project: JSPWiki
Issue Type: Task
Components: Editors
Reporter: Juan Pablo Santos RodrÃguez
(leaving it here, so it doesn't remain buried on the ML)
As of 2.11.3 we support markdown as an alternate wiki syntax. However not all
functionality of the plain editor is carried over onto the markdown syntax. As
noted on the ML:
h4. <span/> separators
JSPWiki syntax allows to set some css class/style by using the %%.. %%
directives which render span elements. On Markdown you do this by adding a
{.your_css_class} constructs at the end of the paragraph, and the Markdown
engine infers where to start applying it (ussually, the start of the
paragraph). To explicit only a section of a paragraph (a span) you have to add
an empty html comment, some like <!---->my text
here{.bg-info} (f.ex, on the sign: snip). There are a lot of places on the
Wiki.Snips file that rely on this separator. It's ugly for a Markdown file, but
I haven't found any other way to note where to begin..
h4. nScope property on tabs: and font: snips
In these cases, the ending element of the value on the nScope contains some
variable text, so I've thrown a \\w+ in hopes that this would automagically
catch that variable part, but I'm afraid it is not enough.
Something similar occurs on scope property of fontDlg:, colorDlg: and iconDlg:
snips
h4. suggest property on *Dlg: snips
The suggest: property usually contains an element with one or several regular
expressions. I haven't touched any of those as a) I don't understand most of
them, b) not sure where or how they're used, and c) also a) again.
Something similar happens on linkPart2:, linkPart3:, linkDlg: and pluginDlg:
snips, with the lback and match properties
h4. lipstick: snips
Lastly, I think I've managed to correctly implement the lipstick
element: but anoher pair of eyes would be more than welcome. Properly speaking,
another pair of eyes looking at the whole file would be more than welcome.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
