KwickXML

| 19 Comments

Hi y’all,

We’ve made another change to the Thumb. This time it is how y’all mark up your comments. No longer can you use tags with square brackets to give style to you comments. Instead you need to use XML tags. Most of the tags will be the same as you are used to, except you will be using angled brackets instead of square brackets. Here is a short list of tags to get you going until I can put together complete documentation.

  • Links: <url href="…">…</url>
  • Quotes: <quote author="…">…</quote>
  • Bold: <b>…</b>
  • Italics: <i>…</i>
  • Stricken: <s>…</s>
  • Underlined: <u>…</u>

Please feel free to experiment in the comments in this thread, but please preview your comments before making them.

19 Comments

So how do we put non-markup related angled brackets into our comments? (Such as simple mathematical equations) or do we need to put them in as XML entities?

After hitting Preview, it still says “Use Kwickcode Formatting to markup your comments.” It should say KwickXML, and KwickXML (there and in the initial edit box) should link to an example page like at http://www.dererumnatura.us/archive[…]07/test.html

Also, Kwickcode allowed url=address, which was more convenient than url href=address Also, I had to quote the address above, otherwise it says “mismatched tag ‘url’” Also, when I hit Preview, it displayed it correctly but removed the url tag from the edit box, so I’m trying it unpreviewed

Entities: < (&lt;) > (&gt;)

The Preview problem mentioned above doesn’t just apply to <url>. For instance, try entering

<eqn>x = 1</eqn>

and hitting Preview and then see that the Comments: box only contains

x = 1

The message on the preview page has been updated. An example page is comming. Many of the features of KwickXML are disabled for comments. The one you link to on my personal blog doesn’t mention that.

Yes the new format is not as lenient as the previous one, but it does make for faster rebuilds and can do somethings that the KwickCode could not like nested quotes and nested lists.

Equations are not permitted in comments by design. It is to limit security risks.

<eqn><eqn> results in mismatched tag ‘kwickxml’ instead of mismatched tag ‘eqn’

Now I see what you are talking about, re missing tags. I’ll look into it.

Equations are not permitted in comments by design. It is to limit security risks.

I don’t understand how it’s a security risk, but in any case that doesn’t have anything to do with url tags disappearing. For instance, enter

<url href="x">y</url>

and then hit Preview, and the edit box only contains

y

<eqn><eqn> results in mismatched tag ‘kwickxml’ instead of mismatched tag ‘eqn’

That’s because the eqn tag isn’t the first mismatch. The kwickxml tag produces the first mismatch. You don’t see the kwickxml tag because it is inserted by the software to wrap your comment to make it suitable for an XML processor. This is what the processor sees:

<kwickxml><eqn><eqn></kwickxml>

Which is parsed as

<kwickxml>
  <eqn>
    <eqn>
      </kwickxml>

The kwickxml end tag is unmatched because it appears without a preceeding start tag on its level.

Yes the new format is not as lenient as the previous one, but it does make for faster rebuilds and can do somethings that the KwickCode could not like nested quotes and nested lists.

Um, yes, of course it has additional features – I certainly wasn’t suggesting going back to the old format. But your page says it’s a port of kwickcode with features added, so why not keep the previous good features like url= and allowing addresses to not be quoted? In any case, not quoting the address should give an apt error message, not “mismatched tag ‘url’”.

Also, it seems to take much longer to post; I (of course) don’t know whether than has anything to do with the new format.

Also, since you aren’t concerned with eqn, I guess I need to avoid it in examples. This too says mismatched tag ‘kwickxml’: <url><url>

The preview issue is fixed.

ts Wrote:

Um, yes, of course it has additional features — I certainly wasn’t suggesting going back to the old format. But your page says it’s a port of kwickcode with features added, so why not keep the previous good features like url= and allowing addresses to not be quoted? In any case, not quoting the address should give an apt error message, not “mismatched tag ‘url’”.

This can’t be done, since it violates the XML format. The meat of processing is done by XML::Parser::Lite, and I am not about to write my own pseudo-XML parser just so we can have those features.

Also, since you aren’t concerned with eqn, I guess I need to avoid it in examples. This too says mismatched tag ‘kwickxml’:

This is because the kwickxml tag is the first one to be mismatched, as I explained above.

The kwickxml end tag is unmatched because it appears without a preceeding start tag on its level.

That’s akin to a C compiler saying “mismatched ‘]’” upon encountering “[(]”. That would be very bad from a human engineering standpoint. The same is true here, but you’re probably using a canned XML parser and don’t have control over it.

P.S. I see we’re posting “simultaneously”, which is why it looks like I’ve ignored answers you’ve already given. Sorry about that. P.P.S. Thanks for fixing the preview thing. And, um, you’re welcome for my pointing it out.

Backing up to your question as to why eqn tags are security risks,

To process the equation the software writes files to the server and then runs some programs on them before deleting the files. Not knowing how secure this process was, I’ve opted to limit it to crew members. (It was the same for equation support in KwickCode.)

Reed, may I humbly I suggest that you change “… Wrote:” to “… wrote:”. Thanks.

Just a test. I’d been unable to post recently.

Use KwickXML formatting to markup your comments:

Markup or mark-up is a noun. The verb is mark up, with a space. You can (usually) tell when to write such a phrase solid, because then it is (usually) accented on the first syllable.

In addition, as anyone who was born in Brooklyn can tell you, the plural of you is youse.

On the main page, someone needs to delete the link to KwickCode and add a link to an explanation of KwickXML. The phrase “KwickXML” under “post a comment” might be converted into a link to the complete documentation once it is written.

test test test

About this Entry

This page contains a single entry by Reed A. Cartwright published on August 8, 2005 2:05 AM.

Ya gotta love August was the previous entry in this blog.

Chris Mooney: The Republican War on Science is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Categories

Archives

Author Archives

Powered by Movable Type 4.381

Site Meter