Lynne's answer is right regarding the Since there is no tab on the last line, there are no leader dots and the page number is not right justified. As an alternative to what Lynne wrote, you might want to add simply a second tab in the reference page, so that the page number get's pushed to the right also for line 2. ... View more

Maybe another idea … You could leverage search for that. Just add the tags and add a hyperlink to the tag, handing over the search string. Like this: http://help.adobe.com/en_US/framemaker/2015/using/#rhsearch=tables&ux=search You can also narrow the search more down to the exact string my putting the string into quotes (%22). Like this: http://help.adobe.com/en_US/framemaker/2015/using/#rhsearch=tables&ux=search You might want to add a # to the tags in general so that it becomes easier to distinguish them for your scenario from regular search strings. This will open the search panel and prefill it with the search results. The quotes make just make it sharper here: http://help.adobe.com/en_US/framemaker/2015/using/#rhsearch=%22tables%22&ux=search You can also use multi-space tags. In this case, make sure to replace the space with %20 in the URL http://help.adobe.com/en_US/framemaker/2015/using/#rhsearch=%22Round%20trip%20table%20properties%22&ux=search. This might be another approach. Also, it's a nice effect: The page currently open just stays open. Only the search panel opens, displaying the results. Cheers, Stefan ... View more

We use MIF for localization and I have the impression that switching to MIF 2015 has drastically decreased the number of matches, which would make sense if the TM was established with a different MIF 1.0 format. There should be no decrease in the number of matches just by switching from MIF12 to MIF 2015, as there were only changes in the MIF format that do not affect the CAT Tool filters. All the latest releases of SDL Trados Studio, Across, memoQ, Star Transit and Wordfast support FrameMaker (2015 release). So, my suggestion is to check with your LSP which CAT tool they are using and in which version and make sure they update to the latest version of their tool. Another temporary workaround (or better: "hack") could be to "fake" the MIF version statement in the MIF files, so that an older CAT tool version that supports only FrameMaker 12, will still process the MIF 2015 files. I have tested this with an older version of SDL Trados Studio (2011) and a bunch of complex FrameMaker 2015 files and did not find any problem. However, this is of course not an "official" solution and just a "hack" – use at your own risk. The only "official" recommendation I can give you is, of course, to update your CAT Tool to a version that supports FrameMaker 2015. Here you go with a list of MIF statements: <MIFFile 8.00> <MIFFile 9.00> <MIFFile 10.0> <MIFFile 11.0> <MIFFile 12.0> <MIFFile 2015> Please note that the newer versions of CAT tools which support FrameMaker 2015, might support also the new Right-To-Left support and languages introduced in FrameMaker (2015 release) like Arabic, Farsi, Hebrew, and Thai. They usually also set the paragraph / character style language setting in the MIF and might change also the text direction attribute. However, this is only important if you have your western language MIF files translated into Arabic, Farsi, Hebrew or Thai. ... View more

As long as you use proper Unicode fonts for these languages (like the Windows system fonts for these languages), both languages should work fine with the new font engine in FrameMaker (2015 release). However, there is no "official" support yet and there are no spell checkers etc. ... View more

regarding the format names: sounds like an error in the r/w rules file. But the main questions is: Why still SGML and not XML? Also, why going through Arbortext? Currently, everyone is moving from Arbortext to FrameMaker … You might find the webinar from Tom Aldous interesting: Be a migration wizard: Transition XML Files Smoothly from Arbortext to FrameMaker ... View more

