<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi,<br>
<br>
I'm trying to fine tune paragraph and list styles in filters and I'm not sure about the interpretation and application of text-properties of a paragraph style. There is a big difference in application of text-properties of an automatic and of a named paragraph
style from MS Office point of view. <br>
<br>
Named style:<br>
----------------<br>
Any text run should inherit it's text-properties in case it's paragraph inherits from the named style.
<br>
<br>
Automatic style:<br>
-------------------<br>
In case of DOC/DOCX the text-properties store the "Run Properties for the Paragraph Mark", which DO NOT affect formatting of any text run in the paragraph, but DO affect formatting of the list label. Any unspecified text-properties for the list label should
be inherited from the Paragraph Mark's text-properties to maintain compatibility with MS Word.<br>
<br>
In case of PPT/PPTX the text-properties store "End Paragraph Run Properties", which DO NOT affect formatting of any text run of the paragraph, but are to be used if another run is inserted after the last run specified. Also in case of empty paragraphs any
unspecified text-properties for the list label should be inherited from End Paragraph Run Properties to maintain compatibility with MS PowerPoint.<br>
<br>
Current approach:<br>
---------------------<br>
If I remember correctly we ignore text-properties of the automatic paragraph style in the textlayout in case of ODP files. And we seem to apply them on any text run in case of ODT files. According to my tests LO/OOo do the same in the layout, but their filters
simply save the text-properties into automatic paragraph styles only in case of empty paragraphs. As expected their compatibility with MS Office suffers a lot especially in case of list label formatting.<br>
<br>
I can continue with fine tuning of list styles in filters and use the same approach as LO/OOo in means of text-properties saving, but as soon we start working on editing support we might miss the information.
<br>
<br>
The question:<br>
----------------<br>
Should I proceed with the current approach or do we want to discuss the current ODF interpretation?<br>
<br>
<br>
br,<br>
<br>
-matus<br>
<div><br>
<div style="font-family: Tahoma; font-size: 13px;"><font size="2">-- <br>
Matus Uzak<br>
Software Designer<br>
Ixonos Slovakia s.r.o.<br>
Sturova 27, 040 01 Kosice, Slovakia<br>
mobile 0421 918 718 958<br>
email: matus.uzak@ixonos.com<br>
http://www.ixonos.com</font></div>
</div>
</div>
</body>
</html>