Hi Adrian,
>
> This sounds like a great addition to the automatic admin
> documentation. Would you be willing to code up the patch?
I don't know where to start for such changes.
I would be happy if I could contribute such a patch.
I think that you need to know a lot of internals ?
Regards,
Dirk
I'd like to update the french translations urls in
http://code.djangoproject.com/wiki/TranslateDocumentation with this
new content :
http://vrac.biologeek.com/askimet_error.txt and I get an Askimet
rejected spam error.
So, how can I do to update this page?
Regards,
David
--~--~-~--~
gabor wrote:
> so what do you think about the following approach:
>
> try ascii-decoding
> if fails, try utf8-decoding
> if fails do iso-8859-1-decoding (this cannot fail).
>
> ?
Dumb question maybe. How do you know this encoding ladder will work?
> but imho this should happen only in "specia
Malcolm Tredinnick wrote:
> On Wed, 2006-08-09 at 21:51 +0200, gabor wrote:
> [...]
>> phew... the immortal
>> how-tolerant-we-should-be-when-doing-unicode-conversion problems :-)
>
> Agreed. This is much easier on my side of the fence (lobbing problems),
> than your side (solving them).
> [...]
The Django team discovered and fixed a small security hole in the
django/bin/compile-messages.py helper script, which is the script that
compiles message files (.po files) into binary format (.mo files).
The compile-messages.py script uses the name of the .po file to build
arguments to a system c
