Error using a colon in index entry sorting

[Rick Quatro]

Hi Greg,

 

I tried to email you offlist, but the email bounced back as undeliverable.
Please email me your phone number or give me a call.

 

I am sorry for posting this to the list.

 

Rick

 

Rick Quatro

Carmen Publishing Inc.

585-283-5045

rick at frameexpert.com

 

 

 

From: framers-bounces at lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of Greg Williams
Sent: Wednesday, January 30, 2013 11:35 AM
To: framers at lists.frameusers.com
Subject: Error using a colon in index entry sorting

 

Hi Framers,

First time poster; Structured FM 11.0.1.382, Vista 32-bit; DITA 1.2

I'm having an issue with sorting index entries. I'm adding index entries in
the XML of a DITA topic and then using FM to output the file. Specifically
I'm trying to get "see also" entries to sort to the top of the main index
entry, but I can simplify my problem for descriptive purposes. I've read a
good deal of literature concerning sorting index entries in FM and in the
DITA 1.2 spec, and I have a good idea of how it should work. 

Here's a simplified example. Working in FM, I have a file with a main index
entry "FrameMaker" and a sub-entry "problems". I want "problems" to be the
first sub-entry in a long list of sub-entries under "FrameMaker" (for
obvious reason). I insert an indexterm element and enter the following in
the Marker dialog: FrameMaker:problems[FrameMaker:aaa]. I quickly generate a
standard index and everything looks great - the sub-entry is the first under
"FrameMaker". I save and close the file. The XML looks like this ("["
substituted for "<"): 

[indexterm]FrameMaker[indexterm]problems[index-sort-as]FrameMaker:aaa[/index
-sort-as][/indexterm][/indexterm]

When I reopen the file in FM, the text for this indexterm in the dialog box
reads: FrameMaker:problems[FrameMaker\:aaa]. Note the backslash inserted
before the ":aaa" sorting. My sub-entry is no longer the first in the list
of FrameMaker sub-entries. The XML looks the same throughout this process,
of course.

Can anyone tell me what I'm doing wrong, why FM is inserting this backslash,
and/or how I can avoid having this backslash appear? It appears to be a bug,
but maybe I'm missing something... Any help is greatly appreciated.

(A coworker of mine just filed this as a bug with Adobe.)

Regards,

Greg Williams
London, Ontario

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20130131/6fa88d24/attachment.htm>