Re: Other possible areas to cover under ITS

Hello Francois,

Some very interesting ideas. A few comments below.

At 23:37 05/02/23, Richard, Francois wrote:
 >
 >Hello,
 >
 >Here are some areas that are not exactly covered in
 >http://people.w3.org/rishida/localizable-dtds/ or could be added to some
 >sections. I am not sure if all of these fall in the scope of ITS, but here
 >is the list I came up with:
 >
 >- Preview information such as XSLT, specific XML editor.
 >It useful when it is necessary to preview the XML content in an effort of
 >display context info to help in the l10n of the content.

I'm not sure I understand this. There is the stylesheet PI for
XSLT (http://www.w3.org/1999/06/REC-xml-stylesheet-19990629/).
Would that do the job, or do you mean something else?

 >- Font information to indicate either that the element carries a font
 >information (to be l10ed) or to indicate which specific font to use to
 >render l10ed content.

Why should font information be in the document? Are the stylesheet
languages we have (CSS, XSL-FO) not good enough?

 >- Substitution rules: It help in define automatic substitution. For
 >instance for unit of measure, URL l10n (http://.../en/US/...  ->
 >http://.../fr/CA/...). The list is long and it would be nice to be able to
 >embedded the rules themselves. It could be part of 2.19

Should the rules be embedded in the actual documents?
I think it might be better to have a pointer to such rules,
external to the document, because such rules are likely
the same for a lot of documents. Also, quite some part of
such rules could be expressed in XSLT (in particular XSLT 2.0).

 >- Element syntax: Some elements need to follow certain syntax. I am
 >thinking about a coma-delimited list for instance.

This is much more general than just localization. XML Schema
has regular expressions (patterns) for this. I don't think
we should do anything more in this area, because there is
quite some contention; some people consider using commas,...
as bad XML design.

 >- Targeted country: With the limitation of locale, it is useful to be able
 >to specify a country for which the content is targeted. This might be in
 >2.12 already.

Is that before the localization, or after? Before, there
are potentially very many targets. Afterwards, it may indeed
make sense to have some kind of indication e.g. to say
"measures in this document are in locale X". If we want
to do something in this direction, it is crucial to coordinate
with the I18N Core WG, because they have some work items
in this direction (locale identification,..., in particular
for Web Services).

 >- Segmentation rules. Some element could follow a specific segmentation
 >that needs to be specified.

Again, the question is whether the actual rules should be in
the document, or just a pointer.

Regards,    Martin.

Received on Friday, 25 February 2005 07:58:37 UTC