Re: [translate-pootle] More trunk patches!
On Mon, 10 May 2010 10:16:34 +0200 F Wolff frie...@translate.org.za wrote: Op Do, 2010-05-06 om 09:47 -0400 skryf Jacques Beaurain: We have some multiline comments and I actually want to add some that might contain HTML links too. Maybe we need to add to add the Django filters: |safe|linebreaks|clean Similar to the general description too. What do you think? What does each of the filters do? Would this mean that it will interpret the HTML literally? safe would make it interpret html literally which is what Jacques wants, I'm not sure it's a good idea for most users. clean just makes sure the html doesn't break anything. linebreaks would convert newlines to br / tags, that's probably a good idea. cheers, Alaa -- ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] More trunk patches!
I believe safe was already there, I wanted linebreaks to be added (but safe to remain) and clean to ensure we do not break the structure of the HTML. This is not a big deal for me if it is not the trunk behaviour as it is easy to override with custom templates. -Original Message- From: Alaa Abd El Fattah [mailto:a...@translate.org.za] Sent: May-10-10 5:53 AM To: translate-pootle@lists.sourceforge.net Subject: Re: [translate-pootle] More trunk patches! On Mon, 10 May 2010 10:16:34 +0200 F Wolff frie...@translate.org.za wrote: Op Do, 2010-05-06 om 09:47 -0400 skryf Jacques Beaurain: We have some multiline comments and I actually want to add some that might contain HTML links too. Maybe we need to add to add the Django filters: |safe|linebreaks|clean Similar to the general description too. What do you think? What does each of the filters do? Would this mean that it will interpret the HTML literally? safe would make it interpret html literally which is what Jacques wants, I'm not sure it's a good idea for most users. clean just makes sure the html doesn't break anything. linebreaks would convert newlines to br / tags, that's probably a good idea. cheers, Alaa -- ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle -- ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] More trunk patches!
Op Ma, 2010-05-10 om 12:15 -0400 skryf Jacques Beaurain: I believe safe was already there, I wanted linebreaks to be added (but safe to remain) and clean to ensure we do not break the structure of the HTML. This is not a big deal for me if it is not the trunk behaviour as it is easy to override with custom templates. Ok. Your explanation of 'linebreaks' and 'clean' make sense, but I'm not sure about 'safe'. It would mean that developers would need to write escaped HTML when they want to talk about HTML, such as Use lt;br /gt; between lines in your translation and they would need to know that it will be used on Pootle, since I don't think any other translation tool behaves that way. Do I understand it correctly? Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/virtaal-060-released -- ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] More trunk patches!
Hi Friedel, No it means exactly the opposite. The Django safe filter means that the text as passed should be rendered verbatim to the page and that any literal HTML or other tags should be rendered unmodified instead of turned into lt; gt; etc. So developers will be able to write HTML unescaped when they want to talk about HTML. What Alaa meant was that this might have unexpected side effects when people are not writing HTML, e.g the following comment: #. This means x 10 Might create invalid HTML since the is not written as lt; to the page. I do want to point out that safe was already there, I suggested adding linebreaks and clean. Cheers, Jacques -Original Message- From: F Wolff [mailto:frie...@translate.org.za] Sent: May-10-10 12:34 PM To: translate-pootle@lists.sourceforge.net Subject: Re: [translate-pootle] More trunk patches! Op Ma, 2010-05-10 om 12:15 -0400 skryf Jacques Beaurain: I believe safe was already there, I wanted linebreaks to be added (but safe to remain) and clean to ensure we do not break the structure of the HTML. This is not a big deal for me if it is not the trunk behaviour as it is easy to override with custom templates. Ok. Your explanation of 'linebreaks' and 'clean' make sense, but I'm not sure about 'safe'. It would mean that developers would need to write escaped HTML when they want to talk about HTML, such as Use lt;br /gt; between lines in your translation and they would need to know that it will be used on Pootle, since I don't think any other translation tool behaves that way. Do I understand it correctly? Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/virtaal-060-released -- ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle -- ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
