When searching, umlauts are put before the alphabet. Page 'ö' will be listed before page 'a'. Usually 'ö' is listed after 'o', 'ä' after 'a' and 'ü' after 'u'.
On Oct 19, 10:29 am, Hans <[email protected]> wrote: > Dan, it is important that we don't confuse various issues here! > My suggested code changes were directed to > > 1. Have messages display utf-8 characters and not code. > you suggested changes to function function BOLTmsg() > $BOLTsession['MSG'][$id] = BOLTurl2utf($value); > This seems to fix the coded utf message problem. > > 2. Have a correct redirect to a new page if the page name contains > '&' characters. > I suggested changes to BOLTredirect() so $nextpage is utf encoded, > since it is > not filtered or translated at all before that, but taken straight from > input. > This seems to fix the redirect problem. > > Now you say: > > > 1) It doesn't display properly in the url bar of the browser like other utf > > pages. > > 2) I can't seem to edit it. Ignores my changes... > > But the changes above 1. and 2. do not change the url in the browser bar. > So if you got a problem with that it is a different issue. > As to editing: it works fine here. > > Question: were htmlcharacter codes allowed/working in urls before at some > point? > i suspect not, and the '&' is always used as a separator for url arguments. > Only percent-encoded html character codes makes it possible to use > html special characters in page names. > > Cheers, > Hans --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
