Page 1 of 1

Umlaut-problem with wikilink-plugin

Posted: Mon Sep 25, 2006 2:16 am
by stm999999999
hello,

another problem with the wikilink-plugin:

I have a german blog with words with umlauts (is this the right english word?)

And I want to make a wikilink with ((Pfarrbüro)) to a static-page "Pfarrbüro". But it does not work, because s9y gives not "Pfarrbüro" to the wiki-plugin but Pfarrb& #252;ro (without the space, but I must make it here, because the forum will transfer it to ü and you will not see any difference)

so in line ~300

Code: Select all

$entry = serendipity_db_query("SELECT id, permalink FROM {$serendipity['dbPrefix']}staticpages WHERE headline = '" . serendipity_db_escape_string($ltitle) . "' ORDER BY timestamp DESC LIMIT 1", true, 'assoc');
makes a db-query:

Code: Select all

SELECT id, permalink FROM kirche_staticpages WHERE 
headline = 'Pfarrb& #252;ro' ORDER BY timestamp DESC LIMIT 1
and of course this cannot find a page with the headline Pfarrbüro :-(

Is there a way to fix this, so the wiki-plugin gets normal ü instead of & #252;?

Posted: Mon Sep 25, 2006 11:43 pm
by judebert
Once again, I'm stymied by languages. Sorry I can't help out more in this respect. It's on my list of things to learn.

Posted: Sun Oct 01, 2006 10:05 pm
by garvinhicking
Hi!

I believe some other markup plugin transforms the "ü" into the HTML entity. Which markup plugins that you have installed could cause this? Does the HTml entity already exist in the serendipty_entries.body column?

Regards,
Garvin

Posted: Mon Oct 02, 2006 12:08 am
by stm999999999
garvinhicking wrote:Hi!

I believe some other markup plugin transforms the "ü" into the HTML entity. Which markup plugins that you have installed could cause this?
I must figure this out, but i must be something like this. I take it at the first plugin place, now it works fine.

Posted: Mon Oct 02, 2006 12:16 am
by stm999999999
it is "textile" but I do not know why

Posted: Mon Oct 02, 2006 12:33 am
by garvinhicking
Damn. Textile is one of the most wicked plugins, because its code is butt-ugly and not maintained by other people. I think there is a much more recent version of it floating around, but harder to get up-to-date for us because it uses the polluted global namespace...