- From: David Lee <David.Lee@marklogic.com>
- Date: Fri, 14 Sep 2012 13:04:22 -0700
- To: David Carlisle <davidc@nag.co.uk>
- CC: "public-microxml@w3.org" <public-microxml@w3.org>
You could put your svg data in element content instead of attribute content then post-process that to HTML (moving it to an attribute). Also how often do people hand edit large SVG data ? ----------------------------------------------------------------------------- David Lee Lead Engineer MarkLogic Corporation dlee@marklogic.com Phone: +1 812-482-5224 Cell: +1 812-630-7622 www.marklogic.com -----Original Message----- From: David Carlisle [mailto:davidc@nag.co.uk] Sent: Friday, September 14, 2012 4:01 PM To: David Lee Cc: public-microxml@w3.org Subject: Re: What to do about newlines in attribute values? On 14/09/2012 20:45, David Lee wrote: > The only use case I can think of is if you are post-processing > MicroXML to produce HTML, In which case these little issues go away > as your processing code can reformat things however HTML wants them, But the issue (to me) is if we ban newlines in attributes then it makes it inconvenient to enter the original microxml. If I want to enter a microxml svg path I'd have to make sure my editor never wrapped it The fact that that restriction isn't in svg or html and so a post processor serialising to xml or html can later wrap it doesn't really help as the constraint is on _me_ at the authoring stage, David
Received on Friday, 14 September 2012 20:04:59 UTC