On Tue, Oct 20, 2009 at 3:25 PM, Hans <[email protected]> wrote: > > 2009/10/20 The Editor <[email protected]>: > >> We can revisit all this in the next round. I am more concerned about >> getting to 3.3 first. It is possible when we evaluate everything, we >> may find we don't these. But even so, in general I don't have any >> burden to support page names with weird punctuation in the core. I >> think it is more appropriate for a plugin. > > Dan, what I was exploring and like to achieve is the full use of html > entities in page names. Since BW already accepts UTF-8 characters in page > names, it is only logical to create the easiest mechanisms which support > input of html entities in page names. Just that. We can already create page > names including the characters which are otherwise entered in a documents > content as html entities: by inserting the % encoded characters directly. It > is not as if they are not allowed. By adding the necessary html decoding > before url encoding we have the simple means of entering html entities in > page names. The special handling of '&' is needed for that, and escaping '&' > for url encoding makes it impossible to enter html entities in page names. > > And I think the scope of the characters covered by html entities (and thus > correctly represented by browsers) is far bigger than mere "weird > punctuations". > See http://htmlhelp.com/reference/html40/entities/ > and the lists of characters available in HTML 4: > 1. Latin-1 Entities > 2. Entities for Symbols and Greek Letters > 3. Special Entities > > It seems strange to open up BW for easy use of thousands of Chinese > characters in page names, and the whole scope of unicode characters from > many languages, yet make it impossible to enter html entities.
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. 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. 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... Cheers, Dan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
