Opened 3 years ago
Closed 2 years ago
#5943 closed enhancement (wontfix)
When you create a glossary in a project, it stays for one set.
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Translate Site & Plugins | Keywords: | |
| Cc: |
Description
When you create a glossary inside a project (not the locale glossary), it stays in that sub project.
EG: I created one for a project in the stable set, and it didn't show up for the dev set.
Why do project glossaries work in that way? That means it's possible that translations are summited in the other sets with other translations... And not only that, you can create conflicting glossaries.
I think it would help us being consistent in a project, when a project glossary is for ALL sets and not for just one set.
And maybe have an option where you can choose for which sets it's shown, if people want to filter it for one or more sets and not all?
Note: See
TracTickets for help on using
tickets.
Project glossaries are linked to a translation set and apply to the project of the translation set and any sub-projects. Since plugin projects have no parent project with translations it's not possible to have a glossary there. That's a limitation of GlotPress which can't be changed at the moment.