Yes, it's no problem using several versions of FrameMaker on the same computer. I've had versions 8, 9, 10 and 2015 sitting on the same PC without any issues, however, these are the common caveats: If you've got a full version of Acrobat Pro installed, do not install the PDF printer instance coming with FrameMaker When uninstalling a version of FrameMaker later, it's possible that the uninstaller messes up the registry. I've just had this happen when uninstalling FM9, my 2015 version wouldn't launch due to missing registry entries. This can be fixed, though, my 2015 version is running again. Bernd ... View more

Ah… looks like I've mixed up header and heading. A misunderstanding, sorry. Bernd ... View more

https://forums.adobe.com/people/heather+ceana  schrieb The newest thing is that all of the chapters, except the front cover, now have inconsistencies in the pre-set colors: Dark Grey, Pale Green, Forest Green, Royal Blue, Mauve, Light Salmon, Olive, and Salmon. Heather, I have recently noticed something regarding the pre-defined color sets, which I believe to be a bug in FrameMaker: If you have a template document with, e.g., all colors defined as "Process Colors" (instead of spot colors which most are), this information will only be maintained if you open this template document and then "Save as..." with a different name. If, however, you use this template with the "File > New > Document..." (CTRL + N) command to create a new file based on this template, all the pre-defined colors are reverted back to spot colors. No longer process colors. And if you combine these newly created documents into a book, just the first one will have the correct colors, while all the following ones (created from the first one used as a template) will have the wrong definitions. So it's nothing you actively did, or did wrong, just creating new files using the standard routine in FrameMaker causes this problem. Bernd ... View more

You've been looking in the wrong place to add a line style to be used below paragraphs. These lines need to go to the reference page (there are already the frames for the single and the double line). The steps one by one: Go to the reference page and draw a graphic frame (using the corresponding tool). Name it as desired. Within that frame, draw the line you want to have below your heading, and adjust the parameters as needed. Go back to the working pages, and define the paragraph format to use the newly created frame below the paragraph. Done. I hope this helps. Bernd ... View more

mezybella​, I've had a similar problem initially, in my case with a non-functional "Continue" button in the installer window. You should specifically look for your version of Internet Explorer. You have to have a current version installed, the FrameMaker installer won't work without it. I've had an older version (because I'm using Firefox and not IE), and couldn't install FM. I'll never understand why and how an FM installation would be dependent on that browser, though… Bernd ... View more

Regular text flows transition fine when opening FM7 files in later versions. As Jeff correctly said, you might need to re-define your paragraph and character formats to use current unicode fonts, especially if books are written in a foreign language. However, there's one problem I remember from the days when switching to FM8 (first unicode version): Marker text (e.g. index markers) written in foreign languages (like Greek or Russian or using other characters beyond ASCII) don't get transferred correctly. I remember having used scripts for converting marker text to plain text, then open in FM8 (or later), and then run the script to make marker text from the now correctly transferred text again. Bernd ... View more

Amitoj  schrieb We are trying to see if we could have an absolute path instead of relative path for the next release. With an absolute path, it would be much easier to manager and copy paste same onto windows explorer. thanks, Oh no. Please don't. Never ever. This would immediately ruin perfectly working translation management for thousands of documents in dozens of languages and take me to what I absolutely *hate* on Indesign. Always referring to the wrong image folders when working on a newly translated version of a document. The relative path feature is one of the absolute highlights and essential functions of FrameMaker which needs to be maintained. Bernd ... View more

Lothar, you probably can't do anything about it, the Arial Unicode font is highly problematic. There's a similar thread about text which cannot be searched in a PDF. I've done several tests, and the results showed that it's definitely the font which makes the difference: http://www.meissner-dokuteam.de/Files/Frame/Test_FM_imported_graphics_2.pdf There's a minor difference because the thread above is about imported PDF graphics which are not searchable in FrameMaker PDF output, but it's basically the same problem. Bernd ... View more

Don, that's easy, just two steps to be done: Define a new character format (e.g. "xref") that has just the desired character appearance, e.g "blue text color" and "underlined". Define your cross reference format to use this new character format. The definition would then be e.g. "<xref><$paratext><Default Para Font>. This definition uses the character format for the referenced text and switches back to the default character format (from the paragraph format) after the referenced text, see attached screenshot. Bernd Edit: too slow… 😉 ... View more

Arnis, I think you're on to something. We've been using Arial and Arial Unicode fonts, because these fonts are also used in the original software of the device. The problem seems related to the following factors: Font and font type (TTF, OTF) Indesign version exporting the PDF Resulting encoding in original image (TT (CID)/Identity-H vs. Type-1/user defined vs. TT/ANSI…) I've done several tests with several fonts and got a PDF with new results, some images are working and some are not. The conclusion from this file (although this is not a statistically relevant number of fonts and formats) seems to be: Unicode OTF fonts seem to work fine some "serious" Unicode TTF fonts also work when exported from ID CS5.5 and later, but not with CS4 Arial and Arial Unicode don't work at all, except in EPS format Bernd ... View more

Bob, turning off font embedding in an exported PDF is not an option which Indesign offers. I can just control if I embed subsets or the full font, with the default being "subset when less than 100%". I could turn this function off for EPS, but EPS is not the problem here. ... View more

