As said before pgc get the raw text
But that is not how the gc.com markdown work. It did the day of the release but was changed. Perhaps after iIcomplain in the thread in the forum
The has to be a space(start or end of line is also ok) before and after the formatting * or ** to make it italic or bold. That is to make the {*FTF*} tag look correct and usernames with more the two * in the to be correct
Another non standard is that for heading beginning and ending # is required to avoid incorrect formating of old logs
The real problematic markdown that i have found is that having with only - or = that is often used as a partitioning of the log text. I often used it to separate the log part for the cache and a part for the trip. It will make the rows above header 1 och header 2.
if you like to use it a separator a blank row is needed above and 3 - will be a sparator like below
Lock at Aggbjörn 2011 #2: Auforfe where the 3 top logs look terrible. On of them i mine.
Another change is that numbered list had to start with 1 to reduce unintentional list on old logs
Not a numberd list
3. bar
4. bar
a numbrerd list with whew the numbers will be changed
1. foo
3. bar
4. bar
- foo
- bar
- bar
The last part is that the preformated text is not in the documentation but works
Add a blank line and put 4 spaces in the beginning of each line and the test will be in monospace font. No markdown tags will work. It useful for listing caches for challenges so it is readable, many checkers generate output like that
The markdown editor that gc.com uses is:
http://www.toptensoftware.com/markdowndeep/dingus
There are more markdown listed inte the formate there and some works on gc.com
