> Note: you can already enter any of those special chars directly into > your browser and/or a link and they work fine, thanks to UTF.
Yes, I said so. It is not as if we are talking about illegal characters. > For instance I just created a page like this: test.Ξ⇔—© (Greek > letter, mapping mark, dash, and symbol) and it all works fine. The > only thing we are talking about are special characters (mostly > punctuation) that tend to produce problems in the core. No. I don't understand why you insist we are talking about "mostly punctuation" characters. This is not true. I gave links to pages with lists of HTML 4 entities. And we are not talking about characters which "produce problems in the core", I think. As page name characters they are url encoded. And characters like <>"# and a few more are not allowed and filtered out already. > Of course you cannot currently enter htmlentities for these chars and > have it work. You have to enter the actual symbol. So that might be > something worth pursuing. I'm just not convinced--as I much prefer > what you have go in come out. Not be automatically translated more > than necessary. I'll try and work on this some later today, but I have > a busy schedule today... Okay, I try to convince you: I appreciate the principle of "what goes in comes out", but although we can enter symbols covered as html entities directly, a) it may not always be convenient, and b) we cannot use html entities as code in page names, as the ampersand is a special HTML character, and used as argument separator in urls. So we have the situation where we can enter HTML entities in the page content, and have these saved as they are, as code, and displayed decoded in a normal page, but we cannot do or expect to do the same for page names. Instead we can agree that HTML entities get translated to url % codes, and that way they get displayed decoded, as symbols etc. in the address bar as well as in page lists, messages etc. ~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 -~----------~----~----~----~------~----~------~--~---
