Re: [DOC-HE] Re: [PHP-DOC] cvs: phpdoc / Makefile.in

one of us didn't understand but i am not sure who :)

i said that I converted our standard character set (iso-8859-8-i a.k.a. 
windows-1255) TO Unicode. I understood that this is what you guys wanted. 
No? And iconv did make this conversion.

Why do you say that iconv can't encode the current files? 

# iconv -f windows-1255 -t utf-8 mysql-connect.xml -o ~/web/mysql-connect-unicode.xml
#

http://shimi.staff.fresh.co.il/mysql-connect-unicode.xml

On Fri, 16 May 2003, Gabor Hojtsy wrote:

> > No, I translated a template file, of the RT3 program... yet, this doesn't 
> > matter. It converted all the hebrew there to Unicode, and didn't touch the 
> > English at all. (as should have been done! and the UI of RT3 works for me 
> > perfectly in Hebrew)
> 
> So your conversion tip does not matter that much in our case, as you 
> converted UTF8 to some windows encoding which are both supported by 
> iconv. The question is how we will be able to get some iconv / xsltproc 
> supported encoding out of the current files, which are using an encoding 
> which is not supported.
> 
> > About windows I don't know, but... does it matter? I mean- the server that 
> > actually builds the manuals is running Linux, I guess :)
> 
> No it does not matter what DLL is needed on windows, but the question 
> was if xsltproc uses iconv or not. And I tried to find some connection 
> which I was able to find from my windows experience and not from my 
> linux experience. I thought I have written this down in an understanable 
> way.
> 
> Please concentrate on the topic (it seems to me that in both questions 
> you just went offtopic, or I don't understand something).
> 
> 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."