I was aware that none of the variables are really set to take UTF
pagenames at present (system, data or info), though I will likely try
to rework that code if I get some time before going 3.xx. It may be
easy or hard, I don't really know. More than likely easy...
Here's a fix for the include bug that will be in the next release.
functions.php, ~lines 153-155
if (isset($args['page'])) $page = $args['page'];
else $page = $args[''][0];
$page = BOLTfilter(BOLTpageshortcuts($args[''][0]), 'page');
It would be good to test every function, condition, command that can
takes a page name to make sure they all work, as well. Almost all of
them do in one way or another. They should be easy enough to fix--the
time consuming part is tracking them all down. For that matter, we
might be able to modify the BOLTfilter code and solve many of these
problems in one shot. I'l look into it. Use the fix above for now.
It's actually an improvement over what we had as it now allows us to
use page shortcuts in the include function. Nice!
Cheers
Dan
2009/3/18 Linly <[email protected]>:
>
> Hi Dan, Great success. I tested in a fresh installation, enabling the
> "utfPages: true". Here is the report:
>
> * Creat page [[一.二]] -> OK
> * Copy to page [[一.二三]] -> OK
> * Rename [[一.二三]] to [[一.一二三]] -> OK
> * Delete [[一.一二三]] -> OK
> * Edit page [[一.二]] -> OK
> * Set info var in page [[一.二]] -> OK
> * Use {::variablename} to retrieve the data -> OK.
> * But use {一.二::variablename} to retrieve the data -> Failed
> * In an English named page {main::variablename} is -> OK
> * Use Chinese variable name {::一二三} -> Failed
> * The system msg all looks good. -> OK
> * [(search group='一')] -> OK
> * [(include page='一.二')] -> Failed
> * Use [(info)] to write Chinese named page to info.test -> OK
> * retrieve the data '{info.test::一.二}' -> Failed
>
> Cheers, linly
>
> On 3月19日, 上午3時10分, Hans <[email protected]> wrote:
>> 2009/3/18 The Editor <[email protected]>:
>>
>> > Yes, I added a small exclusion array to the utf to url conversion
>> > functions. Currently: < > \ / * % are excluded from urlencoding. I
>> > could add ' and " if we wanted. I wanted to retain at least have some
>> > semblance of filtering!
>>
>> I probably would exclude from page names all url "reserved" and
>> "unsafe" characters.
>> Seehttp://www.blooberry.com/indexdot/html/topics/urlencoding.htm
>>
>> ~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
-~----------~----~----~----~------~----~------~--~---
