----- Original Message ----- To: "Sagi Bashari" <[EMAIL PROTECTED]>
> On Sat, 16 Mar 2002, Sagi Bashari wrote: > > > > > ----- Original Message ----- > > From: "Tzafrir Cohen" <[EMAIL PROTECTED]> > > > > > On Sat, 16 Mar 2002, guy keren wrote: > > > > > > > > > > > > > > oh, please, don't. visual hebrew is here to stay! :) > > > > > > In that case, since there is an installation of a new version of PHP RSN, > > > don't forget to compile it with fribidi support. IIRC this gives better > > > logical->visual than the built-in implementation of hebrev. > > > > > > fribidi has to be installed, of course. Source RPMs are available from > > > various sources (I'll have to check what RPM is installed on my system). > > > > > > > I think that it's better to display it in logical hebrew , and have visual > > hebrew support if the client does not support logical (atleast keep the data > > in the database in logical hebrew and not visual). > > > > I belive that browsers that do support logical hebrew, will display it > > better than visual. And once we add Visual hebrew support already, it won't > > be too hard to leave logical hebrew option. > > > > How simple/complicated is it to add support for logical->visual > conversion? > > There are two problems, the way I see it: > > 1. Layout problems: you have to know in advance the width of every part of > the page that will contain Hebrew characters (as opposed to the "spirit" > of HTML) > > 2. Care must be taken to do logical->visual conversion exactly once for > each piece of text > > Also note that not any browser that claims to be (or in fact is) > netscape>=6.1, mozilla>=0.9.1, MSIE>=5.0 supports logical Hebrew. > > In short: this complicates the site. Site builders have always hated > visual Hebrew for that. > > There is another option worth mentioning: multiple languages user > interface. This works fine with English/Logical-Hebrew. (But it adds a > layer of complication to the code, and it takes some tme to get right) > Well, I thought it's already been said that we're only going to have hebrew content support, and not hebrew user interface. So, it should actually be pretty simple. We need to transfer all the content from the database through a php function, say hebrev() to convert it to visual hebrew, right? so instead, lets write simple function that decides if to reverse it, or not. But, then we'll have a problem - hebrev() does not work good in HTML, which means that all the data in the database should be plaintext - no html in articles/comments. Is that a problem? maybe we can still get over it by allowing some simple tags (ie. <b/u/i>, etc) and building some simple engine that'll reverse the text inside those tags. Again, If no HTML is needed, then it's really simple. Sagi ---------------------------------------------------------------------------- To unsubscribe, send a message to [EMAIL PROTECTED] Archives available at http://www.mail-archive.com/[email protected]/
