Hi Dave,

meanwhile, I've fixed a bug (tests for nonexisting styles were added)
and zipped the extension on Windows. Please, get the copy from github ( 

https://github.com/milossramek/translation-scripts/blob/master/odtclean/LOGuidesStyles.oxt)
Milos


On 12/29/20 8:02 AM, Dave Barton wrote:
> Hi Milos,
>
> This edition of the extension installs and seems to work OK in LO
> 7.0.4.2 (x64) and 6.4.7.2 (x86) on Win10.
>
> Dave
>
> On 28/12/2020 20:18, Milos Sramek wrote:
>> Hi Dave,
>> thank you for testing.
>> The extension was created on Linux, so maybe the zip utilities are not
>> really compatible. But I've tried that also on Windows using LO 6.3 and
>> 7.0 and it worked without problems. I do not know where can the problem be.
>>
>> I've created the extension on Windows, too, please download it from
>> here. If it works for you, I'll replace that one on Github
>> https://www.sospreskoly.org/~milos/LOGuidesWin.oxt
>> Milos
>>
>>
>> On 12/28/20 6:39 PM, Dave Barton wrote:
>>> Attempting to install the oxt in LO 7.0.4.2 (x64) and 6.4.7.2 (x86) on
>>> Win10  generates the following error:
>>>
>>> (com.sun.star.lang.WrappedTargetRuntimeException) { { { Message = "Bad
>>> Zip File, ZipException: Zip END signature not found!", Context =
>>> (com.sun.star.uno.XInterface) @1d35768a930 (ImplementationName =
>>> "com.sun.star.packages.comp.ZipPackage") } }, TargetException = (any) {
>>> (com.sun.star.packages.zip.ZipIOException) { { { Message = "Bad Zip
>>> File, ZipException: Zip END signature not found!", Context =
>>> (com.sun.star.uno.XInterface) @1d35768a930 (ImplementationName =
>>> "com.sun.star.packages.comp.ZipPackage") } } } } }
>>>
>>> Strangely it installs in AOO 4.1.8 without any error.
>>>
>>> Dave
>>>
>>> On 28/12/2020 16:34, Milos Sramek wrote:
>>>> Hi Olivier and all,
>>>> now that CG70 and MG70 are published I have cleaned the documents
>>>> manually and by the script. You can find the archives in
>>>> https://nextcloud.documentfoundation.org/apps/files/?dir=/Shared/SK%20community/Cleaned&fileid=322834
>>>>
>>>> I suggest to replace the chapter files in the Published directory by
>>>> their cleaned versions without producing the full odt and pdf book.
>>>> Thus, the next version will start from the cleaned document.
>>>> If you agree, I will replace them.
>>>>
>>>> I've created a simple extension, which highlights the character styles
>>>> used in the guides:
>>>> https://github.com/milossramek/translation-scripts/tree/master/odtclean
>>>> https://github.com/milossramek/translation-scripts/blob/master/odtclean/LOGuidesStyles.oxt
>>>>
>>>> If highlighted, an author can see if styles are really used instead of
>>>> direct formatting - in that case additional manual cleaning would not be
>>>> necessary and it would be sufficient only to run the script. I suggest
>>>> then to produce the cleaned files after publishing the guide.
>>>>
>>>> To summarize, I suggest to include two additional steps to the Producing
>>>> LO Guides document
>>>> - for authors: use the extension and use the character styles consistently
>>>> - for a specific person (me for now): to run the script after publishing
>>>> the guide and to replace the chapter files in the published directory
>>>>
>>>> Milos
>>>>
>>>> On 12/17/20 8:55 PM, Olivier Hallot wrote:
>>>>> Hi Milos, All
>>>>>
>>>>> Em 17/12/2020 16:41, Milos Sramek escreveu:
>>>>>> Hi,
>>>>>>
>>>>>> I suggest to include file cleaning in the workflow. In cleaning one
>>>>>> removes direct formatting, which is necessary for translation. Currently
>>>>>> I do that after a guide is published - the cleaned files can be found
>>>>>> here: 
>>>>>>
>>>>>> https://nextcloud.documentfoundation.org/index.php/apps/files?dir=/Shared/SK%20community/Cleaned
>>>>>>
>>>>>> The current problem is that nobody knows about them and a new version of
>>>>>> a guide starts from an uncleaned version in the Published and thus I
>>>>>> have to repeat the laborious manual cleaning part again an again.
>>>>> BTW, last time I tried odtclean.py in my Linux box it failed, something
>>>>> related to python version. Actually, is it still of use?
>>>>>
>>>>>> My suggestion is to add another step after step 7 in the "How to publish
>>>>>> a chapter" section (page 15, 2 - Producing LO Guides.odt): a "Cleaned"
>>>>>> directory, the contents of which will then be used to start a next
>>>>>> version of the guide. I will then produce the cleaned files.
>>>>>>
>>>>> I think the cleaned files should be the published files. In other words,
>>>>> only publish cleaned files.
>>>>>
>>>>> Olivier
>>>>>
>

-- 
email & jabber: [email protected]


-- 
To unsubscribe e-mail to: [email protected]
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

Reply via email to