Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B13319351 for ; Thu, 21 Jun 2012 09:24:24 +0000 (UTC) Received: (qmail 46655 invoked by uid 500); 21 Jun 2012 09:24:24 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 46589 invoked by uid 500); 21 Jun 2012 09:24:24 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 46571 invoked by uid 99); 21 Jun 2012 09:24:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jun 2012 09:24:23 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of zheng.easyfan@gmail.com designates 209.85.213.47 as permitted sender) Received: from [209.85.213.47] (HELO mail-yw0-f47.google.com) (209.85.213.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jun 2012 09:24:17 +0000 Received: by yhjj56 with SMTP id j56so538734yhj.6 for ; Thu, 21 Jun 2012 02:23:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=gXI/vMJYOHOp4zeaXu7rLVeVbvP7ALE+zF4SMm6gXIQ=; b=zIo/ZUezc/3RtRpfZOGjYOAjEWdLX8dF/s4mEqqhF1q6cgDpCfAJM3biDSgXSFjebA kdrOM+yDjb1+N+8JQFfvDDalxccxysDw6GWmAQwLXpGpnumUkoA0yuuijtD8oCs0u/eQ AsyT+Y/yOx/R2KAO2L8PP+sWybTlb7IZ8K7b6mg0GbTVvf4i4BFl8P10CEiDmOBSPBN5 Cv+s4xG4euu56wSh3HPYoTMa1mRjqIkj5dLn8xU3M81iu7aINHhM+QbLe7h4iT/Zuipa laRUUSPAHlWPWuKkc2gUQkA0XdA52WI061AlFTlVp8SlMbo4vgWCU8oko9006lKglpSl 1LLQ== MIME-Version: 1.0 Received: by 10.236.126.15 with SMTP id a15mr31554894yhi.14.1340270636518; Thu, 21 Jun 2012 02:23:56 -0700 (PDT) Received: by 10.236.103.100 with HTTP; Thu, 21 Jun 2012 02:23:56 -0700 (PDT) In-Reply-To: References: <4FE19A8E.2080705@googlemail.com> Date: Thu, 21 Jun 2012 17:23:56 +0800 Message-ID: Subject: Re: Question about text clipping mechanism in word processor From: Fan Zheng To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=20cf3010e35d314c7804c2f813e3 --20cf3010e35d314c7804c2f813e3 Content-Type: text/plain; charset=ISO-8859-1 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 > 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 > > Above values are correct. > > Kind regards, Joost > > --20cf3010e35d314c7804c2f813e3--