Re: cvs: phpdoc / Makefile.in

From: Date: Fri, 16 May 2003 14:00:23 +0000
Subject: Re: cvs: phpdoc / Makefile.in
References: 1  Groups: php.doc php.doc.he 
Request: Send a blank email to phpdoc+get-969353526@lists.php.net to get a copy of this message
DLL? I am talking about iconv on redhat linux (7.3) that I used... it worked fine converting to UTF-8. Again, there are two possible encodings for hebrew. They both use the exact same character set, and the difference being the letters ordering. Previously iso-8859-8 was used (and is called "Visual Hebrew"). That needed special rendering at the browsers, and eventually they came up using iso-8859-8-i(nverse) (also called "Logical Hebrew") - and this is what we at Israel use everywhere for the past 5+ years. Again, I successfully made UTF-8 files from hebrew using the following command: iconv -f windows-1255 -t utf-8 original -o target On Fri, 16 May 2003, Gabor Hojtsy wrote: > >>iconv (the unix utility) supports hebrew only by the non standard > >>representation of it (?) which is windows-1255 > >> > >>i have successfully translated the RT ticketing system (v3) to hebrew at > >>UTF-8 using iconv. > > > > The problem is more: > > > > /usr/bin/xsltproc xsl/phpweb.xsl manual.xml > > /dat/dev/php/phpdoc-all/he/bookinfo.xml:1: error: Unsupported encoding > > iso-8859-8-i > > <?xml version="1.0" encoding="iso-8859-8-i"?> > > > > Anything we can replace it with? > > Hm, AFAIK xsltproc works with iconv, so probably only the iconv > supported encodings can be used. The windows version requires the iconv > dll to be in place, but I cannot find any dependencies related to iconv > on linux. Though there is probably a dependency. The question is up for > the doc-he guys, what encoding they are able to work with? > > Goba > -- Best regards, Shimi ---- "Outlook is a massive flaming horrid blatant security violation, which also happens to be a mail reader." "Sure UNIX is user friendly; it's just picky about who its friends are."

« previous php.doc (#969353526) next »