Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Locale Glossaries (Global glossaries across projects) #227
Currently the glossaries are assigned to a translation set of a project. But GlotPress also inherits a glossary from a closest parent project when there isn't one existing for the current translation set, see .
I don't think that GP should loose the ability to have glossaries per projects, I'd rather have one global glossary per locale which is used as a base for each project.
Clearly, one giant universal glossary will not do.
Something in between is called for.
A hierarchy of glossaries:
Details, practical needs, examples
Several English terms have multiple translation suggestions. This is due to different translation needed in different context. Therefore, to automatically apply a translation it must have a concise general glossary or/and automatic translations must present multiple possible translations, maybe formatted in a coherent way, for example: item -> [kohde, nimike, tuote, kohta, merkintä, jne].
changed the title from
Global glossaries across projects
Locale Glossaries (Global glossaries across projects)
Oct 4, 2016
This is a summary of today's chat: https://wordpress.slack.com/archives/glotpress/p1475600842000583