Description

Documentation for usage of translation string keys in the a-plus repository. Also, updated typical makemessages call, which changes due to updation to Django 3 in development of a-plus 1.10.

Why?

In the PR 838 of a-plus, translatable strings are replaced with keys in the source code. The change in protocol as well as the format of these string must be documented.

How?

By adding documentation here in the GNU gettext styleguide.

Testing

Remember to add or update unit tests for new features and changes.

How to test your changes in A-plus
How to test accessibility

What type of test did you run?

[ ] Accessibility test using the WAVE extension.
[ ] Django unit tests.
[ ] Selenium tests.
[ ] Other test. (Add a description below)
[x] Manual testing.

I checked that the documentation looks good in the fork on Github and that the links work. I did not test the site works locally.

Did you test the changes in

[ ] Chrome
[x] Firefox
[ ] This pull request cannot be tested in the browser.

Think of what is affected by these changes and could become broken

Translation

[ ] Did you modify or add new strings in the user interface? (Read about how to create translation)

Programming style

[ ] Did you follow our style guides? There isn't a style guide for Markdown.

Have you updated the README or other relevant documentation?

[ ] documents inside the doc directory.
[ ] README.md.
[ ] Aplus Manual.
[x] Other documentation (mention below which documentation). This is the documentation :D

Is it Done?

[x] Reviewer has finished the code review
[x] After the review, the developer has made changes accordingly
[ ] Customer/Teacher has accepted the implementation of the feature

Clean up your git commit history before submitting the pull request!

apluslms / apluslms.github.io