public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Damien MATTEI <Damien.Mattei@unice.fr>,
	Kawa mailing list <kawa@sourceware.org>
Subject: Re: xml literals
Date: Mon, 22 May 2017 15:44:00 -0000	[thread overview]
Message-ID: <9c5623e9-985a-75ea-d7bf-5c81667bc884@bothner.com> (raw)
In-Reply-To: <201705221126.45847.Damien.Mattei@unice.fr>

On 05/22/2017 02:26 AM, Damien MATTEI wrote:
> hello,
> 
> i just want to genrate something like this:
> 
> <TD align=center>
> 
> but seems not available in kawa, see the errors:
> ./kawa --output-format html
> #|kawa:2|# #<td align=center>toto</td>
> /dev/stdin:2:13: missing attribute value
> /dev/stdin:2:14: missing space before attribute
> /dev/stdin:2:19: missing '=' after attribute
> /dev/stdin:2:20: missing attribute value
> /dev/stdin:2:21: missing space before attribute
> /dev/stdin:2:24: missing '=' after attribute
> /dev/stdin:2:25: missing attribute value
> /dev/stdin:2:26: missing space before attribute
> /dev/stdin:2:28: missing '=' after attribute
> /dev/stdin:3:1: missing attribute value
> /dev/stdin:3:1: missing '>' after start element

The error messages could do with improvement. but the fix is simple:
Attributes values have to be quoted in XML and XML literals,
though not always in HTML:

#<td align="center">toto</td>

> any idea?
> for creating  this with literals:
<TABLE DIR=LTR BORDER width="315" id="table_observateurs">

With XML literals:
#<TABLE DIR="LTR" BORDER width="315" id="table_observateurs"></TABLE>

However, note that case is significant in XML (though not HTML), so I recommend lower-case:

#<table dir="LTR" border width="315" id="table_observateurs"></table>

Using function call syntax:

(html:table dir: "LTR" width: 315 id: "table_observateurs")

Number attribute values don't have to be quoted - it should work either way.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  parent reply	other threads:[~2017-05-22 15:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 14:11 Damien MATTEI
2017-05-15 16:06 ` Per Bothner
2017-05-15 16:50   ` Damien MATTEI
2017-05-15 16:57     ` Damien MATTEI
2017-05-15 18:51       ` Per Bothner
2017-05-22  9:26         ` Damien MATTEI
2017-05-22 10:14           ` Sudarshan S Chawathe
2017-05-22 13:44             ` Damien MATTEI
2017-05-22 13:55               ` Damien MATTEI
2017-05-22 15:44           ` Per Bothner [this message]
     [not found]             ` <CADEOadc_87ON2=Tsjd+Ca4d90GoeKABpR3vsrHiP=5SMTKPNZQ@mail.gmail.com>
2017-05-23 13:11               ` Fwd: " Damien Mattei
2017-05-23 19:36           ` Per Bothner
2017-06-06  9:26         ` Damien MATTEI
2017-06-07 14:17           ` Damien MATTEI
2017-06-07 14:36             ` Damien MATTEI
2017-06-07 16:24             ` Per Bothner
2017-06-07 18:16               ` Per Bothner
2017-06-09 15:13                 ` Damien MATTEI
2017-06-09 18:17                   ` Per Bothner
2017-06-10 17:22                     ` Per Bothner
2017-06-13  9:15                     ` Damien MATTEI
2017-06-13  9:37                       ` Damien MATTEI
2017-06-13 17:21                       ` Per Bothner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9c5623e9-985a-75ea-d7bf-5c81667bc884@bothner.com \
    --to=per@bothner.com \
    --cc=Damien.Mattei@unice.fr \
    --cc=kawa@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).