pology checks are now integrated with Lokalize: http://l10n.kde.org/docs/translation-howto/check-gui.html

pure msgfmt checks are to come (as a scripts)...

Missing automatic syntax checks and "goto error" functionality makes QA hard in lokalize in comparison to KBabel. It's good that KBabel is still running :)
Just adding myself to CC list.

*** Bug 194770 has been marked as a duplicate of this bug. ***

Yeah, it would be an important feature definitely that so much translators said to me earlier, even if not with an automatical operation, but with a selection e.g.

Someone is working on this feature? It's very important.

Thanks,
Sweta

(In reply to comment #1)
> pology checks are now integrated with Lokalize:
> http://l10n.kde.org/docs/translation-howto/check-gui.html
> 
> pure msgfmt checks are to come (as a scripts)...

Is this possible with Lokalize ?
I read this :
"Some specialized programs like Lokalize will assist you with this. Lokalize even contains an automated syntax check (among others) that saves you a lot of the work."
But i dont see Lokalize to do any checks when saving the file

I sorely miss the validation checks that kbabel does. It forces me to edit with lokalize, save, then load in kbabel and verify the file and save it - thank goodness kde3/kbabel is still available in openSUSE.

Yes, of course, I could verify with my own scripts, but kbabel places the editor automatically on each wrong string and shift-pgdn positions me on the next, which is highly convenient.

Any idea if/when the lokalize team plan to add that feature?

*** Bug 248125 has been marked as a duplicate of this bug. ***

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 65061
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

Hi,

I think automatic msgfmt on saving will be simpler than having to install pology, configure and it run every time you translate something.

Maybe finishing this:
https://phabricator.kde.org/D13521

Regards