Can this site not wreck inline XML indentation and JSON quotes?

Site Feedback
1

This website software tries too hard to prettify text, requiring us to replace slanty quotes (’ ') with straight quote characters in inline JSON.
It also does not respect indentation, necessary for clear visual structure identification.
Neither the BlockQuote (Ctrl+Shift+9) option nor the Preformatted Text (Ctrl+Shift+C) option helps.

Is there a html workaround, or better yet a board adjustment for this?

2

I've turned off the typographer feature for now, although generally you should be putting JSON/XML into fenced code blocks using three backticks (```) before and after the content.

3

Let's test some XML ...
Source_XML.txt (1.8 KB)
Inline, nothing marked:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> false 1509572780 3 3 false 1509573381 3 3 false 1511304721 1 1 false 1514209758 1 1 false 1517059496 2 1

Parts are missing from the metadata.

With triple back quote:

<alarm-response-list total-alarms="19" throttle="5">
    <alarm-responses>
        <alarm id="59fa40ac-00d5-1000-0113-008010a864d7">
            <attribute id="0x11f4d">false</attribute>
            <attribute id="0x11f4e">1509572780</attribute>
            <attribute id="0x11f56">3</attribute>
            <attribute id="0x11fc5">3</attribute>
        </alarm>
        <alarm id="59fa4305-0374-1000-0113-008010a864d7">
            <attribute id="0x11f4d">false</attribute>
            <attribute id="0x11f4e">1509573381</attribute>
            <attribute id="0x11f56">3</attribute>
            <attribute id="0x11fc5">3</attribute>
        </alarm>
        <alarm id="5a14ae11-1081-1004-0113-008010a864d7">
            <attribute id="0x11f4d">false</attribute>
            <attribute id="0x11f4e">1511304721</attribute>
            <attribute id="0x11f56">1</attribute>
            <attribute id="0x11fc5">1</attribute>
        </alarm>
        <alarm id="5a4101de-008f-1000-010a-008010a864d7">
            <attribute id="0x11f4d">false</attribute>
            <attribute id="0x11f4e">1514209758</attribute>
            <attribute id="0x11f56">1</attribute>
            <attribute id="0x11fc5">1</attribute>
        </alarm>
        <alarm id="5a6c7da8-b05a-1006-010a-008010a864d7">
            <attribute id="0x11f4d">false</attribute>
            <attribute id="0x11f4e">1517059496</attribute>
            <attribute id="0x11f56">2</attribute>
            <attribute id="0x11fc5">1</attribute>
        </alarm>
    </alarm-responses>
    <link type="application/xml" href="http://192.168.100.215:8080/spectrum/restful/alarms?id=2ef6a596-ccd2-463b-85b8-d2a6f3e5bb1a&amp;start=5&amp;throttlesize=5" rel="next"/>
</alarm-response-list>

Sweet!

With BlockQuote:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> false 1509572780 3 3 false 1509573381 3 3 false 1511304721 1 1 false 1514209758 1 1 false 1517059496 2 1

No good, metadata lost.

Preformatted text:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
false 1509572780 3 3 false 1509573381 3 3 false 1511304721 1 1 false 1514209758 1 1 false 1517059496 2 1

Same problem, metadata lost.

Let's try the html code mark, if I recall properly:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> false 1509572780 3 3 false 1509573381 3 3 false 1511304721 1 1 false 1514209758 1 1 false 1517059496 2 1

No luck either.

Bottom line for XML: Use triple back quote before and after.

Now some JSON tests ...

OpenUV.txt (895 Bytes)

As is, inline:

{"result":
{"uv":0,
"uv_time":"2019-09-20T00:51:51.837Z",
"uv_max":6.3027,"uv_max_time":"2019-09-20T07:10:40.662Z",
"ozone":277,"ozone_time":"2019-09-20T00:06:36.984Z","safe_exposure_time":{"st1":null,"st2":null,"st3":null,"st4":null,"st5":null,"st6":null},"sun_info":{"sun_times":{"solarNoon":"2019-09-20T07:10:40.662Z","nadir":"2019-09-19T19:10:40.662Z","sunrise":"2019-09-20T01:01:24.509Z","sunset":"2019-09-20T13:19:56.814Z","sunriseEnd":"2019-09-20T01:04:17.763Z","sunsetStart":"2019-09-20T13:17:03.560Z","dawn":"2019-09-20T00:33:19.651Z","dusk":"2019-09-20T13:48:01.672Z","nauticalDawn":"2019-09-20T00:00:19.158Z","nauticalDusk":"2019-09-20T14:21:02.165Z","nightEnd":"2019-09-19T23:26:30.126Z","night":"2019-09-20T14:54:51.197Z","goldenHourEnd":"2019-09-20T01:38:25.055Z","goldenHour":"2019-09-20T12:42:56.268Z"},"sun_position":{"azimuth":-1.6422939223001876,"altitude":-0.0418291891456217}}}}

The JSON was not indented originally. The " marks came through okay.
Manual indentation by spaces was lost, though New Lines came through.

Bottom Line:

The change to the board settings kept the quotes straight, but wrecked XML metadata.
The triple back quote works great.

I would see if there is a board setup option to add the triple backquote markup option to the markup bar, and revert the formatting change.

As a Power User, I would add the triple quotes around any supplied JSON in the original post before trying to grab it off the post, to insure straight quotes. Either that, or grab the JSON from edit mode, where it is "unimproved".

4

A post was split to a new topic: OpenUV api problem

5