LibreOffice plugin to pipe whole Writer documents through Google Translate, that ought to keep most of the page formatting.

⌈⌋ ⎇ branch:  PageTranslate


Check-in [76510a454a]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:More error notes and changed MyMemory behaviour.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 76510a454a35816d50c3a4ebf6a928cdaaf71b86
User & Date: mario 2021-02-09 16:26:37
Context
2021-02-09
16:27
Use world map for new menu entry "From ➜ To 🗺<" check-in: 9b23b4db86 user: mario tags: trunk
16:26
More error notes and changed MyMemory behaviour. check-in: 76510a454a user: mario tags: trunk
2021-02-08
16:00
Prettier error/esxception dialog, and From→To language selection mode now available per menu entry. (Only used by MyMemory for now.) check-in: ab2252ef7a user: mario tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Added NEWS. 































































































































>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62

1.7 (unreleased)
 * Prettier error/exception dialog, and From→To language selection mode.
 * Add langdetect as dependency/bundle.
 * Add mymemory backend without dependency on python-translate.
 * Add a few more languages in submenus.
 * Fix for new Google Translate page (div "result-container" instead of "t0")

1.6 (2021-01-30)
 * Changes to adhoc ssl support without requests.
 * More logging.
 * Add a few more help pages.
 * Add default flags `-o -t {lang}` for cli backend.
 * Rewrite  according to reality.
 * Add TextPortion handling (slow mode): paragraph enumeration.
 * Introduce cmd and email fields, redesign dialog to make association clearer.

1.5 (2020-05-30)
 * Add TextFrames support and config option.
 * Introduce XNamedAsEnumeration wrapper
 * Add <kbd>🏴</kbd> to Draw/Impress. Submenus still missing there however.
 * Remove log. module predeclaration. Prepare for DeepL web support.
 * More AOO compat.
 * Shorten dialog height, as that was the sole reason for AOO not showing it up
   and yielding window=None in the handler.

1.4 (2020-05-28)
 * Prepare for TextFrame support, reinstate self.t=translationbackends.*
 * UTF-8 fixes for Py2+3
 * AOO compatibility with unocompat, and urllib (Py2/3) handling.
   PropertyValue() simplification for tradutor/selection mode.
 * Compatibility with AOO uno and python (2.7, not 3.x),
 * Fix reference to translate-python method (Translator().translate)

1.3 (2020-05-25)
 * Fix missing settings(ctx), and apply crlf and debug options.
 * Use registry instead of config file for storing settings.
 * Add cli(), translate_python() providers, basic deepl_api(), and non-working
   deepl_web() implementation.

1.2 (2020-05-24)
 * Extract via_* classes into pythonpath/translationbackends.
   As well as requests/http/urllib-fallback code into separate module.
 * Add dialog option for python-translate.

1.0 (2020-05-24)
 * Introduced temporary json config file and settings window.
 * remove excessively nested folder structure
 * Introduce requests, restructure regex+http methods into classes to allow
   different translation backends (deepl), prepare for config settings.
 * Unicode flags for languages in submenu

1.0 (2020-05-06)
 * Add preliminary support for Draw/Impress documents.
 * Addons.xcu image references changed. New toolbar button.

0.9 (2020-05-04)
 * Restructured Addons.xcu for extra buttons.
 * More language options in Tools menu.
 * Reenable cursor/selection mode (Tradutor trigger).
 * Crude table translation.
 * Introduce text splitting (paragraphs longer than 1900 characters); untested.
 * Bugfixes

Changes to help/en/vnd.include-once.pagetranslate/config.page.

︙︙
44
45
46
47
48
49
50
51


52
53
54
55
56
57
58
59
60
61
62

      <title>❏ Microsoft Translator</title>
      <p>Requires an authorization key, and a `pip install translate` system package.
      There's also a free/test <link href="https://azure.microsoft.com/en-us/pricing/details/cognitive-services/translator/">subscription for an API key</link>.
      Not tested within PageTranslate yet.</p>
    </item>
    <item>
      <title>❏ MyMemory</title>
      <p>Should have an email address in the according input box (though optional).


      Also requires `pip install translate`, unless the full OpenOffice plugin bundle
      was installed. Doesn't yield quite as good machine translations. But it's
      an open source service.
      </p>
    </item>
    <item>
      <title>❏ Command line tool</title>
      <p>Allows to send each text paragraph to a local application. To use it, set the
      command in the according input field again. Placeholders are `{lang}` for the
      target language, and `{text}` for the paragaphs or current text section. (Both get
      automatically escaped). For <cmd>translate-cli</cmd> you might need








