In my previous email, I included a note that said:
Note: Some elements marked as not being localizable via xml:lang, such
as screenshot and icon elements, are localizable via folder-based
content localization.
I've thought about it some more, and concluded that screenshot and
icon are actually
To compliment the new i18n model, I've added the following
restrictions on XML base:
[[
xml:base attribute
The xml:base attribute may be used in a configuration document to
specify a base URI other than the base URI of the document. For the
purpose of this specification, the value of xml:base
On 20 Mar 2009, at 10:46, Marcos Caceres wrote:
To compliment the new i18n model, I've added the following
restrictions on XML base:
[[
xml:base attribute
The xml:base attribute may be used in a configuration document to
specify a base URI other than the base URI of the document. For the
I believe that when creating content, it is easier/clearer to have multiple
files. There is less confusion and therfore less errors.
Benoit Suzanne
Widget Factory Project Manager - Orange Labs - FT/RD/SIRP/SOL/SLAM
t. +33 (0)145 298 198 - m. +33 (0)680 287 553
2009/3/19 Anne van Kesteren ann...@opera.com:
On Thu, 19 Mar 2009 20:37:50 +0100, Giovanni Campagna
scampa.giova...@gmail.com wrote:
Actually both of them are invalid per RFC2616 and thus should raise
SYNTAX_ERR.
I do not want to enforce validity in the XMLHttpRequest API. That seems
On Fri, 20 Mar 2009 18:59:52 +0100, Giovanni Campagna
scampa.giova...@gmail.com wrote:
You may just enforce validity of known or possibly unsafe headers
(Content-Type being the most important)
I don't think that is the right place.
Or actually, they don't per current spec, but I think they
