| Name | django-extended-makemessages JSON |
| Version |
1.4.0
JSON |
| download |
| home_page | None |
| Summary | Extended version of Django's makemessages command that exposes selected GNU gettext tools options and adds new custom options, which further simplify message detection and translation files management. |
| upload_time | 2025-01-13 14:39:27 |
| maintainer | Michał Pokusa |
| docs_url | None |
| author | Michał Pokusa |
| requires_python | None |
| license | MIT License Copyright (c) 2024-2025 Michał Pokusa Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
| keywords |
django
extended
sort
sorted
messages
translations
makemessages
gettext
alias
fuzzy
untranslated
check
header
po
i18n
internationalization
localization
l10n
msgmerge
msguniq
msgattrib
xgettext
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# django-extended-makemessages
<p float="left">
<a href="https://pypi.org/project/django-extended-makemessages/">
<img src="https://img.shields.io/pypi/v/django-extended-makemessages?color=0073b7"/>
</a>
<a href="https://www.djangoproject.com/">
<img src="https://img.shields.io/badge/3.2.x, 4.x.x, 5.x.x-a?style=flat&logo=django&label=django&labelColor=0c4b33&color=616161">
</a>
</p>
Extended version of Django's makemessages command that exposes selected GNU gettext tools options and adds new custom options, which further simplify message detection and translation files management.
- [🎉 Features](#-features)
- [🔌 Instalation](#-instalation)
- [🚀 Overview](#-overview)
- [🧰 Usage](#-usage)
### 🎉 Features
All the options of `makemessages` command are available, plus:
- Sorting messages by `msgid`
- Disabling fuzzy translations
- Detecting message marked with `gettext` functions imported as aliases
- Keeping the header from constantly changing
- Extracting all string
- Removing flags from the output files
- Checking for untranslated messages and outdated `.po` files
- Copying comments from code to `.po` files for context
## 🔌 Instalation
> [!NOTE]
> This package is useful only during development. There is no need to install it in production environments.
1. Install using `pip`:
```bash
$ pip3 install django-extended-makemessages
```
2. Add `'django_extended_makemessages'` to your `INSTALLED_APPS` setting.
```python
INSTALLED_APPS = [
...
'django_extended_makemessages',
]
```
## 🚀 Overview
### Sorting messages by `msgid`
Django's `makemessages` command sorts messages based on location in the source code. This leads to situations where code refactoring can change in the order of messages in the `.po` file. As a result, the version control system shows a lot of changes that do not reflect the actual changes in the code and are confusing.
Below you can see, that despite only adding the `"Delivery"` message, the diff shows more changes.
<img src="https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/sorting-messages-by-msgid-1.png" width="100%"></img>
Using the `--sort-output` option sorts messages by `msgid`. As a result, the diff will show only added or removed messages, since the order in which they appear in the source code does not affect the generated `.po` files.
<img src="https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/sorting-messages-by-msgid-2.png" width="100%"></img>
### Disabling fuzzy translations
By default, similar messages are marked as fuzzy and their translation is inferred from previously translated strings within the same .po file. This often leads to incorrect translations and requires additional manual review.
In the following example, `"Dessert 🍨"` is marked as fuzzy and its translation is inferred from the `"Desert 🐪"` message.
<img src="https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/disabling-fuzzy-translations-1.png" width="100%"></img>
You can use the `--no-fuzzy-matching` option to disable fuzzy matching. This way all messages will have to be translated manually.
<img src="https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/disabling-fuzzy-translations-2.png" width="100%"></img>
### Detecting messages marked with `gettext` functions imported as aliases
It is a common practice to <a href="https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#standard-translation">import functions from `django.utils.translation` module as `_` alias</a>. This works because under the hood, `xgettext` command accepts it as one of the keywords for marking strings for translation.
That is not a problem, if you import only one function. However, if you need to import more than one function, you have to use its full name. This is because `xgettext` does not recognize aliases for functions other than `_`.
<img src="https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/detecting-messages-marked-with-alias-1-1.png" width="100%"></img>
<img src="https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/detecting-messages-marked-with-alias-1-2.png" width="100%"></img>
You can manually add aliases using the `--keyword` option with <a href="https://www.gnu.org/software/gettext/manual/html_node/xgettext-Invocation.html#Input-file-interpretation:~:text=%2D%2Dkeyword%5B%3Dkeywordspec%5D">this syntax</a>. However, a more convenient way is to use the `--detect-aliases` option, which will automatically recognize and add aliases for functions from the `django.utils.translation` module.
By doing so all messages marked with aliases will be detected and added to the `.po` file.
<img src="https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/detecting-messages-marked-with-alias-2-1.png" width="100%"></img>
<img src="https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/detecting-messages-marked-with-alias-2-2.png" width="100%"></img>
### Keeping the header from constantly changing
Using the `--keep-header` argument preserves the header of the `.po` file exactly as it was before the command was run. This is useful when you want to keep the header unchanged, for example, if you do not want to include the `"Report-Msgid-Bugs-To"` or `"POT-Creation-Date"` fields in the `.po` file.
### Extracting all strings
By default, `makemessages` command extracts only strings marked for translation. However, you can use the `--extract-all` option to extract all strings from the source code.
The usefullness of this is questionable, but `xgettext` command provides such option, so it is exposed here as well.
### Removing flags from the output files
Messages with placeholders are marked with flags, e.g. `python-format` or `python-brace-format`. These flags might be useful for translators, but are not required and can make the `.po` file harder to read.
You can use the `--no-flags` option to remove all or the `--no-flag` option to remove specific flags from the output files.
### Checking for untranslated messages and outdated `.po` files
It is not hard to forget about updating translations after changing the source code. To prevent this, you can add a step to your CI/CD pipeline or a helper script, that will do it for you.
Option `--no-untranslated` checks for untranslated messages in the `.po` files. If any untranslated messages are found, the command will fail.
Using `--check` allows you to verify that all translations are properly extracted and included in the `.po` files. It works similarly to the `makemigrations --check`, but for translations. If any `.po` file would be added or changed, the command will fail.
Combining these options can help you keep your translations up to date.
### Copying comments from code to `.po` files for context
When translating messages, the context in which they are used is very important, as it and can greatly affect wording, grammar or even the translation itself.
Functions like `pgettext` accept an `context` parameter, which can be used to <a href="https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#contextual-markers">differentiate between messages with the same `msgid`</a>. However, in many cases, a longer, more detailed comment could provide a clearer description of how the message is used.
Django's `makemessages` command by default only copies comments that start with `"Translators"`:
<img src="https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/copying-comments-from-code-1.png" width="100%"></img>
<img src="https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/copying-comments-from-code-2.png" width="100%"></img>
You can use `--add-comments TAG` to override this, or use `--add-comments` to copy all comments.
## 🧰 Usage
```
usage: manage.py extendedmakemessages [-h] [--locale LOCALE] [--exclude EXCLUDE] [--domain DOMAIN] [--all] [--extension EXTENSIONS]
[--symlinks] [--ignore PATTERN] [--no-default-ignore] [--no-wrap] [--no-location]
[--add-location [{full,file,never}]] [--no-obsolete] [--keep-pot] [--no-fuzzy-matching]
[--add-comments [TAG]] [--extract-all] [--keyword [KEYWORD]] [--force-po] [--indent] [--width WIDTH]
[--sort-output | --sort-by-file] [--detect-aliases] [--keep-header] [--no-flags]
[--no-flag {fuzzy,python-format,python-brace-format,no-python-format,no-python-brace-format}]
[--no-previous] [--no-untranslated] [--check] [--dry-run] [--version] [-v {0,1,2,3}] [--settings SETTINGS]
[--pythonpath PYTHONPATH] [--traceback] [--no-color] [--force-color]
Runs over the entire source tree of the current directory and pulls out all strings marked for translation. It creates (or updates)
a message file in the conf/locale (in the django tree) or locale (for projects and applications) directory.
You must run this command with one of either the --locale, --exclude, or --all options.
In addition to the options available in Django's makemessages command, this command exposes selected
msgmerge/msguniq/msgattrib/xgettext options that make sense for usage in a Django project.
On top of that, this command also includes some custom options, which further simplify managing translations,
but are not part of GNU gettext tools.
options:
-h, --help show this help message and exit
--locale LOCALE, -l LOCALE
Creates or updates the message files for the given locale(s) (e.g. pt_BR). Can be used multiple
times.
--exclude EXCLUDE, -x EXCLUDE
Locales to exclude. Default is none. Can be used multiple times.
--domain DOMAIN, -d DOMAIN
The domain of the message files (default: "django").
--all, -a Updates the message files for all existing locales.
--extension EXTENSIONS, -e EXTENSIONS
The file extension(s) to examine (default: "html,txt,py", or "js" if the domain is "djangojs").
Separate multiple extensions with commas, or use -e multiple times.
--symlinks, -s Follows symlinks to directories when examining source code and templates for translation strings.
--ignore PATTERN, -i PATTERN
Ignore files or directories matching this glob-style pattern. Use multiple times to ignore more.
--no-default-ignore Don't ignore the common glob-style patterns 'CVS', '.*', '*~' and '*.pyc'.
--no-wrap Don't break long message lines into several lines.
--no-location Don't write '#: filename:line' lines.
--add-location [{full,file,never}]
Controls '#: filename:line' lines. If the option is 'full' (the default if not given), the lines
include both file name and line number. If it's 'file', the line number is omitted. If it's
'never', the lines are suppressed (same as --no-location). --add-location requires gettext 0.19 or
newer.
--no-obsolete Remove obsolete message strings.
--keep-pot Keep .pot file after making messages. Useful when debugging.
--no-fuzzy-matching Do not use fuzzy matching when an exact match is not found. This may speed up the operation
considerably.
--add-comments [TAG] Place comment blocks starting with tag and preceding keyword lines in the output file.
Without a tag, the option means to put all comment blocks preceding keyword lines
in the output file.
--extract-all Extract all strings.
--keyword [KEYWORD] Specify keywordspec as an additional keyword to be looked for. Without a keywordspec, the option
means to not use default keywords.
--force-po Always write an output file even if no message is defined.
--indent Write the .po file using indented style.
--width WIDTH Set the output page width. Long strings in the output files will be split across multiple lines in
order to ensure that each line's width (= number of screen columns) is less or equal to the given
number.
--sort-output Generate sorted output.
--sort-by-file Sort output by file location.
--detect-aliases Detect gettext functions aliases in the project and add them as keywords to xgettext command.
--keep-header Keep the header of the .po file exactly the same as it was before the command was run. Do nothing
if the .po file does not exist.
--no-flags Don't write '#, flags' lines.
--no-flag {fuzzy,python-format,python-brace-format,no-python-format,no-python-brace-format}
Remove specific flag from the '#, flags' lines.
--no-previous Don't write '#| previous' lines.
--no-untranslated Exit with a non-zero status if any untranslated messages are found in any .po file.
--check Exit with a non-zero status if any .po file would be added or changed. Implies --dry-run.
--dry-run Restore the .po file to its original state after running the command.
--version Show program's version number and exit.
-v {0,1,2,3}, --verbosity {0,1,2,3}
Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output
--settings SETTINGS The Python path to a settings module, e.g. "myproject.settings.main". If this isn't provided, the
DJANGO_SETTINGS_MODULE environment variable will be used.
--pythonpath PYTHONPATH
A directory to add to the Python path, e.g. "/home/djangoprojects/myproject".
--traceback Raise on CommandError exceptions.
--no-color Don't colorize the command output.
--force-color Force colorization of the command output.
```
Raw data
{
"_id": null,
"home_page": null,
"name": "django-extended-makemessages",
"maintainer": "Micha\u0142 Pokusa",
"docs_url": null,
"requires_python": null,
"maintainer_email": null,
"keywords": "django, extended, sort, sorted, messages, translations, makemessages, gettext, alias, fuzzy, untranslated, check, header, po, i18n, internationalization, localization, l10n, msgmerge, msguniq, msgattrib, xgettext",
"author": "Micha\u0142 Pokusa",
"author_email": null,
"download_url": "https://files.pythonhosted.org/packages/a4/91/c34cbfa82d86e4ad3202d0933bdc06847e1741ba16c19ffc51a05cacd845/django_extended_makemessages-1.4.0.tar.gz",
"platform": null,
"description": "\n# django-extended-makemessages\n\n<p float=\"left\">\n <a href=\"https://pypi.org/project/django-extended-makemessages/\">\n <img src=\"https://img.shields.io/pypi/v/django-extended-makemessages?color=0073b7\"/>\n </a>\n <a href=\"https://www.djangoproject.com/\">\n <img src=\"https://img.shields.io/badge/3.2.x, 4.x.x, 5.x.x-a?style=flat&logo=django&label=django&labelColor=0c4b33&color=616161\">\n </a>\n</p>\n\nExtended version of Django's makemessages command that exposes selected GNU gettext tools options and adds new custom options, which further simplify message detection and translation files management.\n\n- [\ud83c\udf89 Features](#-features)\n- [\ud83d\udd0c Instalation](#-instalation)\n- [\ud83d\ude80 Overview](#-overview)\n- [\ud83e\uddf0 Usage](#-usage)\n\n### \ud83c\udf89 Features\n\nAll the options of `makemessages` command are available, plus:\n\n- Sorting messages by `msgid`\n- Disabling fuzzy translations\n- Detecting message marked with `gettext` functions imported as aliases\n- Keeping the header from constantly changing\n- Extracting all string\n- Removing flags from the output files\n- Checking for untranslated messages and outdated `.po` files\n- Copying comments from code to `.po` files for context\n\n## \ud83d\udd0c Instalation\n\n> [!NOTE]\n> This package is useful only during development. There is no need to install it in production environments.\n\n1. Install using `pip`:\n\n ```bash\n $ pip3 install django-extended-makemessages\n ```\n\n\n2. Add `'django_extended_makemessages'` to your `INSTALLED_APPS` setting.\n ```python\n INSTALLED_APPS = [\n ...\n 'django_extended_makemessages',\n ]\n ```\n\n## \ud83d\ude80 Overview\n\n### Sorting messages by `msgid`\n\nDjango's `makemessages` command sorts messages based on location in the source code. This leads to situations where code refactoring can change in the order of messages in the `.po` file. As a result, the version control system shows a lot of changes that do not reflect the actual changes in the code and are confusing.\n\nBelow you can see, that despite only adding the `\"Delivery\"` message, the diff shows more changes.\n\n<img src=\"https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/sorting-messages-by-msgid-1.png\" width=\"100%\"></img>\n\nUsing the `--sort-output` option sorts messages by `msgid`. As a result, the diff will show only added or removed messages, since the order in which they appear in the source code does not affect the generated `.po` files.\n\n<img src=\"https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/sorting-messages-by-msgid-2.png\" width=\"100%\"></img>\n\n### Disabling fuzzy translations\n\nBy default, similar messages are marked as fuzzy and their translation is inferred from previously translated strings within the same .po file. This often leads to incorrect translations and requires additional manual review.\n\nIn the following example, `\"Dessert \ud83c\udf68\"` is marked as fuzzy and its translation is inferred from the `\"Desert \ud83d\udc2a\"` message.\n\n<img src=\"https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/disabling-fuzzy-translations-1.png\" width=\"100%\"></img>\n\nYou can use the `--no-fuzzy-matching` option to disable fuzzy matching. This way all messages will have to be translated manually.\n\n<img src=\"https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/disabling-fuzzy-translations-2.png\" width=\"100%\"></img>\n\n\n### Detecting messages marked with `gettext` functions imported as aliases\n\nIt is a common practice to <a href=\"https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#standard-translation\">import functions from `django.utils.translation` module as `_` alias</a>. This works because under the hood, `xgettext` command accepts it as one of the keywords for marking strings for translation.\n\nThat is not a problem, if you import only one function. However, if you need to import more than one function, you have to use its full name. This is because `xgettext` does not recognize aliases for functions other than `_`.\n\n<img src=\"https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/detecting-messages-marked-with-alias-1-1.png\" width=\"100%\"></img>\n\n<img src=\"https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/detecting-messages-marked-with-alias-1-2.png\" width=\"100%\"></img>\n\nYou can manually add aliases using the `--keyword` option with <a href=\"https://www.gnu.org/software/gettext/manual/html_node/xgettext-Invocation.html#Input-file-interpretation:~:text=%2D%2Dkeyword%5B%3Dkeywordspec%5D\">this syntax</a>. However, a more convenient way is to use the `--detect-aliases` option, which will automatically recognize and add aliases for functions from the `django.utils.translation` module.\n\nBy doing so all messages marked with aliases will be detected and added to the `.po` file.\n\n<img src=\"https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/detecting-messages-marked-with-alias-2-1.png\" width=\"100%\"></img>\n\n<img src=\"https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/detecting-messages-marked-with-alias-2-2.png\" width=\"100%\"></img>\n\n### Keeping the header from constantly changing\n\nUsing the `--keep-header` argument preserves the header of the `.po` file exactly as it was before the command was run. This is useful when you want to keep the header unchanged, for example, if you do not want to include the `\"Report-Msgid-Bugs-To\"` or `\"POT-Creation-Date\"` fields in the `.po` file.\n\n### Extracting all strings\n\nBy default, `makemessages` command extracts only strings marked for translation. However, you can use the `--extract-all` option to extract all strings from the source code.\n\nThe usefullness of this is questionable, but `xgettext` command provides such option, so it is exposed here as well.\n\n### Removing flags from the output files\n\nMessages with placeholders are marked with flags, e.g. `python-format` or `python-brace-format`. These flags might be useful for translators, but are not required and can make the `.po` file harder to read.\n\nYou can use the `--no-flags` option to remove all or the `--no-flag` option to remove specific flags from the output files.\n\n### Checking for untranslated messages and outdated `.po` files\n\nIt is not hard to forget about updating translations after changing the source code. To prevent this, you can add a step to your CI/CD pipeline or a helper script, that will do it for you.\n\nOption `--no-untranslated` checks for untranslated messages in the `.po` files. If any untranslated messages are found, the command will fail.\n\nUsing `--check` allows you to verify that all translations are properly extracted and included in the `.po` files. It works similarly to the `makemigrations --check`, but for translations. If any `.po` file would be added or changed, the command will fail.\n\nCombining these options can help you keep your translations up to date.\n\n### Copying comments from code to `.po` files for context\n\nWhen translating messages, the context in which they are used is very important, as it and can greatly affect wording, grammar or even the translation itself.\n\nFunctions like `pgettext` accept an `context` parameter, which can be used to <a href=\"https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#contextual-markers\">differentiate between messages with the same `msgid`</a>. However, in many cases, a longer, more detailed comment could provide a clearer description of how the message is used.\n\nDjango's `makemessages` command by default only copies comments that start with `\"Translators\"`:\n\n<img src=\"https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/copying-comments-from-code-1.png\" width=\"100%\"></img>\n\n<img src=\"https://raw.githubusercontent.com/michalpokusa/django-extended-makemessages/main/resources/copying-comments-from-code-2.png\" width=\"100%\"></img>\n\nYou can use `--add-comments TAG` to override this, or use `--add-comments` to copy all comments.\n\n## \ud83e\uddf0 Usage\n\n```\nusage: manage.py extendedmakemessages [-h] [--locale LOCALE] [--exclude EXCLUDE] [--domain DOMAIN] [--all] [--extension EXTENSIONS]\n [--symlinks] [--ignore PATTERN] [--no-default-ignore] [--no-wrap] [--no-location]\n [--add-location [{full,file,never}]] [--no-obsolete] [--keep-pot] [--no-fuzzy-matching]\n [--add-comments [TAG]] [--extract-all] [--keyword [KEYWORD]] [--force-po] [--indent] [--width WIDTH]\n [--sort-output | --sort-by-file] [--detect-aliases] [--keep-header] [--no-flags]\n [--no-flag {fuzzy,python-format,python-brace-format,no-python-format,no-python-brace-format}]\n [--no-previous] [--no-untranslated] [--check] [--dry-run] [--version] [-v {0,1,2,3}] [--settings SETTINGS]\n [--pythonpath PYTHONPATH] [--traceback] [--no-color] [--force-color]\n\nRuns over the entire source tree of the current directory and pulls out all strings marked for translation. It creates (or updates)\na message file in the conf/locale (in the django tree) or locale (for projects and applications) directory.\n\nYou must run this command with one of either the --locale, --exclude, or --all options.\n\nIn addition to the options available in Django's makemessages command, this command exposes selected\nmsgmerge/msguniq/msgattrib/xgettext options that make sense for usage in a Django project.\n\nOn top of that, this command also includes some custom options, which further simplify managing translations,\nbut are not part of GNU gettext tools.\n\noptions:\n -h, --help show this help message and exit\n --locale LOCALE, -l LOCALE\n Creates or updates the message files for the given locale(s) (e.g. pt_BR). Can be used multiple\n times.\n --exclude EXCLUDE, -x EXCLUDE\n Locales to exclude. Default is none. Can be used multiple times.\n --domain DOMAIN, -d DOMAIN\n The domain of the message files (default: \"django\").\n --all, -a Updates the message files for all existing locales.\n --extension EXTENSIONS, -e EXTENSIONS\n The file extension(s) to examine (default: \"html,txt,py\", or \"js\" if the domain is \"djangojs\").\n Separate multiple extensions with commas, or use -e multiple times.\n --symlinks, -s Follows symlinks to directories when examining source code and templates for translation strings.\n --ignore PATTERN, -i PATTERN\n Ignore files or directories matching this glob-style pattern. Use multiple times to ignore more.\n --no-default-ignore Don't ignore the common glob-style patterns 'CVS', '.*', '*~' and '*.pyc'.\n --no-wrap Don't break long message lines into several lines.\n --no-location Don't write '#: filename:line' lines.\n --add-location [{full,file,never}]\n Controls '#: filename:line' lines. If the option is 'full' (the default if not given), the lines\n include both file name and line number. If it's 'file', the line number is omitted. If it's\n 'never', the lines are suppressed (same as --no-location). --add-location requires gettext 0.19 or\n newer.\n --no-obsolete Remove obsolete message strings.\n --keep-pot Keep .pot file after making messages. Useful when debugging.\n --no-fuzzy-matching Do not use fuzzy matching when an exact match is not found. This may speed up the operation\n considerably.\n --add-comments [TAG] Place comment blocks starting with tag and preceding keyword lines in the output file.\n Without a tag, the option means to put all comment blocks preceding keyword lines\n in the output file.\n --extract-all Extract all strings.\n --keyword [KEYWORD] Specify keywordspec as an additional keyword to be looked for. Without a keywordspec, the option\n means to not use default keywords.\n --force-po Always write an output file even if no message is defined.\n --indent Write the .po file using indented style.\n --width WIDTH Set the output page width. Long strings in the output files will be split across multiple lines in\n order to ensure that each line's width (= number of screen columns) is less or equal to the given\n number.\n --sort-output Generate sorted output.\n --sort-by-file Sort output by file location.\n --detect-aliases Detect gettext functions aliases in the project and add them as keywords to xgettext command.\n --keep-header Keep the header of the .po file exactly the same as it was before the command was run. Do nothing\n if the .po file does not exist.\n --no-flags Don't write '#, flags' lines.\n --no-flag {fuzzy,python-format,python-brace-format,no-python-format,no-python-brace-format}\n Remove specific flag from the '#, flags' lines.\n --no-previous Don't write '#| previous' lines.\n --no-untranslated Exit with a non-zero status if any untranslated messages are found in any .po file.\n --check Exit with a non-zero status if any .po file would be added or changed. Implies --dry-run.\n --dry-run Restore the .po file to its original state after running the command.\n --version Show program's version number and exit.\n -v {0,1,2,3}, --verbosity {0,1,2,3}\n Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output\n --settings SETTINGS The Python path to a settings module, e.g. \"myproject.settings.main\". If this isn't provided, the\n DJANGO_SETTINGS_MODULE environment variable will be used.\n --pythonpath PYTHONPATH\n A directory to add to the Python path, e.g. \"/home/djangoprojects/myproject\".\n --traceback Raise on CommandError exceptions.\n --no-color Don't colorize the command output.\n --force-color Force colorization of the command output.\n```\n",
"bugtrack_url": null,
"license": "MIT License Copyright (c) 2024-2025 Micha\u0142 Pokusa Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ",
"summary": "Extended version of Django's makemessages command that exposes selected GNU gettext tools options and adds new custom options, which further simplify message detection and translation files management.",
"version": "1.4.0",
"project_urls": {
"Changelog": "https://github.com/michalpokusa/django-extended-makemessages/blob/main/CHANGELOG.md",
"Repository": "https://github.com/michalpokusa/django-extended-makemessages"
},
"split_keywords": [
"django",
" extended",
" sort",
" sorted",
" messages",
" translations",
" makemessages",
" gettext",
" alias",
" fuzzy",
" untranslated",
" check",
" header",
" po",
" i18n",
" internationalization",
" localization",
" l10n",
" msgmerge",
" msguniq",
" msgattrib",
" xgettext"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "a46f39d1fac648b82b88267ee5edf9a98cb5fc621cb745cd720903f2bea7f166",
"md5": "cba3fb325a28a866283958ee5a26e7cb",
"sha256": "9274251ebeb10132dcc0d0c62dbce1b42b6a1462afc77b4c91cc5cbbb33369bb"
},
"downloads": -1,
"filename": "django_extended_makemessages-1.4.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "cba3fb325a28a866283958ee5a26e7cb",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": null,
"size": 12526,
"upload_time": "2025-01-13T14:39:25",
"upload_time_iso_8601": "2025-01-13T14:39:25.780749Z",
"url": "https://files.pythonhosted.org/packages/a4/6f/39d1fac648b82b88267ee5edf9a98cb5fc621cb745cd720903f2bea7f166/django_extended_makemessages-1.4.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "a491c34cbfa82d86e4ad3202d0933bdc06847e1741ba16c19ffc51a05cacd845",
"md5": "0fdba3218a21aa9b260a872036c40216",
"sha256": "1ca11866b53d2b8d4c1b6f272849499aa536ee1566282993844b3f9ae8cc1935"
},
"downloads": -1,
"filename": "django_extended_makemessages-1.4.0.tar.gz",
"has_sig": false,
"md5_digest": "0fdba3218a21aa9b260a872036c40216",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 185504,
"upload_time": "2025-01-13T14:39:27",
"upload_time_iso_8601": "2025-01-13T14:39:27.878731Z",
"url": "https://files.pythonhosted.org/packages/a4/91/c34cbfa82d86e4ad3202d0933bdc06847e1741ba16c19ffc51a05cacd845/django_extended_makemessages-1.4.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-01-13 14:39:27",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "michalpokusa",
"github_project": "django-extended-makemessages",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "django-extended-makemessages"
}
