Craig, I went your way, and works just great! thanks a lot. I guess I was making things more complicated than they should.....
THANKS! =) On Feb 4, 10:52 pm, "Craig Ogg" <[EMAIL PROTECTED]> wrote: > On Feb 4, 2008 4:41 PM, Christian W. Koch <[EMAIL PROTECTED]> wrote: > > > I've been looking for this like crazy, I started using the markup > > filters with great succes (love at first sight) but there's a little > > problem. I use special carachters, like ã and things like that > > to support different languages. So, if I store it just like that in > > the DB then the filter just spits it out literally instead of the > > actual carachter "ã" > > This may not be the answer you are looking for, but generally I find > it is better to just store the actual characters in the database. > Allowing data to go from the db into HTML without escaping is > generally considered a security hole. If you are unable to do this > (for database encoding reasons, for example), you could translate the > character entities back to characters before sending them on your > template. > > If you want to take that route, there is an example of doing this at > the top of html2text.py[1]. > > Craig > > [1]http://www.aaronsw.com/2002/html2text/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---