Of course I've looked in there! Had to figure out how to get it to do that! % encoding is a simply php function.
The problem with % encoding page names is only that BoltWire has filters everywhere to validate input. Mostly for security reasons, but also to reduce bugs and crashes. To get % encoding on BoltWire is easy (actually I have to ADD an extra step to convert % to _), but then the filters kick in and BoltWire crashes. It's just a question of tracking down all the filters, functions etc., that might be affected and fixing them. It might be a simple process, it might be challenging. And what do I do with pages that don't use UTF pages. Two filters? I'm not giving up... It's not that hard. Just over extended. and to be honest, I work largely on inspiration. When I get an idea and a hankering to tackle something, I'm a beast. When I don't see a way through something clearly, I just hold off, until I do. I learned something about that from Pm. He had an amazing sense of judgment and timing. Well, riding BoltWire and riding PmWiki were definitely two different experiences... But then again, BoltWire develops pretty rapidly. Pro's and cons. Cheers, Dan On Wed, Feb 25, 2009 at 8:38 PM, Linly <[email protected]> wrote: > > Hi Dan, > > Have you ever looked into the text inside backup file? It seems ALL > the non A-z, 0-9 characters were transformed to "percent-encoding" > characters. > > I found the Chinese characters are correctly encoded there. So the > "percent-encoding" is the standard php function or you have done the > "percent-encoding" already? > > Cheers, linly > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
