Article View: adobe.framemaker
Article #21920Re: Faulty line-breaks in generated FrameMaker 6 Index
From: Claire Fine
Date: Fri, 17 Jan 2003 14:05
Date: Fri, 17 Jan 2003 14:05
2 lines
936 bytes
936 bytes
Bill, Actually I figured getting rid of the non-breaking space was the answer but was hoping not. I was hoping for a "smart" non-breaking space-- ignore the "non-breaking" attribute if the result is "breaking" a number.
Technical Details
Message-ID:
<1de769db.3@WebX.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-03!sn-xit-06!sn-xit-01!sn-xit-08!supernews.com!newsfeed.online.be!newsfeed01.sul.t-online.de!t-online.de!WebXReferences:
<1de769db.-1@WebX.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fd315,1d983dea061f1017 X-Google-Attributes: gidfd315,public X-Google-ArrivalTime: 2003-01-17 06:07:52 PST From: "Claire Fine" <clairef@nuthena.com> Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-03!sn-xit-06!sn-xit-01!sn-xit-08!supernews.com!newsfeed.online.be!newsfeed01.sul.t-online.de!t-online.de!WebX Newsgroups: adobe.framemaker Subject: Re: Faulty line-breaks in generated FrameMaker 6 Index Message-ID: <1de769db.3@WebX.la2eafNXanI> Date: Fri, 17 Jan 2003 06:05:49 -0800 References: <1de769db.-1@WebX.la2eafNXanI> Lines: 4 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit