Add glossary with all the languages, but without strings

[inson1]

Describe the problem

Its used for "notes" (glossary) for communication with other people who are going to translate it

Describe the proposed solution

.

Alternatives considered

.

Importance

nice to have

[navorite]

well there is already the description key in the messages.json which describes the key to be translated so no need for glossary, and you can find it in the UI of weblate next to the string to be translated.

[inson1]

@navorite yes, but Glossary is also for translation documentation in one language - if there is same word in different strings - you should always translated x as y. It is just standard, at least what I have seen.

[navorite]

@navorite yes, but Glossary is also for translation documentation in one language - if there is same word in different strings - you should always translated x as y. It is just standart, at least what I have seen.

But how would that bring any benefit? It just creates an unnecessary extra layer of complexity.

[inson1]

@navorite sorry I dont get the complexity. Glossary is always shown on right side (if some word from Glossary is detected in that string)

[navorite]

@navorite sorry I dont get the complexity. Glossary is always shown on right side (if some word from Glossary is detected in that string)

What would you add inside it? What things need to be clarified?

[inson1]

@navorite If there is one word used more than once, people can translate it differently. That is the main point of Glossary. And its just standard, look at others weblate projects

[navorite]

@navorite If there is one word used more than once, people can translate it differently. That is the main point of Glossary. And its just standard, look at others weblate projects

The question still stands, what terms do we need to add inside it?

[inson1]

@navorite none, translators will do it, every language is different

[navorite]

74 suggested otherwise though and you agreed with it

[inson1]

@navorite no, #74 was about main directory being glossary, this issue is about adding second directory that is glossary For example Bleachbit - has 2 directories - main where are the translations and other one that is the glossary. OpenCalc - google play/F-droid translations, app translations, glossary Slicer

[navorite]

Oh, thanks for clarifying. I think I understand you now. Can you check if this is the correct setup you want?

[inson1]

@navorite glossary is done, but I think you set review mode (idk how to call it) on all languages? Its good for english. I meant this, but review mode looks maybe better. this

[inson1]

@navorite + strings for edit disappeared + there is some error

[navorite]

@navorite glossary is done, but I think you set review mode (idk how to call it) on all languages? Its good for english. I meant this, but review mode looks maybe better. Or what is the blue color? this

It's only enabled for source strings (English in this case), and since you are trying to add a glossary term to English it refuses. I can set up access for you I think.

[inson1]

@navorite no, I didnt meant that. Glossaries are done. Just there 2 maybe 3 problems :/ I add them to their issues.

[inson1]

@navorite second image was just example how I meant to solve the issue about read only strings in english, first image was text in translated strings in czech