Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
Be.eM
Enthusiast
Be.eM
Enthusiast
Activity
‎Jun 23, 2022
12:16 AM
1 Upvote
Here is an overview (from FM2015, but has been the same for pretty much all versions of FM) of special characters and how to enter them in dialog boxes: https://help.adobe.com/en_US/framemaker/2015/using/using-framemaker-2015/frm_references_re/frm_shortcuts_sh/Dialog_boxes-.htm
... View more
‎Jun 17, 2022
07:08 AM
1 Upvote
@LinSims: I think it just edits the name in the para tag catalog if the target format ("change to") does not yet exist. In Robert's case the target format most likely exists and will just be assigned to the "found" places. This is how I understood the task here… Anyway, as this might be interesting for @RobertNunemacher too, there are two options in which the plugin works: If the target format exists, it will just be applied to the found items If the target format does not yet exist, the format name of the found items will be renamed accordingly, the format definition stays the same In both cases the source format may optionally be deleted from the catalog (or kept, if it is still to be used)
... View more
‎Jun 17, 2022
06:52 AM
1 Upvote
… a manual process, if you don't want to use the plugin. Which is paid after half an hour of manual work or so 😉 A nice weekend to you, too. Bernd
... View more
‎Jun 17, 2022
06:44 AM
1 Upvote
Yes, this is correct. As I said, you weren't talking about a replacement of paragraph formats via the plugin mentioned above, so my answer is wrong. However, if you are searching for a complete paragraph, this includes the "return" in the end of the paragraph. Now if you replace this "find" content by whatever you've got in your clipboard by "paste", this "paragraph end" return will probably be replaced, too.
... View more
‎Jun 17, 2022
06:22 AM
1 Upvote
Unfortunately, these aren't mine… I've just bought that plugin, too.
... View more
‎Jun 17, 2022
06:21 AM
1 Upvote
I guess this just caused by Heading4 being definied as a run-in Heading. Did you check the paragraph format? Edit: no, your question is not related to the plugin above, so my answer might be wrong. Bernd
... View more
‎Jun 16, 2022
02:06 PM
2 Upvotes
The "FindChangeFormatsBatch" plugin might be exactly what you're looking for. But there's a strategy (correct order of replacements) required for not having only one level of headings left in the end… 😉
... View more
‎May 30, 2022
06:57 AM
Same here. I've been using such combinations of vector art and text (like in callouts) over images for decades, without any problems. Simply placing FrameMaker vector elements over imported vector or raster images does not create those white lines. However, I've experienced that "white-line-syndrome" always, when there's a combination of vector art and a raster image which contains transparency, for example an image of a device (cut out in Photoshop, or a 3D rendering with alpha channel) placed over a colored background in FrameMaker, and maybe some text or logos above that all. This is a typical combination of graphics and text as used on title pages of manuals. The "transparency reduction" which happens when creating a PDF from FrameMaker is what causes these white lines, because all image parts containing tranparency are cut to small portions, in which the transparent image and the underlying colored background (etc.) are combined into one single "puzzle part". Edit: please note that pixel based effects like "shadows", "glow" or similar which can be applied in Illustrator cause the same problem/effect. They always create some form of pixel based transparency, which will then be reduced on PDF creation, with the unwanted side-effect of the white lines. Bernd
... View more
‎May 20, 2022
02:51 AM
1 Upvote
Hi Fabian, I've tested it by modifying the environment variable (to "/Temp/Test"), restarted the computer and started a PDF creation with a document that reproducibly crashes in FM2015 when doing so. Unfortunately this crash still happens, and it seems definitely tied to reaching 32-bit limits. There is a leftover *.tps file on the server, which reached a size of about 4.38 GB, and the content of the newly defined (and previously almost emtpy) Temp/Test folder is now also about the same size (4.14 GB). This is exactly what a 32-bit process would do. I'm afraid cleaning folders or modifying the environment variable doesn't solve it. It just creates a more or less empty folder to start with, so you can create more temporary files until you reach the 4 GB limit. An interesting fact in addition: Throwing that 4GB *.tps file onto Distiller creates a perfectly fine PDF file. This has been working before, too (no change by the environment variable). Of course this brings up one question: if the *.tps is sufficient for a complete PDF file, what is it that FrameMaker still wanted to write to that *.tps file, which made it finally crash? Bernd
... View more
‎May 19, 2022
11:04 AM
Fabian, you mean changing the environment variable for the Temp folder, i.e. pointing it to a different folder solves the problem? We have this problem here with a few documents, reproducible on several FM2015 installations in Win7/64 Pro. Finding a solution would be perfect… Bernd
... View more
‎May 09, 2022
12:27 AM
1 Upvote
Installing the trial would have been possible in Windows 7, too, simply by unplugging the computer from the net (i.e. leaving it without internet access) before installing FrameMaker. Turning the trial into a licensed version (by logging in/entering the serial) is what permanently fails in Windows 7. Because this step requires contact between your computer and the Adobe licensing server, which denies contact from old IE versions. From Windows 7 it doesn't matter if this is IE10 or IE11, both don't work, no matter which of the listed solutions you try.
... View more
‎May 03, 2022
01:16 AM
1 Upvote
As I've reported in this thread (the last three postings there, scroll down), the standard solution doesn't seem to work in all cases. I tried to install FM 2019 (also perpetual license) in a Win 7/64 environment, which was a supported platform when FM 2019 was released. I tried all the steps described in the standard solution, and failed miserably. It's simply not possible to get FM installed there, with the current solution set. I can imagine the same (or similar) problems are there with Windows 11. I have been successful with installing FM 2019 in Windows 10, though, using the 3rd solution (replacing the set-up.exe). I'm also wondering about the always repeated justification "it's only because Microsoft doesn't support IE10 any longer". No, this is not true. It's because Adobe Servers are set to no longer accept communication coming from IE10. You can easily confirm that when plugging off the internet connection for installing FM2019. Installation goes through smoothly, without any problem. But then you're stuck with having a demo installed. The problem is not installation, the problem is getting through to registration/activation on the Adobe servers. And this is nothing Microsoft has changed. By the way, IE11 (which is currently part of the solution) will be no longer supported by Microsoft in a few weeks, too. What will happen then? Everything with FrameMaker registration/activation is tied to a certain 3rd party software tool. I don't know who ever might have thought that this is a great idea, making MY software depending on a 3rd party software application which has been outdated even when it was new… Internet Explorer, the GOAT browser. Bernd
... View more
‎Apr 21, 2022
02:32 AM
@pulkitn, there's a new observation I made, while still trying to get that licensing info entered. When I click on the "License software" button in the Trial Window and try to log in, the Adobe Application Manager (PDapp.exe, version 10.0.0.49) is launched in background (visible in the Windows Task Manager). This seems to be the application which tries to perform the login, even when launched from within FrameMaker. Since I still continue to get the error message above (no internet connection) all I can do is exiting/canceling this step, being set back to the time limited demo. When trying to launch the Adobe Application Manager in Windows 7 separately, I get an error message ("download error (12175)"), too. Obviously also this application has ceased to work or communicate with Adobe. Is it possible that the failure of licensing FM2019 is related to the Application Manager, which is no longer able to connect? Bernd
... View more
‎Apr 20, 2022
01:40 AM
@pulkitn, unfortunately I have to report that this solution does not work, at least not on Windows 7/64 pro. The exe file you've linked seems to be for a different OS version. Anyway, installation of FM2019 in Win 7/64 also fails using the previously described solution. I have copied the AASIapp.exe to the corresponding P7 folder (which did not contain an older version yet, though). On this computer there's a running version of FM2015 already installed, also Internet Explorer 11 with TLS 1.2 enabled. When starting the FrameMaker 2019 installer, all I get is the same old message regarding the required browser/OS update. However, there is nothing more to be updated. I've also done the recommended registry edits (solution 2) for both the AASIapp.exe and Set-up.exe. Restarted the computer, still doesn't work. Anything else to check? I really need to be able install our existing FM2019 licenses… several of them. Update: by removing the network connection from the computer I've been able to install FM2019 as a demo. Afterwards I had to replace the AASIapp.exe in the P7 folder again, because it was overwritten by an older version. However, even after reconnecting to the internet and restarting the computer, I'm still not able to enter my license information now. FrameMaker still pretends to have no internet connection, although the help menu shows the option to log off with my user name (which is probably there because of the working FM 2015 version). The message says there is no internet connection or the time on the computer is wrong (which it isn't): Update #2: I've misunderstood the instructions above. I understood "…just have to replace give Setup.exe…" that I'll have to rename the ZIP file to Setup.exe. This is wrong. After simply unzipping it, I found the file "Set-up.exe", which I then copied into the FrameMaker setup folder, replacing the existing file. Using this file the initial installation went through, however, I still get the error message shown above when trying to log in for entering the license information. Bernd
... View more
‎Apr 19, 2022
12:57 AM
1 Upvote
Try this: https://helpx.adobe.com/tech-comm-suite/kb/deprecated-internet-explorer-10-with-ims.html
... View more
‎Mar 24, 2022
03:11 PM
Which fonts are used to display these files? Do they support Chinese and/or Japanese texts? Is the encoding (unicode) correctly written to file when exporting the translations to MIF? This looks like double-byte text displayed by single-byte fonts.
... View more
‎Mar 20, 2022
02:55 AM
Regarding this error message you might want to check out this troubleshooting info: https://helpx.adobe.com/tech-comm-suite/kb/deprecated-internet-explorer-10-with-ims.html
... View more
‎Mar 07, 2022
12:07 PM
Winfried, the setting you describe is only OK as long as you don't use, for example, EPS files with embedded fonts which aren't installed in the system. I've learned that this setting should always be disabled to avoid problems in typical FrameMaker work and use cases. Anyway, this setting should simply stick (even without saving it as separate setting), when accessed from the Windows/Printer settings. I've never done it from within FrameMaker. Bernd
... View more
‎Feb 25, 2022
02:18 AM
I don't understand the need for an integrated browser application to a) log into FrameMaker/register and b) displaying varying web content within FrameMaker at all. Why rely on a separate application for displaying web content? And why the MS Internet Explorer, which has been outdated, sub-par and flakey for decades? I was totally happy with the browser-free FM versions 3-13…
... View more
‎Feb 23, 2022
08:18 AM
1 Upvote
For now the best solution (which really has no disadvantages for me) is simply disabling that welcome screen completely, as described here. Just make sure that you're adding (or editing) both entries: DontShowWelcomeScreen=On ShowTabbedWelcomeScreen=Off
... View more
‎Feb 23, 2022
08:12 AM
2 Upvotes
Matt, I understand that Adobe resources shouldn't be bound to fix old versions, in most cases. However, this is not what I have requested. There's only one thing I really, really insist in, and this is: Don't break software which has been running perfectly in an unchanged environment. I have clearly written that this error happens with FM2019 in a Win7 environment. There are no longer any Windows updates breaking anything. This is my form of "hardware + software bioshpere" where system and software version are matching and working perfectly together. I also have old Macs with old MacOS running old CreativeSuites up to CS6. These work flawlessly and fine there. I'd never expect old software to run in new systems, but I definitely expect that it continues to run (and remains installable there) as long as the "hardware + software bioshpere" isn't corrupted. As I said, software should at least run as long as the original system requirements are met. Bernd
... View more
‎Feb 23, 2022
05:33 AM
Matt, you keep repeating that "beyond Adobe's control" thing again and again, but this is simply not true. Adobe keeps moving the goal posts for older software permanently, so even completely untouched FrameMaker installations in completely untouched Windows systems start failing with this problem. Example: I'm running one of my FM2019 licenses (15.0.6. 956) in a Parallels VM running Windows 7/64 Pro. This has been a perfect environment for FM2019 at the time when it was installed, and this has been perfectly running without fail (and just the known bugs) until now. Now it shows the same failure with the Welcome screen exploding. This is just another example (after the dreaded "Windows Explorer 10 support deprecated" problem) for causing problems with older software versions, which shouldn't happen as long as the originally stated system requirements for the software in question are met. These are all problems which are caused by software components which are primarily in Adobe's interest (marketing in the Welcome screen, licensing and signing in), not the user's interest. So I'm really questioning that "just buy the subscription for the latest, latest fancy features" mantra, I don't understand why perfectly working (and fully paid for) software starts to fail even without changing anything on the user's side. Bernd
... View more
‎Feb 17, 2022
02:09 AM
I've got an older computer on which I'm running Flare 2017 and FrameMaker 2015 (and other versions). I've done a quick test with one of the Flare Template projects (EmployeeManual). For doing so I've added a new FrameMaker Target to the project (everything set to "default") and started an output build. The build starts, Flare launches FrameMaker and creates the output files, a book file, a TOC file, and chapters (not all of them, but this might have to do with a setting in the project). Opening these files in FrameMaker shows usable results. However, I've then opened the same project in Flare 2021 (on another computer, with FrameMaker 2015 and 2019), and get this error message, which confirms what those Flare sources say: So the answer to your question is: It does actually work, but only with older versions of Flare (here: 2017). If you could get hold of such an older version you should be able to migrate your projects. Bernd
... View more
‎Feb 06, 2022
09:53 AM
Hello Mohamed, which FrameMaker version are you using? They work well for me with FM2015, but I've noticed major problems with print/crop marks since FM2019, mainly with CMYK output. They still work as usual with RGB output (Distiller), although "RGB" and "Print Marks" are contradictory terms.
... View more
‎Feb 04, 2022
03:05 AM
3 Upvotes
Yes, this text clipping does happen and it is depending on the font metrics. There are a few fonts with which it doesn't happen (or to a lesser degree), but there is no distinct parameter in the paragraph or character formats with which it could be avoided. However, I found an easy solution which allows you to precisely control the distance to the upper frame border. I suppose you're using a special paragraph format for these callouts. You'll need to modify this format as follows: 1. On the Reference page, create a new empty graphic frame with a useful name (I've named it "Callout frame above" in the example shown below). Note: The name is given when creating the frame and cannot be modified afterwards! The title above is just text which does not control the frame's name. Make sure the frame is transparent and does not contain any color fill: 2. Next: In the paragraph format, enable this frame to be used as "frame above". Now you can use the height of this frame to control the distance of the paragraph to the upper text frame border. Bernd
... View more
‎Jan 20, 2022
02:06 AM
I don't know if this is related, but "FrameMaker fails saving [whatever] on a network server" is a common denominator. I've had similar problems when trying to save PDF files on a network server, and the reason was… Windows Defender. Maybe it's worth a check.
... View more
‎Jan 17, 2022
04:26 AM
Thanks for that ride on the time machine… FrameMaker 3.1 on Mac was the first version I've been working with. On a Mac Quadra 800, later converted to a PowerMac 8100 🙂 Bernd
... View more
‎Nov 12, 2021
04:03 AM
2 Upvotes
The existing answers all talk about moving paragraph formats between files, which is not what you're trying to do. You want to apply parameters of one paragraph format to another format. This is how I do it: Write down the names of the three formats you'd like to update. Delete these three formats from the format catalog. Existing paragraphs using these formats now become irregular (*). Open the paragraph designer and display the source format of which you want to take the parameters (LTTopicList). While displaying this format in paragraph designer, enter the name of the first target format in the paragraph designer and click Apply. This creates a new paragraph format, using the parameters from the source format. Now repeat this action twice, each time entering the next one of the three target format names. In the end you've got four copies of the same format, with the required names. Afterwards you can update them all to take over the new parameter sets. Bernd
... View more
‎Oct 25, 2021
01:09 AM
2 Upvotes
Daniela, just use <$paranum> instead of <$sectionnum>. This should solve it. Bernd
... View more
‎Aug 12, 2021
01:45 PM
PDF Bookmarks are a document property which can explicitely be selected for deletion when saving as optimized PDF. Check your optimization settings. In current Acrobat Pro versions, check the settings under "Delete objects", bookmarks are there. In older Versions of Acrobat Pro, the bookmarks could be deleted under "User data", either by enabling "comments…" or or "private application data", I don't remember at the moment. Bernd
... View more
Copyright © 2025 Adobe. All rights reserved.
AdChoices