
Signature
Paul Oldham, Milton, Cambridge, UK
http://the-hug.org/paul/stroke/
Howdy Paul!
Can't say for sure.
I hand wrote all of my html code by hand (no Dreamweaver or anything like
that.)
I use WS_FTP95 Pro which uses Notepad.
So... in answer to your question: No, it is not intentional.
Yours is the first feedback that I've had in over 4 years that there is any
problem reading my site!
My keyboard character code is Unicode.

Signature
Dave ????
"Noli illigitemi carborundum decendus"
http://www.howdydave.com
> > See my VNS site:
> >
[quoted text clipped - 3 lines]
> Konqueror. From the source it looks like it's Unicode as every other byte is
> null. Is that intentional?
Bob - 19 Sep 2003 02:15 GMT
"Dave ©¿©¬" wrote:
> Howdy Paul!
>
[quoted text clipped - 11 lines]
>
> My keyboard character code is Unicode.
Hi Dave
Your homepage comes up just fine, but there are problems with
http://www.howdydave.com/vns.html
no matter how it is accessed.
Bob
> Dave ©¿©¬
> "Noli illigitemi carborundum decendus"
[quoted text clipped - 13 lines]
> > Paul Oldham, Milton, Cambridge, UK
> > http://the-hug.org/paul/stroke/
Paul Oldham - 19 Sep 2003 19:06 GMT
> I hand wrote all of my html code by hand (no Dreamweaver or anything like
> that.)
Respect. It's the one true way.
> I use WS_FTP95 Pro which uses Notepad.
>
> My keyboard character code is Unicode.
I suspect that's your problem then. Try setting it to something else.

Signature
Paul Oldham, Milton, Cambridge, UK
http://the-hug.org/paul/stroke/
jedi and son - 19 Sep 2003 20:34 GMT
> > I hand wrote all of my html code by hand (no Dreamweaver or anything like
> > that.)
[quoted text clipped - 6 lines]
>
> I suspect that's your problem then. Try setting it to something else.
Heh, While I did learn to code by hand I have to confess that I do use
Dreamweaver....greatly speeds page coding when you're not handcoding
containers and relationships. The other nice thing is that it's bloating is
not nearly as bad as MS Frontplague....on that note...Ironically, Daves VNS
page came in fine for me...I am guessing that his adjustments occurred
before I viewed it from this thread?
Best Wishes!
Jedi and Son
Paul Oldham - 20 Sep 2003 09:42 GMT
> > In article <evsab.4134$CO7.2369@news02.roc.ny>,
> > dave@_nospam_howdydave.com
[quoted text clipped - 9 lines]
> containers and relationships. The other nice thing is that it's bloating
> is not nearly as bad as MS Frontplague...
Yeah. To be fair, if people are going to use an web editor that's the one
that most people seem to think is best. Certainly the professionals where I
hang out almost all use that if they don't use a text editor. I use Xemacs
myself.
> ...on that note...Ironically, Daves VNS
> page came in fine for me...I am guessing that his adjustments occurred
> before I viewed it from this thread?
Are you using IE as your browser? I could view Unicode version fine under IE
(and Konqueror). It was other browsers that couldn't cope.

Signature
Paul Oldham, Milton, Cambridge, UK
http://the-hug.org/paul/stroke/
spam@spam.com - 22 Sep 2003 17:56 GMT
I'll second the unreadable in Netscape.
IE works fine.
Dave ©¿©¬ wrote:
> Howdy Paul!
>
[quoted text clipped - 11 lines]
>
> My keyboard character code is Unicode.
jallan - 22 Sep 2003 23:31 GMT
"Dave ©¿©¬" <dave@_nospam_howdydave.com> wrote in message news:<evsab.4134$CO7.2369@news02.roc.ny>...
> Howdy Paul!
>
[quoted text clipped - 11 lines]
>
> My keyboard character code is Unicode.
More exactly for that page you are using Unicode encoding form UTF-16
with BOM at the beginning indicating little-endian order.
It looks fine in IE but when I check the VIEW Menu to see what the
encoding is I find a ghosted bullet against a ghosted entry "Unicode"
which otherwise doesn't appear on the menu. "Unicode (UTF-8)" appears
on the menu separately.
On viewing other web pages this ghost entry "Unicode" does not show at
all on the Menu although "Unicode (UTF-8)" does.
Accordingly I suspect IE has hidden support for UTF-16 which works
here even though UTF-16 encoding is not selectable. Perhaps the
support was not dependably debugged for the latest release though it
works with your page.
Netscape and Mozilla do not currently support UTF-16.
Opera claims to support UTF-16 but selecting it doesn't work for your
page.
I suggest using UTF-8 if you really want to work with Unicode here.
Jim Allan