PDFMaker 9 adding bookmarks to Word index markers

Hi folks,
I recently updated to Acrobat 9.5.1 and am seeing an odd, annoying problem. I use Microsoft Word 2007 to create a document with a non-standard heading style called "Message Bar." When I make my PDF, I ask PDFMaker to create a Level 3 bookmark for this style. This has worked well, without a hitch for several years.
In recent document updates, however, PDFMaker appears to be picking up the index marker that sits next to the Message Bar heading and creating a separate bookmark. Curiously enough, it also adds consecutive numbering at the front of the bookmark, so that the first "index bookmark" is 1b<Message>, the second is 2b<DifferentMessage> and so on, through the document (and there are close to 1000 of these messages). After doing that, the normal bookmarks for this style are also listed. Both bookmarks point to the same (correct) location in the PDF doc.
In the PDF preferences, the only headings/styles checked for bookmarks are Heading 1, Heading 2 and Message Bar.
As a quick workaround, I deleted all the "index bookmarks" in Acrobat Pro and moved the standard bookmarks (with no extraneous numbering) into the proper place. As we update the doc and PDF every couple of months, I hope I won't have to do this forever. Nor am I keen to move my index markers to another line (or style).
Is this a bug? Has anyone else seen something like this? Google didn't turn anything up. Appreciate any advice.

Thanks Bill, yes I've created an index in Word but the links don't convert as they do for a table of contents.
In PDFmaker, enabling Create Bookmarks, Add Links, Convert cross-references, Convert footnotes, Enable advanced tagging, and all options on the Bookmarks tab doesn't have any effect.
Word doesn't build an index in quite the same way as a ToC (in Word itself the index entries aren't bookmarked) so I'm a bit pessimistic about this feature being in PDFMaker but it'd be nice if someone could confirm this. I've only tested in Word 2003 but I doubt 2007 works differently.

Similar Messages

Problem with index markers and importing MS Word 2007 files

This was ugly in that it wasn't caught until after a book had been typeset and the index was being finalized. I'm now having to go back and manually insert a zillion index markers. Not fun.
This was my first project since migrating from FM 7.1 to FM9.0.3.
Source documents are Microsoft Word 2007. Am working in Microsoft Windows 7 64-bit.
When the Word files were imported into FrameMaker, only SOME of the index markers were imported. The difference between those that were imported and those that weren't was seemingly random.
I did some testing and found the problem and a solution.
Looking at the source Word .docx file, and displaying hidden text shows two types of index markers:
1. { XE "word to be indexed"}
2. {xe "word to be indexed"}
Note the difference in case and the extra space after the opening brace in #1. Markers of type 1 were imported fine. Markers of type 2 were stripped by the import process.
The solution:
Backsave the Word file to Word 2003 format (.doc) before importing into FrameMaker.
I backsaved to Word 2003 and imported using both the "Microsoft Word" and "Microsoft Word 2007" filters and both filters imported correctly. It's only when trying to import a Word 2007 .docx file directly that things run amok.
Grr...

Thank you for posting your solution, Dan. It's cold comfort, but I've also ran into this issue in the past, almost certainly well before Word2003 though, probably as far back as Word2000 or earlier.
In your testing, did you try saving as RTF to see if the markers were homogenized, by any chance? In my simple testing just now, Word itself recognized the index field correctly no matter whether I changed the field to "xe" or "XE", but FM's import of the .docx file format wouldn't recognize "xe", only "XE". But importing an RTF file handled both upper- and lower-case entries.
Ah, yes, that's it -- saving the Word2007 file as RTF (with 2 fields, one caps, one lower-case) changed cap field to lower-case when the RTF is opened in Word again, so saving as RTF does homogenize the fields to lower-case. Is it possible that your file(s) were changed to or saved as RTF at any point in their life-cycle? I believe some older versions of Word were actually RTF under the hood, too -- if you do Save As in Word2007 you can scroll through the File Type entries and see "Word 97-2002 & 6.0/95 - RTF (*.doc)" I believe some doc management systems change binaries to RTF too, or conversely some apps create RTF but they name the files as doc.
So Word itself recognizes either lower- or upper-case, and FM's RTF import handles both, but not the .docx import.
Sheila

How I generate index markers using Applescript and tagged text!

One of the challenges I've faced in automating the book making process using Applescript with inDesign is that there don't seem to be any AS commands for making new index markers (anyone please correct me I if I'm wrong about this).
I've tried various js scripts which do an OK job, but they don't make the actual native markers. This means you have to wait until the book (consistiing of multiple ID files) is complete (so that all the page numbers have been established) to generate the index.
Recently, I read a tweet from someone with a link to a technique which uses tagged text and find and replace with GREP to edit the tags, inserting the tagged text index tags in the text file and then re-placing the text file in the ID page. In itself, this works great. But I'm dealing with literally thousands of separate text frames, none of them connected in a story.
The books typically consist of around 1200 pages with almost that many people, each of whose names I need to index with "Lastname, Firstname" references. And those particular strings don't (can't) appear anywhere on the pages. There will also be about 50 ID files all combined into one book. So it is imperative that I have ID generate the native index markers. To help keep things straight and efficient, I'm creating separate small text frames to hold the lastname, firstname strings. I created an object style for these frames which sets the attributes to "nonprinting", and I place the frames in the margin.
Then I realized that I don't actually have to have ID export the tagged text files for each. I exported one prototype and copied its tags to properties in my script, and then I concatenate them with the respective list item values I import from the database.
At the proper point in the page building script, I tell "textwrangleer" to make a new document, set its contents to the index string for the current record, save it to disk, overwriting the previous one, and then tell ID to "place" it in the index text frame, which generates the ID index mark.
I actually got an AS error when I first tried this: "file doesn't exist" or some such. Then I realized that the "place" command was happening too soon, so I inserted a .5 sec delay in the script, and it worked.
This is actually my first major script for actual work, and I'm so excited about it! I promises to cut production time down to about a thenth of what it was.
I still have to add some logic to branch between handlers with slightly different parameters for five different page formats, but the same page building handler will work on all of them.

A note on this:
Daniel Swanson wrote:
I've tried various js scripts which do an OK job, but they don't make the actual native markers. This means you have to wait until the book (consistiing of multiple ID files) is complete (so that all the page numbers have been established) to generate the index.
These scripts typically search for words and immediately write out the page numbers they are found on -- one shot indexing.
The solution is to add both the topic and its page reference to the current document's index:
if (app.activeDocument.indexes.length == 0)
app.activeDocument.indexes.add();
app.activeDocument.indexes[0].topics.add(app.selection[0].contents).pageReferences.add(app.selection[0]);
The first lines only make sure there is an index to add to (per default, a new document has none).
The last line adds a selected word to the index (it must be a plain text string, hence the use of its 'contents'), and then adds a reference to the selection in the text itself.
Adding the same word a second time will for a change (quite untypically for ID's Scripting) not result in an error but simply add another page reference to the existing one.
When doing this in a loop: remember to work backwards, because the index marker itself gets inserted into the running text, and that will throw off your text indices.

Is there a script that will generate Index Markers based on Notes?

I need a way to generate index markers/entries within InDesign based on content that has been added in InCopy. I need this becasue InCopy users can't add Index Markers. One type of content they can add is Notes. Can I use these to generate index markers?
N.b. I have figured a way for InCopy users to add character styles to words I can then generate a simple keyword index based on these. However I now need to be able to cater for sub level topics, cross references to other topics in the index and equivalent terms, and the character style method won't suffice.
Any advice/tips on other methods to create indexes based on IC content would be useful.
Thanks
I'm using InCopy CS6 and InDesign CS6.

Me again ;-)
couldn't test with InCopy but I hope those lines will create a note if some text is selected. contents of the note = the selected text. create a shortcut to the script.
#target InCopy
try{
currSel = app.selection[0];
currContent = currSel.texts[0].contents;
newNote = currSel.parentStory.notes.add(LocationOptions.BEFORE, currSel.insertionPoints[0]);
newNote.texts[0].contents = currContent;
}catch (e){
alert(e)
changed the first script slightly. Note it's still just a example of how it could work:
var currDoc = app.activeDocument,
allStories = currDoc.stories,
l = allStories.length;
//checking for at least one existing index ...
if(!currDoc.indexes[0].isValid){
currDoc.indexes.add();
while(l--){
currStory = allStories[l];
allNotes = currStory.notes;
n = allNotes.length;
while(n--){
currNote = allNotes[n];
noteContents = currNote.texts[0].contents
//create the source
currSource = currStory.characters.itemByRange(currNote.insertionPoints[0].index, currNote.insertionPoints[0].index + noteContents.length);
currTopic = currDoc.indexes[0].topics.add(noteContents);
//this is by default PageReferenceType.CURRENT_PAGE ... changes optionally
currTopic.pageReferences.add(currSource)
currDoc.indexes[0].update();
currNote.remove();
Hope it'll be of some help
Hans-Gerd Claßen

Problem with index markers

My index markers are not recognizing page ranges when using the "to next use of style" in one of my book documents but works in all the other documents. I tried to export as IDML but it didn't fix the problem. I do notice that the marker looks different in the story editor from the ones in the other documents. I tried to delete the marker and reindex but the it didn't fix the problem and the marker still looks different.

Thank you for posting your solution, Dan. It's cold comfort, but I've also ran into this issue in the past, almost certainly well before Word2003 though, probably as far back as Word2000 or earlier.
In your testing, did you try saving as RTF to see if the markers were homogenized, by any chance? In my simple testing just now, Word itself recognized the index field correctly no matter whether I changed the field to "xe" or "XE", but FM's import of the .docx file format wouldn't recognize "xe", only "XE". But importing an RTF file handled both upper- and lower-case entries.
Ah, yes, that's it -- saving the Word2007 file as RTF (with 2 fields, one caps, one lower-case) changed cap field to lower-case when the RTF is opened in Word again, so saving as RTF does homogenize the fields to lower-case. Is it possible that your file(s) were changed to or saved as RTF at any point in their life-cycle? I believe some older versions of Word were actually RTF under the hood, too -- if you do Save As in Word2007 you can scroll through the File Type entries and see "Word 97-2002 & 6.0/95 - RTF (*.doc)" I believe some doc management systems change binaries to RTF too, or conversely some apps create RTF but they name the files as doc.
So Word itself recognizes either lower- or upper-case, and FM's RTF import handles both, but not the .docx import.
Sheila

Acrobat pdfmaker com addin for word 2010 crashes when processing large files

I am trying to use the pdfmaker com addin for word 2010 to create a PDF document. Whenever I try and create the document, the acrobat addin crashes word.
I attempted to perform this on both an x86 and x64 machine and it failed both times at around the approximately same point (during/immediately after determining the bookmarks).
The document is large (862 pages, 2425 bookmarks, 311 300dpi graphics, for a total file size of 49.2MiB)
I can generate the PDF by just printing, but the whole point of using the pdfmaker is so that we don't have to perform 2.5K of manual cross-links.
Machine information:
Windows 7 (x64) SP1
Office 2010 (x64) 14.0.6112.5000
Acrobat X Pro (x86) 10.1.3
Crash Report:
Version=1
EventType=APPCRASH
EventTime=129853934132967189
ReportType=2
Consent=1
UploadTime=129853934134215189
ReportIdentifier=4e4f5b16-c16a-11e1-ae3f-5c260a5c33cf
IntegratorReportIdentifier=4e4f5b15-c16a-11e1-ae3f-5c260a5c33cf
Response.BucketId=41559749
Response.BucketTable=4
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=WINWORD.EXE
Sig[1].Name=Application Version
Sig[1].Value=14.0.6024.1000
Sig[2].Name=Application Timestamp
Sig[2].Value=4d83e2f6
Sig[3].Name=Fault Module Name
Sig[3].Value=wwlib.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=14.0.6024.1000
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4d83e39e
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000031b4aa
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
UI[3]=Microsoft Word has stopped working
UI[4]=Windows can check online for a solution to the problem and try to recover your information and restart the program.
UI[5]=Check online for a solution and restart the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
LoadedModule[8]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161 _none_08e61857a83bc251\MSVCR90.dll
LoadedModule[9]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df _5.82.7601.17514_none_a4d6a923711520a9\Comctl32.dll
LoadedModule[10]=C:\Windows\system32\GDI32.dll
LoadedModule[11]=C:\Windows\system32\USER32.dll
LoadedModule[12]=C:\Windows\system32\LPK.dll
LoadedModule[13]=C:\Windows\system32\USP10.dll
LoadedModule[14]=C:\Windows\system32\IMM32.DLL
LoadedModule[15]=C:\Windows\system32\MSCTF.dll
LoadedModule[16]=C:\Windows\system32\nvinitx.dll
LoadedModule[17]=C:\Program Files\NVIDIA Corporation\CoProcManager\_etoured.dll
LoadedModule[18]=C:\Program Files\NVIDIA Corporation\CoProcManager\nvd3d9wrapx.dll
LoadedModule[19]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[20]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[21]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[22]=C:\Windows\system32\ole32.dll
LoadedModule[23]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[24]=C:\Program Files\NVIDIA Corporation\CoProcManager\nvdxgiwrapx.dll
LoadedModule[25]=C:\Program Files\Microsoft Office\Office14\wwlib.dll
LoadedModule[26]=C:\Program Files\Microsoft Office\Office14\gfx.dll
LoadedModule[27]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[28]=C:\Windows\system32\MSIMG32.dll
LoadedModule[29]=C:\Program Files\Microsoft Office\Office14\oart.dll
LoadedModule[30]=C:\Program Files\Common Files\Microsoft Shared\office14\mso.dll
LoadedModule[31]=C:\Windows\system32\msi.dll
LoadedModule[32]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[33]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1d f_6.0.7601.17514_none_fa396087175ac9ac\Comctl32.dll
LoadedModule[34]=C:\Program Files\Common Files\Microsoft Shared\office14\Cultures\office.odf
LoadedModule[35]=C:\Windows\system32\VERSION.DLL
LoadedModule[36]=C:\Windows\system32\uxtheme.dll
LoadedModule[37]=C:\Windows\system32\dwmapi.dll
LoadedModule[38]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[39]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[40]=C:\Program Files\Microsoft Office\Office14\1033\wwintl.dll
LoadedModule[41]=C:\Program Files\Common Files\Microsoft Shared\office14\1033\MSOINTL.DLL
LoadedModule[42]=C:\Program Files\Common Files\Microsoft Shared\office14\MSORES.DLL
LoadedModule[43]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\MSPTLS.DLL
LoadedModule[44]=C:\Program Files\Common Files\Microsoft Shared\office14\riched20.dll
LoadedModule[45]=C:\Windows\system32\mscoree.dll
LoadedModule[46]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[47]=C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPC.DLL
LoadedModule[48]=C:\Windows\system32\Winspool.DRV
LoadedModule[49]=C:\Windows\system32\SHELL32.DLL
LoadedModule[50]=C:\Windows\system32\propsys.dll
LoadedModule[51]=C:\Windows\system32\ntmarta.dll
LoadedModule[52]=C:\Windows\system32\WLDAP32.dll
LoadedModule[53]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[54]=C:\Windows\system32\rsaenh.dll
LoadedModule[55]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[56]=C:\Windows\System32\msxml6.dll
LoadedModule[57]=C:\Windows\system32\profapi.dll
LoadedModule[58]=C:\Windows\system32\SXS.DLL
LoadedModule[59]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
LoadedModule[60]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.619 5_none_88e41e092fab0294\MSVCR80.dll
LoadedModule[61]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\f73f0a9c9a83dcd3f f428be509a7992f\mscorlib.ni.dll
LoadedModule[62]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorsec.dll
LoadedModule[63]=C:\Windows\system32\WINTRUST.dll
LoadedModule[64]=C:\Windows\system32\CRYPT32.dll
LoadedModule[65]=C:\Windows\system32\MSASN1.dll
LoadedModule[66]=C:\Windows\system32\imagehlp.dll
LoadedModule[67]=C:\Windows\system32\ncrypt.dll
LoadedModule[68]=C:\Windows\system32\bcrypt.dll
LoadedModule[69]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[70]=C:\Windows\system32\USERENV.dll
LoadedModule[71]=C:\Windows\system32\GPAPI.dll
LoadedModule[72]=C:\Windows\system32\cryptnet.dll
LoadedModule[73]=C:\Windows\system32\SensApi.dll
LoadedModule[74]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\Microsoft.Education.Word.MathExtension.dll
LoadedModule[75]=C:\Windows\assembly\GAC\Extensibility\7.0.3300.0__b03f5f7f11d50a3a\Extens ibility.dll
LoadedModule[76]=C:\Windows\assembly\GAC_MSIL\office\14.0.0.0__71e9bce111e9429c\office.dll
LoadedModule[77]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
LoadedModule[78]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\Microsoft.Education.Mathematics.Common.dll
LoadedModule[79]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\c40ec0f4cd203c88029 8f94c0427dd54\System.ni.dll
LoadedModule[80]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Drawing\222eb8aa336 953a6b0216db2b0c4770d\System.Drawing.ni.dll
LoadedModule[81]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Windows.Forms\dc5bb 74eefdbf954cdfb70dd534d5564\System.Windows.Forms.ni.dll
LoadedModule[82]=C:\Windows\assembly\GAC_MSIL\Microsoft.Office.Interop.Word\14.0.0.0__71e9 bce111e9429c\Microsoft.Office.Interop.Word.dll
LoadedModule[83]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Configuration\193d0 3ca60573c92f92d9b07fa5bc243\System.Configuration.ni.dll
LoadedModule[84]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Xml\24d1b7ccbedaa36 02bae6a6acea9929e\System.Xml.ni.dll
LoadedModule[85]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\MathControls.dll
LoadedModule[86]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\MathEngine.dll
LoadedModule[87]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Shared\sqmapi.dll
LoadedModule[88]=C:\Windows\system32\shfolder.dll
LoadedModule[89]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Shared\MathRichEditNative.Dll
LoadedModule[90]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Shared\mathenginen.dll
LoadedModule[91]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\MathResources.dll
LoadedModule[92]=c:\Program Files\Common Files\Microsoft Shared\VSTO\vstoee.dll
LoadedModule[93]=C:\Windows\system32\urlmon.dll
LoadedModule[94]=C:\Windows\system32\iertutil.dll
LoadedModule[95]=C:\Windows\system32\WININET.dll
LoadedModule[96]=C:\Windows\system32\Normaliz.dll
LoadedModule[97]=c:\Program Files\Common Files\Microsoft Shared\VSTO\10.0\VSTOLoader.dll
LoadedModule[98]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.616 1_none_08e61857a83bc251\MSVCP90.dll
LoadedModule[99]=C:\Windows\system32\oledlg.dll
LoadedModule[100]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[101]=C:\Windows\system32\MSVCR110_CLR0400.dll
LoadedModule[102]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\ec4aeb1a93320223 07604cba8284778b\mscorlib.ni.dll
LoadedModule[103]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\52974bd8d9753cf71a 27181621dcf4eb\System.ni.dll
LoadedModule[104]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\a4252f50e54a5 d2987e41709da9a117a\System.Core.ni.dll
LoadedModule[105]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.V28a60cc2#\f165 482199ea49be235ec53ad93e6889\Microsoft.VisualStudio.Tools.Office.Runtime.ni.dll
LoadedModule[106]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O5949707a#\6d99 2851fc846eac2e388d2348711376\Microsoft.Office.Tools.ni.dll
LoadedModule[107]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.V883708cb#\bc02 fe4c18b7e176e9bee4c72ff4cb32\Microsoft.VisualStudio.Tools.Applications.Runtime.ni.dll
LoadedModule[108]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.V1955d7fd#\cc04 39da7e5347e89d6586ce262c1f69\Microsoft.VisualStudio.Tools.Applications.ServerDocument.ni.d ll
LoadedModule[109]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.Vf9a08577#\86f6 f20538156d2008fff97542e09765\Microsoft.VisualStudio.Tools.Applications.Hosting.ni.dll
LoadedModule[110]=C:\Windows\system32\Secur32.dll
LoadedModule[111]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[112]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\1204d7ae7e 0e637669e244a02b97983b\System.Drawing.ni.dll
LoadedModule[113]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\d7d8 56d242ddc80d696aa425195e5252\System.Windows.Forms.ni.dll
LoadedModule[114]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\nlssorting.dll
LoadedModule[115]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Deployment\475303e 370c565f47cd7d159485f24d9\System.Deployment.ni.dll
LoadedModule[116]=C:\Windows\system32\dfshim.dll
LoadedModule[117]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\0523 c17527d811bdc9606a0c62145f3d\System.Configuration.ni.dll
LoadedModule[118]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\771d4e20776373 ee95d2058b4d3f20a8\System.Xml.ni.dll
LoadedModule[119]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Security\819aca5f3 26d35ce5f478c20366d0f5c\System.Security.ni.dll
LoadedModule[120]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml.Linq\76b84571f 4497227f40c72e246939ac0\System.Xml.Linq.ni.dll
LoadedModule[121]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.Oab3f8ec6#\0a3a f5db2975c482e98e96c99bb938af\Microsoft.Office.Tools.Word.Implementation.ni.dll
LoadedModule[122]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O4a946565#\a550 db8b700051717681470a0b2b07d3\Microsoft.Office.Tools.Common.Implementation.ni.dll
LoadedModule[123]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O854200f9#\a3df 0bec1a202ce176b839f788d40f44\Microsoft.Office.Tools.Common.ni.dll
LoadedModule[124]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.Oeab01fba#\9d47 6070258253869ff6ca2201f33b54\Microsoft.Office.Tools.Word.ni.dll
LoadedModule[125]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O2eb0cc9a#\3994 dd35eb969eb2221f1886598f08cc\Microsoft.Office.Tools.v4.0.Framework.ni.dll
LoadedModule[126]=C:\Users\kking\AppData\Local\assembly\dl3\D5O6KVBP.4TZ\YDKV3YJ1.QPK\2fd1 b7b3\d265be4b_e524cd01\PCREFindAddIn.DLL
LoadedModule[127]=C:\Users\kking\AppData\Local\assembly\dl3\D5O6KVBP.4TZ\YDKV3YJ1.QPK\21e1 fe8e\00b3e430_67b7cb01\Microsoft.Office.Tools.Common.v4.0.Utilities.DLL
LoadedModule[128]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[129]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFMOfficeAddin.dll
LoadedModule[130]=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Visual Studio Tools for Office\x64\VSTOWordAdaptor.dll
LoadedModule[131]=C:\Windows\system32\MSVCR100.dll
LoadedModule[132]=C:\Program Files (x86)\Microsoft Visual Studio 11.0\Visual Studio Tools for Office\x64\VSTOWordAdaptor.dll
LoadedModule[133]=C:\Windows\system32\MSVCR110.dll
LoadedModule[134]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\USP10.DLL
LoadedModule[135]=C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL
LoadedModule[136]=C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\1033\VBE7INTL.DLL
LoadedModule[137]=C:\Windows\assembly\NativeImages_v2.0.50727_64\stdole\be0906e176cf1f8ed8 1084df7042ee1c\stdole.ni.dll
LoadedModule[138]=C:\Windows\system32\explorerframe.dll
LoadedModule[139]=C:\Windows\system32\DUser.dll
LoadedModule[140]=C:\Windows\system32\DUI70.dll
LoadedModule[141]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7 601.17825_none_2b253c8271ec7765\GdiPlus.dll
LoadedModule[142]=C:\Program Files\Microsoft Office\Office14\msproof7.dll
LoadedModule[143]=C:\Program Files\Microsoft Office\Office14\MSOHEV.DLL
LoadedModule[144]=C:\Program Files\Microsoft Office\OFFICE14\PROOF\1033\MSGR3EN.DLL
LoadedModule[145]=C:\Windows\system32\MPR.dll
LoadedModule[146]=C:\Windows\System32\drprov.dll
LoadedModule[147]=C:\Windows\System32\WINSTA.dll
LoadedModule[148]=C:\Windows\System32\ntlanman.dll
LoadedModule[149]=C:\Windows\System32\davclnt.dll
LoadedModule[150]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[151]=C:\Windows\system32\wkscli.dll
LoadedModule[152]=C:\Windows\system32\cscapi.dll
LoadedModule[153]=C:\Windows\system32\netutils.dll
LoadedModule[154]=C:\Windows\system32\SFC.DLL
LoadedModule[155]=C:\Windows\system32\sfc_os.DLL
LoadedModule[156]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Csi.dll
LoadedModule[157]=C:\Windows\system32\WINHTTP.dll
LoadedModule[158]=C:\Windows\system32\webio.dll
LoadedModule[159]=C:\Windows\system32\PSAPI.DLL
LoadedModule[160]=C:\Windows\system32\WS2_32.dll
LoadedModule[161]=C:\Windows\system32\NSI.dll
LoadedModule[162]=C:\Windows\System32\netprofm.dll
LoadedModule[163]=C:\Windows\System32\nlaapi.dll
LoadedModule[164]=C:\Windows\system32\srvcli.dll
LoadedModule[165]=C:\Windows\System32\npmproxy.dll
LoadedModule[166]=C:\Windows\system32\HLINK.DLL
LoadedModule[167]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[168]=C:\Windows\system32\WINMM.dll
LoadedModule[169]=C:\Program Files\Microsoft Office\OFFICE14\PROOF\MSSP7EN.DLL
LoadedModule[170]=C:\Program Files\Microsoft Office\Office14\mscss7en.dll
LoadedModule[171]=C:\Program Files\Microsoft Office\Office14\css7Data0009.dll
LoadedModule[172]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFMWord.dll
LoadedModule[173]=C:\PROGRA~2\Adobe\ACROBA~1.0\PDFMaker\Common\X64\ADOBEP~1.DLL
LoadedModule[174]=C:\Windows\system32\COMDLG32.dll
LoadedModule[175]=C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[176]=C:\Windows\system32\apphelp.dll
LoadedModule[177]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[178]=C:\Windows\system32\EhStorShell.dll
LoadedModule[179]=C:\Program Files (x86)\Google\Drive\googledrivesync64.dll
LoadedModule[180]=C:\PROGRA~1\MICROS~1\Office14\GROOVEEX.DLL
LoadedModule[181]=C:\Windows\WinSxS\amd64_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.61 61_none_0a1fd3a3a768b895\ATL90.DLL
LoadedModule[182]=C:\PROGRA~1\MICROS~1\Office14\1033\GrooveIntlResource.dll
LoadedModule[183]=C:\Windows\System32\cscui.dll
LoadedModule[184]=C:\Windows\System32\CSCDLL.dll
LoadedModule[185]=C:\Windows\system32\ntshrui.dll
LoadedModule[186]=C:\Windows\system32\slc.dll
LoadedModule[187]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[188]=C:\Windows\system32\actxprxy.dll
LoadedModule[189]=C:\Program Files\Internet Explorer\ieproxy.dll
LoadedModule[190]=C:\Windows\system32\thumbcache.dll
LoadedModule[191]=C:\Windows\system32\SHDOCVW.dll
LoadedModule[192]=C:\Windows\system32\ieframe.DLL
LoadedModule[193]=C:\Windows\system32\OLEACC.dll
LoadedModule[194]=C:\Windows\system32\SearchFolder.dll
LoadedModule[195]=C:\Windows\System32\cscobj.dll
LoadedModule[196]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\ACE.DLL
LoadedModule[197]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AGM.DLL
LoadedModule[198]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\BIB.DLL
LoadedModule[199]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\BIBUtils.DLL
LoadedModule[200]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\Cooltype.DLL
LoadedModule[201]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\JP2KLib.DLL
LoadedModule[202]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\ARE.DLL
LoadedModule[203]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AdobePDFL.dll
LoadedModule[204]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AdobeXMP.dll
LoadedModule[205]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AXE8SharedExpat.dll
LoadedModule[206]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFMEngine.dll
LoadedModule[207]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\pdfsettings.dll
LoadedModule[208]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\MPS.dll
LoadedModule[209]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFPort.dll
Sec[0].Key=LCID
Sec[0].Value=1033
Sec[1].Key=skulcid
Sec[1].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=41559749/nBucketTable=4/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Word
AppPath=C:\Program Files\Microsoft Office\Office14\WINWORD.EXE

I recently ran into this with a bitmap in a 265 page document. I copied the bitmap to IrfanView and then back (I think that was the step -- I am already forgetting) and the copied it back. The problem went away. My student may look a bit more at the file -- I asked so I could give a more definitive comment here.
The result I had suggests that it is a problem in WORD or the bitmap that WORD was using. Why WORD can deal with it and not Acrobat, I am not sure. However, when printing to the Adobe PDF printer there was not a problem, just with PDF Maker.

Broken PDF Bookmarks from Word doc with Headings

This used to work with older versions of Acrobat Pro (I have the latest version of Acrobat 8 pro). I just author a Word doc which has headings, and then I use the Acrobat menu in Word to create the PDF, making sure "Create Bookmarks from Word Headings"is selected.
The resulting PDF does indeed have the PDF Bookmarks there correctly, but they do not point to the locations of the headings in the actual document. In other words, they're not really bookmarking anything.
Can someone confirm the workflow that is supposed to ensure the bookmarks will actually point to the heading locations? What else could be wrong?
Thanks in advance! Attaching source word file (rename xml extension to docx) and resulting PDF file.
SK

Thanks Bill. I am using 8.1.4, and Word 2007. Don't really want to downgrade though (it's been around for several years now). One thing I've been wanting to try is re-installing to the latest PDFMaker COM Add-in (PDFMOfficeAddin.dll), but I don't know how to. The add-remove programs doesn't seem to allow me to re-install individual components.
Just to confirm, the PDF bookmarks are meant to point to the Word heading locations, correct? I was wondering if you could try converting the Word file (just rename the .xml extension to .docx), and looking at the resulting PDF bookmarks. If they work as expected for you, then it's definitely something about my particular system configuration.
The Word headings to PDF bookmarks feature is so basic, and Word 2007 has been around for several years now, if there was a problem with it I'm sure there would be a fix from Adobe by now.
Thanks for any further insights!
SK
PS - Are other people experiencing the issue I am running into? Trying to gauge if this is a common problem...

X-refs and index markers in absolute paths don't work

A problem has arisen that did not exist before:
If I have added files to a book using an absolute path, all X-refs and index markers in those files then don't work. The index *generates* without trouble, but if I then try to Alt-click an item in the index that refers back to a file with an absolute path I get the error "Cannot find the file named X. Make sure the file exists." This also means, of course, that the corresponding hyperlinks in a generated PDF file also don't work.
X-refs and index markers in files added using *relative* paths work okay.
What is wrong?
(I use FM9 / Windows 7.)
Regards,
Knut Högvall

Hi Michael,
Yes, I use 9.0p255.
No, the files don't have to be on different volumes. They can even be in the same folder (not that they are, but they *could* be; they are in fact in separate folders, but on the same volume). What matters is how I select the file in the File dialog box when I add the file to the book. To get an absolute link, I first click the Network button, select the top volume, and then navigate down to the file. The absolute path is displayed in the book window as \\<volume>\folder\file.fm" while a relative path is indicated by "..\..\file.fm".
If I add a file using an absolute path it doesn't work; if I add the exact same file using a relative path, it works.
How do I check the hypertext content in the index?
Regards,
- Knut

FM save as RTF -- how to keep index markers?

I have to export an FM book with a comprehensive index (from index markers) to word-processor files for the author to update for a new edition. But when I open the RTF in Word, there are no index markers. Curiously, I've done this before, and can't recall having any difficulty. Am I missing something obvious?

What's puzzling me is that I've done this before: I'm looking at Word documents from a book exported from FM with all the index markers present. I did this in February 2008, and can't remember that I'd had any problems doing it, so I assumed that it had been just a simple Save As.
But now it seems I must've done it via some workaround. I agree that mif2go will probably do it, but I'm not keen to buy it for a one-off job: I haven't got mif2go, but I have got Ixgen (http://www.fsatools.com/), and one option that seems likely to work is to use Ixgen to expand index markers to text (with a specific character format); then save as RTF; then, in the word processor, convert that text to index markers.
(It's a bit of a drag, but better than having to redo three indexes — subject, cases, statutes — when the edited docs come back to me.)
Any better ideas?

How can I assign index markers to a list of names coming from Excel

I have to build up indexes on directories. The list of names comes from Microsoft Excel and is saved as a text file. I need to assign index markers to the list (sometimes up to 2000 names) so I can build up an index after the layout is done.

Indesign cs6
On Thu, Feb 19, 2015 at 11:07 AM, John T Smith <[email protected]>

How do I bookmark a word in Pages5?

I used to be able to bookmark a word anywhere in the document and create a hyperlink to that word from some other place in the same document. I used to use Inspector to do this in Pages 4. I don't see those options anymore in Pages 5 (or, am I missing them?). Please help me with this. I created a whole bunch of bookmarks and hyperlinks in my documents but most of them are not working with the new version of Pages. Please help.

Bookmarks are one of many, many useful features removed in this "upgrade." The only help available is to remove PAges 5.0 from your computer and use 4.3

Safari 5.1 in iMac OS X 10.6.8.Adding Bookmarks to "unsorted Bookmarks" folder puts them in a black hole. I can't find the "UB" folder. Where is it? Should I add it to the folder list somewhere on the left pane? OR? Help, please!

Safari 5.1 in iMac OS X 10.6.8.Adding Bookmarks to "unsorted Bookmarks" folder puts them in a black hole. I can't find the "UB" folder. Where is it? Should I add it to the folder list somewhere on the left pane? OR? Help, please!

It looks like that the installation process of one of the applications have caused some trouble. One of them may have changed or added kext files.
For that, the Window server crashed if you try to open a non Apple application like Firefox
Start the system in safe mode by holding the shift key on power on.
If save mode is reached, perform a permissions repair with the Disk Utility.
Don't bother about upcoming warnings like "could not repair file xy" as that occur cause you use the tool on a running system and opened files can not get touched by the tool.
After repair is done reboot system to normal and try to open Firefox.
If the problem persits, please report back here.
Lupunus

Pdfmaker not working in word 2007

Hi guys
I'm an IT Technican in college. A guy in marketing department has problem with pdfmaker add-in in office word 2007.
I logged in as administrator and there was pdfmaker button in word 2007, but when he logged in, he doesnt have the pdfmaker button in word 2007.
i checked addin tool, on his account, his is disabled but whenever i try to enable it.
the message comes up saying -
"this addin is installed for all users on this computer, and can only be connected or disconnected by an administrator"
BUT on my account (administrator) the addin is already enabled.
what even more strange. on his account, rest of office 2007 applications (excel, powerpoint etc) have the pdfmaker button, but not word 2007.
how to fix the problem?
adobe is fully up to date.
cheers
wesley

Disable settings in Office are per user basis, so it can happen that it is disabled for the user and not for you.
How did you try to enable it ? did you use the dialog that comes up by Word Options>Add-ins>Disabled Items>Go

I want to import a MS Word Index into a .pdf file using Adobe Pro. How do I do that?

I want to import a MS Word Index into a .pdf file using Adobe Pro. It is for a book. The book has been converted to a .pdf for printing, but it needs an Index for the last page of the book. I tried to embed a new index (starting from scratch but no luck. Any suggestions? Thank you for your time.

Now I want to search this "myArrayStrings.get(r)" in another file. How to do that?Store the returned String. Do the same thing you did to read the first file to read the second file (i.e. read it in line-by-line and store the lines in a list). Then check if that list contains the String you stored from the first list.
E.g. (using your code):
String name = myArrayStrings.get(r); // assuming r is initialized somewhere before this
if ( otherList.contains( name ) ) { // assuming otherList is your second list
// do something
}

Need script to export Indesign to word and keep word index codes

Hi,
I have a document and the index was created by importing word docs with indexentries. Now the client wants to revise the book and wants the text converted back to Word, but he wants to keep the orginal word index codes. Is that possible? Exporting as tagged text results in showing the index codes, but also much other codes which are not needed.
Would be greatfuull for some tips, or preferable a script that does the trick.
kind regards
Peter
Indesign cs5.5 Imac 27 inch. Max osx 10.7.4 language Dutch

designer1955 wrote:
Exporting as tagged text results in showing the index codes, but also much other codes which are not needed.
What were you going to do with this Tagged Text file? That's only good for re-importing it back into InDesign.
Anyway, it doesn't require a script at all. I had the clever idea of testing this, and indeed: index entries in InDesign are exported in RTF.

PDFMaker 9 adding bookmarks to Word index markers

Similar Messages

Maybe you are looking for