|
>
>
|
|
|
<








44
45
46
47
48
49
50
51
52
53
54
55
56

57
58
59
60
61
62
63

      <title>❏ Microsoft Translator</title>
      <p>Requires an authorization key, and a `pip install translate` system package.
      There's also a free/test <link href="https://azure.microsoft.com/en-us/pricing/details/cognitive-services/translator/">subscription for an API key</link>.
      Not tested within PageTranslate yet.</p>
    </item>
    <item>
      <title>❏ MyMemory</title>
      <p>Should have an email address in the according input box (though
      optional).  No longer requires the python-translate module, but
      <file>langdetect</file> (for supplying the correct source language). 
      Which is why it sometimes fails, and possibly requires the Tools →
      PageTranslate → From ➜ To option.  Doesn't yield quite as good machine
      translations.  But it's an open source service.  </p>

    </item>
    <item>
      <title>❏ Command line tool</title>
      <p>Allows to send each text paragraph to a local application. To use it, set the
      command in the according input field again. Placeholders are `{lang}` for the
      target language, and `{text}` for the paragaphs or current text section. (Both get
      automatically escaped). For <cmd>translate-cli</cmd> you might need
︙︙

Changes to help/en/vnd.include-once.pagetranslate/config.xhp. 

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

<?xml version="1.0" encoding="UTF-8"?>
<helpdocument version="1.0">
   <meta>
      <topic id="topic_d1e3" indexer="include" status="PUBLISH">
         <title xml-lang="en" id="title_d1e3">Translation settings</title>
         <filename>/help/vnd.include-once.pagetranslate/config.xhp</filename>
      </topic>
      <history>
         <created date="2020-02-02T22:22:22"/>
         <lastedited date="2020-06-20T10:23:01.66+02:00"/>
      </history>
   </meta>
   <body>

      <bookmark id="bm_d1e7" branch="hid/vnd.include-once.pagetranslate:OptionsPageTranslate"
                xml-lang="en">
         <bookmark_value>PageTranslate settings</bookmark_value>










|








1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

<?xml version="1.0" encoding="UTF-8"?>
<helpdocument version="1.0">
   <meta>
      <topic id="topic_d1e3" indexer="include" status="PUBLISH">
         <title xml-lang="en" id="title_d1e3">Translation settings</title>
         <filename>/help/vnd.include-once.pagetranslate/config.xhp</filename>
      </topic>
      <history>
         <created date="2020-02-02T22:22:22"/>
         <lastedited date="2021-02-08T17:49:08.362+01:00"/>
      </history>
   </meta>
   <body>

      <bookmark id="bm_d1e7" branch="hid/vnd.include-once.pagetranslate:OptionsPageTranslate"
                xml-lang="en">
         <bookmark_value>PageTranslate settings</bookmark_value>
︙︙
57
58
59
60
61
62
63
64


