harpanet / dokuwiki_st3 Goto Github PK

This 'issue' is to discuss and identify Stylistic choices to be implemented. I'll start by adding a screenshot of the existing test page.

Breakdown by Line:

1. Headings are on a line by themselves. I've left the 'markers' (==== etc.) the same colour as the heading to make them stand out even more. (The could easily be changed to 'containers' - see below).

15. Separator lines are significant to show separation.

17, 19. Control Macros stand out quite clearly to ensure they're not missed. Note the comment on line 21.

29. Inline styles have two elements. i) the 'containers' which in this case are the ** for bold and '' for monospace. These 'containers' have been faded out so they don't distract the eyes when reading the text. ii) the content, in this case the words bold and monospaced. Bold is obviously displayed in bold; As we can't change fonts within an ST3 document, I've opted to highlight monospaced text with a light-grey background. (I tend to use monospace to highlight a command or piece of code and it tends to be styled like this with a different background so I've followed that principle.)

33. As mentioned, I'm not sure if we should be showing any styles inside 'monospaced' blocks. It's hard to tell from the DokuWiki syntax page as monospace is shown as the inner segment (which is a logical way of including it). Maybe we just don't worry about this at all.

Time to implement <code ...> and <file ...> blocks (then later 'soft' code blocks which are indented by 3 spaces).

Now it starts to get more complicated. :-(

I've added a Dev branch and made it the default one. (I also added the Emoticon Grammar so I could highlight the FIXME's in the testpage.)

I have added the Grammar for Italics, with updates to the testpage. As you can see, the italics causes quite a few problems.

Any chance you can have a go at the RegExes for Italics to see if we can sort the problem?

Possibly the first thing is to stop the // in URLs from causing a problem. (I tried putting a ^:// in there to tell it not to recognise // following a colon, but that didn't work).

This is going to take some possibly complicated RegEx to fix. Any ideas?

How do we stop Italics / Bold / Monospace etc. from recognising their closing markers when the closing markers appear inside a Raw section?

Hi, can you take a look at the Regular Expression for the Bold node in the dokuwiki_st3.tmLanguage file in the Skeleton_bold branch. (Ref: 6d0c0b0 )

The current RE is copied from the Markdown.tmLanguage file.

I know I could remove the double underscores from the #Open line, but I thought I'd leave it there so you could see the entire expression as it existing in Markdown.

There are possibly a bunch of other stuff in the RE we can remove as well, but it would take me days to try and decode what it's doing.