W3C home > Mailing lists > Public > public-forms@w3.org > April 2012

Re: submission/@encoding

From: John Boyer <boyerj@ca.ibm.com>
Date: Mon, 23 Apr 2012 13:57:54 -0700
To: Erik Bruchez <erik@bruchez.org>
Cc: ebruchez@gmail.com, Forms WG <public-forms@w3.org>
Message-ID: <OFE3D8C349.1753642D-ON882579E9.0070884A-882579E9.00732BB8@ca.ibm.com>
Actually, XML 1.0 is making a statement about parsing, not serialization, 
so technically we can't rely directly on the XML 1.0 spec.

However, submission/@encoding is one of those attributes that is meant to 
be parallel to the same attribute on the XSLT output element, which 
requires serialization support for UTF-8 and UTF-16 and all other formats 
are optional.  Of course, XSLT output was meant to mirror XML input which 
is why I said "technically" above.

John M. Boyer, Ph.D.
Distinguished Engineer, IBM Forms and Smarter Web Applications
IBM Canada Software Lab, Victoria
E-Mail: boyerj@ca.ibm.com 

Twitter: http://twitter.com/johnboyerphd
Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 

From:   Erik Bruchez <erik@bruchez.org>
To:     Forms WG <public-forms@w3.org>
Date:   23/04/2012 11:27 AM
Subject:        Re: submission/@encoding
Sent by:        ebruchez@gmail.com

On Thu, Apr 19, 2012 at 6:45 AM, Steven Pemberton
<Steven.Pemberton@cwi.nl> wrote:
> In 
> it says:
>        encoding
>        Author-optional attribute specifying an encoding for 
> The default is "UTF-8".
> Does this mean that we only require UTF-8 and the rest are MAYs? Should 
> not say more here?

XML 1.0 says the following [1]:

"All XML processors must accept the UTF-8 and UTF-16 encodings of Unicode"

So when dealing with XML, UTF-8 and UTF-16 are required. When dealing
with other text content, I don't know.

Either way, I am not sure if we need to say more.


[1] http://www.w3.org/TR/REC-xml/#charsets
Received on Monday, 23 April 2012 20:58:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:06 UTC