65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118

               <paragraph id="par_d1e76" role="paragraph" xml-lang="en">Requires an authorization key, and a `pip install translate` system package.
      There's also a free/test <link href="https://azure.microsoft.com/en-us/pricing/details/cognitive-services/translator/">subscription for an API key</link>.
      Not tested within PageTranslate yet.</paragraph>
            </listitem>
            <listitem id="item_d1e83" xml-lang="en">
               <emph>❏ MyMemory</emph>
               <br/>
               <paragraph id="par_d1e88" role="paragraph" xml-lang="en">Should have an email address in the according input box (though optional).


      Also requires `pip install translate`, unless the full OpenOffice plugin bundle
      was installed. Doesn't yield quite as good machine translations. But it's
      an open source service.
      </paragraph>
            </listitem>
            <listitem id="item_d1e93" xml-lang="en">
               <emph>❏ Command line tool</emph>
               <br/>
               <paragraph id="par_d1e98" role="paragraph" xml-lang="en">Allows to send each text paragraph to a local application. To use it, set the
      command in the according input field again. Placeholders are `{lang}` for the
      target language, and `{text}` for the paragaphs or current text section. (Both get
      automatically escaped). For <item type="command">translate-cli</item> you might need
      the <item type="variable">-p</item> provider option as well.
      See also the <link href="https://pypi.org/project/translate/">translate-python
      documentation</link> on how to prepare a separate <item type="fileitem">~/.python-translate.cfg</item>.
      </paragraph>
            </listitem>
         </list>
      </paragraph>

      <paragraph id="sect_d1e116" role="section" xml-lang="en">
         <paragraph id="hd_d1e118" role="heading" level="2" xml-lang="en">Operation flags</paragraph>
         <list id="terms_d1e121" xml-lang="en">
            <listitem id="item_d1e123" xml-lang="en">
               <emph>❏ quick linebreak handling</emph>
               <br/>
               <paragraph id="par_d1e128" role="paragraph" xml-lang="en">Might speed up table processing with Google Translate, as it avoids sending each newline-split sentence separately.
      It simply conjoins multiple lines temporarily with <item type="command">"/#§/"</item> in place of a
      linebreak (and then rejoins them), so there are less requests. Primarily helps with
      tables, but less for documents with lengthy paragraphs.</paragraph>
            </listitem>
            <listitem id="item_d1e135" xml-lang="en">
               <emph>❏ also iterate over TextFrames</emph>
               <br/>
               <paragraph id="par_d1e140" role="paragraph" xml-lang="en">Handles normal and floating TextFrames. Those are essentially subdocuments in a Writer page.
      But you probably don't need this option for standard office documents.</paragraph>
            </listitem>
            <listitem id="item_d1e144" xml-lang="en">
               <emph>❏ super slow mode</emph>
               <br/>
               <paragraph id="par_d1e149" role="paragraph" xml-lang="en">Iterates over paragraph segments, to keep more inline formatting - but seriously harms mid-sentence translations.
      And currently the formatting still bleeds into adjoining paragraph segments, so not very useful in practice yet.</paragraph>
            </listitem>
            <listitem id="item_d1e153" xml-lang="en">
               <emph>☑ debug mode</emph>
               <br/>
               <paragraph id="par_d1e158" role="paragraph" xml-lang="en">Will fill up the <item type="fileitem">/tmp/pagetranslate-libreoffice.txt</item> log file quicker.
      Currently the debug mode is enabled by default anyway.</paragraph>
            </listitem>
         </list>
      </paragraph>

   </body>
</helpdocument>








|
>
>
|
|
|
<

|


|











|
|
|
|


|




|


|


|


|


|


|








57
58
59
60
61
62
63
64
65
66
67
68
69

