Desktop Specification 0.9.4 *final* draft ;)

[Owen Taylor]

On Mon, 2003-07-14 at 15:38, Richard Moore wrote:
> On Monday 14 July 2003 01:29, Havoc Pennington wrote:
> > On Mon, Jul 14, 2003 at 12:00:00AM +0000, Richard Moore wrote:
> > > localestring	Are these always going to be UTF-8? Would it be worth having
> > > a hook to allow support for other encodings to be added in future?
> >
> > The encoding is determined by the Encoding= field, if it's
> > Legacy-Mixed then the encoding of localestring is determined by the
> > locale of the string (as given in the table in the spec), if it's
> > UTF-8 then the file is all UTF-8.
> 
> That's not what the 0.9.4 draft spec says, at the end of the 'Character set 
> encoding of the file' section it says 'The encoding for values of type 
> localestring is UTF-8.'

In the 0.9.4 revisions, almost all references to the deprecated
Legacy-Mixed were summarily removed, except for the appendix explaining
how it worked.

I think this was premature ... unless Legacy-Mixed is *actually*
removed, not just deprecated, then the text explaining how it integrates
with the rest of the spec is needed, though it might make sense to
provided reminders of the deprecated status at each mentin.

Regards,
						Owen