Adding '&' to array $BOLTutfEscapeChars will prevent any input of '&' to be url encoded and prevent '&' to be part of page names. That would be very regrettable, and such restriction is not necessary.
Input '&' gets url-encoded to '%26'. That will be part of page file names created with '&' in the name field. There will be no confusion with '&' as url character, as it is encoded as '%26'. All url-encoded names display fine in searches, are accessible with actions etc. My edit action will open such a page fine for editing. The title will display the '&', but the address bar will display '%26'. Example: create page 'test.a&b' results in page 'test.a%26b'. This handles fine in page lists and actions. But it won't work to create a markup link like [[test.a&b]] nor [[test.a&b]] because the & is treated as special url character , i.e attributes separator. Still we can write links as [[test.a%26b]] But to translate the link to 'test.a%26b' will be difficult if not impossible, since when link markup is rendered all '&' are already '&' Otherwise a link markup like [[test.a&b]] may be useful for writing amps and other entities as htmlcharactercodes in links. ~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 -~----------~----~----~----~------~----~------~--~---
