Re: [libreoffice-documentation] Producing guides - add a "Cleaned" directory
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=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
>>
>
--
To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org
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
Re: [libreoffice-documentation] Producing guides - add a "Cleaned" directory
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=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: sramek.mi...@gmail.com
--
To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org
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
Re: [libreoffice-documentation] GS7008 Base
Rob, If you can replace the poor quality images quickly, that would be great. Fixing the difference in icon sets is IMO less urgent because many other chapters are also inconsistent, but still worth doing. Thanks! Jean On Mon, 28 Dec 2020 at 21:10 Rob Westein wrote: > Hi, > > I've updated the 6.4 Base guide to 7.0. Uploaded file > GS7008-GettingStartedWithBase_01-RW.odt to the "Work In Progress folder". > > No big changes. > > The only thing I'm worried about are the images used in the guide. The > images vary in quality and several icon sets are used throughout the > Guide > > What do you think: should I replace them? > > Thanks, > > Rob > -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org 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
Re: [libreoffice-documentation] Producing guides - add a "Cleaned" directory
Hi Milos Thanks for the cleaner and the extension. One small adjustment... It happens that LOGuidesStyles.oxt does not check if the character style exist in the file. So before accessing one of the Guide character style (highlight on/off), can we check if the style exist in the document (may have been removed). Kind regards (1) https://extensions.libreoffice.org/en/extensions/show/875 Em 28/12/2020 13:34, Milos Sramek escreveu: > 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=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 >> > -- Olivier Hallot LibreOffice Documentation Coordinator Rio de Janeiro - Brasil - Local Time: UTC-03:00 LibreOffice – free and open source office suite: https://www.libreoffice.org Respects your privacy, and gives you back control over your data http://tdf.io/joinus -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org 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
Re: [libreoffice-documentation] Producing guides - add a "Cleaned" directory
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=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
>>
>
--
To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org
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
Re: [libreoffice-documentation] Producing guides - add a "Cleaned" directory
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=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: sramek.mi...@gmail.com -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org 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
Re: [libreoffice-documentation] get access to nextcloud / olivier hallot
Hi Peter Em 27/12/2020 10:46, Peter Heijink escreveu: > Hi reader, ?Olivier Hallot? > > with reference to "After your login is confirmed, contact the > Documentation leader through the mailing list to obtain access to the > LibreOffice Documentation folder on TDF NextCloud." > i would like to get access to see what is going on. My SSO account name > is peterH > I added your login to the cloud. PLease access https://nextcloud.documentfoundation.org > Among others i would like to add to the wiki pages regarding python. > /Lowering the threshold/ for BASIC users to make the step to python, in > a simple manner, no IDE environment. Part of the idea is to create a > downloadable python file with functions that will make python > /attractive/ to implement. The file contains functions that show an > extension of the functionality of LibreOffice, that can not be achieved > with basic: > - insert an autoincremented number as barcode or QR code > - send a document as PDF attachment using the address book of Thunderbird > - store invoice data in a database, data extracted from a received > invoice in XML format > - MRI objects (trivial but useful ) > - use the dispatcher (identical) > - write debug output to a writer document > So it remains at the application level, and leave the user prepared for > the next step, own macro writing, upgrading to IDE... > > Of course if this interacts with projects/ideas in development i would > like to share with that. > We have a group of Python (and other script languages) enthusiasts that reads this list. On Python, please visit https://wiki.documentfoundation.org/Macros Kind regards -- Olivier Hallot LibreOffice Documentation Coordinator Rio de Janeiro - Brasil - Local Time: UTC-03:00 LibreOffice – free and open source office suite: https://www.libreoffice.org Respects your privacy, and gives you back control over your data http://tdf.io/joinus -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org 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
