On Tue, 22 Jan 2002, Ira Abramov wrote: > On Tue, 22 Jan 2002, Tzafrir Cohen wrote: > > > > > I have heard too much bad criticsm about it > > > a. please give me pointers, > > I meant pointers about it being bad or insecure :) >
Download the code and read the installation instructions (If they haven't changed them yet). Also search bug-traq. Note the time it took the to react to various bugs. > but thanks for all the input! > > > BTW: One mistake you should *not* make is using an 8bit character set. > > Most sites (including the nukof above) use an 8bit encoding, like > > ISO-8859-* or windows-125* . > > > > This means that no content could be added in any language that is not > > hebrew or english (not even french, as some letters are missing. Surely > > not russian or arabic). > > > > What you should do is write the whole translation in UTF-8. > > umm, isn't UTF-8 8 bit with occasional 16? :) Sort of. Characters can take more than two bytes (depends on which characters it is. ASCII chars takes 1 byte. Hebrew chars take two bytes) > > I thought UTF-8 is problematic with some of the browsers... Explorer shows it fine. So is mozilla. A couple of days ago someone reported this list some problems with konqueror. But I know that kfm (of KDE1) at least knew how to display UTF-8. The same applies to lynx. > > are there any Hebrew sites currently using UTF-8 Hebrew so I can test > them with several browsers and study them? > > > The obvious problem is that currently UTF-8 is not ver well supported by > > text editors. > > also, what translates entered Hebrew in an HTML form into UTF-8 for > presentation? I'm sorry, I never did any web programming, all this > encoding voodoo is chinese to me. are those translations built into PHP > and Zope? No need to. For them this is simply a text string. They don't really care about its encoding (I believe). Hmm... Unless you need to do some sorting. I haven't given enough thoughts to that. > > > 1. Use vim 6.0, or any other editor that does support UTF-8 > > see, I didn't even know :) > time to check out Hebrew for VIM. is it still a special compile time > option, or is it in by default? if anyone knows, please add this info to > the IGLU FAQ too... Not related to the "hebrew" support. vim 6.0 added a number of relevant features: 1. a general-purpose keyboard layout facility (although we already had a hebrew and a farsy layouts) 2. Support for editing UTF-8 text files. > > > 2. Edit the text in ISO-8859-8(-i), and convert it to the real translation > > in a script/makefile using iconv. > > > > I used method (2). > > sounds good. but that means HTML tags are still parsable and all, > right? HTML tags are ASCII. They are encoded the same in both UTF-8 and ISO-8859 > > > > or does anyone know how I can make Squisdot/Zope accept Hebrew without > > > mangling letters as symbols on the way into the DB? I see it was done on > > > IGLU once or twice. > > > > This shouldn't be a problem. If the database is 8bit-clean, then > > ISO-8859-8 and UTF-8 text should both fit in nicely, as they are basically > > char strings. > > well, try to post anything to a plain-vanilla squishdot and you lose > lots of the text. that's via the standard interface. if you post via the > management interface it does it OK. Did the IGLU site need extra modifications? -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
