|
|
Posted by N Cook on 09/27/69 11:16
"N Cook" <diverse@tcp.co.uk> wrote in message
news:d6a292$sir$1@inews.gazeta.pl...
>
> "Toby Inkster" <usenet200504@tobyinkster.co.uk> wrote in message
> news:pan.2005.05.16.07.16.25.456865@tobyinkster.co.uk...
> > N Cook wrote:
> >
> > > http://www.divdev.fsnet.co.uk/dysch.htm
> >
> > As I said yesterday, this is a UTF-16 file. You ought to specify that
it's
> > UTF-16 in the HTTP headers.
> >
> > Better yet -- convert it to UTF-8 (which handles Hebrew characters just
> > fine!) and specify UTF-8 in the HTTP headers.
> >
> > --
> > Toby A Inkster BSc (Hons) ARCS
> > Contact Me ~ http://tobyinkster.co.uk/contact
> >
>
> The Hebrew text as perceived by Google covers 'letters'
> & # 1488 ... & # 1514 (no spaces)
> Is there a simple way of converting them to equivalents
> that will not upset Google. I'm thinking of a cut & paste
> into an online facility like online language translation.
> I couldn't find one using keywords {convert "utf-16 to utf-8" online }
>
>
>
>
>
>
For the archives, for anyone else not so computer-wise.
It looks as though all that is required is when it comes to saving file to
disk , in my case from Notepad, to
select coding option in "Save As" as UTF-8 rather than Unicode which I had
done before.
Will try ftp, UTF-8 version revised file this week
Navigation:
[Reply to this message]
|