W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2005

FW: Internationalization Core comments on XHTML2 (PR#7677)

From: Richard Ishida <ishida@w3.org>
Date: Wed, 16 Mar 2005 12:44:08 -0000
To: <public-i18n-core@w3.org>
Message-Id: <20050316124408.B1DDF4EF4E@homer.w3.org>

Steven has told me to send this to the public list.

From: Steven Pemberton [mailto:steven.pemberton@cwi.nl]
Sent: 04 March 2005 22:38
To: ishida@w3.org; w3c-html-wg@w3.org
Cc: xhtml2-issues@mn.aptest.com
Subject: Re: Internationalization Core comments on XHTML2 (PR#7677)


Many thanks for your comments, which we discussed at the just-finished
face-to-face. You can find the discussions at:


However, here is a summary.

5: Accept. This will cause the value of the encoding attribute to be used in
the accept-charset field of the HTTP headers, in order to give priority to
that encoding when requesting the document.

7: Accept. Furthermore, we do already point to the XML spec as the normative

7a: We believe that section 14.1 is the correct section.

8: It means decimal digits [0-9]. We will correct. Thanks. We are describing
lexical structure, so we believe that the current definition is correct

8a. We intend to point to a new version of Modularization. The current
version has modules and datatypes we no longer wish to use, so we will not
be referencing it.

9. URI is the name of the datatype. Its definition is an IRI. We shall point
to the newest IRI spec.

10. The attribute set you should be looking at is the one called Common.  
That is the one that is on all XHTML elements, not Core. Core are just the
attributes that don't belong anywhere else.

14. Accept. We will require xml:lang on the html element.

14a. Therefore, accept.

21. We propose the following solution. Retain the 'title' attribute for
historical and mindshare reasons, but encourage the use of metadata of the
following form for cases where markup is needed of the content:

	<p id="expl">
		<meta about"#expl" property="title">Marked up text
The title attribute ten just becomes a shorthand.
The meta element is not required to be a child of the <p>; it may be
anywhere in the document.

22. We have deleted the sentence in question.

24. Reject*

25. Martin Duerst was present for this discussion, and we agreed that the
default would not be to use stylesheets, but to normally require the quotes
in the text, but that the author could use stylesheets for those cases where
it is better for the quotes not to be in the document.

We will improve the example.

27: Accept.

33: Accept.

34: duplicate of 21

35: We will check the text for ambiguitites.

35a: Accept.

35b: This should go in a user's guide (which we anticipate producing).

35c: Since the behaviour in *correct* situations (i.e. when the document
really is in that language) will be identical, and only in error situations
will be different (and in XHTML2 clearer than in XHTML1), we believe that
retaining the name is acceptable.

37: Accept.

38: Part 1. If this is necessary for XHTML, then it is necessary for all
XML-based languages. We would then prefer to see an XML-wide solution, and
not an XHTML-specific one. We will consider possible solutions, but would be
grateful to see a firmer proposal from you.

Part 2. If you need to do this, then please use the <meta> version above.

38a. Accept. We will tweak.

39. Accept.

39a. Accept.

40. Accept.

41. Accept.

42. Accept.

42a. You can use <meta about="#yourelement" property="dc:creator">Your

42b. We will attempt to define a datatype that requires the timezone.

42c. No. Please see 8a above.

43: Accept.

44. See 21 above.

45. Accept.

46. Accept. The HTTP protocol solves the problem you refer to.

47. Sentence removed.

48. Accept.

49. Fixed.

50. Accept.

51. Thanks for your input.

Please let us know if any of these responses are unacceptable.

Many thanks,

Steven Pemberton
For the HTML WG

*Just kidding.
Received on Wednesday, 16 March 2005 12:44:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:01:07 UTC