- From: <bugzilla@jessica.w3.org>
- Date: Sat, 03 Oct 2015 05:43:46 +0000
- To: www-international@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28255
Martin Dürst <duerst@it.aoyama.ac.jp> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |duerst@it.aoyama.ac.jp
--- Comment #15 from Martin Dürst <duerst@it.aoyama.ac.jp> ---
I agree with Nigel and David. For HTML, we have both external and internal
mechanisms for indicating language (as well as charset, i.e. character
encoding). Nobody has ever questioned this, and its usefulness has been widely
validated in practice. I cannot see any reason that WebTTV would be different
here.
It is clear that for some usage scenarios, e.g. asset/content management
systems, external information will work well. But there are other usages where
internal information works much better (or is essentially the only thing that
works).
The spec shouldn't dictate how the data is managed, stored, and so on, but
should be amenable to various different needs. The request isn't in any way
academic; in fact one use case where it's most helpful is very small projects.
If Web technology were only supporting the use case of big users who have the
resources to set up an asset management system, then we would be doing
something wrong.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 3 October 2015 05:43:49 UTC