Description of problem: It is quite often that same Glossary term carries different meaning in different context. For example, "Never" in NetworkManager connection list means "not yet" (in Chinese, 尚未), but in xscreensaver, as shown in certain precautions had to be taken, among them that xscreensaver never runs as root. "Never" should be translated with "never ever" (in Chinese, 永不) Even if they carry the same meaning, they may have different translation conventions amongst projects. Like menu item "Help" are translated differently between GNOME and KDE. So to translators, Context (or project) shows them the project convention; while Description shows them the definition of the term. Version-Release number of selected component (if applicable): 3.6.0 Expected results: After search terms input, Glossary UI should be able to show the context (or project) and description of the corresponding glossary. Additional info:
From looking at how translators use glossaries in other tools and how they basically ignore our glossary feature, I think we need to totally rethink how we do glossaries. My first thought is we should have project and user based glossaries that can be turned on/off in the editor.
(In reply to Luke Brooker from comment #1) > From looking at how translators use glossaries in other tools and how they > basically ignore our glossary feature, I think we need to totally rethink > how we do glossaries. True. They don't use our glossary feature because: 1. We don't provide project information and glossary definition. 2. Our glossary panel is too small for most of the translators. And spreadsheet program is good enough to give translators an overview of a glossary. > My first thought is we should have project and user based glossaries that > can be turned on/off in the editor. Given the usage pattern of translators, we need a tab or even maximum window to show glossary. We may also offer auto complete in cell editor.
Yep. This is all stuff I would like to improve on in the new editor. But the main reason, to me, seems to be that they can't create/edit their own glossaries or even project based glossaries. Aren't they just admin based at the moment?
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-170