Re: [widgets] i18n proposals document

Hi,

 

I need confirmation that I understand the impact of F1 from the "Finding
missing localized content", specifically how the dynamic setting of the
xml:base on the element influences subsequent localized content
resolving, so please review my understanding and correct me if I have
got it wrong. 

 

Is the expectation that the dynamically set xml:base is limited to the
element itself and not recursively applied to all other resource
resolution? That is, the dynamically set xml:base does not override the
"base-folder" determined by the ua and widget locale matching. From the
example (see excerpt from proposal below), the xml:base would be
resolved to the widget root for the content element, but not impact the
resource resolving for the elements in the index.htm file which
reference the a.gif and the b.gif files. These would resolve to the
locale/en-us-xx/  locale. Would their xml:base be expected to
dynamically be set accordingly?

 

Thanks,

Andy

 

Consider the following widget. Assume the widget's locale is "en-us-xx"
and the file the user agent is searching for is "index.html".

widget.wgt
  config.xml
  index.html
  a.gif
  b.gif
  hello/d.gif
  locales/en-us-xx/a.gif
  locales/en-us/a.gif
  locales/en-gb/a.gif
  locales/en-gb/index.html
  locales/en/a.gif
  locales/en/c.gif

PROPOSAL F1: The user agent searches for the missing file in the folder
hierarchy that matches the widget's locale. If the file is not in the
hierarchy of locale folders, then the user agent searches for the file
at the root of the widget package. The container for localized content
(the folder called "locales") is not searched for missing content. If
the missing file is found somewhere in the folder hierarchy of locale
folders or at the root of the widget, and no xml:base has been
explicitly set by the author for this element, then the user agent must
set xml:base of that element to be an alternate locale folder, or to the
root of the widget package, that contains the file. This is the editor's
preferred proposal.

Using the example widget above, in the case where the src attribute of
the content element is "index.html", the user agent would first look in
the "/locales/en-us-xx", then in "/locales/en-us", and then in the
"/locales/en" folder, but would fail to find the file. So then the user
agent would search at the root of the widget, where it would find a that
matches the file name of the file it is searching for. The user agent
now dynamically sets the xml:base of the content element to the root of
the widget. 

--------------------------------->8