Whoever is interested, may download from:

http://www.bononiadocta.it/Lazarus/pohelper.zip

the version 0.1 of PoHelper, a tool I've developed to help me in translation maintenance.

I've put there the features I felt necessary for routine translation work, which were not avialable elsewhere.

It provides:

A quick verification of the state of all translations (Translated, Untranslated, Fuzzy and format argument errors). Items with format argument errors are marked as Fuzzy.

A graphical representation of all the translations requiring maintenance, for a given language, in a given directory tree.

Missing translations are represented with a yellow full pie, others are represented with a pie partitioned for translated/untranslated/fuzzy entries and a question mark for format argument errors (the same as PoChecker new graphical display, available in trunk). Optionally all translations can be seen (including those 100% translated), or missing translations can be hidden.

Opening a translation (by clicking on it) with a choice of two configurable external editors (left-click/right-click). I use both Virtaal and Poedit, depending on needs, so I made it that way.

Creating a new empty translation from template, for missing translations, and then opening it in the selected editor.

Performing a clean-up of translations, by removing PreviousId from non-Fuzzy items, and then saving all the translations which have been somehow modified in the session (added/removed Fuzzy flags, removed PreviousId, etc).

A few more things to come.

It should be complementary to PoChecker as it doesn't provide all the statistics and more exhaustive tests of PoChecker, but does provide utilities which are outside the scope of PoChecker.

The human interface should be self-explaining. If not, just ask.

If found useful, it could be added to Lazarus Tools, or to Lazarus Components (it could be integrated in the IDE). If not, I'll just keep it for myself.

I'll be thankful to whoever will test it and report bugs, suggest improvements, or asks for useful features.

Giuliano

13.10.2014 16:31, Giuliano Colla ?????:

[...]

Cleanup functions break e.g. lazaruside.ru.po. It looks corrupted in PoEdit. I didn't have time to investigate further.

IMO all this should be integrated into PoChecker.

Il 14/10/2014 00:39, Maxim Ganetsky ha scritto:

Cleanup functions break e.g. lazaruside.ru.po. It looks corrupted in PoEdit. I didn't have time to investigate further.

Yes, you're right. I've been too bold. There are two issues which didn't come out in my simpler tests: multiline strings aren't properly rewritten, and / are doubled. I'll need some time to understand why and fix. I merged Translation unit with Bart's SimplePoFiles, and it would appear that I didn't adjust all the incompatibilities.

IMO all this should be integrated into PoChecker.

The final goal would be to have those function added to the LCL Translations unit. Then it'll be up to Bart to decide if he wants to take advantage of them or not.

Giuliano

Il 14/10/2014 11:01, Giuliano Colla ha scritto:

[...] and / are doubled.

Sorry, I meant *\* are doubled.

Giuliano

Maxim Ganetsky wrote

IMO all this should be integrated into PoChecker.

I disagree, as I have explained now many times before.

The added functionality that is in SimplePoFiles unit could/should however preferrably be integrated into Translations unit.

Bart

Il 14/10/2014 11:01, Giuliano Colla ha scritto:

Fixed. Now CleanUp removes around 900 stale PreviousId from lazaruside.ru.po, without corrupting it.

Please test.

Giuliano

14.10.2014 21:50, Giuliano Colla ?????:

Where to get it?

Il 14/10/2014 23:31, Maxim Ganetsky ha scritto:

You're right, I forgot to say. Same place. i.e.:

http://www.bononiadocta.it/Lazarus/pohelper.zip

Giuliano

Hi!

Here is the Hungarian translation for pohelper!
However I did not test pohelper yet... :)

2014-10-14 23:45 keltez?ssel, Giuliano Colla ?rta:

Il 15/10/2014 11:05, P?ter G?bor ha scritto:

Hi! Here is the Hungarian translation for pohelper! However I did not test pohelper yet... :)

Thanks a lot.
Let me know if you find some bugs, or would like to add/change some features.

Giuliano

Hi!

Tips (mostly for the GUI):

- Setting up an external editor would be better to define the command line instead of a simple FileOpen form (or combined). In my case poedit is on the path (so it can run without path name) and someone may need to pass parameters too.
- List of files (TMemo) is not read-only
- Too long lines are wrapped and looks confusing
- TListBox would be better (instead of TMemo)
- Anchors not optimized for window resizing
- Missing (for me) descriptive hints for buttons
- Two strings in pohelpermain are not translatable (required changes and the updated 'hu' translation attached):
'Nothing to do',
aPofile.PoName+' saved' ==convert=to=resource=as==> '%s saved'

2014-10-15 11:12 keltez?ssel, Giuliano Colla ?rta:

Let me know if you find some bugs, or would like to add/change some features.

Thank you for the feedback.

I've put it temporarily in hold, because in the meantime I have begun elaborating a more complete solution: a po "swiss army knife", i.e. to put together in a single package a collection of tools for po files handling.

It should include PoChecker, of course, then a PoHelper and also a minimal PoEditor.

They should all share the basic environment and configuration, so that the choices made on PoHelper would be "remembered" by PoChecker, etc.

The reason for a PoEditor is not to reinvent the wheel, but to provide some extra facilities not available to my knowledge in current editors:

* a "global find", to verify the consistency of translations in the same file or across multiple files
* a "global replace" to adjust the consistency, if required,
* the capability of displaying and editing the header: currently available editor provide it in a limited way, and with different capabilities.
* the capability to handle comments and "extracted-comments" ( https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html )

Again suggestions and critics are welcome.

Giuliano

Il 25/10/2014 15:15, P?ter G?bor ha scritto: