I'm gong to be reviewing all the utf code throughout the core system during the next set of releases (after we get 3.3 out) with an eye toward simplifying it. In the main time, this array blocks these characters from getting urlencoded, thereby solving numerous bugs--often with page shortcuts and the like.
We can revisit all this in the next round. I am more concerned about getting to 3.3 first. It is possible when we evaluate everything, we may find we don't these. But even so, in general I don't have any burden to support page names with weird punctuation in the core. I think it is more appropriate for a plugin. Cheers, Dan On Tue, Oct 20, 2009 at 2:33 PM, Hans <[email protected]> wrote: > > 2009/10/20 The Editor <[email protected]>: >> >> Hans, I'm going to release a new version soon which will add & to the >> BOLTutfEscapeChars array. At the moment it doesn't seem to work the >> way I would like. I prefer the core to be simpler. The purpose of page >> names was to allow internationalizations, not odd punctuation. > > This is regrettable, in my opinion. Why is it important to add & to > the BOLTutfEscapeChars array? Why is it necessary? What is the > function of this array in general? Maybe I am not understanding > something here. > > ~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 -~----------~----~----~----~------~----~------~--~---
