Re: Variations of mapping from Japanese encodings to Unicode

[Mark Davis <mark@macchiato.com>]

We plan only backwards compatible changes at this point. One of the reasons
import was dropped was exactly that it could be done with entities, and the
older definition was complicated by the need to resolve conflicts. I will
bring this up at the UTC, though, so that we can record this as a policy.

mark
—————

Γνῶθι σαυτόν — Θαλῆς
[http://www.macchiato.com]
----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
To: "Mark Davis" <mark@macchiato.com>; "MURATA Makoto"
<muraw3c@attglobal.net>; <ietf-charsets@iana.org>
Cc: <mark.davis@us.ibm.com>
Sent: Wednesday, September 05, 2001 20:14
Subject: Re: Variations of mapping from Japanese encodings to Unicode


> Hello Mark,
>
> Is it possible for the UTC to provide a version of this DTD that
> is guaranteed not to change (even if it may become outdated by
> a new version)? This would help avoid problems in the future.
>
> As for <import>, I think the main functionality that Makoto needs
> (small file size, no data duplication) can be achieved with
> XML entities.
>
> Regards,  Martin.
>
> At 07:43 01/08/30 -0700, Mark Davis wrote:
> >The DTD was changed in the last version (December last year). The changes
> >are listed in http://www.unicode.org/unicode/reports/tr22/#Modifications
> >
> >The major change was the removal of <import>, which the UTC felt made the
> >validity checking too cumbersome. In the previous version, you could use
> >imports to override mappings in another version.
> >
> >Unfortunately, I see that you use <import> extensively, so that you would
> >have to regenerate the files in their complete form.
> >
> >[There are three more changes that were approved this year for 2022 and
some
> >other minor cases, but they are backwards compatible.]
>
>