generate: Be smarter when no generate_merge setting is set
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
By default, i18n_tool extract creates django-partial.po and djangojs-partial.po.
But by default, i18n_tool generate does nothing with them. There should be a default config for generate_merge, like so:
generate_merge:
django.po:
- django-partial.po
djangojs.po:
- djangojs-partial.po
I don't know whether there should be a default setting for make.po and underscore.po. Those are already in reasonably-named files. But leaving files named 'partial' around seems bad. Especially when the rest of the tooling assumes you're merging into the final versions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the i18n_tool extract and generate entry points and the generate_merge configuration handling. Verify how django-partial.po and djangojs-partial.po are produced, then define the default merge behavior and decide whether make.po and underscore.po belong in it. Done means generate handles the partial catalogs by default without requiring explicit configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- internationalization, localization
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100