... if anybody ever referred to XML as “Echh Smell” ...

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Lawrence D'Oliveiro <ldo@nz.invalid> writes:

... if anybody ever referred to XML as “Echh Smell” ...

Lol. Not me.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 08:00 this Monday (GMT):

... if anybody ever referred to XML as “Echh Smell” ...

I'm sure someone has, but that feels wrong to me.
--
user <candycane> is generated from /dev/urandom

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 22 Apr 2025 21:00:03 -0000 (UTC), candycanearter07 wrote:

Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 08:00 this Monday (GMT):

... if anybody ever referred to XML as “Echh Smell” ...

I'm sure someone has, but that feels wrong to me.

The musing was prompted by some who feel JSON is the bee’s knees, and who look on XML as, shall we say, Old Skool ...

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 22/04/2025 23:39, Lawrence D'Oliveiro wrote:

On Tue, 22 Apr 2025 21:00:03 -0000 (UTC), candycanearter07 wrote:

Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 08:00 this Monday (GMT):

... if anybody ever referred to XML as “Echh Smell” ...

I'm sure someone has, but that feels wrong to me.

The musing was prompted by some who feel JSON is the bee’s knees, and who look on XML as, shall we say, Old Skool ...

There's a famous quote about XML....


XML is like violence – if it doesn’t solve your problems, you are not
using enough of it.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 23 Apr 2025 06:39:56 +0100, mm0fmf wrote:

XML is like violence – if it doesn’t solve your problems, you are not using enough of it.

I was slightly disillusioned when I found that there were certain
characters that were not allowed in XML files, even when entity-encoded.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 00:16 this Thursday (GMT):

On Wed, 23 Apr 2025 06:39:56 +0100, mm0fmf wrote:

XML is like violence – if it doesn’t solve your problems, you are not
using enough of it.

I was slightly disillusioned when I found that there were certain
characters that were not allowed in XML files, even when entity-encoded.

You could always use unicode, maybe?
--
user <candycane> is generated from /dev/urandom

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 25 Apr 2025 04:30:03 -0000 (UTC), candycanearter07 wrote:

Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 00:16 this Thursday (GMT):

I was slightly disillusioned when I found that there were certain
characters that were not allowed in XML files, even when entity-encoded.

You could always use unicode, maybe?

Not even Unicode. Just a CTRL/C character.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2025-04-22, Lawrence D'Oliveiro <ldo@nz.invalid> wrote:

On Tue, 22 Apr 2025 21:00:03 -0000 (UTC), candycanearter07 wrote:

Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 08:00 this Monday (GMT):

... if anybody ever referred to XML as ???Echh Smell??? ...

I'm sure someone has, but that feels wrong to me.

The musing was prompted by some who feel JSON is the bee???s knees, and who look on XML as, shall we say, Old Skool ...

XML old skool!!!!!?????

Bloody 'ell, does that make me pre-historic in prefering csv text files :-)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Jim Jackson <jj@franjam.org.uk> wrote:

XML old skool!!!!!?????

Bloody 'ell, does that make me pre-historic in prefering csv text
files :-)

Timeless! \o/

--
4. Hitchhiker 36: "It comes from a very ancient democracy, you see ..."

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 25 Apr 2025 17:32:33 -0000 (UTC), Jim Jackson wrote:

XML old skool!!!!!?????

I think it was down to its verbosity and syntactic clutter compared to something a bit more concise, like JSON.

Bloody 'ell, does that make me pre-historic in prefering csv text files
:-)

CSV is popular because of its simplicity (once you get past some annoying little dialectic variations). I even added SYLK export in a project once, though I suspect nobody else remembers what that is any more ... (DIF, anybody?)

There are other ancient formats that remain popular because they are so
simple to both generate and parse. E.g. with all the advances in 3D
graphics technology over the past few decades, good old OBJ remains in
common use as a basic format for transferring large amounts of geometry
between different apps.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Jim Jackson <jj@franjam.org.uk> wrote at 17:32 this Friday (GMT):

On 2025-04-22, Lawrence D'Oliveiro <ldo@nz.invalid> wrote:

On Tue, 22 Apr 2025 21:00:03 -0000 (UTC), candycanearter07 wrote:

Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 08:00 this Monday (GMT):

... if anybody ever referred to XML as ???Echh Smell??? ...

I'm sure someone has, but that feels wrong to me.

The musing was prompted by some who feel JSON is the bee???s knees, and who >> look on XML as, shall we say, Old Skool ...

XML old skool!!!!!?????

Bloody 'ell, does that make me pre-historic in prefering csv text files :-)

Being old doesn't mean it's bad :D
--
user <candycane> is generated from /dev/urandom

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Sn!pe <snipeco.2@gmail.com> wrote at 14:08 this Sunday (GMT):

candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
wrote:
[...]

XML old skool!!!!!?????

Bloody 'ell, does that make me pre-historic in prefering csv text files :-)

Being old doesn't mean it's bad :D

There's many a good tune played on an old fiddle.

Yeah, and USENET itself :>
--
user <candycane> is generated from /dev/urandom

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 24/04/2025 02:16, Lawrence D'Oliveiro wrote:

I was slightly disillusioned when I found that there were certain
characters that were not allowed in XML files, even when entity-encoded.

Not even in CDATA section? I wonder what characters those might be.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

hrtuybxi@outlook.com wrote:

On 24/04/2025 02:16, Lawrence D'Oliveiro wrote:

I was slightly disillusioned when I found that there were certain
characters that were not allowed in XML files, even when entity-encoded.

Not even in CDATA section? I wonder what characters those might be.

https://www.w3.org/TR/REC-xml/#charsets

Character Range
[2] Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] |
[#xE000-#xFFFD] | [#x10000-#x10FFFF]
/* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */

Most of the control characters are explicitly excluded, plus some
unicode code points.

And, yes, even in CDATA sections, because CDATA references the above
"Char" definition to define what characters are allowed in CDATA:

[20] CData ::= (Char* - (Char* ']]>' Char*))

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 28 May 2025 20:18:54 +0200, hrtuybxi wrote:

On 24/04/2025 02:16, Lawrence D'Oliveiro wrote:

I was slightly disillusioned when I found that there were certain
characters that were not allowed in XML files, even when
entity-encoded.

Not even in CDATA section? I wonder what characters those might be.

The one I encountered was chr(3), a.k.a. CTRL/C. Somehow one of the
operators had managed to enter that into a comments field, causing my export-to-XML function to fail.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)