I have developed a few tools to help with translation and spell checking of the translation but I cannot integrate that into Lokalize.
It would help me a lot if there was a button (with a shortcut of course) that on a selected entry it would execute a shell script that we can edit and modify, with parameters packed in JSON format and URL Encoded.
Example:
myscrpt.sh ‘{“Original”: “%s: is not a regular file”, “translated”: “%s: nuk eshte skede e rregullt”, “Approved”: “Needs review”, “Original lang code”: “en-UK”, “Translated lang code”: “sq-AL”, …. including unit metadata …. }
but also capture the output of the script as JSON and show it in the translated area.
Result should be like for a successful translation:
{“Translated”: True, “Translated Text”: “ “%s: nuk eshte skedar i rregullt“,
“Original lang code”: “en-UK”, “Translated lang code”: “sq-AL”}
Unfortunately we need to use other spell checking services. The existing hunspell ones are usually good for email, tales, some story-writing, but for computer applications, they are not good.
Now, this is the case with Albanian language only, AFAIK, a few other languages might be in the same boat.
However, we have other projects that we have translated Microsoft applications and products into Albanian and I have tools that can leverage from that treasure. And there is another team that made an Android app and they are helping us by letting us use their API end points for translation.
My goal here is to use curl to do the actual endpoint calling, but having a button on the Lokalize app to call a shell script would very helpful not just me and the Albanian team but to everyone else.
I like the overall idea, but I’m not very fond of the JSON requirement. I would prefer a simpler solution, where Lokalize would send the various parameters as normal (command-line) arguments to a given command (script, or in general, an executable).
It’s easy to write a simple Bash script to process strings (perhaps using awk, sed or other external tools), and I don’t think there’s anything to gain by having the input (and output) as JSON.
BTW, you can already use Pology sieves for processing (entries in) PO files:
It has some integration with Lokalize, in that you can open the resulting PO entries in Lokalize. You can also run a sieve from Lokalize, but only automatically, not manually.
No JSON doesn’t have to be a hard requirement. I just thought it might make it easier to encapsulate various parameters encoded in any language with their special character sets or unicode.
I didn’t know that about Pology.
Does Lokalize put the pology response back into the translated text box?
I can’t run pology because it just fails every time.