[CharlesS]

Why is it that:

a with grave accent == ���Ã_
i with acute accent == �Ã_

As you can see, these special characters don't show up correctly. There may be more - those are the ones I've noticed so far. Would it be possible to enable these?

Thanks,
Charles

[selowitch]

Originally posted by CharlesS:
Why is it that:

a with grave accent == ���Ã_
i with acute accent == �Ã_

As you can see, these special characters don't show up correctly. There may be more - those are the ones I've noticed so far. Would it be possible to enable these?

Thanks,
Charles

You need to use the appropriate HTML entities instead, using either the decimal or hexadecimal codes:

a with grave accent: decimal &192; hex &#00C0;
i with acute accent: decimal &205; hex &#00CD;

However, because HTML is disabled in this thread, those aren't showing up as the characters, just their codes. And I think that's up to the admins, if I'm not mistaken. So, unless HTML is enabled in a given thread, you're stuck with plain text, which doesn't include the accented characters.

[Ω]

The ? in my name is not actually a question mark.

[Diggory Laycock]

é á ö - It seems like you can cheat and put in mac accented chars (non-standard HTML).

This appears to render in Safari, FireFox and MS:IE (mac versions tested).

[CharlesS]

Originally posted by Diggory Laycock:
� � � - It seems like you can cheat and put in mac accented chars (non-standard HTML).

This appears to render in Safari, FireFox and MS:IE (mac versions tested).

Then why don't the two accented characters I entered show up correctly?

[Diggory Laycock]

Originally posted by CharlesS:
Then why don't the two accented characters I entered show up correctly?

Hmm, not sure - are you using Safari?

I just typed option-e then e. é

I notice that the chars in your quote of my post didn't come through.

[CharlesS]

Originally posted by Diggory Laycock:
Hmm, not sure - are you using Safari?

I just typed option-e then e. é

I notice that the chars in your quote of my post didn't come through.

Yeah, I was using Safari when I posted that.

I'm quoting you now with Camino. Let's see if it makes any difference...

[CharlesS]

Hmm, seemed to work. Let's try quoting your other post:

Originally posted by Diggory Laycock:
é á ö - It seems like you can cheat and put in mac accented chars (non-standard HTML).

This appears to render in Safari, FireFox and MS:IE (mac versions tested).

And my characters that wouldn't display properly: à í

edit: hmm, I guess it's a Safari issue, then. The characters here all seem to show up fine in Camino.

[Diggory Laycock]

Very odd - I use Safari to post and It seemed to work.

[CharlesS]

Originally posted by Diggory Laycock:
Very odd - I use Safari to post and It seemed to work.

What do you have the Default Encoding set to in the preferences?

[Diggory Laycock]

Originally posted by CharlesS:
What do you have the Default Encoding set to in the preferences?

Western (ISO Latin 1)

[CharlesS]

Originally posted by Diggory Laycock:
Western (ISO Latin 1)

Okay, that seems to be the problem. I had Safari set to UTF-8.

I'm going to try a bunch of chars again with ISO Latin 1 on and see if they all show up correctly:

á é í ó ú à è ì ò ù â ê î ô û ä ë ï ö ü ç ã ñ

œ ? ® † ¥ ø ? “ ‘ ” ’ å ß ? ƒ © ? ? ? ¬ … æ ? ? ? ? µ ? ? ÷

It's unfortunate, though, because this means that there are characters which it will be impossible to enter. It also means that if I enter accented characters using ISO Latin 1, then users who use UTF-8 in order to see other languages like Japanese, Arabic, etc. will not be able to see them...

edit: hmm, even with the setting set to ISO Latin 1, a bunch of characters in the second line still don't seem to show up correctly. Oh well...

[selowitch]

Folks, wouldn't it be easier to convince an admin to turn on HTML by default, and then using HTML entities to make these characters?

[voodoo]

Originally posted by selowitch:
Folks, wouldn't it be easier to convince an admin to turn on HTML by default, and then using HTML entities to make these characters?

From the sound of it they'd rather rip their liver out with a spoon and eat it than to allow html in posts.

[Demonhood]

Originally posted by voodoo:
From the sound of it they'd rather rip their liver out with a spoon and eat it than to allow html in posts.

there's no way we'll ever turn HTML on for the forums. it'd open us and all our members to far too many security issues.

[CharlesS]

Originally posted by Demonhood:
there's no way we'll ever turn HTML on for the forums. it'd open us and all our members to far too many security issues.

Yeah, no kidding. Then all someone'd have to do would be to type <BLINK> with no </BLINK> and every post below his would blink.

Or you could just type </HTML> to always get the last word in a debate...

Seriously, though, maybe this could be solved by making it a user setting which text encoding to use. Then the BB software would know what it was receiving and could convert to and from whichever encoding it uses internally...

[tooki]

Or people would put in that JavaScript that puts up a "Ha! You're a loser!" dialog that reappears when you press OK, leaving you to force-quit the browser.

So, um, no.

Hell no.

tooki

[bradoesch]