Re: Faulty line-breaks in generated FrameMaker 6 Index

Article View: adobe.framemaker

Article #21984

#21984

From: Bill Swallow
Date: Fri, 17 Jan 2003 16:25

4 lines
1033 bytes

Right, but if you allow line breaks after commas, then it should work OK. But I still think that there is very little need for non-breaking spaces in index entries, as the space is the logical place to break entries to begin with, especially given the original scenario:

ixEntry, 35, 42-46, 76, 83, 142
anotherIxEntry, 3, 49, 125

Technical Details

Message-ID: <1de769db.6@WebX.la2eafNXanI>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-03!sn-xit-01!sn-xit-08!supernews.com!newsfeed.online.be!newsfeed01.sul.t-online.de!t-online.de!WebX

References: <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 08:38:06 PST
From: "Bill Swallow" <bill_swallow@yahoo.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-03!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.6@WebX.la2eafNXanI>
Date: Fri, 17 Jan 2003 08:25:45 -0800
References: <1de769db.-1@WebX.la2eafNXanI>
Lines: 7
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message