W3C home > Mailing lists > Public > www-forms@w3.org > December 2002

Newlines and tabs

From: Alex Rosen <arosen@novell.com>
Date: Fri, 06 Dec 2002 11:54:39 -0700
Message-Id: <sdf09038.061@prv-mail20.provo.novell.com>
To: <www-forms@w3.org>

There are a few areas where the spec is silent about how it handles certain characters.

(1) Must the XForms processor support a <label> value that contains newlines or tabs?

(2) What should the processor do if it encounters an <input> value that contains newlines or tabs?

(3) Must the processor preserve newline and tab characters, even in the face of XML end-of-line normalization and attribute-value normalization?  Without significant gyrations, CR characters in XML text content, as well as CR, LF and TAB characters in attribute values, get lost when you round-trip an XML document using one of the standard parsers. I'm worried that the fields in the initial instance data will be different when they come back to the server, even if they're not modified on the client at all. Should we require the XForms processors to not lose this information, or should we warn XForms authors that this information might get lost?

On another topic, I've seen numerous XForms containg <label> values that end in colons. I assume that this is not the intent of the spec - adornments such as colons should be the (optional) job of the XForms processor, not the XForms document, right? Maybe the spec should mention this?

Received on Friday, 6 December 2002 13:56:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:07 UTC