acute accents: á, é, í, ó, ú

grave accents: à, è, ì, ò, ù

circumflex: â, ê, î, ô, û

c-cedilla: Ç, ç

diaeresis & umlauts: ä, ë, ï, ö, ü

a-e ligature: diæresis, Æneus

o-e ligature: f˛tus, ‘dipus

n- and m-dash: 1ˆ10˜yes

quotes: Œsingle,‚ „double‰

By the way, the greater-than sign and ampersand don't get iso-encoded--that's a no-no.

Report (greatly amended): The following characters are incorrectly entered into the database when submitted through a web browser's editing field: oe ligature, n-dash, m-dash, all curly quotes. If they are manually entered into a database object, they are rendered correctly to the web page, but incorrectly into an editing field (textarea).

Tested in MSIE 5.1.3, iCab 2.6, OmniWeb 4.1b1v332 and Opera 5.0b3.393. Mozilla 0.95 posts incorrect characters (looks like Unicode--not sure).   5:38:11 PM    

e-acute: é

e-grave: è

e-circumflex: ê

cedilla: ç

diaeresis & umlauts: ä, ë, ï, ö, ü

a-e ligature: diæresis   5:09:48 PM    

Résumé çedilla ä-ümlaut. cool.

Weird. These characters got posted just fine, but didn't survive an edit. So I tried re-entering them in the editing field, but couldn't get them back. I think Radio processes text differently on a new posting than post-editing.

Update:

Yeek! I just noticed that the default template has no character-set meta tag. I'll have to add one and test the browser posting again.

<caron>? There's no <caron> in my table (view source to see where Radio inserted <caron> in the test above). Ah, my iso table is being bypassed by the kernel. String.macToLatin and string.latinToMac are kernel verbs. Rats.

Update 2:

Adding the meta character tag fixes the problem with editing. That's a step!   4:58:33 PM    

Also had to import the DocRenderer3 suite, for compatibility with my sites.

  4:07:15 PM    

No luck with Opera, Mozilla, or Omniweb either. The characters come out differently when posted and viewed with these, although in some combinations text comes back correctly in the weblog editing field!  3:19:23 PM    

One thing has bugged me foreverÑthe combination of MSIE (Mac) and Manila doesnÕt play well with high-ascii characters. This is a stumbling block for using Manila (& Radio) to produce professional web sites.

I've gotten used to flipping over to BBEdit to get the numeric entity for quotes, apostrophes and long dashes, but I canÕt expect my graphic designer and writer to do this. And after all, the Mac has supported typographic characters since 1984!

This is caused by two problems:

1. Radio/Frontier expect different encoding than is sent by MSIE (Mac). I think that MSIE is sending text in iso-8859-1, but Radio assumes itÕs Mac-Latin.
2. Userland still hasnÕt updated the table at html.data.iso8859.mac, which is used to convert high-ascii characters to iso entities. ThereÕs discussion about this at http://frontier.userland.com/discuss/msgReader$6081. You can download my corrected version.

2:49:27 PM    

I've been using Frontier for years. Even though I'm used to using Manila sites, Radio 8 takes everything a leap further towards integrating the web browser into my desktop. The polished interface and quick response makes it feel like a desktop app. But there's a strange new feeling of connectedness, when I'm using this app and type command-N because I want to open a new browser window to view a site on the web.

I've resisted switching to Radio 8, because I wasn't prepared to convert to 8's new CMS scheme. Even now, two of my projects are set up using the Static Sites tool in Radio 7. What do you know? Radio 8 comes with the old object database-based static sites tool installed! Easy as pie (I'll confirm thisin a few minutes when I've brought over my sites).

I'm having fun!  2:47:19 PM