sight.. why not stick to one standard ;)
On 11/14/06, Iman Rahmatizadeh <[EMAIL PROTECTED]> wrote:
Yeah thats it. Numbers are LTR & text is RTL.
Yeah thats it. Numbers are LTR & text is RTL.
On 11/14/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 11/14/06, Iman Rahmatizadeh <[EMAIL PROTECTED]> wrote:
> I guess this should work ok, so this way pages written previously wont
be
> harmed, and we have support for programmatically setting
On 11/14/06, Iman Rahmatizadeh <[EMAIL PROTECTED]> wrote:
I guess this should work ok, so this way pages written previously wont be
harmed, and we have support for programmatically setting the direction.
Eelco, wouldn't you consider adding the method to Component instead of
WebPage ?
Well, the
I guess this should work ok, so this way pages written previously wont be
harmed, and we have support for programmatically setting the direction.
Eelco, wouldn't you consider adding the method to Component instead of
WebPage ?
On 11/13/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
This would b
This would be the minimal thing to make a RTL language look ok.
Japanese for instance is a LTR language (like English and German are).
Eelco
On 11/13/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
I'm not sure. Isn't it that the whole form / page layout require
changes to make it look right
I'm not sure. Isn't it that the whole form / page layout require
changes to make it look right. Same is true for japanese etc. That is
why we allow for per locale properties file.
Juergen
On 11/13/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Hi,
I converted the form input example this weeken
Hi,
I converted the form input example this weekend so that it uses one
page and a properties (or xml) file per supported locale. One problem
I have to fix is the fact that Persian (fa IR) is a 'left-to-right'
language (see http://www.i18nguy.com/markup/right-to-left.html).
Now, it kind of sucks
