sphinx-doc / sphinx-doc/sphinx
Be able to share assets between translations.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
In the case of Nextcloud, the documentation is shipped with the software. And if we have translations, it means assets are duplicated, increasing the package size.
Describe the solution you'd like
It would improve the package size if the assets would be shared between the various translations.
As seen here
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
No files, tests, or entry points are named. Start by locating Sphinx's translation and asset packaging paths, then determine how assets are currently duplicated; done means translated outputs share common assets while preserving package correctness and reducing duplication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100