FrameMaker 6.0 A.C.E. Test

I've seen quite a few questions about the FrameMaker 6.0 A.C.E. test, but nobody seems willing to really talk about it. I have seen no prohibition from outlining the scope of this test, so here are my experiences.
Sean
[email protected]

(This is copied from a post I made to the regular FrameMaker forum.)
It cost me 150 USD to take the FrameMaker 6.0 ACE test. To prepare, I went through each example in CIB (sorry, FrameMaker Classroom in a Book), and also read through each chapter in the UG (user guide). I've been using FrameMaker on and off since 1991.
I know of no sample test.
Go here: http://partners.adobe.com/asn/training/acehowto.html.
Get the exam bulletin here: http://partners.adobe.com/asn/training/acehowto.html#164209.
When I went to take the test, all I knew was that I had 90 minutes available in which to complete the test. I did not know the format of the test. I had asked, but nobody answered. I thought perhaps there was an NDA about the test, but I reviewed my documentation and can find no such gag, so here goes:
1. All the questions in the test were appropriate.
2. The test assumes no skills other than your use of FrameMaker. Thus, you really have to be aware of what options are where, and what the various menu items and switches in dialog boxes do. Pay *particular* attention to the Format and Special menus. Also, consider your workflow, from setting up books and templates, through importing graphics, color, and manipulating text. Really, most aspects of using FrameMaker were touched upon.
3. I finished the test in about 20 minutes. I found the test to be underwhelming, but a lot of that is because I have a tonne of stick time on the product. I certainly did improve my score by reviewing CIB and the UG; though, I could have passed without doing so. (It was my $150, so reading the books and doing the examples was a good idea that I do not regret.)
4. For the most part, the test was multiple choice. At the time, I did not know it would be. I rather wish more info were available about the test.
I don't remember how many questions there were on the test, certainly less than 100, maybe about 70? I took the test on a computer. You cannot use reference materials. You can review all your answers before submitting them for scoring.
5. The test was scored and I got my results immediately after I took it. I did not expect that, either. I thought I would have to wait 4-6 weeks.
6. The A.C.E. Certification arrived promptly, within the advertised timeframe, from Adobe. It took about three weeks to get to me.
7. When I took the test, I was prepared to throw away the first $150 in failing the test, just to get an idea what the test was like so I could pass it the second time.
8. There seem to be a few more resources for those looking to become a Photoshop A.C.E. than there are for FrameMaker. However, given the relative popularity of each tool, go figure.
Cheers,
Sean
Adobe Certified Expert (FrameMaker 6)

