> Of course, it might be possible to extend the PrettyLink regexp to > account for the un-encoded brackets, but hacking regexp almost always > gives me a nosebleed :-(
The problem here is that changing the PrettyLink RegEx would most likely do more harm than good - it's a can of worms. > If FF3 left the brackets encoded, it would be easier to copy/paste > the permalink URL into a PrettyLink syntax. Actually, I've noticed that while Firefox's location bar decodes entities when displaying them in the location bar, some characters (well, space chars anyway) are encoded when copying the URI: 1. visit http://tiddlywiki.com/#%5B%5BHelp%20and%20Support%5D%5D 2. Firefox 3's location bar will display decoded characters: http://tiddlywiki.com/#[[Help and Support]] 3. copying that URL into the clipboard will yield the following: http://tiddlywiki.com/#[[Help%20and%20Support]] So if we could get the Mozilla folks to encode all entities in that way, Firefox users would regain full use of permalinks. Does this make sense? -- F. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/TiddlyWikiDev?hl=en -~----------~----~----~----~------~----~------~--~---
