Date: prev next · Thread: first prev next last
August 2019 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=126649

--- Comment #14 from Regina Henschel <rb.henschel@t-online.de> ---
Created attachment 153756
  --> https://bugs.documentfoundation.org/attachment.cgi?id=153756&action=edit
line style palette with OOXML preset line styles

I have investigated a little bit in regard to line style palettes.

The palette standard.sod was delivered already in StarOffice 5.2, however in
binary format. OOo1.1.5 is able to read the old file format and convert it to
XML format. The content has not changed compared to our version.

The other file style.sod seems to be a dummy. There had been localized versions
with really different styles. Now this palette is useless. It has 6 similar
styles, were "2" and "3" are identical, and "4", "5" and "6" are identical. I
suggest to remove this file.

I suggest to use the attached file as ersatz. It contains the line styles as
they are defined in the OOXML standard, transformed to ODF format.

This could be done independently of all the other improvements needed for line
styles.

Andreas, I didn't want to get in your way. But I needed the styles for test
documents for my current developer work on the import/export filters. And so I
thought, if I have already created the file, I can make it available.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.