Re: submission/@encoding

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.

Cheers,
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: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw





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 
http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_submission_Element_2
> it says:
>
>        encoding
>        Author-optional attribute specifying an encoding for 
serialization.
> The default is "UTF-8".
>
> Does this mean that we only require UTF-8 and the rest are MAYs? Should 
we
> 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.

-Erik

[1] http://www.w3.org/TR/REC-xml/#charsets