Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
Hi,
I'm trying to troubleshoot some index issues and would like to be able to view the final index markup in the edit window.
I followed the instructions in the Help file for this and I can see the preliminary index markup, but the _final pseudo tags contain no content. Do I need to code something extra special in my fosi in order to see the final index generated text?
Thanks,
KM
Suzanne,
If you mean when doing a Print Preview with composer, yes, the index does appear in its final sorted version. Unfortunately, it still isn't sorted correctly, and there are some odd extra spaces, which is one reason I wanted to try looking at the final markup to see if I could figure out what is going on.
Thanks,
Kim
I see a lot of tags:
<num-index.psu*><usetext userule="2" id="0" fid="65535"><_final><_prelim></tiv>
<ixpt*>...</ixpt*><ixsub1*>..</ixsub1><ixpgstr*>...</ixpgstr*>
----many of these until the end----
</num-index.psu*>
All the preliminary index markup seems to be there in its unsorted order. I can't see the final index until I do a Preview or Compose it.
Maybe I'm doing something fundamentally wrong in the FOSI while producing the index. I inherited the FOSI and I'm trying to add functionality that was missing, but most of the index stuff was already there, just not picking up all the part nos. and in the wrong sort order so I'm trying to fix those things.
OK. I am seeing the following errors:
[A12550] ERROR (indexing): Can't use page string for page key; may need explicit key.
[A12550] ERROR (indexing): Can't use page string for page key; may need explicit key.
[A12550] ERROR (indexing): Can't use page string for page key; may need explicit key.
[A12550] ERROR (indexing): Can't use page string for page key; may need explicit key.
[A12550] ERROR (indexing): Can't use page string for page key; may need explicit key.
[A12550] ERROR (indexing): Can't use page string for page key; may need explicit key.
[A12550] ERROR (indexing): Can't use page string for page key; may need explicit key.
[A12534] ERROR: (indexing) No index records found in preliminary index.
But I am seeing the preliminary index markup in the document - like this:
<ixpt>9740-0183</ixpt><ixsub1>1-</ixsub1><ixpgstr>1-00</ixpgstr>
<ixpt>9740001-E20</ixpt><ixsub1>1-1</ixsub1><ixpgstr>1-00</ixpgstr>
<ixpt>9740001-E301</ixpt><ixsub1>1-2</ixsub1><ixpgstr>1-00</ixpgstr>
I did try changing userule to 1 and exporting it to an external file. I get the preliminary index markup there as well. But when I compose it, I do get the sorted index and the page strings are there ..so it's doing something, somewhere, with the preliminary markup...
Suzanne,
Thanks. I fixed the page string error and can now see the final index markup in the Edit window. I've figured out why I'm getting some extra spacing in the output, too. But I still haven't gotten the sort problem figured out.
I need all the alpha groups before the numerical groups in this index, but if I use a custom collation file it will change the sort order for all indexes, won't it? while I just want to change the part number index, but still be able to have a normal alphabetic glossary if I need it. or am I mistaken?
Kim
Suzanne,
I did read about the sortas attribute, but my partno elements do not have an attribute for that and I can't alter the DTD to add one. Can I create a pseudo attribute for this?
By the way, is your book now published? is it available?
Thanks,
Kim
I am back again with one more question. I have my final index markup sorting the way I want it, but now I need to be able to insert a text break or blank line after every ten items listed as per military spec. Is there any way to do that with just FOSI, or FOSI and an ACL script, or do I need to export the index to accomplish this?
Thanks, KM
Suzanne,
Thanks for this! After a liddle fiddling, it works like a charm.
KM