Great, I thought this might work better. I'll put out a quick update
in a moment or two.
Thanks for your help!
Cheers,
Dan
PS. There's probably more testing to do, and perhaps some changes to
allow things like {二} or {一:二} or {一::二}. I don't think it would be
that difficult. We will have to change the markup rules to allow utf,
and then do some kind of utf2url conversion, somewhere in the code so
things matches what is stored in the index and info pages. We should
get this fixed before we go to 3.xx as it could break indexes or info
pages one way or the other depending on how we fix it. I guess we
should probably have everything saved as utf except page names, as
Linly mentioned, though it probably won't matter at this point...
On Wed, Mar 18, 2009 at 2:44 PM, Hans <[email protected]> wrote:
>
> 2009/3/18 The Editor <[email protected]>:
>>
>> Actually, try this and see if it doesn't work... ~lines 54-56
>>
>> if ((!isset($_GET['p'])) || ($_GET['p'] == '')) $pageLink =
>> BOLTconfig('BOLTdefaultPage', 'main');
>> else $pageLink = $_GET['p'];
>> $pageLink = strtolower(BOLTutf2url($pageLink))
>>
>> I just put the strtolower after the utf2url conversion, rather than
>> before. Seems to work fine now. What do you think?
>
> yes, that looks good!
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
