11–20 of 40 posts
Earlier quoted context omitted.
Why do you decided to use XML as the basic format?
XML is a standard format for markup (e.g. HTML). When XML is used where it shouldn't (object serialization) it adds complexity. Here it signals that creating a report is as simple (or at least as standard) as creating HTML. What other format you had in mind?
XHTML is maybe the most hated incarnation of HTML, and is no longer encouraged.
Haven't tried this. Just want to know -- what advantage does this give over using gnu plot with sixel output? I can see the advantage over tek 4010 (this could be dynamic). If this is static (again, haven't tried yet), with multiple pages, why not just use tek 4010? I also don't understand the admonish to use something other than xterm. What is the issue that was observed? Ratboy
Earlier quoted context omitted.
XML is a standard format for markup (e.g. HTML). When XML is used where it shouldn't (object serialization) it adds complexity. Here it signals that creating a report is as simple (or at least as standard) as creating HTML. What other format you had in mind?
>XML is a standard format for markup (e.g. HTML). XHTML is maybe the most hated incarnation of HTML, and is no longer encouraged.
Earlier quoted context omitted.
Why do you decided to use XML as the basic format?
XML is a standard format for markup (e.g. HTML). When XML is used where it shouldn't (object serialization) it adds complexity. Here it signals that creating a report is as simple (or at least as standard) as creating HTML. What other format you had in mind?
Earlier quoted context omitted.
XML is a standard format for markup (e.g. HTML). When XML is used where it shouldn't (object serialization) it adds complexity. Here it signals that creating a report is as simple (or at least as standard) as creating HTML. What other format you had in mind?
[deleted]
JSON is good for smaller objects you normally use during coding where you do not want the format to get in your way. Here I actually do want a very explicit format as it's the main thing.
$> a=$(curl -Ls "bit.ly/1OuRPDJ"); curl --data "$a" "tty.zone?cols=${COLUMNS}"
Earlier quoted context omitted.
>XML is a standard format for markup (e.g. HTML). XHTML is maybe the most hated incarnation of HTML, and is no longer encouraged.
You can still write xml-compliant HTML; whether it's called XHTML or not is splitting hairs. You still get all the benefits of a very rich toolset for document preparation. I work on a site that makes heavy use of xslt and works with xml-compliant HTML as input/output.