L2/03-045

Title: Feedback on Public Review Issues
Source: W3C
Date: Feb 14, 2003

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Date/Time:    Fri Feb 14 15:55:12 EST 2003
Contact:      w3c-i18n-ig@w3.org
Report Type:  Other Question, Problem, or Feedback

Dear Unicode Consortium,

This is feedback from the Core Task Force of the I18N Working
Group of the W3C on your issue 1, Language tag depreciation,
at http://www.unicode.org/review/.

The W3C does not use and does not plan to use language tags,
and strongly recommends against their use
(see http://www.w3.org/TR/unicode-xml/#Language).
We are therefore not affected by a depreciation, and the
depreciation may send the right signals to potential users.
However, we are somewhat concerned that depreciating them
may run some political risk, namely that it may increase
the risk of use of even more obscure mechanisms.

For the Core TF of the I18N WG of the W3C,

Martin Duerst.

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Date/Time:    Fri Feb 14 15:58:05 EST 2003
Contact:      w3c-i18n-ig@w3.org
Report Type:  Other Question, Problem, or Feedback

Dear Unicode Consortium,

This is feedback from the Core Task Force of the I18N Working
Group of the W3C on your issue 4,  sharp S collation weight,
at http://www.unicode.org/review/.

The W3C currently has no specification that would be affected
by this change. We therefore see no obstactle to going forward
with this change.

For the Core TF of the I18N WG of the W3C,

Martin Duerst.

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Date/Time:    Fri Feb 14 16:05:58 EST 2003
Contact:      w3c-i18n-ig@w3.org
Report Type:  Error Report

Dear Unicode Consortium,

This is feedback from the Core Task Force of the I18N Working
Group of the W3C on your issue 5  Object Replacement Char,
at http://www.unicode.org/review/.

The W3C does not use and does not plan to use the object
replacement character, and recommends against its use
(see http://www.w3.org/TR/unicode-xml/#Object). We also
say "Browsers may ignore this character." If we interpret
browsers as doing 'default rendering', then this would
correspond to classifying this character as "default ignorable".
But this is not a strong preference.

For the Core TF of the I18N WG of the W3C,

Martin Duerst.