Carl,

Michael has an excellent point here. Once your information is in
UTF-8, there is no more need to carry along character set information.
For legacy support, your application can read 1:90 before updating
the IIM block and use the appropriate character set (instead of the
system set); this preserves the legacy data.

Hans Fremuth
Metability Software

> On 18 Jul 2008 at 15:16, Carl Rambert wrote:
> > E) 1:90 Coded Character Set -- IIM has a rich set of choices for
> > this property. Unfortunately, the (typical) absence of this metadata
> > property means "default system character set" which varies on
> > different platforms. XMP is only implemented in UTF-8. The platform
> > interoperability benefit that XMP offers is an important motivation
> > for defining this schema. It warrants mention in the introduction.
>
> Hm, I don't get the idea of this comment: 1:90 is not included into
the XMP schema as it
> completely pointless: the character encoding of an XMP packet has to
follow the XMP rules
> which are - as you say - "use UTF-8".
> >