- From: <bugzilla@jessica.w3.org>
- Date: Wed, 06 Oct 2010 06:55:45 +0000
- To: public-i18n-bidi@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10813
fantasai <fantasai.bugs@inkedblade.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |fantasai.bugs@inkedblade.ne
| |t
Resolution|WONTFIX |
--- Comment #4 from fantasai <fantasai.bugs@inkedblade.net> 2010-10-06 06:55:45 UTC ---
> If HTML does specify anything about how the text in a dialog is rendered, it
> would probably be best to defer to CSS.
Deferring this to CSS is a red herring; this has nothing to do with CSS.
> The strings passed to functions such as alert() are entirely Unicode
> strings without markup. As such, the semantics of such strings are entirely
> defined by Unicode. It would be inappropriate for HTML to add additional
> requirements that might contradict what Unicode says (now or in the future).
Perhaps making this more explicit would help. I'm not seeing where the argument
to alert() is defined as a Unicode string so I can't offer any specific text,
but mentioning in the Simple Dialogs section that the given message must be
displayed according to the normative requirements of Unicode, and citing as
examples the mandatory line breaking rules and bidi behavior, would help here.
This would make it easier for the i18n Working Group to justify the submission
of tests for correct behavior. It would also clarify that white space is not
supposed to be collapsed as it is when displaying HTML.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You reported the bug.
Received on Wednesday, 6 October 2010 06:55:49 UTC