Bug 342614

Summary:	Improve/include cooperation with Pology
Product:	[Applications] lokalize	Reporter:	Vit Pelcak <vit>
Component:	general	Assignee:	Simon Depiets <sdepiets>
Status:	RESOLVED FIXED
Severity:	wishlist	CC:	adrian, sdepiets
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:	https://commits.kde.org/lokalize/52b94d0b6c41cb7e77ef64fcf9b32e403522b436	Version Fixed In:
Sentry Crash Report:

Description Vit Pelcak 2015-01-08 08:54:41 UTC

Pology is cool CLI tool for translation of KDE.
I think it would be vary nice thing if Lokalize was able to use its abilities better.

There are plenty features which would be very nice. For example spellcheck including whitelisting, pomerge, poscatter, sieve ... see http://pology.nedohodnik.net//doc/user/en_US/index-mono.html

Reproducible: Always

Comment 1 Adrián Chaves (Gallaecio) 2018-05-27 11:21:39 UTC

I feel this request is too broad. I believe it would be better if you suggested the integration of specific pology tools, with separate reports per tool, and if you would describe how you see those integrations working (i.e. how would Lokalize change as a result?).

Comment 2 Vit Pelcak 2018-07-22 06:16:17 UTC

Hello.

I would appreciate at least the possibility for syntax checks pology can do. 

However spellcheck would be also nice to have.

Comment 3 Simon Depiets 2018-09-29 11:02:30 UTC

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 342615, bug 65061, 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