W3C home > Mailing lists > Public > public-i18n-its@w3.org > January to March 2005

Re: Allowed Characters

From: Martin Duerst <duerst@w3.org>
Date: Fri, 25 Feb 2005 12:11:18 +0900
Message-Id: <6.0.0.20.2.20050225120650.07a289b0@localhost>
To: "Yves Savourel" <yves@opentag.com>, <public-i18n-its@w3.org>

XML Schema can use patterns to limit allowable characters
in attributes and in text-only elements. Unfortunately,
this mechanism isn't available for mixed content (e.g.
an element that contains text as well as (potentially)
other elements, such as a <p>).

I also know that in the context of the ISO work on schemas,
which is done in various parts, one part is supposed to be
a 'language' to specify character restrictions.

In the use cases for localization, is it envisioned that
such restrictions would be done on a per-instance base,
or would they be on a DTD/Schema base (or both, depending
on the use case)?

Regards,   Martin.


At 22:27 05/02/23, Yves Savourel wrote:
 >
 >> From Tim's comments on Requirements for localisable DTD design:
 >>
 >> 2.17 Allowed Characters
 >> How can you enforce this ? Isn't it up to the content authoring
 >> tool to do this job ? Are there hooks that already provide such
 >> functionality ? (eg. notes to translators imploring them to use
 >> only ASCII, or strings of a certain length ?)
 >
 >I'm not sure how much such an information on what characters can be used will be
 >used, but it seems a logical complement to things such as the 'maximum size'
 >information, etc.
 >
 >>From past experience I recall mostly two cases:
 >- Preventing the use of forbiden characters in the translation of paths and
 >filenames (while I'm not a fan of localizing paths, sometimes it's simply
 >required by the translation customer).
 >- Using half-width Katakana in Japanese (for translation of LCD panels with
 >limited font resources).
 >
 >-ys 
Received on Friday, 25 February 2005 03:11:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:44 GMT