- From: <bugzilla@jessica.w3.org>
- Date: Sat, 09 Oct 2010 20:55:55 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10808
Aharon Lanin <aharon.lists.lanin@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aharon.lists.lanin@gmail.co
| |m
--- Comment #4 from Aharon Lanin <aharon.lists.lanin@gmail.com> 2010-10-09 20:55:53 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > Could you give some examples of real world pages that are suffering due to the
> > lack of this feature in current browsers?
>
> There are a lot of such samples. One example is the Persian/Arabic/Hebrew
> version of addons.mozilla.org <https://addons.mozilla.org/fa/>. In this web
> site, we display localized text (which is RTL) along with the non-localized
> text coming from add-on authors, such as an add-on's name and description.
>
> Another more extreme example is non-RTL languages on the same website, when
> displaying the information about an add-on which only has its information in an
> RTL language.
>
> This problem may be the single most annoying problem that multi-langugage
> websites have to struggle with today.
I agree with that assessment. I have done RTL/bidi support for several products
and in each one, dealing with potentially-opposite-direction strings was the
biggest single time drain. They pop up on every page, and have to be dealt with
on an individual basis.
> Basically, any website which gets some
> of the information that it displays from direct user input is affected by this.
> Other very prominent websites include multi-language weblogs,
> non-multi-language websites which display comments from users, and web mail
> applications.
It's not just direct user input. It's most strings coming from various
databases: product names and descriptions, person names, business names,
addresses, etc. etc.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 9 October 2010 20:55:57 UTC