Image embedding sadly skipped if filename contains whitespace about qlmarkdown HOT 9 CLOSED

Markdown was born to be a simple language, then unfortunately, perhaps also due to the absence of a rigid syntax, it has branched into a myriad of flavors with different functionalities and extensions.

My application uses the engine cmark-gfm that is a fork from commonmark. Macdown uses a different engine (hoedown).

I have no intention of intervening on the engine code (I am not an expert C developer) to change the standard behavior.
If cmark-gfm were to add this feature, I will be happy to support it in my app.

from qlmarkdown.

@sbarex as you can see by the cross-project-link I inquired over as cmark-gfm. Let's see what they make of it.

from qlmarkdown.

Thanks, I didn't know the syntax of angle brackets!

from qlmarkdown.

White space is not allowed inside url, they must be encoded as %20.
See the markdown link specification:

... a nonempty sequence of characters that does not include ASCII space or control characters...

from qlmarkdown.

Thanks for quoting the specification.

Could QLMarkdown nevertheless consider this as a convenience option if it does not harm/complicate syntax parsing too much?

The guys from MacDown have also added this convenience option as can be seen on the screenshot.

from qlmarkdown.

I just remind that markdown's goal was an easily human readable/writeable markup language.
Having to transform   to %20 everywhere contradicts both that goals IMHO.

from qlmarkdown.

• Switching to hoedown: Neither an option to me as a layman (QLMarkdown overally looks/feels better than Macdown) and I guess also not to you.
• So my remaining option is to lobby for this feature at cmark-gfm, right?

from qlmarkdown.

When I started developing the app I didn't do a full research on what markdown engines existed. I chose cmark-gfm because it is maintained by github, although I later discovered that it is not used for managing github pages !

from qlmarkdown.

Closing as WONTFIX

• @Lemmingh informed me that URIs with spaces within round brackets would lead to ambiguity and that I can simply wrap filenames containing spaces within rounded AND angled brackets, which the Markdown syntax already supports.
• Markdown [link](</my uri>) produces HTML <p><a href="/my%20uri">link</a></p> as shown in https://spec.commonmark.org/0.30/#example-488
• I tested this and QLMarkdown via its rendering engine cmark-gfm supports this syntax just fine. See screenshots below.

Markdown Specification

https://spec.commonmark.org/0.30/#links

A link contains link text (the visible text), a link destination (the URI that is the link destination), and optionally a link title. There are two basic kinds of links in Markdown. In inline links the destination and title are given immediately after the link text. In reference links the destination and title are defined elsewhere in the document.

A link text consists of a sequence of zero or more inline elements enclosed by square brackets ([ and ]).

[…]

A link destination consists of either

• a sequence of zero or more characters between an opening < and a closing > that contains no line endings or unescaped < or > characters, or

• a nonempty sequence of characters that does not start with <, does not include ASCII control characters or space character, and includes parentheses only if (a) they are backslash-escaped or (b) they are part of a balanced pair of unescaped parentheses. (Implementations may impose limits on parentheses nesting to avoid performance issues, but at least three levels of nesting should be supported.

[…]

An inline link consists of a link text followed immediately by a left parenthesis (, an optional link destination, an optional link title, and a right parenthesis ).

Screenshot

from qlmarkdown.