World Outline and German Umlauts

[Jörg Kantel]

Hi,

I tried to follow the screencast »World Outline for Poets« and I had success. But the result didn't look very nice (You can see it here: <http://gu.blorkmark.com/>) because all my german umlauts gets scrambled (see the attached screenshot). I suppose the problem results due to the fact that I'm working on a Macintosh and the server is a Windows machine (it seems to be the old Frontier Mac OS Roman vs Windows Latin 1 problem).

Any idea how I can made it looking nice?

wkr (and pls excuse my bad (d)english)

J"org Kantel

--
J"org Kantel <jo...@kantel.de>
Der Schockwellenreiter <http://www.schockwellenreiter.de/>
Cognitiones Publicae <http://cognitiones.kantel-chaos-team.de/>
Buergerstr. 66, 12347 Berlin (Neukoelln)
-- Verschtehen Sie, isch 'abe garrr kein Wooerd! --

[Dave Winer]

I don't know what changes need to be made, but I'm open to making them, if they don't involve heavy lifting...

[Jörg Kantel]

Hi Dave,

2012/6/21 Dave Winer <dave....@gmail.com>:

> I don't know what changes need to be made, but I'm open to making them, if
> they don't involve heavy lifting...

thanks! I didn't know exactly what to do, but the issue was mentioned
here <http://tech.groups.yahoo.com/group/frontierkernel/message/2629>
and around seven years ago for a similar problem (Windows encoding to
Mac encoding <http://www.frontierweb.de/archiv/2005/02.html>) André
Radke gave mit a hint with

[code]
if system.environement.isMac {string.latinToMac(s)}
[/code]

where s is the whole text to be converted (see here
<http://docserver.userland.com/string/latinToMac>). I'm not quite
sure, but I think the use of the opposite verb
<http://docserver.userland.com/string/macToLatin> could solve the
problem.

Just my two cents
J"org

[Andrew Shell]

I think the problem is which character encoding your browser is using.
When I clicked your link everything was as you see it but when (in
Firefox) I clicked "View > Character Encoding" and changed it from
"Unicode (UTF-8)" to "Western ISO-8859-1". It's not consistent
though, when I created a blogpost with my account I saw the characters
perfectly.

One thing to try is to add a meta tag to the header in your template
telling the browser which character encoding to use.
See this page: http://htmlhelp.com/tools/validator/charset.html.en

Here is my blog post with the meta tag added to the header:
http://yqshq.blorkmark.com/

On a side note, the OPML editor doesn't seem to handle multibyte
characters at all. I tried pasting some Hebrew into an outline and
even in the outline all the characters turned into question marks.
That's probably a much bigger project then getting umlauts to work.

Cheers,
Andrew Shell

[Jörg Kantel]

Hi,

2012/6/21 Andrew Shell <and...@andrewshell.org>:

> I think the problem is which character encoding your browser is using.
>  When I clicked your link everything was as you see it but when (in
> Firefox) I clicked "View > Character Encoding" and changed it from
> "Unicode (UTF-8)" to "Western ISO-8859-1".  It's not consistent
> though, when I created a blogpost with my account I saw the characters
> perfectly.

thanks for this hint. I added a custom template to my world outline
(following the screencast of today) and put this additional line in
the head of the HTML:

[code]
<meta http-equiv="content-type" content="text/html; charset=macintosh">
[/code]

(iso-8859-1 didn't work -- because that's the Windows encoding)

Now the german umlauts are correct within the browser but the text is
still scrambled within the OPML file on S3(see
<http://static.scripting.com/tulsa/wo/kantel/2012/06/21/archive001.opml>)
because there is still the wrong encoding:

[code]
<?xml version="1.0" encoding="ISO-8859-1"?>
[/code]

I need a place where I can change the template for OPML. ;o)

(In general in my opinion it would be better if the OPML Editor is
writing UTF-8 by default on both platforms. But I think that would be
a very hard work.)

wkr (and again excuse my bad (d)english)

[Jörg Kantel]

It seems it is not really a solution of the umlaut problem. i
considered a additional failure:

With the charset all _my_ files will be shown correctly in the browser
but e.g. not in the file-list or toc (see
<http://2751.mediahackers.org/eineErsteLsungDesUmlautproblems> vs
<http://2751.mediahackers.org/>) where the umlaut is still wrong.

Any idea?

wkr

[Daniel Boese]

Hi,

I seem to have a similar problem in my river, it scrambles German Umlauts and French accents:
http://ec2-204-236-194-210.compute-1.amazonaws.com/rivers/admin/

Anything I can do to change this?

daniel