Your crash might be related to the crash that is described in this recent thread: consitently crash pasting text frame into graphic frame ... View more

And also try adding the <$alphabetics> building block back into the SortOrderIX paragraph: <$symbols><$numerics><$alphabetics> ... View more

Try changing your GroupTitlesIX paragraph to use upper case: Symbols[\ ];Numerics[0];A;B;C;D;E;F;G;H;I;J;K;L;M;N;O;P;Q;R;S;T;U;V;W;X;Y;Z,Å,Ä,Ö ... View more

Try the following, in order: Reboot and try opening the file again. Make a copy of the problem file. If the copying fails, the issue is with your filesystem. Get a good repair tool and use it. Try a "Heroic Open" from FrameMaker. This command bypasses a lot of error checking code and does its best to open the file: Type Esc o H (i.e. press and release the Escape key, then type a lowercase letter o followed by an uppercase (i.e. shifted) letter H. Choose your problem file, and click Open. If the file does open, do an immediate Save As MIF Close the problem file. Open the MIF that you saved above. Save the MIF as a FrameMaker file. Extract any ASCII strings from the file. This might give you most or all of the text you've typed: The Linux "strings" command will do this for you: strings myfile.fm > myfile.txt Or use a text editor. ... View more

I've not time to check this, but if a search string has a backslash, that backslash might be consumed by the compiler or interpreter. Try a double backslash, e.g. "\\PStart of a line". Note also that there are new find properties and values for regular expressions. These don't appear in the FDK documentation: #define FS_FindCustomizationFlags 15 /* IntT the following ored together */ ... #define FF_FIND_USE_REGEX ((IntT) 0x10) #define FS_RegexFlavour 17 /*Enum one of the following*/ #define FR_USE_PERL 1 /*Use perl flavour*/ #define FR_USE_GREP 2 /*Use grep flavour*/ #define FR_USE_EGREP 3 /*Use egrep flavour*/ ... View more

Don't look for patterns - you're wasting your time. An internal error looks like this: Internal Error: 12044, 22580916, 22581210, 25525605 It is accompanied by a FrameLog text file. This includes a stack backtrace (the hexadecimal addresses of the internal procedures that were in progress): The first number in the internal error is the version of FrameMaker that you are using. So it has nothing to do with the actual error. The remaining three numbers in the internal error are the first three addresses in the stack backtrace, in decimal. They depend on where Windows has chosen to load FrameMaker, and so typically differ between instances of the same error. The FrameLog file also contains various other information, including: the version of FrameMaker in use, with the locale, mode, and view the version of Windows in use the last few fcodes (internal FrameMaker function codes) relocation information (the addresses of each FrameMaker component): combining this with the stacktrace shows exactly what procedures were in progress Windows exception and backtrace details. It is only useful to Adobe engineers, ... View more

If you search the FDK Programmer's Reference for FP_PDFPageHeight, you'll find the following documentation within the Object Reference chapter, FO_Book section: Property Type Meaning FP_PDFPageHeight MetricT Page height for the generated PDF FP_PDFPageWidth MetricT Page width for the generated PDF So these are properties of type MetricT . You must set them using the call F_ApiSetMetric(). #include "fapi.h" VoidT F_ApiSetMetric(F_ObjHandleT docId, F_ObjHandleT objId, IntT propNum, MetricT setVal); (RTFM for more details.) In your case, you need something like the following: F_ApiSetMetric(FV_SessionId, bookId, FP_PDFPageHeight, 297*FV_METRIC_MM); F_ApiSetMetric(FV_SessionId, bookId, FP_PDFPageWidth, 210*FV_METRIC_MM); where bookId is the id of your book, that you later pass as the first parameter of F_ApiSave(). ... View more

I'd suggest that you set the FP_PDFPageHeight and FP_PDFPageWidth properties for the FO_Book object. See also the other PDF properies listed for books in the FDK Programmer's Reference. If this doesn't work, try asking again in the Adobe: FrameMaker Scripting forum. ... View more

This might be a difference in the font configuration within the maker.ini file. This is found within the FrameMaker application. There is also a user-specific copy that can override the main settings. See the top of the main maker.ini file for details. I'd investigate the following. The Angles setting defines the vocabulary that is used for italicized fonts. This is the default for FM12: ; ; Definition of the font vocabulary: ;  Angles, Variations: a list of the words. ;  Weight: the list of words and the associated weight for Windows, if any. ; Angles=Regular, Kursiv, Slanted, Oblique, Italic, Obliqued Look for differences between FrameMaker 12 and 2015. Don't forget to check for overrides in your personal maker.ini files. Also, search for Akzidenz-Grotesk in the files. Are there any settings in one file that are not in the other? Likewise for Kursiv. Finally, the following might provide a workaround: Quit FrameMaker 2015. Open your personal FrameMaker 2015 maker.ini file in a text editor. This file is typically in \Users\<username>\AppData\Roaming\Adobe\FrameMaker\<version>. Add the following two lines: [WindowsToFrameFontAliases] AkzidenzGrotesque Pro, Italic, *=AkzidenzGrotesque Pro, Kursiv, *, Regular (I'm assuming there isn't already a WindowsToFrameFontAliases section) Save the maker.ini file Restart FrameMaker 2015. If necessary try this again, changing the first occurence of AkzidenzGrotesque Pro to any variation you can find displayed in Windows, or within the font file itself (e.g.  AkzidenzGrotesque-Pro or AkzidenzGrotesquePro). If this works, consider adding the setting to the main maker.ini file so it applies to all users. ... View more

FrameMaker 2015 adds support for mini TOCs, which probably do what you want. See Getting started with mini TOC. No experience myself; we're still on FM12 ourselves. ... View more

Some suggestions: Confirm that your FM10 application can display the TIFF files: Identify a TIFF file that is referenced in the FM8 MIF, but that is not displaying when you open the MIF. Create a new document using FM10. Import the TIFF file. Confirm it displays correctly. FrameMaker cannot display all variants of the TIFF format. For example, it doesn't do transparency or CMYK. If the TIFF doesn't display, use a graphics editor to convert it to a supported format, such as an RGB PNG file. After opening the FM8 MIF, confirm that the View menu has an entry to Hide Graphics. If the View menu instead says Show Graphics, there is a statement in the FM8 MIF that is disabling graphics display. Choose View > Show Graphics to reverse this. Post the original FM8 MIF here. Preferably an <ImportObject ... > # end of ImportObject, and the object that wraps it (e.g. a <Frame>). You're posting the FM10 MIF, resulting from opening the FM8 MIF and re-saving it as MIF. Whatever is causing the problem might be stripped out by this process. Compare the FM8 and FM10 MIF files for a single graphic. Any major differences might give a hint of the problem. Expect some minor differences, such as changes in the <Unique> identifiers. ... View more

The last time I reconfigured the UI in this way was a long time ago (FrameMaker 4 or 5, if my memory is any good). So my own experience is a bit out of date. I'm not sure whether or not you can pass a parameter in the way you're trying. Another approach you could try is to modify the config files so that your chosen key combination emits the keystrokes to select Emphasis (e.g. F8, then "Emphasis").This was certainly something I did back long ago, but I cannot remember the precise details, nor do I know if it would still be possible. Sorry I cannot be more help. ... View more

You might be able to do all you require by modifying FrameMaker configuration files. This Adobe-authored document describes how to do so for FrameMaker 7.0:: http://www.daube.ch/docu/fm-documentation/FM/fm07-Customizing_Frame_Products.pdf The above document has not been updated for any newer versions. The documents below give some extra information about customizing more recent versions of FrameMaker: http://www.daube.ch/docu/files/etb-customising-fm.pdf http://www.daube.ch/docu/files/etb-customising-fm12.pdf See also the many other useful resources on the Working with FrameMaker section of Klaus Daube's website. ... View more

For Unix command lines with multiple lines, you can add a backslash at the end of each line. This makes Unix concatenate the lines before interpreting them. For example this: yum --enablerepo=sina-cd-* install \   sina-mgmt_meta_all_in_one_* will be interpreted as this: yum --enablerepo=sina-cd-* install  sina-mgmt_meta_all_in_one_* No idea on the keyboard shortcut, I'm afraid - but it wouldn't surprise me if they use different shortcuts for different UI languages. ... View more

FrameMaker has no control for these features. However, the default figure style in most OpenType fonts is tabular lining figures.This might be the case for Font Bureau's Interstate. I'd suggest creating a paragraph format with pair kerning disabled, and minimum, maximum, and optimum word spacing all set to 100%. These settings are to prevent FrameMaker from respacing your text. Then use that paragraph format in a test table, and see how it behaves. To insert a numeric space, use the keyboard shortcut Esc-space-one (i.e. press and release the three keys, one after the other). ... View more

The FrameMaker application has a top-level file named fmreg.txt. This contains registry settings used to setup the application, with a placeholder for the actual install directory. FrameMaker checks for these registry settings at startup, and applies them if missing - including immediately post-install. To do so, creates a temporary file, replacing the placeholder for the install directory with the actual value. The file you are seeing is almost certainly this temporary file. Compare it with the fmreg.txt file to verify. ... View more

A further alternative would be to import the Word files into FrameMaker 12. Then select all, and copy to the clipboard. Open a document in FrameMaker 2015, and paste into that document. This gives you the working import filters of FrameMaker 12, and the other benefits of using FrameMaker 2015. If you were feeling really brave, you could try replacing the filters in FrameMaker 2015 with those from FrameMaker 12. I don't have FrameMaker 2015, so I'm guessing a bit, but: Quit both versions of FrameMaker. Backup the maker.ini file within FrameMaker 2015 by making a copy, say as maker.ini-2015. Rename the filters subdirectory within FrameMaker 2015, say to filters-2015 In the [APIClients] section of the FrameMaker 2015 maker.ini file, remove all entries that reference the filters subdirectory, and replace them with the equivalent entries from the FrameMaker 12 file. A diff of the two files will help you to see where changes are required. Copy the filters directory from FrameMaker 12 into FrameMaker 2015 Restart FrameMaker 2015 and test. Obviously this has lots of scope for breaking things. I'd not waste too much time on this - most likely, either it will or won't work, and that's it. If it doesn't work, quit both versions of FrameMaker and back out your changes. ... View more

Early versions of FrameMaker 8 had a bug in the SVG importer that could cause FrameMaker to crash. Ensure that your copy of FrameMaker 8 is fully patched. Downloads are here: Adobe - FrameMaker : For Windows I believe that you must install each patch in turn. ... View more

The revhistory element in DocBook might provide some inspiration. ... View more

See How to detect the OS with ExtendScript? ... View more

The results of your testing indicate that FrameMaker is defaulting to using inches. The default units might be hard-wired, but might instead be derived from the units (View > Options, Display Units and/or Font Units) for either the template or the EDD. I'm afraid that I don't have any structured application available right now to test this myself. ... View more