Arnis, I can confirm that problem, we're experiencing it here, too. The problem seems to be related to the internal character encoding in the PDF which changes on the way through FrameMaker (2015). Detailed example: we're creating images in Adobe Indesign (existing XML workflow) which are then placed in FrameMaker. For years we have exported these images to EPS which worked flawlessly in FrameMaker. PDF output from FM still maintains the text in the images as such, which can be copy/pasted or searched in the resulting PDF afterwards. Recently we started to output the images from Indesign to PDF (high quality print joboptions) instead of EPS, because the preview quality in FrameMaker is better and the format more up-to-date and universably usable. The PDF itself still contains the text correctly encoded and searchable. However, when importing these images to FrameMaker and saving a PDF from there renders the text in the images to garbage with an unusable ("identity-H") encoding. The fonts (unicode, OTF or TTF) are embedded as subsets in both the EPS and PDF exports from Indesign. Imported EPS in FrameMaker creates searchable PDF output, imported PDF does not. So using EPS instead of PDF might solve the OP's problem for now. I haven't yet found a reproducible solution for the imported PDF. Update: made a simple PDF that demonstrates the problem. Bernd ... View more

Just for making this clear: it's totally normal (happens here too) that FrameMaker becomes unresponsive (including a partially blank or dimmed screen) while saving a PDF if you have selected the "CMYK" option. However, FrameMaker recovers from these symptoms once the PDF export has been finished. If you save to PDF with the RGB option selected the screen doesn't go blank, everything looks more "normal", but you still can't click anything during export. So the question is if your FrameMaker is able to finish PDF export when saving it locally. Bernd ... View more

Is that writing a PDF with local files into a local folder, or files opened via network and PDF to be written there too? I've experienced major problems with creating FrameMaker PDFs over a network when having the network drives mounted via the Parallels "Shared Folders/Drives" function. If you connect to the network drives (or server) via the regular Windows  network functions the PDF creation works much faster and better. And sometimes only then. Bernd ... View more

Well, "no FM to ID direct path" is not entirely true. There is the DTP Tools plugin which could at least be tested, although they do NOT support equations. It seems a little bit outdated (officially supporting ID up to CS6 and FM8 MIFs), though. However, I've successfully transferred some FrameMaker content to ID this way, even with later MIF versions. DTP Tools - MIF Filter for Adobe InDesign Bernd ... View more

mattrsullivan  schrieb Are you using Adobe Illustrator? If so, import the native AI into FrameMaker instead of export formats. If you're using Photoshop, use PSD, not export formats. Matt, I've tried your suggestion to use native formats (see attached screenshot), and noticed two things: PSD doesn't work with a transparent background. Still only EPS with clipping path is able to give such a result (as described in my old FM9 tutorial). Illustrator works fine (just like PDF), but it's necessary to adjust the document size to the size of the content. This was easier with EPS, as FrameMaker reads the bounding box and clips the image accordingly. At least with Illustrator files this is a fine solution, but the missing option of having transparent backgrounds with PSD files might be a show stopper. Bernd ... View more

Sorry, this interface regularly f###s up my links, had to repair other links as well. This is the full tutorial link as mentioned above: http://www.meissner-dokuteam.de/Files/Frame/Transparency2_p250.pdf Bernd ... View more

It seems to be a combination of quirks. First, I've re-saved the EPS after mirroring to create the missing "Left.eps", and this file came out correctly with transparent background. Then I made a new "Right.eps" out of this file, which initially didn't work again. Then I tried to delete the eps and import it again, which made me notice this: After fixing this problem, re-importing and re-selecting the "Fill = None" option the file came out as expected. Test file fixed. ... View more

Use a file upload service (like dropbox or similar) and post the link here. ... View more

I also made this tutorial years ago (for FM9, but still works this way) for files saved from Photoshop: ... View more

Could upload a ZIP of the EPS and the FrameMaker file (or an extract of it just containing the table shown above) and post the link here? ... View more

One more thing to check: in the EPS export options (when saving in Illustrator), is the background set to "transparent"? ... View more

FrameMaker is not able to display transparencies (or transparent backgrounds) within the application, imported eps graphics will always look like this. However, it should be correctly displayed when printing or saving as PDF. If this does not work, select the graphic in question (here: the arrow), and - using the the graphics toolbar - set the background (fill color) to "None". Now it should be correct in printouts and PDF. Bernd ... View more

dauphinb  schrieb Will we have any problem accessing/converting our large collection of legacy documents in FM10 and FM8 formats? (We don't need to back-save new docs, but we do need to be able to open/reuse old ones.) We're doing this regularly with lots of old FM8/9/10 books. No issues at all, as long as FM8 is the oldest version (for unicode support). You could even go back via MIF, as long as no functions specific to later versions are used. Bernd ... View more

Funktioniert hier auch mit Firefox Also works using Firefox ... View more

https://forums.adobe.com/people/Stefan+Gentz+%5BAdobe%5D  schrieb I recommend contacting the vendor of the font and asking for the two code points U-202A and U-202B to be added. Both code points are necessary for reasonable RTL publishing. Just to complete the bug tracking on this: I've contacted Linotype, and they actually added the required glyphs to the Helvetica World font. It works now (version 1.07) correctly with the insertion of the RTL/LTR control characters. Thanks Stefan, and also thanks to Linotype support. ... View more