Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Nested projects or project grouping #263

Closed
lurdan opened this issue Apr 30, 2013 · 6 comments · Fixed by #9731
Closed

Nested projects or project grouping #263

lurdan opened this issue Apr 30, 2013 · 6 comments · Fixed by #9731
Assignees
@nijel
Labels
enhancement Adding or requesting a new feature.
Milestone
5.0

Comments

@lurdan
Copy link
Contributor

lurdan commented Apr 30, 2013 •
edited by nijel
Loading

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 )
@rvanlaak rvanlaak mentioned this issue Mar 24, 2016
Closed
@nijel
Copy link
Member

nijel commented Mar 20, 2018

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 global glossary #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
Copy link
Member

nijel commented Sep 5, 2019

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 nijel removed the undecided These features might not be implemented. Can be prioritized by sponsorship. label Nov 1, 2019
@nijel
Copy link
Member

nijel commented Nov 1, 2019

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

@nijel nijel mentioned this issue Dec 13, 2019
Open
@nijel nijel changed the title Nested subprojects or subproject grouping in one project Nested projects or project grouping Feb 25, 2020
@nijel nijel mentioned this issue Mar 6, 2022
Closed
1 task
@nijel nijel mentioned this issue Apr 29, 2022
Open
@nijel
Copy link
Member

nijel commented Jun 10, 2022

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
Copy link
Contributor

m-aciek commented Oct 19, 2022

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.

@m-aciek m-aciek mentioned this issue Oct 19, 2022
Open
2 tasks
weblate pushed a commit that referenced this issue Feb 21, 2023
@Blinue
Merge pull request #263 from 0x4E69676874466F78/main
b5c04db 
New Russian translation
@nijel nijel added this to the 4.19 milestone Apr 13, 2023
@nijel nijel mentioned this issue Jul 3, 2023
Closed
@nijel nijel self-assigned this Aug 2, 2023
@nijel nijel mentioned this issue Aug 7, 2023
Merged
5 tasks
nijel added a commit that referenced this issue Aug 10, 2023
@nijel
urls: Generic object path parsing
51f5b40 
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).

Changed widgets URLs to better fit in the new structure. Redirects for
old ones are in place.
This was referenced Aug 11, 2023
Merged
Merged
nijel added a commit that referenced this issue Aug 16, 2023
@nijel
templates: use shared breadcrumb renderer
02ee900 
This will make projectlanguge and category work consistently at all
levels.

Issue #263
nijel added a commit that referenced this issue Aug 24, 2023
@nijel
models: add component categorization
8c2c88b 
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263
@github-actions
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nijel nijel

Labels
enhancement Adding or requesting a new feature.
Projects
None yet
Milestone
5.0
Development

Successfully merging a pull request may close this issue.

Add component categorization nijel/weblate
3 participants
@lurdan @nijel @m-aciek