🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: adobe.framemaker
Article #781

Re: Stange behaviour when converting text insets

#781
From: Sheila_Carlisle
Date: Tue, 10 Feb 2009 16:35
7 lines
1236 bytes
I just did a simple test and I see the reordering of insets that are marked as "retain source's formatting", yes.

In a series of 3 insets: the first inset was marked to keep the source format and it stayed where it was, the second one was marked to retain source and it moved up below the first inset, and the third inset was set to "reformat using current" and it stayed where it was.

Nasty, nasty.

For the short term this sounds like something that could be solved by having an API or FrameScript move through the file converting each inset one by one, but then if you do have links that need to be re-worked that would be a big pain.
Technical Details
Message-ID: <59b7d3a2.3@webcrossing.la2eafNXanI>
Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!newshub.sdsu.edu!webcrossing
References: <59b7d3a2.-1@webcrossing.la2eafNXanI>

Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,8588e9331eda6613
X-Google-Attributes: gidfd315,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: Sheila_Carlisle@adobeforums.com
Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!newshub.sdsu.edu!webcrossing
Newsgroups: adobe.framemaker
Subject: Re: Stange behaviour when converting text insets
Message-ID: <59b7d3a2.3@webcrossing.la2eafNXanI>
Date: Tue, 10 Feb 2009 08:35:55 -0800
References: <59b7d3a2.-1@webcrossing.la2eafNXanI>
Lines: 14
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit