Link problem in FP converted from Word doc

When I create a Flashpaper SWF from MS Word document and I
create links in the Word document, the specified link target ("New
Window") is ignored. The link loads into the same browser window
and displaces my page.
Any solutions to this dilemma?

I have the exact same problem making this software completely
useless but it appears only when embedded in an html page.

Similar Messages

  • Converting from word doc does not save pictures or links

    Hi,
    I have word 2000 and I can convert a text word doc into flash
    paper and a pdf but when I put a picture in the word doc with a
    hyperlink on the picture and convert to flash paper or a pdf it
    looks like it is converting but when I open up the flash paper or
    pdf file the picture with the hyperlink is never there.
    What am I doing wrong or is word 2000 too old?

    Hi again!
    I just reinstalled word and now the picture will print to
    flashpaper or a pdf but when you put the hyperlink on the picture
    nothing will print so now I know it is the hyperlink that is the
    problem.
    Anyone know why the hyperlink makes it to not print?

  • Links breaking when converting from word docs to PDFs in Acrobat X Pro

    I have experienced this same problem when trying to convert word documents to PDFs in Preview:
    For hyperlinks that are active in MS Word (2011 version for Mac), but take up more than one line (they include a line break), the same links in the converted PDFs will only recognize the first line of text in the hyperlink (the hyperlinks in the docs I need to convert are the full URLs that are also hyperlinks to the same URL). As a result these links open a URL that is shortened and doesn't exist.
    Is this a common problem, and is there a way have the full links be recognized automatically when converting to PDFs?
    I have been able to get around this so far by creating the "invisible rectangle" links in Acrobat behind where the full link should be, but it is painstaking for large docs with many links.
    Any help would be much appreciated!
    Cheers,
    Tim

    Afraid not
    This is an Old Problem that has been banted about since Acrobat has existed. We have two companies that are blaming each other for the Problem Adobe and Microsoft. Instead of Blaming each other Adobe needs to get their head  out of their back side and fix the problem. I mean 15 years is enough to do blaming.
    You can take the same PDF's with links created Mac Office  Document and open in Office for PC and create  the PDF and it works in Acrobat. Or you can create the PDF in MacOffice and open in Acrobat PC and it works. So the problem is squarely with Acrobat. But they refuse to fix it.
    You might download and try PDFPen Pro and see if  can create working Links in it. or a Utility called CUPS-PDF. CUPS-PDF installs a Print Driver Much Like Acrobat Use to.
    You go to it to create the PDF. It is sent to a special folder. and the PDF are named with number appended to begining (example: Job_1TheMoon.docx.pdf).  Rename as desired and open may have links.

  • Very STRANGE problem when importing/converting from Word

    I've been trying to convert a form created in Word XP to PDF. When I use the "Convert to Adobe PDF" button or when I try to import the document into Adobe Designer, every line of the form, whether text box or form field, is overlaid with a copy of the screen banner (for example, the current banner as I type this is the Firefox logo followed by "Adobe Forums - Add Discussion - Mozilla Firefox"). I can't grab the banner image to delete it. At best, the image is barely translucent, so I can almost read the text that should be visible. At worst, the banner is so dark it completely obscures the other text.
    Right now, the form is completely unusable. It also can't be opened again, once it's closed. The Acrobat Pro 7 error message says that's either because it's not a supported file type (it's a PDF now) or because it's "damaged."
    Any ideas how I can either get rid of these images or keep them from showing up?

    > To Urami: Some of us hate newsreaders. Agreed, the web
    based Adobe forums are
    > pathetic and slow. But newsreaders are not for everyone:
    yet another program
    > running on the desktop, when people edit their posts
    you're not assured of
    > seeing the edited versions, and most are simply ugly
    interfaces that are not
    > comfortable to browse through. Please don't criticize
    anyone for bumping a post
    > or not using a newsreader. Chances are that someone has
    the perfect answer for
    > Nemesis, but doesn't obsessively check the forum every
    day (and happens to also
    > dislike newsreaders), and will have missed seeing it on
    the top page. I don't
    > find the bumping rude at all.
    It's not about "like" or "not like", it's about following
    common code of conduct of
    this forum specified by the posting guidelines, to which by
    the way you agreed upon
    singing up in here.
    Secondly, regardless your personal feeling on the topic, it
    simply works against you
    whether you like it or not. Regular forum participants will
    ignore bumped posts,
    bottom line just to prove that pushing your way while others
    wait nicely in the queue
    is plain rude. All posts are equally impotent and equally
    urgent, it's rather arrogant
    to climb your way back just so you can get answer faster.
    So go ahead, bump away...tho, don't ***** about no body
    entertaining your questions
    but before you do that, familiarize yourself with posting
    guidelines and general forum
    ethics.
    http://www.adobe.com/support/forums/guidelines.html
    the "Don't..." section, topic "Don't 'bump' post."
    Best Regards
    Urami
    <urami>
    If you want to mail me - DO NOT LAUGH AT MY ADDRESS
    </urami>

  • Convert from word .doc file to pages and pages to .doc.

    When I save a pages document in word the formatting is hopelessly changed. I am writing a book and reformatting 400+ pages is not fun. PDF save is not appropriate because I send bits to folks using word. When the formatting is messed up, they have no idea what it actually looks like.
    And of course the reverse is true. When I edit a piece created in word, pages changes the formatting creating hours of work. Are there any solutions to this?
    If I had windows resident w/word would I still have the same issue? No reason to have windows on the Mac otherwise.
    PS: Open office has the same issue.

    Thanks for the input. I spoke to Apple about the issue and they said if I need to share documents with non-Pages using people, and wanted them to see what I see, my only choice is Word. They stated there is and will never be any 'fix' for the issue and I said, well, guess I have to stop using Pages.
    PDFs are great for the finished product but you can't make changes to them and I need my editor to see what I see and make appropriate changes. This is not a font issue, it is about spacing, indentations, images and margins.
    It is worse for my career coaching clients. A simple example: Their Word created Two page Resumes opened in Pages scroll to three or four even when they use Arial or other common font.
    And why Pages crashes 15 times in an hour? No idea... Reload the application. Of course I did. That's not a fix. Well, it must be your documents then. And the finger points where?
    For book writing purposes, Pages offers wonderful layout and easy formatting solutions. They just don't translate to Word making Pages useless except for stand-alone documents I can send as PDFs. And readers, be clear, when I purchased the MacBook Pro and Pages, I clarified how I would use it and that I needed to work between the two products. "Oh, yes, that's simple," said the eager sales dupe.
    What a waste. I am now stuck editing my books myself which any author can tell you is a fool's errand. Back to the keyboard....

  • Hypertext links are not always preserved from Word to PDF, using Aperçu or Adobe, depending on OS 10 or Lion. Why? This generally works perfectly in Windows. Why are Apple and Adobe unable to correctly handle links when converting from Word to PDF?

    Hypertext links are not always preserved from Word to PDF, using Aperçu or Adobe, depending on OS 10 or Lion. Why? This generally works perfectly in Windows. Why are Apple and Adobe unable to correctly handle links when converting from Word to PDF?
    Depending on the system version, and Office Word version:
    - a pure URL link starting with http or even www sometimes works in PDF, either produced by Aperçu or Adobe, sometimes does not work;
    - other kind of links where the text under display is not a URL, never work!
    I like everything with Apple computers and software, except PDF generation. Output files are usually bigger in size, and no better quality, than under Windows. Furthermore, it is weird that something as common as hyperlinks does not work correctly!
    I related this question with Mac OS X Snow Leopard, but the problem is still there with Mac OS Lion.
    This problem seems to have been around for years, without any proper solution from Apple and/or Adobe! To me, this is very embarrassing!

    Greetings NoNameGiven,
    If I understand the problem correctly (I’m not sure I do) you would prefer ‘iii’ to be read as “eye eye eye” rather than “three”? The alt text property is the only way that I know of to make this happen. Hope this helps.
    a ‘C’ student

  • I have two pdf docs that I used Acrobat to convert to word docs.  How do I extract one page from one doc to insert into the other doc?

    I have two pdf docs that I converted to Word Docs using Acrobat Pro.  How do I extract one page from the first doc and insert it into the second doc?  When I "select all" it grabs the entire document.  I need to take pages out, put other pages in, and edit some of the text.

    HI djlarp,
    Try triple-clicking in the text that you want to select--it can sometimes be tricky to select text in a converted document. If that doesn't work, it could be that the PDF document was created from a scanned document, and OCR wasn't enabled when you converted the document. (However, OCR is enabled by default when you convert via the ExportPDF website.)
    If you're unable to select text by triple-clicking, let us know. I would be happy to take a closer look at your files.
    Best,
    Sara

  • Abobe v8: Problems with converting from word 2003 to PDF

    I use one of those free conversion tools, since i am a student. My problem is that i have a word document with a unique page margin. When i convert from word 2003 to pdf everything gets converted except the page margin which is much bigger then it's supposed to be. Do anyone know how i can fix that?, any help are appriciated.
    Kindly Erik

    You cannot fix anything in Reader. If you have a problem with the tool
    used to create your pdf, please ask in their forum.
    Mike

  • Hello, is there a way to redact a word or item from a pdf using adobe pro X the same way you can if you convert a word doc using pro X on a pc?

    hello, is there a way to redact a word or item from a pdf using adobe pro X the same way you can if you convert a word doc using pro X on a pc?

    If the document is not a scanned image or protected from editing then you should be able to edit it. I would have to guess you have a scan and when you converted to Word, you ran OCR (Optical Character Recognition) on it converting the scanned image to live text.
    This is the forum for the free Adobe Reader which can not edit or redact.

  • Acrobat Pro 8.1.2 crashes when displaying pdf made from Word doc containing url text

    Hello,
    I and a few others in my workplace have a similar issue.
    Acrobat crashes when they scroll through and view a pdf file that was created from Word.  The Word document contains url text in its header to the effect of "visit us at www.blah.com ." They're running Acrobat Pro 8.1.2 and Office 2K Pro SR-1 on XP Pro SP2.
    Even though the link is not an active link, (i.e. clicking on it does not open the web page), if I convert a document containing this header to PDF, Acrobat will not allow me to manipulate the file and will crash. When I take the same document and remove the web address, then convert from Word to PDF, I experience no problems with Acrobat (note that this is the identical file, but with the web address removed).This does not explain why Acrobat will work for awhile even with the web address in the header, then stop working. But it does appear to fix my problem with creating a PDF from Word, then manipulating it further.
    Does anyone know how to allow for this text to exist in the header and still have a stable pdf file/acrobat behavior?
    The pdf is attached.
    Thanks....

    To sum up, I've found that if a url beginning with www is in the Word document and then created to pdf Adobe will crash when viewing that pdf.  If it is deleted from the Word document before creating the pdf, Acrobat will not crash when viewing that pdf.

  • From Word DOC to Acrobat PDF... borders and lines get screwed up.

    I've been looking this up for days now and have yet to find a solution.
    I have a MS Word document that has a bunch of tables with borders and sometimes just text with borders for stylistic reasons. In Word, it all looks perfect.
    But, when I convert it to PDF using Acrobat, many of those borders get screwed up in various random ways.
    Sometimes certain borders get thicker, sometimes thinner, sometimes invisible altogether. Sometimes it's only certain lines of the same border (just the left side, or just the top). I see no real pattern to what's causing it to only happen in certain cases only.
    What makes it extra annoying is that if I zoom in or out a certain amount, the borders will look the way they are supposed to look. Some will look perfect at 100% zoom only, and some will look perfect at 75% zoom only.
    This has been driving me insane. Does anyone have any idea how I can fix this?
    Any help would be greatly appreciated.

    Converting Word (table) to pdf - lines screwed up - googled as far back as 2004.
    BUG STILL exists. HELP/FIX PLEASE?
    http://www.pcreview.co.uk/forums/missing-table-lines-conversion-pdf-t878406.html
    http://forums.adobe.com/thread/305508 
    Trying to convert any word doc with tables (& shading) to PDF
    - basic table, black borders throughout
    - shaded headings, black outline border
    - shaded subheadings, black outline border 
    However when convert to PDF:
    - 'displays' NO top cell border for some/all shaded rows
    - shows diff thickness lines
    - each conversion, diff lines missing/incorrectly sized
    - however converted pdf prints perfectly fine 
    Adobe know about the bug, per PRMW's (Paul's) post on 2009-07-15 15:44:34, however only offered a painful time consuming workaround using non-freeware Adobe Pro:
    http://acrobatusers.com/forum/pdf-creation/word-pdf-table-lines-missing-or-faded#comment-7 8139
    - "It is not feasable to edit 200+ tables in the PDF every time the PDF is generated, as we maintain the original in word.
    - "This complete issue seems to have been passed off by Adobe as no problem and that there is a work around. I consider this an unsatisfactory response from a major product supplier. 
    Microsoft TechNet & NitroPdf said it's an Adobe issue & to contact Adobe to fix the bug. 
    Tried, but proble exists:
    * Word 2010 > File  > Save & Send > Create PDF/XPS Document
    * Word 2010 > Save As > Pdf
    * Word 2010 > Print > PrimoPdf  (even tried properties > advanced > dpi 300/600/2400) > Custom
    * Word 2010 > Print > doPDF v7  (even tried 'high quality images)
    * Word 2010 > Print > PDFCreator
    * Word 2010 > Print > CutePdf Writer      (even worse)
    * Nitro Pdf Reader  > Convert From File > (even worse)
    * www.pdfonline.com > Word to Pdf         (even worse)
    * www.wordtopdf.com > email: Sorry, an unexpected conversion failure occurred when converting your file. 
    Software:
    * Word 2010 - tried with .docx & .doc (97 to 2003)
    * Adobe Reader 8.2.6 (freeware), then upgraded to Adobe Reader X 10.0.1 (freeware)
    * GhostScript 9.01 w32 (freeware)
    * CutePdf Writer (freeware)
    * PrimoPdf (freeware)
    * Nitro Pdf Reader 1.4.0.11 (freeware)
    * doPDF 7.2.361 (freeware)
    * PDFCreator 1.2.0 (opensource - www.pdfforge.org) 
    Seems to display better at 300%, but lines still not right (even at 2400%), but who views pdf's at this zoom?
    Message was edited by: shell_l_d

  • Bug? Accessibility Tags Converting from Word 2007

    This seems like a minor issue, but it's one that could create a lot of frustration for a disabled person using a screenreader to read tabular data in a PDF.
    As you know, Acrobat plays nicely with Office apps allowing users to create tagged (structured), accessible PDF documents from MS Office files. I just created a simple docx file with a table (attached), and when I converted it to PDF, I noticed a difference in the tags it creates compared to conversion from Word XP. As you see in the Word file, the table is very basic, except that one of its column headers is split into two cells. This is actually a very common technique for presenting table data. In order to automatically tag the header rows as table header cells <TH> in the PDF, I set the first two rows to "Repeat Header Rows."
    Converting from Word 2007 with the "Save as Adobe PDF," or any other method that uses the Acrobat plugin, creates a tag tree that is missing a <TH> tag. I found the problem when I was testing a file with JAWS screenreading software. Using the JAWS "current cell" command (Ctrl-Alt-Numpad 5) to announce the column headers. It reads the wrong header for the current cell due to the missing <TH>. So, in my example file, it announces $2 and $5 as 2010 amounts rather than 2009. That could be pretty confusing to a screen reading user, to say the least.
    I then compared the result to the new Word 2007 "Save as PDF or XPS" feature. That feature tagged the file properly and the header columns match up.
    Compare the attached "save-as-adobe-pdf.gif" to"save-as-pdf-xps.gif". Note the empty (but necessary) <TH> tag in the latter image.
    Just as a sanity check I had a coworker with Word XP convert the file. Those tags were correct too. So, this must be a problem between Acrobat and Word 2007.
    Anyone have other observations on this? I'm going to be leading some accessibility training and right now, it looks like using the Word 2007 conversion feature is the way to go.
    I'm using Acrobat 9 Pro.
    Thanks,
    Joe

    Hi Joe,
    I sense your frustration. For any organization that has to or wants to engage in providing accessible online information
    a serious logistics support issue raises its head. To do PDF, HTML, whatever the proper way (and it can be done)
    requires more resources (training, knowledge, hardware, software, changes to work flows, perhaps some more staff).
    The is no "work smarter with less & pump out more" in this venue.
    Yes, it is helpful (and necessary) to "be one" with the S508 "paragraphs" - WCAG 1.0 - WCAG 20.
    However, once anyone begins to provide PDFs that must be "accessible" the first, single most important reference is ISO 32000.
    The Adobe PDF References that preceded PDF becoming an ISO Standard are useful; but, ISO 32000 is the standard.
    In this documentation there is full discussion of what *must* be done to provide an accessible PDF.
    Without a firm understanding of this content, other information tends to bring about a defused opacity of focus which can
    contribute to major conceptual errors vis-a-vis accessible PDF.
    Leonard Rosenthol's AUC blog entry provides a link to the ISO permitted Adobe version (free) of ISO 32000-1.
    http://www.acrobatusers.com/blogs/leonardr/adobe-posts-free-iso-32000
    Additional, useful information is found in these two documents:
    (1) - PDF Accessibility API Reference (from the Acrobat SDK)
    https://acrobat.com/#d=J7bWW4LvNoznh8fHCsfZDg
    (2) - Reading PDF Files Through MSAA
    https://acrobat.com/#d=uIOvkVTP74kag3bXFJLIeg
    About JAWS - Yes, much used. However, not the exlusively used AT application.
    If I use Windows Eyes, NVDA, a braille reader, or something else then what?
    JAWS *does not* define "it is accessible"...
    re: (1)
    "Game away and if it ...."
       Consider "Stop before right on red".
       "Compliance" is Stop on Red - Turn Right
       "Intent" (aka usability) is Stop on Red -  Look Good for on coming traffic that has the right of way - Yield - when clear, turn right.
    But, at least we are not talking about "left on red" 8^)
    re: (2)
    Just an observation. A defective product that claims to be "whole" can get entities (individuals/businesses) into a sticky wicket.
    Putting a high volume of defective products on one's selves only increases the probability that one gets 'busted'.
    Quantity replacing Quality just is not a success precursor.
    Case in point - Target and the national class action legal action that was taken against it with regards to "accessibility" of online information/services.
    Resolved now - see NFB's web site.
    re: (3)
    Ah, but what would Judge Judy or Judge Marily say?
    Efficiency does not preclude providing a "whole" product.
    I doubt that there will ever be a seamless "one-click" between products of any of the dominant software houses.
    They are intense competitors. That this is the case does not abrogate others from providing a "whole" product, no?
    So, if the organization wants the "we do accessible PDF" label then it pays the freight - Adobe Pro, training, appropriate work flows, etc
    that permit delivery of PDFs that meet the standards for what a well formed tagged output PDF is (accessible is a sub-set of this).
    For PDF there is no other way.
    If this cannot be done then there is always HTML as an acceptable method (to some it is the preferred and only "true" way).
    However, HTML, done "right" for accessiblilty is just as demanding in its own way.
    With each AT version / dot version release, JAWS - Windows Eyes - NVDA & others hone in closer on utilizing PDF ISO Standard 32000.
    That means if you deploy "accessible" PDF you need to provide PDF that live to the ISO standard.
    Keep in mind that S508's paragraphs began when, effectively, HTML was "it". In software terms that was geologic eons ago.
    For contemporary AT to effectively parse PDF, the PDF must be a well formed Tagged PDF having a format/layout that reflects a logical hierarchy.
    Creation of all this must start in the authoring environment with the content author.
    The post-process PDF output then assures that the PDF elements (tags) are the correct type, have the requisite attributes, etc.
    Without this, AT will not be able to provide the end-user effect utilization of the PDF.
    So, for AT to properly 'work' the PDF, <TH> elements *must* have the Scope attribute's value defined, Row and Column Span values defined, etc.
    Scope, Row Span, Column Span, Table IDs and Headings must be added as part of the post-processing of a PDF using Acrobat Professional.
    An alternative is the Netcentric CommonLook plug-in for Acrobat Professional. What it does, Acrobat Pro can do; however, the CommonLook
    provides a robust user interface. Downside: at some $1k per seat it is not 'cheap' and it has a *steep* learning curve (Sitka Pass?).
    Two table related resources are at this AUC thread (in post 3 and 4). They may be of some usefulness.
    http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=23178
    When the "smelly stuff" gets feed into the maw of the fan it's prudent to not be directly down stream, eh.
    Consider Target and the situation they put themselves in.
    Consider submittal of accessible PDF to fedgov or stategov agencies.
    They won't be in front of the fan if usability of the PDFs becomes an issue.
    Rather, it will be those submitting. After all the agency did say "accessible".
    Better to slow down and do it right or ramp up resource loading to support "schedule" than to stake oneself out as someones "feed" tomorrow, no?
    In the final analysis, for PDF, HTML, or any 'format',  Accessibility is the Usability + Compliance.
    Does it take improvements in professional development/training, adequate hardware/software, *time*?
    Yes. But, it all comes down to "where the rubber hits the road" - what tires are you on?
    It can be done. I do it one small step at a time every day. Often, that's what it takes.
    Deliverables are provided; but, with no mis-labeling and the incremental progress is identified, celebrated and the whole thing continues until
    the "road" is completed properly.
    Don't want wash outs, bridge collapse or what not tomorrow <g>.
    (But then I'm a fan of "Holmes on Homes" which may go a long way towards understanding my point of view when it comes to accessible PDF.)
    re: function(){Return ....
    Good question.
    My guess - either from the cut & paste I initially performed from the application I'd been using to assemble write up and screenshots or something associated with the Adobe Forum application.
    It can't be that I'm 'special'; if that was the case one of my occassional lotto quick picks would have been a big $ winner long ago <G>.
    fwiw -
    You'll find a number of "Accessible PDF" related resources in the threads at the AUC Accessibility Forum.
    http://www.acrobatusers.com/forums/aucbb/viewforum.php?id=18
    Two Accessible PDF related on demand eSeminars are also available.
    Look for Duff Johnson's and Charlie Pike's (on page 2) eSeminars.
    http://www.acrobatusers.com/learning_center/eseminars_on_demand
    Be well...

  • Convert from Word 2007 to Acrobat Pro 9; bookmark issue

    When converting from Word 2007 to PDF using Acrobat Pro 9, enabling "Convert Word Headings to Bookmarks", not only are Headings converted to bookmarks, but bulleted text (styles), as well.  I attached the subsequent PDF, but this forum does not permit the document attachment.  I really only want to show the Headings.  (It may be noteworthy to mention that when using this same set of styles in Word 2003 and Acrobat Pro7 the conversion was seamless.)
    Does anyone know how to correct this?  I have reviewed my Word styles and the issue does not appear to be on the document level.  Am I missing some obscure setting?
    I'd appreciate any help.
    Thanks.
    -PS

    I had a similar situation occur when converting Word 2007 docs to Acrobat Pro 9 Extended via the PDFMaker (Acrobat add-on tab in Word 2007), and I want to share a workaround. In summary, I had extraneous bookmarks appear in the PDF (heading 3s, body text, XE Index tags, etc.)  that I did not select to be in the PDF.  I contacted Adobe's support and ended up talking for approx. 2.5 hrs to 2 different reps with no solution. They reproduced the issue on their end, but couldn't figure out how to fix this. I recently upgraded to Tech Comm Suite 2.5 from 1.0. The Word 2007 conversion to PDF via Acrobat Pro 8.x worked fine.
    Scenario: I have 400-page user guides that I am required to publish as 'Press Quality' with navigable bookmarks to certain headings in the PDF. I have to generate the PDF via the Acrobat Add-On tab in Word, since I do not want to manually insert bookmarks in the PDF for 400 page documents (as you would when using the Adobe Print driver or 'Save As PDF' operation).
    In the Adobe PDF Maker dialog, I have the following Application Settings selected in the General tab:
    Create Bookmarks
    Add Links
    In the Bookmarks tab,  I originally had only two Elements selected for bookmarks:
    Heading 1 (a Word Heading already present) as the Level 1 Bookmark.
    Table of Contents Bookmark (a Word Style I created) as the Level 2 Bookmark.
    As a result, the Convert Word Headings to Bookmarks and Convert Styles to Bookmarks were both enabled in the Bookmarks tab.
    The resulting PDF contained extraneous bookmarks that I did NOT select, such as Heading 2s, 3s, even body text - too much to clean up for 400-page documents! Additionally, and this was annoying too - I noticed that all bookmarks appeared as Level 1 Bookmarks, making the PDF Bookmarks really messy. I converted multiple Word 2007 documents with the same results.
    How I resolved the issue:
    In the Word 2007 document, open the Styles window, select all instances of the specific Word Heading (in my case, Heading 1). All instances of the selected Word Heading will be selected in the doc.
    Click the New Style icon in the lower left part of the Styles window.
    In the Create New Style from Formatting dialog, create a new style name (e.g., I created H1).
    Just to be sure to NOT create the new style from an existing Word Heading, I selected (no style) in the Style Based On field.
    Configure the remaining formatting items as necessary, and then click OK. All of the selected instances from the old Word Heading style are now changed to the new style created (in my case, H1).
    Click the Preferences tab in the Acrobat add-on tab in Word 2007, and open the Bookmarks tab.
    Remove the old Word Heading (in my case, it was Heading 1) so it no longer will be included as a Bookmark in the PDF.
    Select the new Word Style that you created (in my case, H1) to be generated as the Level 2 bookmark. Note: My original Level 1 bookmark, "TOC Bookmark," is still selected. Now, only the Convert Word Styles to Bookmarks is enabled in the Bookmarks tab.
    Generate the PDF once again via the PDFMaker, and no extraneous bookmarks appear in the PDF.
    Note: I also noticed that when Index tags (XE tags) were present in an element selected to be a bookmark in the PDF (such as my new style, H1), they also appeared in the PDF Bookmarks pane. I just moved the XE tags down to the body text so they would no longer appear in the PDF.
    Question for discussion: Maybe there is a bug in the PDFMaker when both Convert Word Headings to Bookmarks and Convert Styles to Bookmarks are selected? The extraneous bookmarks do not appear in my PDF when only Convert Word Styles is selected.

  • How to convert Ms Word (.doc) file to Protected pdf

    Hi all,
    Is anybody out there could help me on how to convert Ms Word (.doc) file to protected pdf file using java? May be there are some jar file I need to download or any tools you used before? Thanks in advance... =)

    Hi all,
    Is anybody out there could help me on how to convert
    Ms Word (.doc) file to protected pdf file using java?
    May be there are some jar file I need to download or
    any tools you used before? Thanks in advance... =)Hi All,
    Thanks for your replies..I think i almost find the solution. I found 2 options to do this. They are :
    1. Get Adobe Acrobat and it's SDK (has to buy)
    2. Get OpenOffice 2.0.4 and it's SDK (opensource)
    So, i do option 2. I install them in my system.then i call them from my ide. Then i follow the code from this link..
    http://weblogs.java.net/blog/tchangu/archive/2005/12/open_office_jav_1.html
    Thanx.. =)

  • How do I convert a WORD doc to pdf on my Mac

    How do I convert a WORD doc to pdf

    Easiest way if you have Word installed: from Word's File menu, do "Save as..." and you will find a pdf option in the "Format" pull-down:
    The example is from Office:Mac 2008; should be similar in Office 2011.

Maybe you are looking for