70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119

               <paragraph id="par_d1e76" role="paragraph" xml-lang="en">Requires an authorization key, and a `pip install translate` system package.
      There's also a free/test <link href="https://azure.microsoft.com/en-us/pricing/details/cognitive-services/translator/">subscription for an API key</link>.
      Not tested within PageTranslate yet.</paragraph>
            </listitem>
            <listitem id="item_d1e83" xml-lang="en">
               <emph>❏ MyMemory</emph>
               <br/>
               <paragraph id="par_d1e88" role="paragraph" xml-lang="en">Should have an email address in the according input box (though
      optional).  No longer requires the python-translate module, but
      <item type="fileitem">langdetect</item> (for supplying the correct source language). 
      Which is why it sometimes fails, and possibly requires the Tools →
      PageTranslate → From ➜ To option.  Doesn't yield quite as good machine
      translations.  But it's an open source service.  </paragraph>

            </listitem>
            <listitem id="item_d1e96" xml-lang="en">
               <emph>❏ Command line tool</emph>
               <br/>
               <paragraph id="par_d1e101" role="paragraph" xml-lang="en">Allows to send each text paragraph to a local application. To use it, set the
      command in the according input field again. Placeholders are `{lang}` for the
      target language, and `{text}` for the paragaphs or current text section. (Both get
      automatically escaped). For <item type="command">translate-cli</item> you might need
      the <item type="variable">-p</item> provider option as well.
      See also the <link href="https://pypi.org/project/translate/">translate-python
      documentation</link> on how to prepare a separate <item type="fileitem">~/.python-translate.cfg</item>.
      </paragraph>
            </listitem>
         </list>
      </paragraph>

      <paragraph id="sect_d1e119" role="section" xml-lang="en">
         <paragraph id="hd_d1e121" role="heading" level="2" xml-lang="en">Operation flags</paragraph>
         <list id="terms_d1e124" xml-lang="en">
            <listitem id="item_d1e126" xml-lang="en">
               <emph>❏ quick linebreak handling</emph>
               <br/>
               <paragraph id="par_d1e131" role="paragraph" xml-lang="en">Might speed up table processing with Google Translate, as it avoids sending each newline-split sentence separately.
      It simply conjoins multiple lines temporarily with <item type="command">"/#§/"</item> in place of a
      linebreak (and then rejoins them), so there are less requests. Primarily helps with
      tables, but less for documents with lengthy paragraphs.</paragraph>
            </listitem>
            <listitem id="item_d1e138" xml-lang="en">
               <emph>❏ also iterate over TextFrames</emph>
               <br/>
               <paragraph id="par_d1e143" role="paragraph" xml-lang="en">Handles normal and floating TextFrames. Those are essentially subdocuments in a Writer page.
      But you probably don't need this option for standard office documents.</paragraph>
            </listitem>
            <listitem id="item_d1e147" xml-lang="en">
               <emph>❏ super slow mode</emph>
               <br/>
               <paragraph id="par_d1e152" role="paragraph" xml-lang="en">Iterates over paragraph segments, to keep more inline formatting - but seriously harms mid-sentence translations.
      And currently the formatting still bleeds into adjoining paragraph segments, so not very useful in practice yet.</paragraph>
            </listitem>
            <listitem id="item_d1e156" xml-lang="en">
               <emph>☑ debug mode</emph>
               <br/>
               <paragraph id="par_d1e161" role="paragraph" xml-lang="en">Will fill up the <item type="fileitem">/tmp/pagetranslate-libreoffice.txt</item> log file quicker.
      Currently the debug mode is enabled by default anyway.</paragraph>
            </listitem>
         </list>
      </paragraph>

   </body>
</helpdocument>

Changes to help/en/vnd.include-once.pagetranslate/errors.duck.

︙︙
69
70
71
72
73
74
75















76
77
78
79
80
81
82
83
84
85
86

87
88


== WARNING:root:NO TRANSLATION RESULT EXTRACTED

If this messsage shows up in the log, the google translate backend
(`pythonpath/translationbackends.py`) requires updating. Specifically the
regex in `rx_gtrans` for extracting the target string.
















== How to report a bug

