On Tue, Sep 22, 2009 at 12:08 PM, DrunkenMonk <[email protected]> wrote:
>
>> Anyway,I've spend a good bit of time trying to track this all down,
>> but the fix is not simple... It will have to wait till next week. I
>> don't have a quick solution. In the mean time, you may just have to
>> add a $query = BOLTurl2utf($query); line to your function. It won't
>> hurt anything should I find a way to fix it, and you get instant
>> functionality now.
>
> I did already. Its a simple fix, but I've had to apply it basically
> any time I've ever wanted to get a bit more out of boltwire, either in
> my own plugins or as bug reports. It really getting in the way of the
> "should just work" feeling boltwire otherwise upholds.
Granted. I will work on it next week. We might possibly be able to do
it right now with no problem. But I want to think about it a bit be
able to test functionality more thoroughly and have time available to
debug, in case there are problems. All I was saying is that this kind
of release will have to wait till next week.
I do strive to make boltwire "just work" as you say. But when we've
patched together some aspect of the engine with duct tape and staples
for awhile, and we figure out after the fact a better architecture,
it's not always easy to remove all the duct tape and staples without
things breaking. :)
> Currently, the source of every page seems to be sent through
> BOLTurl2utf. %b3 should surely not be converted when in a page?
I've tried to systematically run every page through BOLTpageshortcuts,
which does many things, including utf2url. It gives us systemwide
consistency in formatting and page shortcut syntax. But it also means
it may not be that hard to correct. If you got time to tinker, try
commenting out lines 1578 and 1579 of engine.php
// if (BOLTconfig('BOLTutfpages', 'true') == 'true') $link =
BOLTutf2url($link);
// else $link = BOLTutf8_strip($link);
Leave the anchor alone a couple line above this... If it fixes things
great. Any help you can give in tracking down potential problems this
causes would be a step in the right direction. But probably the way it
really should be done is a system wide search of every utf2url/url2utf
function, analyze each instance and cut or not. IE, a thorough
housecleaning of the utf problem. I think you got the gist of the
direction we should go.
Cheers,
Dan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
