Thanks for sharing that Linly! It touched me too on an emotional level, it filled me with surprise, joy and delight.
I was really surprised to see Chinese and other higher Unicode characters in the Firefox address bar Internet Explorer only shows the % encoded raw text. So the new browsers are on our side! The only real limitations for utf-8 encoded page names I see in the restriction for php code to use lower ASCII, and in BoltWires clever tying of action names and markup function names and php function names. There is no translation layer built in, so we have to restrict markup function names like [(search ...)] to lower ASCII. Actually action pages could be renamed to higher Unicode characters without problems I think, if one wants to get fancy. So there should not be any limitations as to page names, but a limitation as regards to function names, variable names (do info variables work with higher utf-8 characters?) The programming challenge is to decode any utf-8 characters cleanly for php handling, and encode any results cleanly. Cheers, ~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 -~----------~----~----~----~------~----~------~--~---