Similar Messages

  • Problem Working With Framemaker 9 Dita XML Files in Framemaker 10

    I just upgraded to Framemaker 10. I am encountering a number of problems when I try to work with my Dita XML help topics, which were last saved in Framemaker 9 format.
    1. Using the Default Dita Template
    When I open one of my documents in Framemaker 10, the Dita 1.2 template ditabase.fm is automatically applied. Everything seems fine. But then when I convert the XML to Eclipse help (which is essentially html, so we're going from XML to HTML) using Dita Open Toolkit ant scripts, I see this message:
    [pipeline] [DOTJ013E][ERROR] Failed to parse the referenced file 'html\c_licensing.xml' due to below exception. Please correct the reference base on the exception message.
    [pipeline] c_licensing.xml Line 25:Attribute "xmlns:ditaarch" must be declared for element type "dita".
    I then opened the xml  file in a text editor, and I saw this on line 25:
    <dita xmlns:ditaarch = "http://dita.oasis-open.org/architecture/2005/">
    Line 25 looks fine to me. Am I missing something? 
    2. Switching to a 1.1 Dita Template
    I tried to work around the above problem. In Framemaker, I tried to set a different structured application as the default one. I closed all files and chose the default Dita 1.1 structured application (it defaults to the Dita 1.1. Composite app.)
    Then I tried to open my file: I got this message inside Framemaker:
    "Validation of XML failed. Continue?
    Error at [FILE PATH], line 25, char 72, Message: Attribute '{http://www.w3.org/2000/xmlns/}ditaarch' is not declared for element 'dita'
    Sounds familiar, doesn't it?
    I switched from the default Dita 1.1. Composite structured application to the Dita 1.1. Topic structured application. Then I dirtied the source file and saved it. The messages I got in FrameMaker log window included the one above, plus I got a variety of Unknown Element messages, things like this:
    Unknown element dita,
    unknown element concept,
    various attributes are not declared for concept,
    unknown element conbody.
    If I switch back to the Dita 1.1 Composite application all of these messages diappear except for this one:
    Attribute '{http://www.w3.org/2000/xmlns/}ditaarch' is not declared for element 'dita'
    My ant conversion scripts from the Dita Open Toolkit are still unable to process this file. They give the same message as is listed in (1) above and the file is not converted to HTML.
    Can anyone help me with this problem? I've also posted this question to the Dita Users Group on Yahoo Groups. If I get an answer in one place, I'll post it in the other.
    Thanks,
    Nina P.

    I really appreciate all the help you are providing with this, Scott. I tried your latest suggestions. Here's what happened:
    Application Mappings:
    I figured out how to add my "BigPage" structured application to the Applications Mappings dialog. I made a new "BigPage"  mapping type, then figured out the non-intuitive part: how to add my individual BigPage topic types to it.  I closed and reopened FrameMaker opened my test document, and, as before (before I did the application mappings) I saw my BigPage applications listed in the Structure Tools > Set Structured Application drop-down. I selected the appropriate application (in this case it was DITA1.1-BigPage-Reference-FM and clicked the "Set" button. 
    It is at this point in Framemaker 9 (and also once, in FrameMaker 10, early in this process, but I haven't been able to replicate it since) that the page size would change to tabloid size, indicating that the document was using the template from the BigPage reference structured application, not the regular DITA1.1 reference application. But this did not happen.
    I tried saving the document, closing it, and reopening it. Once again the default structured application assigned to that document was "reset" to DITA1.1-Reference-FM.  But the fact that the page size did not immediate refresh to tabloid size told me that although I did select the BigPage application in the drop-down, it wasn't being applied.
    Public IDs:
    The public ID in my test reference XML file is:  <!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd" [
    The four public IDs in the DITA1.1-BigPage-Reference-FM entry in structapps.fm (in the Entity Locations section) are:
    -//OASIS//DTD DITA Reference//EN 
    -//IBM//DTD DITA Reference//EN
    -//OASIS//DTD DITA Composite//EN
    -//IBM//DTD DITA Composite//EN
    Do you see anything wrong with the above? .
    Directory Structure: 
    Maybe I cloned the application incorrectly?  Here's what I did:
    1. In C:\Program Files (x86)\Adobe\AdobeFrameMaker10\Structure\xml, I copied the folder called DITA and pasted it into the same directory. I renamed this folder DITA-BigPage
    2. Inside DITA-BigPage, I opened the app folder. Inside each subfolder in app, DITA-Reference-FM, for example, I opened the edd file in Framemaker. In this case, the edd file name was reference.edd.fm.
    3. I edited the top line of reference.edd.fm.  It originally said:
    Structured Application: DITA1.1-Reference-FM.
    I changed it to say:
    Structured Application: DITA1.1-BigPage-Reference-FM
    4. I saved the EDD file. Then I opened the template file in the same folder. It was called: reference.template.fm.
    5. In reference.template.fm, I first changed my page size: Format Menu > Page Layout > Page Size > Tabloid > Set.
    6. Then I imported the element definitions from the corresponding EDD file:  File > Import > Element Definitions > reference.edd.fm > Click Import > Click OK to dismiss verification message.
    7. I repeated the above process for all topic-type folders. For the maps types, I did not change the page size, as these will never display as topics in my online  help. I did nothing to the dtd folder.
    8. Once all this was done, I opened structapps.fm.  I did the following to all Dita1.1 elements in the structure tree.
    Selected the Dita 1.1 XMLApplication element, for instance, the one named Dita1.1-Reference-FM, copied it, and pasted it underneath the original element.
    The original first few lines in the clone looked like this:
    Application Name: DITA1.1-Reference-FM
          Template:              $STRUCTDIR\xml\DITA\app\DITA-Reference-FM\reference.template.fm
          DTD:                       $STRUCTDIR\xml\DITA\app\dtd\reference.dtd
          Read/write Rules:  $STRUCTDIR\xml\DITA\app\DITA-Reference-FM\reference.rules.fm
          DOCTYPE:              reference
    I changed these lines to look like this, using your suggestion to create a variable for the first part of the URLs to enable speed and accuracy:
           Application Name:      DITA1.1-BigPage-Reference-FM
                   Template:                    $STRUCTDIR\xml\DITA-BigPage\app\DITA-Reference-FM\reference.template.fm
                   DTD:                            $STRUCTDIR\xml\DITA-BigPage\app\dtd\reference.dtd
                   Read/write Rules:        $STRUCTDIR\xml\DITA-BigPage\app\DITA-Reference-FM\reference.rules.fm
                   DOCTYPE:                    reference
    I also changed the "Filename" URLs in the "Entity Locations" section of this XMLApplication clone from  $STRUCTDIR\xml\DITA\app\  to $STRUCTDIR\xml\DITA-BigPage\app\.  Applying the "BigPage" variable I'd created for this purpose made this go quickly.
    Finally, after this didn't work the first few times I tried it, I got suspicious that the structapps.fm file in my AppData folder (in my case, it was in the Roaming subfolder under the usual Adobe directories) was overriding the modified structapps.fm file in the Framemaker program directory so I replaced the one in AppData (it had all the original settings) with my modified version.  This had no effect, unfortunately.
    That was my process. After doing the above, the Dita1.1-BigPage applications all listed in the Set Structured App drop-down. They just didn't work,when applied to my XML documents. Nor did the application "remember" what structured application I had set when I opened a new xml document  or closed/reopened the current document or closed/reopened the application.  Did I place the directories correctly for Framemaker 10?  This is the way I did it for FrameMaker 9 and it worked successfully.
    As much as I'd love to solve this mystery, I've thought of a workaround I can fall back on  that doesn't involve using a cloned application.  I will change the page size of a few of the original Dita1.1 sturctured application templates to tabloid size, but leave the Topic structured application at letter size. I'll then apply the Topic structured application to my PDFs and use the others for my help topics.  I'll set this up now. If this doesn't work, then I'll know there's a much bigger problem at the base of this, perhaps even something to do with changing page sizes in templates.

  • How can I get all of my graphics to import from FrameMaker?

    I am evaluating Robohelp HTML version 9, which I'm considering using for single-sourcing FrameMaker 7.1 files.
    I imported my FrameMaker files, and only 2 out of 75 graphics were imported.
    The results window shows that all FM files were imported successfully.
    However, in the Project Manager, only these two files appear.
    The graphics are BMPs, the same as all the other graphics.
    Everything about them seems to be the same as all the other graphics.
    So I prepared a TEST FrameMaker file. I placed the two graphics that had imported successfully first, along with a selection of the other graphics. Guess what? All of the graphics imported successfully into RH.
    Feeling optimistic, I imported my FrameMaker project into RH again, using the same TEST RH project. Guess what? Only the two original graphics appeared and no others.
    Can anyone help me solve this mystery?
    Thanks so much!

    Sounds like an issue with an individual graphic, not with the process itself. If the 2 successful graphics are the first or last in your project, I'd start testing by importing the graphics in closest proximity...otherwise you may have to import in batches to find the offending file.
    If you have a graphic in a format other than that of the "successful" graphics, you may want to test that format in particular.
    One thing to consider: As I'm sure you know, any missing resources (fonts, graphics, xrefs) and any errors in updating your book will keep FrameMaker from operating smoothly. If you are sending FM info elsewhere (PDF, HTML, Help) then these subtle deficiencies can cause problems with info sent out of FM as well. "Fix" your FM files and you might solve seemingly unrelated issues elsewhere.
    *Note: You mentioned you're testing single sourcing...FM7 files will require import to RoboHelp. With an eval copy of TCS3, you'd be able to create a link to FM10 files, allowing you update the RH9 via the FM10 files. It is a similar process, but by linking, you'll eliminate the importing and/or post processing of the HTML and significantly reduce the time needed to update your RH content.
    Also, when purchasing Adobe product, consider Suite purchases and maintenance contracts...I save tons of USD by doing this. See the math at http://blogs.roundpeg.com/2009/12/strategies-for-purchasing-adobe-software/
    -Matt

  • Framemaker 12, Save as PDF and Print PDF Not working...

    We are using Framemaker 12 version 12.0.3.424, it tells me it is the latest patch level, and the issue we are having is that it won't either save as or print to PDF, both options are failing, they start up and then go to a certain point and come up as "not responding" and then just stops. I have managed to get a postscript file on two occasions that got 141 pages out of 1400+. I have gone through a bunch of the threads here and made sure that I have changed Adobe PDF printer to the default and deselected the box about using the specific fonts, still nothing. We are also using Adobe Acrobat XI Standard, and that is now up to the latest patch level as well. I am running out of things to try in order to get this full book put together and ready for delivery. If anyone has any additional things to try that would be great. One thing I feel might be an issue is that some of the files seem to be using a different font, "Times" vs. "Times New Roman", Frame automatically substitutes it, so was wondering if that is the issue.
    Any and all assistance will be great on this.

    > .ps file was running about 57,000kb
    Then you aren't anywhere near a 32-bit file size constraint.
    > We are running 64 bit machines here, though the program I think is the 32 bit version.
    Pretty much all CPUs are 64-bit now. What matters is the OS version, and Win7 and 8 installs are commonly 64-bit these days. FM may not even have specific 32- or 64-bit installs. I've tested FM9 on Win7/64 for file size limits, and it sails past 4GB with no problems.
    > ... stops everytime on one particular page, that has was is an OLE linked .vsd file in it.
    As if the world needed another reason to never ever use OLE for anything anywhere, esp. in Framemaker. Export that object in a stable graphical file format (PDF should work). Import that.

  • Can I run two copies of FrameMaker at the same time?

    I am trying to learn Structured FrameMaker. Is it possible/legal/safe to start two copies of FrameMaker on my PC at the same time?
    Specifically I want to have one copy open in Structured FM to experiment and the other copy in Unstructured to take notes on what I am learning. I am trying to see if I understand the concepts by writing up a tutorial but I do not want to be locked into structured mode when do not have a template which covers all of my needs ( I am still figuring them out) and I do not yet really understand what the structured templates do.
    Will the documents save by the rules of the window they are in? What other problems will/could I encounter?
    Thanks,
    Marjorie

    Marjorie,<p>If your machine has sufficient disk space and memory, yes, you can run multiple copies of FrameMaker at once. To run the different user interfaces at the same time, you'd have to start both copies. Then, change the user interface in one copy. Since the change doesn't take affect until you restart FrameMaker, shut down that copy and start a new one (leaving the first user interface in effect in the other original copy.<p>All that said, I suspect you can do the testing you want in one copy of FrameMaker, using the Structured FrameMaker user interface. The structured user interface simply means you can work with structured documents; you can also work with unstructured documents. Each document is independently structured or unstructured; in fact, each flow is independently structured or unstructured. You might therefore consider using the structured user interface and opening one structured and one unstructured document in a single copy of FrameMaker. Or create a single document with side-by-side flows and put structured content in one and unstructured content in the other.<p>Just remember that some of the dialog boxes are slightly different in the two user interfaces. For example, the marker, anchored frame, insert table, and cross-reference dialog boxes all let you select an element tag. Since there are no element tags in an unstructured flow, the element tag text boxes in these dialog boxes shows <Unstructured>. If you are willing to ignore these differences, I recommend you do your experimentation in a single copy of FrameMaker.<p>--Lynne

  • FAQ: Creating PDF Files from FrameMaker v.6 & earlier Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!

    An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
    GOOD NEWS
    I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
    DON'T USE "SAVE AS PDF"
    But what's wrong with "save as PDF" as currently implemented?
    The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
    (1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
    (2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
    (3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
    (4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
    (5) Some or all text in the resultant PDF file cannot be searched or indexed.
    (6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
    (7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
    (8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
    (9) Some or all page content is missing (other than margin areas).
    (10) Relatively inefficient PDF is generated.
    If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
    It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
    In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
    Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
    Whether the printer supports color (Acrobat Distiller does)
    What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
    Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
    Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
    Resident fonts (Acrobat Distiller doesn't really have resident fonts)
    Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
    Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
    Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
    Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
    Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
    DON'T USE PDFWRITER
    The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
    SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
    The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
    Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
    PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
    PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
    Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
    Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    Case 3: Acrobat 3
    Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
    - Dov

    You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

  • FrameMaker 11 file link broken when published out to RoboHelp 10

    Hello
    I have the Adobe Technical Communication Suite 4 and am trying to test publish a FrameMaker 11 file out through
    the FrameMaker publish button to WebHelp (by way of RoboHelp 10).
    In the FrameMaker 11, file, I have a link to a PDF that sits down in a subfolder.  I have used the following approach:
    1. Highlighted text in a FrameMaker table.
    2. Chose Special>Hyptertext
    3. From the Hypertext panel, I selected Message Client from the Command drop down menu
         and in the syntax field I entered:  message openfile Foldouts/Foldout1.pdf
    4. I then tested the link in FrameMaker by using ALT and CTRL and it works.
    5. Next, I saved the FrameMaker file as a PDF (File>Save As PDF) and tested the PDF.  The PDF links work.
    So with all that said, how come I can't select File>Publish>WebHelp and have the link information carry through to the WebHelp HTM output?
    I tried this Publish option straight out of the box and it did not work.  I also tried creating a custom RoboHelp template (.XPJ file) and it did not work.
    I believe there is a PgfId marker that is generated when the Hyptertext is created in FrameMaker (using the process stated above), but that marker is not getting
    translated into an HREF, once it gets published out through RoboHelp 10.
    I also tried saving the FrameMaker 11 file directly as an HTML file using the FrameMaker 11 - File>Save As HTML process, but no links carried through
    using that process either.
    I do not know if this is a FrameMaker issue or a RoboHelp issue, so I am now posting this in both forums.
    If someone could point me in the right direction, I would really appreciate it.
    Are there certain steps one must do to preserve FrameMaker Hypertext links that get published out through RoboHelp 10 to WebHelp?
    Thanks in advance for your suggestions.
    Jim

    I've deleted the other post as the question is being addressed here. Folks who use Fm only would not be able to help so this is the correct forum as Jeff as explained.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Hyperlinks in FrameMaker 8 File don't work consistently when PDF'd

    I have a FrameMaker 8 file with internal hyperlinks. When I test them in FrameMaker they work but when I PDF the file SOME of them are not working. I'm using Acrobat 8 as well.

    This thread may be dead already, but I'll chime in anyway....
    Kelly (response #5) touches on something that I think is important:  character style changes in a heading or other paragraph style (such as table title) can cause the link to end at the point where the character style changes.
    For example, consider a heading containing italics:  "Configuring the Merlin System."  Whether the hyperlink is broken depends on how you apply the italics:
    If the italics are applied using a named style such as Emphasis, the hyperlink breaks at the "M."  "Configuring the" is hyperlinked, but "Merlin System" is not.
    If the italics are applied without assigning a character style but only by setting Angle to Italics in the Character Designer, the entire heading is hyperlinked.  That's the good news.  The bad news is that your italics are missing in the TOC.
    This behavior is not necessarily buggy.  It is required, in fact, for creating hyperlinks manually:  you mark your text with a named character style and then create a "hyperlink" marker in it.  What would be nice is if Adobe would separate the feature into two flavors:  one that works for generated links regardless of character style, and one that works in its current form for user-created links.
    Fixing bad links:
    If you have Adobe Acrobat Professional, use Tools > Advanced Editing > Link Tool.  It draws a box around each link.  Drag the box handles to resize a link around the proper area.

  • Crane Aerospace and electronics is looking for Test Engineers with LabVIEW experience - please disregard previous post.

    Here is the correct post:
    Are you detail-oriented, creative, and technically skilled at Engineering design and development?  Come to Crane Aerospace & Electronics and use your excellent Engineering skills to design, improve, and deliver the next generation of products in the aerospace and electronics Industry!
    We have a unique and exciting career opportunity for Engineer II, Test.
    You will be responsible for maximizing new product development and manufacturing performance through the creation and deployment of test strategies, tools, and plans.  Design and implement high performance hardware and software for test equipment.  Authoring test procedures and performing Qualification test activities.  Ensure high product quality.
    Responsibilities:
    Collaborate with customers and multi-disciplined engineers to establish/clarify test, qualification, verification and validation requirements.
    Write test plans, procedures, requirements and reports in a highly structured environment.
    Analyze, develop and deploy complex and high performance test hardware and software solutions for automated test equipment. 
    Design, develop, debug, validate & verify the fabrication of manual and automated test equipment at the circuit board and system level, and specify and procure COTS test equipment.
    Develop/maintain hardware documentation including block diagrams, schematics, BOMs, wiring diagrams and wiring lists, software documentation, and configuration control of initial release and updates. 
    Perform detailed calculations to establish test equipment specifications and design margins.
    Maintain existing test systems through bug fixes, improvements and modifications.
    Support the estimation of costs and schedules to develop or upgrade test platforms.
    To perform a number of the above responsibilities with limited supervision.
    Minimum Requirements:
    Experience: 2-5 years.  Previous work experience in aerospace, space or medical electronics industry preferred.
    Knowledge: Microprocessor / Microcontroller hardware and firmware design; Analog Circuit and power supply design; Digital Circuit Design including high-speed serial communication design; Firmware programming in c; Schematic Capture, PADS Logic preferred; Circuit Simulation; Fundamentals of magnetic proximity, temperature, and pressure sensing electronics; ESD; Familiarity with testing standards (MIL-810, MIL-704, and DO-160 preferred).  Basic laboratory test equipment; LabVIEW experience, certification preferred; Developing hardware per DO-254 and software per DO-178 preferred; Experience with Adobe FrameMaker, IBM Rational tools, TestStand, Microsoft Project preferred.
    Skills: Good interpersonal and communication skills (verbal and written)- effectively lead and/or participate in multifunctional teams in a dynamic work environment. Ability to manage multiple tasks, flexibility to switch between tasks and prioritize tasks. 
    Education/Certification: Bachelors Degree in electrical engineering, computer science, physics or related technical discipline.
    Eligibility Requirement: Must be a US Person (under ITAR rules) to be eligible.
    Working Conditions:
    Working conditions are normal for an office/manufacturing environment. Machinery operation requires the use of safety equipment to include but not limited to safety glasses, heel straps, and shop coats.
    Requires lifting 25 lbs
    Apply online today: http://ch.tbe.taleo.net/CH06/ats/careers/requisition.jsp?org=CRANEAE&cws=5&rid=3170
    Crane Aerospace & Electronics offers competitive salaries and outstanding opportunities for career growth and development.  Visit our website at CraneAE.com for more information on our company, benefits and great opportunities.
    In our efforts to maintain a safe and drug-free workplace, Crane Aerospace & Electronics requires that candidates complete a satisfactory background check and pass a drug screen prior to employment.  FAA sensitive positions require employees to participate in a random drug test pool.

    How can you say you are hiring test engineers with LabVIEW, yet the job description doesn't even mention LabVIEW.  All I see in there is CAD design.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Framemaker crashes on start up.

    I have just recently downloaded and installed Frammaker9.
    So we can test it i dont really want to splash out £100's
    So any help here is much apprechiated.
    So after i installed it i got an error.
    And in that log file was this.
    === Header Begin ===
    Internal Error: 9004, 6919244, 9675646, 0
    FrameMaker 9.0.0 for Intel
    Build: 9.0p196
    Window System: MSWindows
    Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 3)
    Generated on: 09 December 2010 10:57:50
    To file: C:\Documents and Settings\USERNAME\Application Data\Adobe\FrameMaker\9\FrameLog_10.12.09_10.57.50.txt
    === Header End ===

    I recently had the same problem although I had a working FM9 installation already. Suddenly it failed during start-up as indicated. It was caused by my default printer being incompatible with FrameMaker. I had changed the default printer to a barcode printer for an unrelated reason. FM9 would fail in the general vicinity of "Localization" and show the logfile message. Changing back to my standard printer eliminated the problem immediately.
    Hope that helps. I hadn't worked through the full Adobe list of system problems before this possibility occurred to me. Maybe it's listed as something to check; maybe not. It does make a difference.

  • FrameMaker 10 Trial not installing Acrobat PDF Creator

    Hi, I am trying to install the Trial Edition of FrameMaker 10 on a Windows 7 PC, for evaluation.
    The installation of FM10 completes, however PDF Creator 10 is not installed even though I select for it to be done.  I would guess that there should be a separate installer process run by the main FM10 installer, to install PDF Creator 10.  This never happens.
    There are no error messages from the install program, but when I check the installer log I find:
    Testing dependency: Adobe PDF Creation Add-On 10 with relationship Recommended
    Adding failed payload to recommended list
    and
    Checking operation result for {AC76D478-1033-0000-3478-000000000005} Adobe PDF Creation Add-On 10 10.0.0.0
    Recording dependent operation failure for payload: {A6828F8A-83D7-4fff-B763-F69122BB1D74} Adobe FrameMaker 10_AdobeFrameMaker10.0.1_en_US 10.0.1.0
    and
    DW050: The following payload errors were found during install:
    DW050:  - Adobe PDF Creation Add-On 10: Install failed
    I understand that attempting to install Adobe products is problematic if previous versions are present on the machine, so I took great care to remove all traces of previous installs of Acrobat etc. before starting.
    Please could someone from Adobe assist? I would like to evaluate FM10 with PDF Creator 10 but am unable to due to the buggy installer.
    Note: What makes this even more frustrating is that running the installer for PDF Creator on its own gives the message 'Cannot Install Alone, Please Run Installer for FrameMaker'!

    Hi,
    Could you please confirm if you already have Adobe Acrobat/ Adobe RoboHelp installed on your machine, if so the add on might not be installed as the componenets required to create a PDF (under Adobe PDF creation Add on) might be already installed there?
    Just do a test to confirm if the PDF creation functionality is working fine--
    Launch FrameMaker
    Create a Dummy Document
    Select File save as PDF
    Verify if you get a PDF file created at the chosen location?
    Good Luck!
    Thanks,
    Anjaneai

  • Missing fonts in FrameMaker 9 even after installing Adobe Type Manager

    Hi,
    We are using Formata family fonts in our templates. We import the templates and don't see the font family.
    We then installed the Adobe Type Manager and tried reimporting the template. No results.
    We then edited the makers.ini file and added the Formata font in DefaultFamily, still we see the font as missing in the Paragraph Desiger and Catalog.
    Any help in this regard is appriciated.
    The FrameMaker version is 9 on Windows XP.
    Thanks,
    Mrini

    Hi Mrini,
    I need not the ATM on Windows XP or higher to install a font.
    1. Open the \Windows\Fonts folder
    2. Drag and Drop the font file otf, ttf or pfm (for ps fonts).
    3. Then the font is available for Windows and for the applications.
    4. Test it with Word and FrameMaker to choose this new font.
    Additional information for FrameMaker and the maker.ini:
    FrameMaker can differ Weight, Angles, Variations, Windows Weight and Angles only.
    Indeed you can define the correct Family Name with information to the Windows font name and information.
    That isn't longer important if you use FrameMaker on Windows platform, but it can be a great challenge
    if you also work with Adobe InDesign.
    InDesign works default with the correct Font Family name with Weight, Angles, Variations.
    - GEorg

  • Line width on framemaker table

    hi there... i've got an issue on generated the framemaker9 - pdf.
    First, After generated to pdf, the table line width looks like not consistent. There are some thin and thick.. how must i do to get the table look nice with the all line is thin...
    procedure that i use to build the table is ------> Custom ruling and shading - choose from table (apply ruling style)
    Second - what is the difference between click or not at convert CMYK to RGB at settings in PDF Setup ? What exactly the function of convert CMYK to RGB ?

    Sha,
    If you have two separate questions, please create two posts. (Converting CMYK to RGB is the default behaviour of all previous versions of FrameMaker on Windows. Switching off this conversion is supposed to pass through the CMYK data when saving as PDF. Whether you need this or whether it works completely as you need it, you have to test.)
    Regarding line widths: Have you printed the page?
    Assuming your line with is set to be 0.5pt. With 72pt/inch and 25.4mm/inch you get a theoretical line width of 0.1764mm.
    Your screen has a resolution of maybe 96ppi (pixel per inch) so each pixel has a width of 0.2645mm. You can see that with pixels so wide, you can not successfully show 0.1764mm in 100% zoom size. The software (e.g. Adobe Reader) tries its best, but sometimes fails. The human eye is very good at detecting patterns and recognizes even slight changes inside a pattern very easily.
    Your printer may have a resolution of 600dpi (dot per inch) so each dot is as tiny as 0.0423mm. This time the printer may use about 4 dots to create the 0.5pt line, with a 1200dpi printer it could be 8 dots.
    So in the end what you see is just a technological limitation. If the so-called "Retina" display makes its way into mass market with >300ppi resolution those effects will fade away...
    - Michael

  • Why does Framemaker 9 crash when I create a pdf?

    Hi Folks,
    I get an error message and a file is created when I try to either create a PDF by 'saving as PDF' or printing. I attach the header of the log file that is created, it says to email this to an Adobe error email address. I don't know if these internal errors make any sense to you.
    === Header Begin ===
    Internal Error: 9004, 6920492, 9676798, 0
    FrameMaker 9.0.0 for Intel
    Build: 9.0p237
    Window System: MSWindows
    Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 3)
    Generated on: 17 December 2012 11:16:16
    To file: C:\Documents and Settings\nglynn\Application Data\Adobe\FrameMaker\9\FrameLog_12.12.17_11.16.16.txt
    === Header End ===
    However, I MUST generate PDFs ASAP. Is there some solution or patch I can download that fixes this issue? I have, obviously, restarted my PC. I have been using Framemaker for 10 years now and have not seen this error before.
    Regards,
    Niall.

    Niall,
    Unfortutanetly the error codes are only decipherable by Adobe's engineers.
    Are you using the PDF Creator add-on that came with FM or do you have a full version of Acrobat (if so, which one)?
    Have you tested PDF creation from any other applicaion to see if it's an Acrobat issue?
    Have tested other FM books/files?
    Have you done an Acrobat repair (Help > Repair ...)?
    Have you had any updates installed recently?
    There was a MS security patch (KB2753842) released last week that has hosed support for OTF CFF & Type 1 PS fonts in many apps (see: http://www.thomasphinney.com/2012/12/windows-security-patch/ ). It doesn't seem to have affected my versions of FM on Win7, bu I see that you're on XP, so I can't say if there may be any issues with this.

  • PDF generation from FrameMaker v8

    The "Save to PDF" feature (in FrameMaker v8) decided to stop working for me.  I used to use it regularly, and it used to work just fine.  I haven't been able to figure out why it is no longer working.
    When I select it, I am shown the "PDF Setup for Selected Files" dialog, as usual, and I press [Set] as usual.  The status bar displays "Opening Chapter1.fm", etc., for each chapter, but then it just quietly stops.  When the target PDF file pre-existed, the target PDF was deleted, but no new PDF file appears in its place.  It does produce a Book.log file which has the following contents:
    %%[ ProductName: Distiller ]%%
    %%[ Error: syntaxerror; OffendingCommand: %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
    %%[ Warning: PostScript error. No PDF file produced. ] %%
    I had the installer attempt to repair the installation, and when that didn't work, I uninstalled, re-downloaded, and re-installed Adobe FrameMaker v8.  I also had the installer repair "Adobe PDF Creation Add-on".   None of this had any impact -- the symptom remains the same.
    I also tried "Print Book..." with "Print to file: Book.ps" and "Generate Acrobat Data [PDF]" set, and Printer: Adobe PDF.  This produced a Book.ps file, but no PDF file, nor did the PDF printer ask for a file name.  I don't normally generate the PDF in this fashion, so I'm not as comfortable with this method, but as a diagnostic, the fact that it also didn't generate the PDF seems to be a clue.  I assume Distiller is malfunctioning?
    Can anyone give me some clues as to where I should look next?  Can I do anything that would provide further diagnostic clues?  Is there any paper that describes the architecture of Distiller / PDF-creator, which I might refer to for tracking down what configuration is messed up?
    Thanks,
    Lonnie

    I re-installed the FM v8 patches, so that now I'm at FM 8.0p277.   Problem still persists, no change to symptoms.
    The hotfix link was an excellent suggestion.  It definitely looked like it might be relevant.  Unfortunately, the hotfix page does not provide a download for XP x64.  I contemplated trying the Server 2003 x64 version, but after reading the warnings that came with it, I chicked out on trying that.  I put in a request to Microsoft for the XP x64 hotfix, which I have not received, but as I studied the hotfix a bit more, it looked less and less likely that this would be the problem, and even that I should probably not install it.  The hotfix itself replaces atmfd.dll with a new one labeled as version 5.1.2.277.   So I checked the version of my atmdf.dll, and I'm at 5.2.2.232.  The hotfix itself was put out in 2008.  I suspect I'm way past it in my Windows updates, and seems like it would be a bad idea to revert back to an earlier version.
    The other thing that deserves mention is the fact that Save to PDF was working for me for the past 3 years, so my system has probably had whatever hotfix it needs.  I willingly concede that there are several holes in this, but it is still fairly compelling.
    I clearly have something wrong with the "Adobe PDF Converter" printer driver.  So I think it is a logical course of action to focus on it.  For example, when I pull up any application (e.g., Notepad), and then Print... to the "Adobe PDF" printer, the "Creating Adobe PDF" progress dialog hangs indefinitely, usually with about 10% of the progress bar elapsed.  It seems like a simpler piece to focus on for now -- solve that, and I'll bet the Framemaker problem gets fixed.
    I don't know how one re-installs the "Adobe PDF Converter" printer driver.  I'm pretty sure it got there when I installed FrameMaker v8.  My "C:\Program Files (x86)\Adobe" directory has these subdirectories:
    Acrobat 8.0
    Adobe Help Viewer
    Flash Player
    FrameMaker8
    Reader 10.0
    Reader 8.0
    There is a subdirectory C:\Program Files (x86)\Adobe\Acrobat 8.0\Acrobat\Xtras\AdobePDF\AMD64
    which I think contains be the "Adobe PDF" printer driver files.  The three DLLs in that directory all have valid digital signatures.  I assume that if one of them became corrupted for some reason, the digital signature would be invalidated.
    Are there any theories for what the "Adobe PDF Converter" might be hanging on?  Anything relevant I can check or test via DevStudio (which I have)?
    Continued thanks for all your efforts,
    Lonnie

Maybe you are looking for