[--
@link[seealso >>https://fossil.include-once.org/pagetranslate/] repository
--]
The project repository https://fossil.include-once.org/pagetranslate/
allows to file a bug report (no registration necessary).

 * The log file MUST be included,
 * together with a sample document (as link),
 * as well as the OpenOffice version (Help → About → Copy)


Insufficient submissions are unlikely to spark developer interest else.








>
>
>
>
>
>
>
>
>
>
>
>
>
>
>











>

|

69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104


== WARNING:root:NO TRANSLATION RESULT EXTRACTED

If this messsage shows up in the log, the google translate backend
(`pythonpath/translationbackends.py`) requires updating. Specifically the
regex in `rx_gtrans` for extracting the target string.

== MyMemory: PLEASE SELECT TWO DISTINCT LANGUAGES

The langauge detection failed. You'll probably have to use the
Tools→PageTranslate→From➜To dialog to specify both input and target
language.

== MyMemory: INVALID EMAIL PROVIDED

Add an email address (Tools→Options→Language→PageTranslate) for MyMemory.

== MyMemory: 'AUTO' IS AN INVALID SOURCE LANGUAGE.

This error shouldn't really happen anymore, as the default fallback
for MyMemory is 'en' and not 'auto'.

== How to report a bug

[--
@link[seealso >>https://fossil.include-once.org/pagetranslate/] repository
--]
The project repository https://fossil.include-once.org/pagetranslate/
allows to file a bug report (no registration necessary).

 * The log file MUST be included,
 * together with a sample document (as link),
 * as well as the OpenOffice version (Help → About → Copy)
 * latest or development version has been tested.

Insufficient submissions are unlikely to spark developer interest.

Changes to help/en/vnd.include-once.pagetranslate/errors.xhp. 

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

<?xml version="1.0" encoding="UTF-8"?>
<helpdocument version="1.0">
   <meta>
      <topic id="topic_d1e1" indexer="include" status="PUBLISH">
         <title xml-lang="en" id="title_d1e1">Errors</title>
         <filename>/help/vnd.include-once.pagetranslate/errors.xhp</filename>
      </topic>
      <history>
         <created date="2020-02-02T22:22:22"/>
         <lastedited date="2021-02-07T14:30:20.342+01:00"/>
      </history>
   </meta>
   <body>
      <link href="vnd.include-once.pagetranslate/index.xhp"/>
      <paragraph id="hd_d1e8" role="heading" level="1" xml-lang="en">Errors</paragraph>
      <paragraph id="par_d1e11" role="paragraph" xml-lang="en">Error messages will largely show up as long-winded popups with Python
 exceptions. Where the text usually starts with "Traceback" and then










|








1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

<?xml version="1.0" encoding="UTF-8"?>
<helpdocument version="1.0">
   <meta>
      <topic id="topic_d1e1" indexer="include" status="PUBLISH">
         <title xml-lang="en" id="title_d1e1">Errors</title>
         <filename>/help/vnd.include-once.pagetranslate/errors.xhp</filename>
      </topic>
      <history>
         <created date="2020-02-02T22:22:22"/>
         <lastedited date="2021-02-08T18:32:09.702+01:00"/>
      </history>
   </meta>
   <body>
      <link href="vnd.include-once.pagetranslate/index.xhp"/>
      <paragraph id="hd_d1e8" role="heading" level="1" xml-lang="en">Errors</paragraph>
      <paragraph id="par_d1e11" role="paragraph" xml-lang="en">Error messages will largely show up as long-winded popups with Python
 exceptions. Where the text usually starts with "Traceback" and then
︙︙
75
76
77
78
79
80
81
82















83
84
85
86
87
88
89
90
91
92
93
94



95
96
97
98
99

      <paragraph id="sect_d1e94" role="section" xml-lang="en">
         <paragraph id="hd_d1e96" role="heading" level="2" xml-lang="en">WARNING:root:NO TRANSLATION RESULT EXTRACTED</paragraph>
         <paragraph id="par_d1e99" role="paragraph" xml-lang="en">If this messsage shows up in the log, the google translate backend
  (`pythonpath/translationbackends.py`) requires updating. Specifically the
  regex in `rx_gtrans` for extracting the target string.</paragraph>
      </paragraph>
      <paragraph id="sect_d1e103" role="section" xml-lang="en">
         <paragraph id="hd_d1e105" role="heading" level="2" xml-lang="en">How to report a bug</paragraph>















         <paragraph id="par_d1e108" role="paragraph" xml-lang="en">The project repository https://fossil.include-once.org/pagetranslate/
  allows to file a bug report (no registration necessary).</paragraph>
         <list id="list_d1e111" xml-lang="en">
            <listitem id="item_d1e113" xml-lang="en">
               <paragraph id="par_d1e115" role="paragraph" xml-lang="en">The log file MUST be included,</paragraph>
            </listitem>
            <listitem id="item_d1e119" xml-lang="en">
               <paragraph id="par_d1e121" role="paragraph" xml-lang="en">together with a sample document (as link),</paragraph>
            </listitem>
            <listitem id="item_d1e125" xml-lang="en">
               <paragraph id="par_d1e127" role="paragraph" xml-lang="en">as well as the OpenOffice version (Help → About → Copy)</paragraph>
            </listitem>



         </list>
         <paragraph id="par_d1e132" role="paragraph" xml-lang="en">Insufficient submissions are unlikely to spark developer interest else.</paragraph>
      </paragraph>
   </body>
</helpdocument>








|
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
|

|
|
|

|
|

|
|

>
>
>

|




75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117

      <paragraph id="sect_d1e94" role="section" xml-lang="en">
         <paragraph id="hd_d1e96" role="heading" level="2" xml-lang="en">WARNING:root:NO TRANSLATION RESULT EXTRACTED</paragraph>
         <paragraph id="par_d1e99" role="paragraph" xml-lang="en">If this messsage shows up in the log, the google translate backend
  (`pythonpath/translationbackends.py`) requires updating. Specifically the
  regex in `rx_gtrans` for extracting the target string.</paragraph>
      </paragraph>
      <paragraph id="sect_d1e103" role="section" xml-lang="en">
         <paragraph id="hd_d1e105" role="heading" level="2" xml-lang="en">MyMemory: PLEASE SELECT TWO DISTINCT LANGUAGES</paragraph>
         <paragraph id="par_d1e108" role="paragraph" xml-lang="en">The langauge detection failed. You'll probably have to use the
  Tools→PageTranslate→From➜To dialog to specify both input and target
  language.</paragraph>
      </paragraph>
      <paragraph id="sect_d1e112" role="section" xml-lang="en">
         <paragraph id="hd_d1e114" role="heading" level="2" xml-lang="en">MyMemory: INVALID EMAIL PROVIDED</paragraph>
         <paragraph id="par_d1e117" role="paragraph" xml-lang="en">Add an email address (Tools→Options→Language→PageTranslate) for MyMemory.</paragraph>
      </paragraph>
      <paragraph id="sect_d1e121" role="section" xml-lang="en">
         <paragraph id="hd_d1e123" role="heading" level="2" xml-lang="en">MyMemory: 'AUTO' IS AN INVALID SOURCE LANGUAGE.</paragraph>
         <paragraph id="par_d1e126" role="paragraph" xml-lang="en">This error shouldn't really happen anymore, as the default fallback
  for MyMemory is 'en' and not 'auto'.</paragraph>
      </paragraph>
      <paragraph id="sect_d1e130" role="section" xml-lang="en">
         <paragraph id="hd_d1e132" role="heading" level="2" xml-lang="en">How to report a bug</paragraph>
         <paragraph id="par_d1e135" role="paragraph" xml-lang="en">The project repository https://fossil.include-once.org/pagetranslate/
  allows to file a bug report (no registration necessary).</paragraph>
         <list id="list_d1e138" xml-lang="en">
            <listitem id="item_d1e140" xml-lang="en">
               <paragraph id="par_d1e142" role="paragraph" xml-lang="en">The log file MUST be included,</paragraph>
            </listitem>
            <listitem id="item_d1e146" xml-lang="en">
               <paragraph id="par_d1e148" role="paragraph" xml-lang="en">together with a sample document (as link),</paragraph>
            </listitem>
            <listitem id="item_d1e152" xml-lang="en">
               <paragraph id="par_d1e154" role="paragraph" xml-lang="en">as well as the OpenOffice version (Help → About → Copy)</paragraph>
            </listitem>
            <listitem id="item_d1e158" xml-lang="en">
               <paragraph id="par_d1e160" role="paragraph" xml-lang="en">latest or development version has been tested.</paragraph>
            </listitem>
         </list>
         <paragraph id="par_d1e165" role="paragraph" xml-lang="en">Insufficient submissions are unlikely to spark developer interest.</paragraph>
      </paragraph>
   </body>
</helpdocument>

Changes to help/en/vnd.include-once.pagetranslate/project.duck. 

1
2
3
4
5


6
7
8
9
10
11

= Project
  [topic]
@link[topic xref=index]

More information on this extension can be found in the development and source code repository:


https://fossil.include-once.org/pagetranslate/index

It's sort of feature complete for the intended purposes. But shouldn't be considered stable or finished. However, there's unlikely to be enough user interest for more releases.

The development package should only be used on Linux installations, for there is little Python support on Windows.
Also take in mind that the OpenOffice package is slightly better equipped with Python dependencies, yet may have some issues with the older Python 2.7 in AOO. Development versions of LibreOffice on the other hand might yield errors for SSL support.






>
>
|






1
2
3
4
5
6
7
8
9
10
11
12
13

= Project
  [topic]
@link[topic xref=index]

More information on this extension can be found in the development and source code repository:

@link[seealso >>https://fossil.include-once.org/pagetranslate/]
  @title Link https://fossil.include-once.org/pagetranslate/

It's sort of feature complete for the intended purposes. But shouldn't be considered stable or finished. However, there's unlikely to be enough user interest for more releases.

The development package should only be used on Linux installations, for there is little Python support on Windows.
Also take in mind that the OpenOffice package is slightly better equipped with Python dependencies, yet may have some issues with the older Python 2.7 in AOO. Development versions of LibreOffice on the other hand might yield errors for SSL support.

Changes to help/en/vnd.include-once.pagetranslate/project.xhp. 

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

17

18
19
20
21
22

<?xml version="1.0" encoding="UTF-8"?>
<helpdocument version="1.0">
   <meta>
      <topic id="topic_d1e1" indexer="include" status="PUBLISH">
         <title xml-lang="en" id="title_d1e1">Project</title>
         <filename>/help/vnd.include-once.pagetranslate/project.xhp</filename>
      </topic>
      <history>
         <created date="2020-02-02T22:22:22"/>
         <lastedited date="2020-06-20T10:04:54.896+02:00"/>
      </history>
   </meta>
   <body>
      <link href="vnd.include-once.pagetranslate/index.xhp"/>
      <paragraph id="hd_d1e8" role="heading" level="1" xml-lang="en">Project</paragraph>
      <paragraph id="par_d1e11" role="paragraph" xml-lang="en">More information on this extension can be found in the development and source code repository:

 https://fossil.include-once.org/pagetranslate/index</paragraph>

      <paragraph id="par_d1e14" role="paragraph" xml-lang="en">It's sort of feature complete for the intended purposes. But shouldn't be considered stable or finished. However, there's unlikely to be enough user interest for more releases.</paragraph>
      <paragraph id="par_d1e17" role="paragraph" xml-lang="en">The development package should only be used on Linux installations, for there is little Python support on Windows.
 Also take in mind that the OpenOffice package is slightly better equipped with Python dependencies, yet may have some issues with the older Python 2.7 in AOO. Development versions of LibreOffice on the other hand might yield errors for SSL support.</paragraph>
   </body>
</helpdocument>










|





|
>
|
>
|
|




1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

<?xml version="1.0" encoding="UTF-8"?>
<helpdocument version="1.0">
   <meta>
      <topic id="topic_d1e1" indexer="include" status="PUBLISH">
         <title xml-lang="en" id="title_d1e1">Project</title>
         <filename>/help/vnd.include-once.pagetranslate/project.xhp</filename>
      </topic>
      <history>
         <created date="2020-02-02T22:22:22"/>
         <lastedited date="2021-02-08T18:32:08.821+01:00"/>
      </history>
   </meta>
   <body>
      <link href="vnd.include-once.pagetranslate/index.xhp"/>
      <paragraph id="hd_d1e8" role="heading" level="1" xml-lang="en">Project</paragraph>
      <paragraph id="par_d1e11" role="paragraph" xml-lang="en">More information on this extension can be found in the development and source code repository:</paragraph>
      <paragraph id="par_d1e14" role="paragraph" xml-lang="en">
         <link href="https://fossil.include-once.org/pagetranslate/">https://fossil.include-once.org/pagetranslate/</link>
      </paragraph>
      <paragraph id="par_d1e18" role="paragraph" xml-lang="en">It's sort of feature complete for the intended purposes. But shouldn't be considered stable or finished. However, there's unlikely to be enough user interest for more releases.</paragraph>
      <paragraph id="par_d1e22" role="paragraph" xml-lang="en">The development package should only be used on Linux installations, for there is little Python support on Windows.
 Also take in mind that the OpenOffice package is slightly better equipped with Python dependencies, yet may have some issues with the older Python 2.7 in AOO. Development versions of LibreOffice on the other hand might yield errors for SSL support.</paragraph>
   </body>
</helpdocument>