nisus.com

I'm using Nisus Writer Pro 2.0.2 on a Mac OS X (10.7.2).

After numerous trials, I face the following problems:

1. The Page numbers in the TOC entries do not correspond to the actual pages in the document.

2. So, I have to "rebuild the TOC" multiple times in order to get at least some entries to refer to the actual pages in the document.

3. Then when I generate a PDF, the pages are totally off.

What am I doing wrong? What are the actual steps, one by one, to generate a TOC, INDEX, and a PDF?

Kindly explain.

Thanks!

A generated TOC's page numbers should be correct whenever you choose to update the TOC manually, or be automatically updated if you make a PDF/printout.
A generated Index's page numbers are only updated when you choose to update the Index manually.

It sounds like this isn't true in your document, and your TOC's page numbers are incorrect, even after updating the TOC or making a PDF. Would you be able to share your file with us privately for testing? Hopefully we'd be able to reproduce the problem, and diagnose it, or offer a workaround.

I sent a copy of my document last night to "Nisus Support," and have been eagerly waiting for a solution!

Thanks!

Would the Tech Support / Web Support people kindly be in touch with me so as to inform me about what's going on with a copyrighted manuscript (300+pages) I sent to them without knowing anyone on the team!

It feels really odd that a Tech Support team would take so much time even to be in touch with a dismayed customer!

Thanks and regards,
rajam

Any progress on resolving my difficulties? Kindly let me know. Thanks!

rajam

Rajam wrote:Would the Tech Support / Web Support people kindly be in touch with me so
...
It feels really odd that a Tech Support team would take so much time even to be in touch with a dismayed customer!

When you wrote tech support on April 23rd, we replied to you immediately (twice that same day actually). Then a few days later (April 25th), when you wrote again, we again replied that very same day, informing you that we were still investigating your issue.

I'm very sorry you've run into trouble with one of our product's features, but I don't feel that characterizing our responses as taking "so much time" or not "in touch" is accurate.

what's going on with a copyrighted manuscript (300+pages) I sent to them without knowing anyone on the team!

We always treat any files submitted to us with the utmost respect, and never share or retain them without the author's permission. However, to be clear, we are not holding any of your copyrighted material. We provided you with a redaction macro that scrambled your document's text completely, with no way to recover it. That scrambled gibberish text luckily reproduces your original issue, which we're still investigating.

Please be patient. We may yet arrive at a solution for you, and will write you back directly when we discover whether we can offer you a workaround or not. Thank you.

That's very kind of you for the response, and thanks!!

I hope a positive solution would be obtained as soon as we all can hope for!

It would help me if the Tech Support team or someone else from out there would keep me informed on a daily basis, so I don't have to be more anxious than ever. It's just a customer's paranoia, as you can imagine!

Thanks much!

Rajam wrote:That's very kind of you for the response, and thanks!!

I hope a positive solution would be obtained as soon as we all can hope for!

It would help me if the Tech Support team or someone else from out there would keep me informed on a daily basis, so I don't have to be more anxious than ever. It's just a customer's paranoia, as you can imagine!

Thanks much!

Just a thought.

Martin has responded far more adequately and graciously than most software support teams I have ever witnessed in 23 years of computer work (17 with Nisus). Then to ask them to keep you informed on a daily basis seems unrealistic and presumptuous at best and even a little rude. Try that with any other software company. Nisus delivers and has demonstrated that. It seems wiser to let Nisus fix the problem and be assured that they will immediately let you know when the issue is resolved, as has been their practice.

I'm truly sorry -- I didn't realize that my *anxiety* would be misunderstood as being "rude."

Would it be alright if I ask politely ... if there's any update on the situation of my manuscript? Is there a workaround or something else to help me get this manuscript in a publishable form, so I can send it to potential publishers? Thanks much!

Rajam wrote:I'm truly sorry -- I didn't realize that my *anxiety* would be misunderstood as being "rude."

Would it be alright if I ask politely ... if there's any update on the situation of my manuscript? Is there a workaround or something else to help me get this manuscript in a publishable form, so I can send it to potential publishers? Thanks much!

We can understand being anxious about an issue that is important to you. Thank you for asking politely, and for your patience. It's been some time since we last communicated with you, so an update is in order.

Last I checked we could reproduce your problem, and it seemed to be some kind of complex interaction between various elements in your document (eg: footnotes, TOC, etc), but we hadn't isolated the exact factors. In that kind of situation we try to see if we can't narrow the problem down, not only for our own sake (to make reproducing/fixing the issue easier), but also so we can offer you a workaround that avoids the trigger. I'll see if we can't come up with a workaround by the end of this week, or at least let you know that you'll have to wait for a fix and product update.

Hi Rajam,

We've finally finished a deeper investigation and here's what we found: the problem is caused by an interaction between widow & orphan control and footnotes. Obviously this is something we need to fix, and we've filed an isolated bug on it.

In the meantime, you should be able to get a TOC with correct page numbers if you don't mind disabling window & orphan control. Please take these steps:

1. Switch to the document's stylesheet, select the "Normal" paragraph style, and turn OFF the "prevent widows/orphans" option.
2. Switch back to Page View.
3. Some of the TOC content is stale (eg: the headings no longer appear in the document at all), so fully rebuild the TOC:
3a. Choose the menu "Rebuild TOC" (either from the Tools menu, or the contextual menu).
3b. From the rebuild dialog, select the "update all content" mode, and then rebuild.
4. Save and reopen the file to clear state and get fresh layout.
5. Save a PDF.

The PDF generated should have all TOC page numbers correctly updated. I hope that helps and works for you for now.

Oh, thank you for your kind response! I'll try the method you have suggested, and will let you know how it worked. Thanks again!

Glad to see this working out for you, Rajam. Martin and the team are great about support, as you can see. Wish you well on the final solution.

Unfortunately, the workaround suggested here didn't solve my problem. The bug is deeper/complex than what it seems to be. I'm still debugging. I'll let you know if/when I arrive at a resolution. Meantime, thanks much for your help.

Hi Rajam- that's a pity to hear. When we were experimenting with the redacted/test document you sent us, the steps above produced a PDF whose TOC page numbers were correct. Please be sure you go through all the steps in the exact order given, and don't take any other actions between the steps.

Of course, it's possible that your unredacted document behaves differently. If you're willing to send us the unredacted document, I can promise to delete it immediately after testing (and perhaps sending you a PDF copy). You could email the file to me directly at: