empty inlines are not valid RST syntax

[danse]

from RST inline markup recognition rules:

The inline markup end-string must be separated by at least one character from the start-string

this means that an empty inline will lead to an RST syntax error:

$ pandoc -f native -t rst | tee /tmp/out | rst2html > /dev/null; cat /tmp/out
Plain [Str "text", Strong []]
<stdin>:1: (WARNING/2) Inline strong start-string without end-string.
<stdin>:1: (WARNING/2) Inline strong start-string without end-string.
hi\ ****

i think that it's preferable to simply drop empty inlines so that they leave no track in the output file. note that empty inlines could come directly empty from the input document or become empty after stripping spaces because of #4329

[jgm]

Yes, dropping empty inlines in the writer seems like the thing to do. +++ Francesco Occhipinti [Mar 07 18 15:41 ]:

…

from [1]RST inline markup recognition rules: The inline markup end-string must be separated by at least one character from the start-string this means that an empty inline will lead to an RST syntax error: $ pandoc -f native -t rst | tee /tmp/out | rst2html > /dev/null; cat /tmp/out Plain [Str "text", Strong []] <stdin>:1: (WARNING/2) Inline strong start-string without end-string. <stdin>:1: (WARNING/2) Inline strong start-string without end-string. hi\ **** i think that it's preferable to simply drop empty inlines so that they leave no track in the output file. note that empty inlines could come directly empty from the input document or become empty after stripping spaces because of [2]#4329 — You are receiving this because you are subscribed to this thread. Reply to this email directly, [3]view it on GitHub, or [4]mute the thread. References 1. http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup-recognition-rules 2. #4329 3. #4434 4. https://github.com/notifications/unsubscribe-auth/AAAL5K4dOvg5jCAzpTlMTXyFkHxAtAoiks5tb_-QgaJpZM4Sgqxv

[jgm]

Closed by ba965d1