You should not unescape recursively. Input to EscapeHTML: '<' Output: '&lt;' : Correct UnescapeHTML: input '&lt;' Output '<' Wrong. This is because you replace '&' with '&' resulting in '<' which is translated to '< ' in the next line. Ludo
-----Message d'origine----- De : fpc-pascal-boun...@lists.freepascal.org [mailto:fpc-pascal-boun...@lists.freepascal.org] De la part de ik Envoyé : mercredi 25 mai 2011 08:34 À : FPC-Pascal users discussions Objet : Re: Re[2]: [fpc-pascal] fpWeb and html and uri escaping/unescapingelements On Tue, May 24, 2011 at 12:21, José Mejuto <joshy...@gmail.com> wrote: Hello FPC-Pascal, Tuesday, May 24, 2011, 10:09:03 AM, you wrote: i> I've created a patch with the Escape and unEscape functions, and place it i> here: http://bugs.freepascal.org/view.php?id=19407 Un/escapeHTML parsing must be in one go, specially the "&" one. Test against: "&lt;" I'm not sure what you mean here. If you have already html entities you should not escape them. If you do not have html entities you should escape them. The Escaping and unescaping works well, I already tested them before I sent them. Right unescape "<", your code "<". -- Best regards, José Ido _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
