Bug 65061

Glossary support with automatic checking against the glossary, right?

Umm, yes, if I understood correctly :-) 
Better yet: 2nd glossary support with automatic checking against the real glossary. 

OK, or a glossary including wrong cases to be avoided.

i expect to implement this QA feature as part of KAider scripting framework in several month (don't have time right time because of university)

moving to KAider

A workaround:
checkout trunk/l10n-kde4/l10n-kde4/de/internal/
install python-qt3 and python-kde3

run:
path/to/checkwordtranslation.py path/to/l10n-kde4/fi [bB]utton Painike
and edit all messages with [bB]utton in msgid and not "Painike" in msgstr
in a python-kde3-dialog

I'm going to implement saving TM searches (i.e. saving search options: shell-like expressions for source, target, inversion bools for source and target independently, filemasks) and capability of running them all or their selection at once.

Then I'll add feature to generate list of searches based on a glossary (including falseFriends to-be-added-to-lokalize-tbx-editor), which can then be edited. As always it will be shareable and I'll encourage putting such qa-lists into lang dirs in svn repository.

Advantages of this are: high-level interface for translators, speed (we work with database instead of parsing po-files), and it will be format-independant (remember i'm dreaming of creating usable XLIFF editor ;)

The check_rules posieve in pology can be used for this. It supports Lokalize, so I don’t think it’s necessary duplicating the functionality in Lokalize.

Git commit 52b94d0b6c41cb7e77ef64fcf9b32e403522b436 by Simon Depiets.
Committed on 29/09/2018 at 11:02.
Pushed by sdepiets into branch 'master'.

Add new ways to launch pology on file(s)

Summary:
Pology is a great tool but is not easily accessible from Lokalize currently, you need to launch a command line or configure a script, which is cumbersome and complicated in user space. After adding a line by line feature a few weeks ago, this review focuses on the file level :

- Launch the Pology "-s lokalize" command on file, files or folders from the Project Overview : this will open problematic messages in different tabs.
{F6285626}
- Launch the Pology "-s lokalize" command from within the file (Ctrl+Alt+P) : this will filter on problematic messages directly from within the file.
{F6285627}

The next step I see would be displaying pology statistics in the TM file, I'm open to your ideas for a better integration. I'm also counting on you to pass the message to your respective communities and update their documentation for the usage of pology.

As the agreement seems to be that syntax checks shall be handle externally, I will close the following bugs :
Related: bug 342614, bug 342615, bug 198872
GUI:

Reviewers: #localization, aacid, adrianchavesfernandez, huftis, mlaurent

Reviewed By: mlaurent

Subscribers: mlaurent

Tags: #localization

Differential Revision: https://phabricator.kde.org/D15759

M  +1    -1    src/CMakeLists.txt
M  +45   -8    src/editortab.cpp
M  +7    -0    src/editortab.h
M  +2    -1    src/editorui.rc
M  +4    -4    src/filesearch/filesearchtab.cpp
M  +9    -9    src/lokalizemainwindow.cpp
M  +4    -4    src/msgctxtview.cpp
M  +11   -0    src/prefs/lokalize.kcfg
M  +7    -6    src/prefs/prefs.cpp
A  +83   -0    src/prefs/prefs_pology.ui
D  +0    -64   src/project/prefs_project_pology.ui
M  +0    -6    src/project/projectlocal.kcfg
M  +53   -5    src/project/projecttab.cpp
M  +7    -0    src/project/projecttab.h
M  +5    -5    src/tm/tmtab.cpp

https://commits.kde.org/lokalize/52b94d0b6c41cb7e77ef64fcf9b32e403522b436