Hi Dan,
On 1/3/21 8:33 PM, Dan Lewis wrote:
> Two questions:
>
> 1) What are the OS that this will work with?
The procedure described below is OS independent (in this new version of
the "cleaning" procedure the odtclean.py script is not required, which
is a significant simplification)
>
> 2)
HI Milos
Em 03/01/2021 11:18, Milos Sramek escreveu:
> Hi Steve,
>
> yes, please, use that file.
>
> I would like to ask you (and anybody else) to help in testing of the
> LoGuidesStyles.oxt extension and document cleaning.
>
> The extension is available from
>
Two questions:
1) What are the OS that this will work with?
2) Where are the directions on how to use it?
Dan
On 1/3/21 9:18 AM, Milos Sramek wrote:
Hi Steve,
yes, please, use that file.
I would like to ask you (and anybody else) to help in testing of the
LoGuidesStyles.oxt extension and
Hi Steve,
yes, please, use that file.
I would like to ask you (and anybody else) to help in testing of the
LoGuidesStyles.oxt extension and document cleaning.
The extension is available from
https://github.com/milossramek/translation-scripts/tree/master/odtclean
and it highlights character
All,
As discussed at a recent Document Team meeting, I am working on an
update to Chapter 13 of the 7.0 Calc Guide (Calc as a Database).
I have assumed that the best ODT file to start with is the cleaned
version in the folder that Milos identified below
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
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.
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,
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
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
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
Hi,
I've uploaded the script and some documentation to github:
https://github.com/milossramek/translation-scripts/tree/master/odtclean
This should solve the problem of 'some' version found 'somewhere'.
Olivier, you wrote:
I think the cleaned files should be the published files. In other words,
Hi, Milos,
I completely agree with you and +1 from me.
There were some reports about the script not working on GNU/Linux, maybe
someone can elaborate?
Lp, m.
V V čet., 17. dec. 2020 ob 20:42 je oseba Milos Sramek <
sramek.mi...@gmail.com> napisala:
> Hi,
>
> I suggest to include file cleaning
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:
>
>
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:
15 matches
Mail list logo