* [WIP] Implement automatic spell-check for docs
fixes#663
The only thing unclear to me so far is how the output of `make spelling`
should be checked - is there a possibility to check for a file (i.e.
`_build/spelling/output.txt`) to be empty, and report a failed build
otherwise?
* fix typo in requirements.txt
* add enchant library
* travis should report errors, order spelling wordlist
* change travis.yml to easier troubleshoot build issues
* fixed more typos, added more words
* add more words, fix more typos
* added more words
* added more words
* revert changes to .travis.yml
* Data model and migration
* Some backwards compatibility
* CRUD for checkin lists
* Show and perform checkins
* Correct numbers in table and dashboard widget
* event creation and cloning
* Allow to link specific exports and pass options per query
* Play with the CSV export
* PDF export
* Collapse exports by default
* Improve PDF exporter
* Addon stuff
* Subevent stuff, pretixdroid tests
* pretixdroid tests
* Add CRUD API
* Test compatibility
* Fix test
* DB-independent sorting behavior
* Add CRUD and coyp tests
* Re-enable pretixdroid plugin
* pretixdroid config
* Tests & fixes
* Fix duplicate source string
* occured -> occurred
All resources I could find listed this as misspelled, but I wasn't too
sure…
Also, it should be checked if all changes to the .po-files are respected
in the corresponding src-files.
* Check that vouchers selected via API are for the correct event
* Choose different subject for reminder mails if auto-expiry is off
* correct english typos
As with PR #660, it should be checked whether the changes to the
.po-files are respected in the corresponding src-files.
Placeholders in subject were not being replaced because there was
no `.format()` called on the subject.
This commit creates a context dict that is used for both the body
and the subject. It is then replaced using `.format_map()`
Fixes https://github.com/pretix/pretix/issues/531
This commit allows transaction comments to display newlines and URLs in
a useful way, helping when additional data (such as a reference to a
ticket system or a longer discussion) is required.
This PR also prevents pretix from having to bring its own chat system ;)
* New concept for fee handling
* More usages
* Remove all usages, make all tests pass
* API changes
* Small fixes
* Fix order of invoice lines
* Rebase migration
