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 E421E9156 for ; Thu, 21 Jun 2012 14:44:12 +0000 (UTC) Received: (qmail 52432 invoked by uid 500); 21 Jun 2012 14:44:12 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 52339 invoked by uid 500); 21 Jun 2012 14:44:12 -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 52216 invoked by uid 99); 21 Jun 2012 14:44:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jun 2012 14:44:06 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yuanlin.ibm@gmail.com designates 209.85.161.175 as permitted sender) Received: from [209.85.161.175] (HELO mail-gg0-f175.google.com) (209.85.161.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jun 2012 14:44:01 +0000 Received: by ggnp4 with SMTP id p4so480179ggn.6 for ; Thu, 21 Jun 2012 07:43:41 -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=qp5ekWAWZJbk66aO7baPko1/a9os4IlvEv/rCv/j3DA=; b=lSigLphkCL8roAqzmymbR2CwTl9XKLjE6HLDCd17GU5Xr341tu6a+Dy8lENYYxUMrN daT7h85PJatXKLtjcdrLPTLoFSRUULQGLz/9H8nIAYxXGVkYDEVqdCd+sTo/WZuY0fO9 XXkwQbpBn4JCmZ2WfjHk2aKtiPSs6ypfV9DtEBnRSgO+Az8vgmRS5AF3gOgmFMpPk1tA t+ZOaXwPO7dIMkhqjd6CNJpLBfw2e7nlQgclZ8ENH2MDGk91WwdI0h9qFH/AyTOft0GH DT1GM4tk9hD+uu2XFLFARQ8j8sf9tXcN05HmsTkxPXE4Y41S2gV3B170SSOGygFan74C YHRA== MIME-Version: 1.0 Received: by 10.60.3.194 with SMTP id e2mr28221274oee.1.1340289821026; Thu, 21 Jun 2012 07:43:41 -0700 (PDT) Received: by 10.182.92.201 with HTTP; Thu, 21 Jun 2012 07:43:40 -0700 (PDT) In-Reply-To: <4FE2CC9C.60603@googlemail.com> References: <4FE2CC9C.60603@googlemail.com> Date: Thu, 21 Jun 2012 22:43:40 +0800 Message-ID: Subject: Re: [RELEASE][3.4.1]Release Bloker: proposing "Bug 119803 - After upgrading to 3.4 RTF User Fields are not saving" From: Lin Yuan To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=e89a8fb202a0adab1f04c2fc8a5f X-Virus-Checked: Checked by ClamAV on apache.org --e89a8fb202a0adab1f04c2fc8a5f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable May related to CWS vmiklos01 which refactor the RTF filter. Seems some field related processing in sw\source\filter\ww8\rtfattributeoutput.cxx is not implemented yet. I will do more investigation to know how many codes need to be added and if it can be contained in 3.4.1 scope. 2012/6/21 J=FCrgen Schmidt > On 6/21/12 3:45 AM, YangTerry wrote: > > > > Re-send it, seems failed last time. > > > > This is a bug about user fields lost after save in RTF file. > > This is a regression issue, it is work fine in OOo 3.3. > >> ej197us@gmail.com > >> 2012-06-07 10:23:13 UTC > >> To duplicate: > >> Create a rtf document with a version < 3.4. > >> Menu Options > >> Insert > >> -Field > >> --Other > >> ---User Fields > >> > >> At this point the variable list is shown. > >> > >> Insert a new variable and click the green check. > >> > >> The variable shows up in the list and appears to be saving. > >> > >> Insert the variable into the document to use it. > >> > >> Close the doc and reopen. > >> > >> When the document reopens the variable is not present and is > de-referenced in the doc. > >> > >> This appears to be a critical error. This function is used by many > developers along with UNO to published merged documents. > >> > >> Resolution: Downgrade OpenOffice to <3.4. > >> > > +1 if it's a regression than it's fine for me. Who will take care of > this issue? > > Juergen > > > --e89a8fb202a0adab1f04c2fc8a5f--