Lists Home |
Date Index |
this i18n novice was perplexed upon first reading of wd-xml11/charmod and
remains perplexed upon rereading cr-xml11/charmod.
it would be clear how to proceed if xml-11 does not mention charmod.
it would be clear how to proceed if xml-11 incorporates charmod and requires
processors to normalize - thereby entailing normalization-checking.
to specify that the processor must, at option, check normalization, but must
not transform to normal form, while the referenced specification requires that
all "producers of strings" ensure (not just check) that they are normalized,
led this implementer to put the proposals back, to wait for later versions.
Rick Jelliffe wrote:
> From: "John Cowan" <email@example.com>
> > It seems that nobody has implemented the optional normalization checking
> > feature of XML 1.1 in an XML 1.1 browser. If nobody does, the feature
> > may go bye-bye when XML 1.1 goes to Rec.
> > Those who care should talk to firstname.lastname@example.org , saying
> > what they are going to do.
> Here was my comment to the comments list:
> Topologi has long implemented normalization on data import in our editor. This is
> an appropriate approach for an editor. So we don't need normalization-checking.
> Personally, I believe that normalization-checking should be an optionally SAX feature
> of XML processors: they may or may not provide it, and it may be normalization-checking
> of the raw input stream or after parsing. (That i18n experts say it should it is required and
> implementation people freak out at doing it is probably the reason why checking *should* be
> required :-) )