[lokalize] [Bug 342614] Improve/include cooperation with Pology

2018-09-29 Thread Simon Depiets
https://bugs.kde.org/show_bug.cgi?id=342614

Simon Depiets  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://commits.kde.org/lok
   ||alize/52b94d0b6c41cb7e77ef6
   ||4fcf9b32e403522b436

--- Comment #3 from Simon Depiets  ---
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-1src/CMakeLists.txt
M  +45   -8src/editortab.cpp
M  +7-0src/editortab.h
M  +2-1src/editorui.rc
M  +4-4src/filesearch/filesearchtab.cpp
M  +9-9src/lokalizemainwindow.cpp
M  +4-4src/msgctxtview.cpp
M  +11   -0src/prefs/lokalize.kcfg
M  +7-6src/prefs/prefs.cpp
A  +83   -0src/prefs/prefs_pology.ui
D  +0-64   src/project/prefs_project_pology.ui
M  +0-6src/project/projectlocal.kcfg
M  +53   -5src/project/projecttab.cpp
M  +7-0src/project/projecttab.h
M  +5-5src/tm/tmtab.cpp

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

-- 
You are receiving this mail because:
You are watching all bug changes.

[lokalize] [Bug 342614] Improve/include cooperation with Pology

2018-07-23 Thread Simon Depiets
https://bugs.kde.org/show_bug.cgi?id=342614

Simon Depiets  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

-- 
You are receiving this mail because:
You are watching all bug changes.

[lokalize] [Bug 342614] Improve/include cooperation with Pology

2018-07-23 Thread Simon Depiets
https://bugs.kde.org/show_bug.cgi?id=342614

Simon Depiets  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.

[lokalize] [Bug 342614] Improve/include cooperation with Pology

2018-07-23 Thread Simon Depiets
https://bugs.kde.org/show_bug.cgi?id=342614

Simon Depiets  changed:

   What|Removed |Added

 CC||sdepi...@gmail.com
   Assignee|sha...@ukr.net  |sdepi...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[lokalize] [Bug 342614] Improve/include cooperation with Pology

2018-07-21 Thread Vit Pelcak
https://bugs.kde.org/show_bug.cgi?id=342614

--- Comment #2 from Vit Pelcak  ---
Hello.

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

However spellcheck would be also nice to have.

-- 
You are receiving this mail because:
You are watching all bug changes.

[lokalize] [Bug 342614] Improve/include cooperation with Pology

2018-05-27 Thread Adrián Chaves
https://bugs.kde.org/show_bug.cgi?id=342614

Adrián Chaves (Gallaecio)  changed:

   What|Removed |Added

 CC||adr...@chaves.io

--- Comment #1 from Adrián Chaves (Gallaecio)  ---
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?).

-- 
You are receiving this mail because:
You are watching all bug changes.