[Django] #22521: Moderinze CSV export docs to cover UTF8 sheets.
Django
--------------------------------------+--------------------
Reporter: brycenesbitt | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.6
Severity: Normal | Keywords: csv
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+--------------------
To the documentation at:
https://docs.djangoproject.com/en/dev/howto/outputting-csv/
I suggest adding:
response.write(u'\ufeff'.encode('utf8'))
At this point any new software should certainly be writing out utf8
spreadsheets, and
the byte order mark is needed by various versions of MS Excel to properly
interpret the utf8 sheets.
--
Ticket URL: <https://code.djangoproject.com/ticket/22521>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: brycenesbitt | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: 1.6
Component: Documentation | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: csv | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
Changes (by claudep):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm not sure it's the role of Django to promote workaround hacks for
proprietary software. BOM markers seem to be controversial for UTF-8
files, so let's that for blogs or Django snippets.
I'm closing the ticket for now, but feel free to open a discussion on
django-dev mailing list, and reopen it if you get support.
--
Ticket URL: <https://code.djangoproject.com/ticket/22521#comment:1>