Markup semantics

[MasterInQuestion]

= Markdown =

https://github.com/orgs/community/discussions/20921
[[
[ MasterInQuestion @ CE 2022-07-19 00:42:12 UTC:
https://github.com/curl/curl/issues/9162#issuecomment-1188472508
    There's semantic difference between "`" (Grave Accent) (U+0060, 0x60, `) and `"` (Quotation Mark) (U+0022, 0x22, ").
    .
    E.g.
    |*| `\x7F` means:
(Character Sequence)
[[
|1| `\` (Reverse Solidus) (U+005C, 0x5C, \)
|2| "x" (Latin Small Letter X) (U+0078, 0x78, x)
|3| "7" (Digit 7) (U+0037, 0x37, 7)
|4| "F" (Latin Capital Letter F) (U+0046, 0x46, F)
]]
    |*| "\x7F" means "\x7F" (Delete) (U+007F, 0x7F, ). ]

----

[ vszakats @ CE 2022-07-19 05:19:25 UTC:
https://github.com/curl/curl/issues/9162#issuecomment-1188609745
    It's a Markdown markup here, meaning to display it as code. ]

----

[ MasterInQuestion @ CE 2022-07-19 05:42:57 UTC:
https://github.com/curl/curl/issues/9162#issuecomment-1188622845
    I know. And such sophisticated markup creates general interoperability issue.
    See [ https://github.com/curl/curl/issues/9153#issuecomment-1185051870 ]. ]

----

[ vszakats @ CE 2022-07-19 05:51:26 UTC:
https://github.com/curl/curl/issues/9162#issuecomment-1188627816
    Speaking of GitHub Issues, I think it's the opposite. ]

----

[ MasterInQuestion @ CE 2022-07-19 06:07:34 UTC:
https://github.com/curl/curl/issues/9162#issuecomment-1188636804
    For GitHub yet has broken rendering on some very fundamental thing.
    .
    What's the purpose of all these sophisticated markups if things may be very well clearly expressed in Plain Text? ]

----

[ vszakats @ CE 2022-07-19 07:39:06 UTC:
https://github.com/curl/curl/issues/9162#issuecomment-1188707772
    The purpose of it is to make posts easier to read and harder to misunderstand. For example code markup will retain spaces and other things.
    It also indicates that it is code/command/input/output, or a `keyword`. Yet it remains readable as plain text as well. ]

----

[ MasterInQuestion @ CE 2022-07-19 07:58:22 UTC:
https://github.com/curl/curl/issues/9162#issuecomment-1188726185
    The crucial problem is that such significant information become lost when copying (from the rendered display) back into Plain Text.
    Which made general parsing / exchanging bothersome. ]

----

[ vszakats @ CE 2022-07-19 08:12:06 UTC:
https://github.com/curl/curl/issues/9162#issuecomment-1188739624
    You can always access the original text for your own submissions.
    For others, you can do the same with the "Quote reply" option, if that's necessary. ]

----

[ MasterInQuestion @ CE 2022-07-19 21:57:32 UTC:
https://github.com/curl/curl/issues/9162#issuecomment-1189590578
    Not always (e.g. locked topic). And the practice is bothersome (not only login required, and the apparent more).
    Even if so:

    Readable in one way, unreadable in another:
    The doomed fate of Markdown, and similar sophisticated markups:
    That demand sophisticated post-rendering to be properly displayed. ]

----

[ jzakrzewski @ CE 2022-07-22 11:01:44 UTC:
https://github.com/curl/curl/issues/9189#issuecomment-1192454350
    "Your editing to the main post screwed up the formatting seriously (and caused misinformation). I reverted your change for readability. [Note 1]"
<^>    Sorry, but I find your post completely unreadable with weird formatting:
    Quoting, notes, jumping around...
    Markdown compared to that is crystal clear. ]

----

[ MasterInQuestion @ CE 2024-05-30 07:16:44 UTC:
https://github.com/curl/curl/issues/9189#issuecomment-1192456554
    Further Markdown related Off-Topic to [ https://github.com/orgs/community/discussions/20921 ], thanks.

    ----

    Try think of any way superior maintaining the very structure:
    These elements are unavoidable for effective representation.

    (assuming rendered Markdown)
    This already put the comparison at a biased position.
    With proper post-rendering (just mere syntax highlighting): the schema should be far more accessible than Markdown.
    Without post-rendering: the schema should also maintain high level of accessibility; while Markdown... seems Markdone.

    ----

    I fear the real problem in fact has little to do with Markdown or whatsoever markup scheme. But the general ability of parsing information.
    These very elements may as well present in Markdown, in no way essentially different. ]

----

[ bagder @ CE 2022-07-22 16:35:28 UTC:
https://github.com/curl/curl/issues/9189#issuecomment-1192750136
    I'm with @jzakrzewski. All this weirdly formatted mumbo jumbo makes it very hard to extract the actual content that might be in there somewhere.
    So, again why would we want this new option? (please reply without all the funny formatting) ]
]]