On Tuesday 12 June 2007 14:22, David Sowder wrote: > Matthew Toseland wrote: > > On Monday 11 June 2007 18:48, David Sowder wrote: > >> Matthew Toseland wrote: > >>> On Monday 11 June 2007 18:14, David Sowder wrote: > >>>> Matthew Toseland wrote: > >>>>> Is this necessary? > >>>> > >>>> Yes. I managed to create a bookmark I couldn't manage later. It > >>>> contained a "&" character. > >>> > >>> I don't understand why. Anything that goes through HTMLNode is > >>> automatically HTMLEncode'd. > >> > >> Yeah, I noticed, but when I tried using HTMLEncoder rather than > >> URLEncoder, it didn't fix the problem, so maybe that's why the auto > >> thing didn't handle it. > > > > Are we talking about inline body text, or tag parameters? > > I'm not quite sure what you mean by that question, but I'll attempt to > answer it with statements. > > A bookmark of mine contained an "&" character, which I had no trouble > naming that way. > I could not manage that bookmark in any way because the interface would > return an error saying the bookmark didn't exist with the "&" and any > remaining characters truncated from the name it said it couldn't find. > The interface uses the bookmark name passed in the URL GET form style by > constructing a URL with the appropriate GET form style arguments, > including the bookmark's name. > The fix I found and committed with r13509 was to URLEncode the > bookmark's name when including it in the URL and then URLDecoding it > when receiving it as an argument.
Ok, that's the specific case where it is necessary. Sorry :| -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20070613/d5903a19/attachment.pgp>
