D 2020-06-07T13:29:18.230
L options
N text/x-markdown
P 64c6540123c71e959ee513a920332d6a7315a649
U mario
W 1638
The settings page allows to define a few operation parameters.
### Primarily which service to use:
❎ **Google Translate** is the default
❏ **DeepL web** interface (doesn't work yet)
❏ **DeepL per API** (as of yet untested)
<div style="padding-left: 20pt">
<b>API key</b> (also for Microsoft Translator)<br>
<input type=text size=20>
</div>
❏ **Microsoft Translator** (requires an authorization key, and a `pip install translate` system package)
❏ **MyMemory** (should have an email address in the "API key" field, also requires `pip install translate`)
<div style="padding-left: 20pt">
<b>Email</b> (optional, but recommended)<br>
<input type=text size=20 value=you@example.com>
</div>
❏ **Command line tool** allows to send each text paragraph to a local application. To use it, set the command in the "API key" field again. For example:
<div style="padding-left: 20pt">
<b>Command</b><br>
<input type=text size=20 value="translate-cli -o -t {lang} [text}">
</div>
Where `{text}` is a placeholder for the current text section. (Automatically escaped.)
### Additional options:
❏ **quick linebreak handling** might speed up table processing with Google Translate, as it avoids sending each newline-split sentence separately.
❏ **super slsow mode** iterates over paragraph segments, to keep more inline formatting - but seriously harms mid-sentence translations. Not very useful in practice.
❏ **also iterate over TextFrames** handles floating textframes / subdocuments.
❎ **debug mode** will fill up the /tmp/pagetranslate-libreoffice.txt file quicker
Z 23dfe8c210665377f91f576ccf4c7ed4