Update loaddata/dumpdata encoding options documentation

[anonymous]

Hi,

I think that in ​http://www.djangoproject.com/documentation/0.96/django-admin/#loaddata-fixture-fixture is missing a howto for options on encoding. For how specify encoding in loaddata and dumpdata

For example if you use non-ASCII names and follows ​http://groups.google.com/group/django-users/browse_thread/thread/bd609cb862da47c0?hl=en (post #6) then when completed you have a strange encoding characters.

So, I think that you should update documentation or mark it as possible bug

[Russell Keith-Magee]

Unless you can point a specific encoding problem with the current SVN trunk, I'm going to mark this wontfix. loaddata/dumpdata has had a lot of bug fixes since 0.96, amongst them the handling of non-ASCII data.

[DXpublica@…]

Well, so although there is no bug in svn with encoding in loaddata/dumpdata, there are bugs of encoding in 0.96.
Perhaps you could mention that in 0.96 documentation (useful for utf8 strings users I think)

Regards,
Xan.

[DXpublica@…]

Replying to DXpublica@telefonica.net:

Well, so although there is no bug in svn with encoding in loaddata/dumpdata, there are bugs of encoding in 0.96.
Perhaps you could mention that in 0.96 documentation (useful for utf8 strings users I think)

Regards,
Xan.

With "mention" I mean you could edit ​http://www.djangoproject.com/documentation/0.96/django-admin/#loaddata-fixture-fixture and point out that there are several bugs with encoding and a recommendation for update to svn

Xan

[James Bennett]

The 0.96 documentation is frozen and won't be edited ever again; our policy is not to edit the "release" once it's been released. And the fact that there were lots of issues with non-ASCII data in versions of Django released before the merge of the Unicode branch is fairly well-known, so trying to document every single thing which could fail would probably replace every line of the old documentation with "unless you try it with Unicode, in which case it doesn't work".

[DXpublica@…]

Okay, so.
I did not known the documentation policy. My intention was to keep polite documentation
I understand your reasons.

So, this is _definitely_ an invalid ticket.

Thanks for your comments,
Xan.