Nested projects or project grouping

[lurdan]

The problem: Weblate can't(may not) handle large project, including multiple independent documents which consists of multiple po files. These subprojects can share glossaries, so it had better create as included in one project.

(ex. I want to set up debian documentation project translation project for japanese. https://github.com/lurdan/trans-ddp )

[nijel]

While implementing related feature I've come to this issue. So there are basically two issues here:

• Adding more structure than just project/component. This can be done using component lists and can be used both to split up projects or to group components in several projects together.
• Having shared glossaries, this is covered by https://github.com/WeblateOrg/weblate/issues/1158

For the setup you describe, it is probably best to use separate projects for independent documents and group them using component lists. The only missing piece is shared glossary.

[nijel]

It might be actually useful to provide tree like a structure within a project. That would not complicate things for smaller projects, but allow complex structure for bigger ones.

[nijel]

Typical example which would utilize some kind of nesting is LibreOffice.

What would be probably useful to have here is: LibreOffice Help / master / Calc / Guide

[Justman10000]

@nijel

Are you working on it? This damn issue existed for 9 years! Only 5 years later came an answer... I don't know...

[nijel]

We have even older issues and we welcome contributions!

I expect we get to this one this year. We're a small team and need to prioritize work.

[m-aciek]

Another use case to consider: Python docs are being translated for all stable releases (e.g. 3.10, 3.9, 3.8 and 3.7 currently). Subprojects or "organization" wrapper for projects plus shared glossary and default translation memory propagation (already can be achieved, but not by default AFAIK) would work for them.

[github-actions[bot]]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.