-- Original Message --
Date: Thu, 27 Jan 2005 18:16:49 +0100
From: maximilian attems <maks(a)sternwelten.at>
To: OpenGuides software developers <openguides-dev(a)openguides.org>
Subject: Re: [OpenGuides-Dev] encoding troubles
On Wed, 26 Jan 2005, IvorW wrote:
I wonder whether this might be the time to
and provide something more flexible. I have in mind something inwardly
pluggable that supplies a normalisation function for node names.
what do you mean by "normalisation",
What I have in mind is a many to one mapping (or rather a several to one
should both reach the same page.
a link to [[café]] should work, as should a link to [[cafe]]. These indicate
that there is
a single wiki page for café, and that the various ways of expressing it
into a "normal form" (in computer science speak).
People would be encouraged to use the accented form in page links.
it would be cool to support the "äöü" and
I agree :)
Currently, n_n_t_n_p reduces multiple whitespace
to a single space, replaces
spaces with underscores and adds Title Case. There is no reason why this
could not apply de-accenting of letters or
turning umlauts into diphthongs.
I think that there is a strong case for this being a plugin.
please explain diphthongs.
Example: the word für can also be written fuer. Schön can be written schoen.
I don't know what the German word for a diphthong is, but it means putting
two vowels together.
Also, ß can be replaced with ss.
i'm not a native speaker and dict doesn't know
why de-accenting letters?
"café" should well be permitted as category.
café will still work (see above).
This would be an option for someone setting up a guide, whether the
title munging rules included such normalisations.
If there were no normalisations, [[café]] and [[cafe]] point to two different
The #REDIRECT mechanism is probably sufficient if there were just a few
needed (as is the case with an English language guide: it would be nice
for [[café]] to work).
Also, this could provide a solution to some of
problem (I originally raised this as an issue with search, but it could
equally be thought of as a node name munging issue).
as i'm not familiar with the openguides code,
i may have misunderstood your statements.
i hope you'll find a solution for this encoding problem. :)
Hopefully my explanations are making more sense to you now.
Book yourself something to look forward to in 2005.
Cheap flights - http://www.tiscali.co.uk/travel/flights/
Bargain holidays - http://www.tiscali.co.uk/travel/holidays/