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
-~----------~----~----~----~------~----~------~--~---
