| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`bytes` takes no additional args in python2 unlike it's taking
an encoding in python3.
Unidecode returns a unicode string in python3 and a bytestring
in python2 which, I believe, was the main cause of error #71.
Now, regardless of whether unidecode is included, all strings
passing through http_quote will be encoded to ascii which should
fix both issues.
Also included is a fix for a failing test when unidecode is used.
Unidecode's `_unidecode` function ignores characters greater
than 0xefff, which '\xe2\x99\xa5' (the heart symbol) is. This
caused users with unidecode to fail '.pdf' was produced rather
than the expected '?.pdf'.
|
|
|
|
|
|
|
|
|
|
|
| |
The logic was coupled with the views which made things difficult
to reuse if you wanted to use the pdf generation somehwere else
than in a view.
With this patch, the logic has been moved to `utils.py` and should
be more easy to reuse.
Tests have been adapted and made compatible with django > 1.7
|
| |
|
| |
|
|
|
|
|
|
| |
The view didn't define any title in context and the templates itself
doen't have unicode content. I forced it making a view with a unicode
title in context.
|
| |
|
| |
|
| |
|
|
|
|
| |
DAMN IT
|
|
|
|
| |
Because Django 1.6 and other fireworks.
|
|
|
|
| |
The future is now ;]
|
|
|
|
|
| |
In near future we should support moar Djangos (and using
Travis for this).
|
| |
|
|\ |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
This isn't great but better than nothing...
|
|
Fixes #11.
|