incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fan Zheng <zheng.easy...@gmail.com>
Subject Re: Question about text clipping mechanism in word processor
Date Thu, 21 Jun 2012 09:23:56 GMT
Hi, All:

Let me talk about my concern.

Regarding the value is correct, there may exist the formatting mechanism
difference.

1. MS Word consider the above-paragraph-spacing  + line-spacing (may also
including the below-paragraph-spacing? not sure) as the available vertical
space for containing text;
2. OpenOffice consider the ling-spacing only as the available vertical
space for containing text;

Is that correct? If yes, then the inner value of line-spacing inside
SvxLineSpacingItem should actually equal to the value
of "above-paragraph-spacing  + line-spacing" stored in DOC files;
And in my opinion, such modification should be in filter but not in
formatting;

A further question is: as the total vertical space include above, line and
below are actually available for containing text, why MS Word trying to
distinguish them? On some other words, what the exact meaning of above and
below paragraph spacing in MS word?

And following the tips from Oliver, such value should only works on the
first line of paragraph. So whether it means that, the
above-paragraph-spacing has some kind of difference definition to the UL
space inside OpenOffice?



2012/6/20 Joost Andrae <Joost.Andrae@gmx.de>

> Hi,
>
> Am 20.06.2012 13:43, schrieb ZuoJun Chen:
>
>  Hi, Fan
>>
>>  I have extracted parameter from first paragraph in sample file
>>
>> 1 Spacing before paragraph 18pt in doc file
>> 2 above-paragraph-spacing  in SvxULSpaceItem: 360
>> 3 line-spacing of said para in doc file: 12pt
>> 4 line-spacing of said para in SvxLineSpacingItem:240
>>
>> Seems that the value mapping works, Looking forward to your further
>> response:)
>>
>
> soffice internally uses twips and msoffice uses pt
>
> https://en.wikipedia.org/wiki/**Twip <https://en.wikipedia.org/wiki/Twip>
>
> Above values are correct.
>
> Kind regards, Joost
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message