What did you send to the LSP? FM or MIF? If you sent MIF, open the MIF you sent them in a Unicode plain text editor (like Notepad++ or UltraEdit) and check the first line. If it's MIF 7 you're out of the Unicode world and will have to run the files through translation again with MIFs properly created from FM 2015. If you send FM, check the files you got back from the LSP. They might have created the MIFs from the FM with an outdated "Save all files in book as MIF" plugin that still creates MIF7. This is the most common problem. Ask the LSP to send you MIFs instead of FMs. Then check version in the MIF header. Compare it with the header of a MIF that you created from FM 2015 (via save as MIF). It's very likely that the problem came up at some point in the process when saving as MIF. Also, open in the MIFs in a Unicode text editor (e.g. Notepad++), scroll to the end of the MIFs and check if the text is shown as Thai or as question marks. If it's question marks, you will have to restart the process with proper FM 2015 MIFs. Also please check with your LSP which CAT tool they use (SDL Trados Studio, Across, memoQ etc.) and if the version of their CAT tool is compatible with FM 2015. All latest versions of the "big" CAT tools like SDL Trados Studio, Across, memoQ can handle FM 2015. ... View more

I guess Martin wants to save down FM 2015 files to older MIF versions because his (or his language services provider's) Translation Tool (CAT) is probably not able to read the MIF files. Most CAT Tool MIF Filters parse the MIF header to understand which version of MIF it is. If the version is higher than what the filter was programmed for, the filter usually rejects to import the MIF file. As I said the most secure way is to upgrade the CAT Tool to the latest version (e.g. SDL Trados Studio 2015) with the latest updates. Alternatively, you have to save the FM 2015 files to MIF and then go through an older FM version (as far down as necessary for the CAT Tool). But this is not recommended. A trick that will probably also work is to fake the MIF version header with an older version info. But again, even if the CAT Tool filter will accept the MIF then, it does not mean that it will process the MIF properly and might mess the MIF up in unexpected ways. ... View more

Long before FrameMaker (2015 release) was released we have worked with several CAT tool providers, to support them in updating their filters for FrameMaker 2015. All the latest releases of SDL Trados Studio, Across, memoQ, Star Transit and Wordfast support FrameMaker (2015 release). Therefore, the best approach ist to ask your Translation Service Provider to upgrade his translation tool to the latest version. If this should be not possible – for whatever reason – you can save down from FrameMaker (2015 release) to FrameMaker 12 and from there again as MIF to get FM12 MIFs. Alternatively, you can save the files as MIF from FM 2015 and open theses MIF files in any older version like FM9 and save from there again as MIF. However, I do do not recommend this – you might loose things, that were introduced in newer versions. ... View more

RoboHelp Server 10 also supports Microsoft IIS. Please check RoboHelp Server 10 is now available! – TechComm Central by Adobe for more details. ... View more

Is it always the same character? Like the character "u"? ... View more

Hi, you will need to use CCP instead of AAMEE. I have asked our enterprise support team to contact you directly. They will reach out to you (probably on the e-Mail that you have used for your account here). Kind regards, Stefan Gentz ... View more

Hi, first question: Who did you contact at Adobe without getting a response? Let me know and I will try to track down what went wrong. The official e-Mail account for Adobe FrameMaker and Technical Communication Suite is TechComm@adobe.com A good starting point for development is the FrameMaker Developer Center: Framemaker Developer Center | Adobe Developer Connection There you can download the FDK 2015 Windows installer. From there you can also download the FDK Installation Guide, an Introduction to the FDK and the details on how to set up your development environment and the complete API Reference. Further down on the page there is also a section called "CMS Connector". There you can also find a sample connect for Adobe's CMS "Adobe CQ" (now "AEM") including full source code. This should give your developers a good first start. Let me know if you need any additional information. Please feel invited to drop me a line to gentz@adobe.com! Kind regards, Stefan Gentz ... View more

Hi, that should be possible. Just setup your own configuration and save the Default.sts as your own settings file. Then you can rename this settings file from *.sts to *.zip or *.sts.zip and unzip it. Now you have all the template files in front of you. There you will also find the three graphics for the index button in the navigation: index_desktop.png index_tab.png index_mobile.png You can replace them with your own ones. Use an image of 31x23 pixels for best results. Of course it makes sense to design a PDF button that fits into the design of the other buttons for a nicer user experience 😉 Now you will have to tweak the file that contain the code for this. This can be done in the Topic.slp file. But this one is a little bit more trick and you need to have knowledge of HTML, CSS and JavaScript to do it. Search for <!-- Function bar with TOC/IDS/GLO/FILTER/FTS buttons --> and <!-- Index --> to find the sections with the code for the index. You can tweak them or – maybe better – add new sections / links for the PDF. If you struggle, Willam van Weelden‌ is an excellent contact for this. He also runs http://www.helpessentials.com/ where you can get customized layouts and skins for RoboHelp. Stefan Gentz ... View more

Hi Jochen, this was not a FrameMaker functionality for sure. In FrameMaker 2015 you can use > File > Package... to collect all the graphics of a document that are located in the same folder as the document or in subfolders and "pack" them along with the document. If all the documents graphics are in the same folder, you can also simply move this folder, while the document is closed. When you reopen the document, FrameMaker will ask you where the images are. Just browse to the new folder, select the graphic FM is asking for and make sure the radio button "Update Document To Use New Path" is selected. FM will now look for all "missing" graphics (referencing to the old location) in the new folder and automatically re-link them. Kind regards, Stefan ... View more

Peter, please also comment with this info on the blog post itself! This is very helpful! ... View more

You're welcome 🙂 ... View more

My first hunch was that it is maybe a bug coming from the style name starting ":" – but no … what's making the change difficult, is the new "Auto Suggest" feature of the style name, that will automatically pick up existing style names. Great feature, but makes renaming in fact difficult. This is how you can change the paragraph style name from :a1XR to :a1 (a little bit more detailed, if someone else should run into the same): Click in the style name field ("Paragraph Tag"). The style name will be selected (highlighted). Press right arrow key once. Cursor will go to the end of the style name. Delete XR. Notice that that "Auto Suggest" dropdown will open. Press ESC key on the keyboard. This will end the "Auto Suggest" mode. (Drop-down will close.) Click "Update All". Confirm the FrameMaker dialog asking you "Rename all :a1XR tags to "a1"? with OK. Now the style name will be properly update as expected. In a nutshell: The solution is to press the ESC key to end the Auto Suggest mode. ... View more

You're welcome 🙂 ... View more

Hi Matt, I just recoded a small video with captivate, published as mp4, referenced the mp4 in a FrameMaker document, assigned a poster image to the video and saved it as a PDF. Worked like a charm. I tried multiple PDF settings (tagged, untagged, multiple joboptions, RGB vs CMYK), but could not produce any problems regarding this. Maybe this is related to a encoding (H.264 / H.265 etc. / Audio Encoding (AAC, MP3, MP2 etc.)? How is your mp4 encoded? How did you create it? And: How big is is? Did you als try it with a smaller one? Suggestion: Record a small video (just a minute or so) with Captivate and try again with a new document. Does the error still happen? Cheers, *Stefan. ... View more

RoboHelp 2015 officially supports Windows 10 since Update 1 (12.0.1). Please see here: RoboHelp (2015 release) – Update 1 released – TechComm Central by Adobe‌ and here: Resolved in Adobe RoboHelp (2015 release) and subsequent patch releases. Older versions of RoboHelp will not be updated to support Windows 10. ... View more

TCS support should be already working with you by now. The crashlogs primarily contain information about the function calls and the parameters, that were made while doing the operation that resulted in the crash. Content of the user document is not in the logs. The “Internal Error” details contain error codes specific to FM and again do not have any content related information. I hope this clarifies your question. ... View more

I will check this with engineering and let you know asap. Meanwhile it would be great, if you could try to find out with your users, in which situations they face these crashes. ... View more

Please feel encouraged to send it to fmerror@adobe.com, as suggested by Arnis Gubins‌. We will definitively look into it. Please put tcs.support@adobe.com on CC. We will definitively look into it. ... View more