Great! Thanks for testing this. I'm sure there are other bugs too. I'll give a look at it tomorrow and see if we can't fix these and any other problems you come up with. Pretty cool, isn't it?
Cheers, Dan On Thu, Feb 12, 2009 at 10:16 PM, Linly <[email protected]> wrote: > > [bug report] The utf8 function seems not like the # (auto number > naming 1000, 1001...). > > I have a form with this line "[session target {p}.#]" works fine on > 2.44, and failed on 2.45. :( > > Cheers, > linly > > On 2月13日, 上午10時03分, Linly <[email protected]> wrote: >> I've tested in Japanese charactors. Same as Chinese. Create, delete, >> change title, are ok, edit is not. >> >> linly >> >> On 2月13日, 上午8時02分, Linly <[email protected]> wrote: >> >> > Great, Dan. It's almost perfect. >> >> > I can create, delete, change title to an utf-8 named page. But I can't >> > edit it. It gave me the meg of: >> >> > "Form submitted. Invalid page name. Please try again." >> >> > when I save the edit. >> >> > Cheers, >> > linly >> >> > On 2月13日, 上午7時15分, The Editor <[email protected]> wrote: >> >> > > I just released a highly experimental version of BoltWire (2.45) that >> > > has 3 or 4 strategically placed lines which convert utf page names to >> > > an encoded url format and back as needed, to give a good semblance of >> > > full UTF page name capabilities. It took awhile to find the exact >> > > right places to place these lines, but I seem to have it working. >> >> > > To use, download 2.45, and set utfPages: true in site.config. >> >> > > Then try entering chinese characters or whatever you want for page >> > > names and please report any problems. Links, {p}, breadcrumbs, >> > > actions, titles, etc. It all seems to work, but there's sure to be >> > > glitches, particularly in the filtering of some function inputs. >> > > Consider this feature experimental, and only available for testing >> > > purposes by those who might wish to try it. There should be no change >> > > in behavior to BoltWire when not enabled. >> >> > > I've tested it a bit on chinese characters, but not much with latin >> > > based alphabets having special characters like é or ñ. If UTF pages >> > > are left off, only the accents should be stripped off. If turned on, >> > > you should keep the accents, but the URL will be encoded for the >> > > character. I'm not sure if this is what we want, but I'm throwing it >> > > out there for some of you to tinker with. Enjoy Linly! >> >> > > Cheers, >> > > Dan >> >> > > P.S. The encoding is essentially standard utf8 % encoding, except I >> > > replaced % with _ to bypass BoltWire filtering. We may want to >> > > eventually use the simpler %'s, but it will just take a bit more time >> > > to get it working properly. So don't build too many pages you plan to >> > > keep. If it changes, those pages could be lost. Just give the current >> > > draft a try and test some things. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
