FrameMaker

Hello -- I have one file in a 32 file book that is not correctly displaying the correct character style format. There is a footnote paragraph style that uses 7.5 pt, 51% process grey font. When we are reference a legal case name, we italicize it using a character style called emphasis (see attached images). We also use the emphasis character style in the main text, which for decades had worked just fine. However, now -- in just one file, applying the emphasis character style anywhere in the body, it brings in the properties of the footnote paragraph style. Previously it would simply ital and leave the other paragraph style properties as-is.  Here's what I've tried to no avail:MIF washImporting character styles from a file that's working as designed. It does nothing at all.Setting up the Character Designer to match the default font properties -- except the italics (this changes the footnote italics to match the main body text).System:Win

I need to take out 3 pages from one document .Fm file and incorprated those pages into another .fm file. quickest and easiest way to do this. 

I am working on a big book which has been made as a structured book. I am working on in unstructured FM2020. The cross references are a challenge. They are made using elements, and I can't make them update. Changing the cross reference format to paratext does not seem to help. Is it possible to make them work in unstructured mode?

When I try to publish a file to Kindle I receive a message that tells me I need Amazon's KindleGen program. Amazon no longer supports it and it is not available. What do I do?

Hello everyone! I recently started using FrameMaker.The question is as follows: how to configure the program so that the label automatically appears on an empty page (for example: "page reserved" or " intentionally left empty").With respect, Igor Chumak.

I am using FM 2019 Unstructured.How can I get the font of the cross-reference (in blue) to match the font of the paragraph containing the cross-reference?The cross-reference format is <Default ¶ Font><zTDref><$paratext>zTDref is set to As Is for everything except color. I have tried with and without <Default ¶ Font> but the cross-references are always in the source font. 

Hello fellows,   Is there a programmatic way to import the paragraph style catalog configuration set to Customized List to another FM file? Framemaker doesn't allow doing that via the UI.   Thanks!

  I made custom toc to use <$elemtextonly>.But It still has suffix text. Does anybody know this problem?  

In opening a small file (2 page letter) that was created two years ago, caused Framemaker 2019 to crash back to the desktop (I tried to attach the file but when I clicked 'Post' it got stripped out, saying the file doesn't match its file extension). Several other files from the same time period cause the same behavior. The file header says <MakerFile 12.0>Can anyone shed some light on this?

Hi I want to run extendscript in framescript. is it possible  ?

Hi  do you know how can I flatten conref in framescript, I have it in extendscript - can you convert it to framescript ? function flattenConref(oDoc) {var oConref = oDoc.FirstTiInDoc;while (oConref.id != 0) {var oNextConref = oConref.NextTiInDoc;var tloc = oConref.TextRange.beg;var eloc = oDoc.TextLocToElementLoc(tloc);var oElem = eloc.child;oConref.ConvertToText();var lElemAttributes = oElem.Attributes;var i = 0;while (i < lElemAttributes.length) {if (lElemAttributes[i].name == "conref") {lElemAttributes[i].values[0] = "";oElem.Attributes = lElemAttributes;break;}i++;}oConref = oNextConref;}}

It seems like I posted something like this a long time ago, but I am not sure. I have some table elements in an FrameMaker document that I want to write out to XML with ExtendScript. I find the XML object in ExtendScript very useful and I am hoping to use that instead of isolating each table and using Save As XML. I suppose I need some kind of recursive function to write the elements and attributes to XML, but if anyone has an algorithm already developed, I would appreciate seeing it (or just having it described in pseudocode). Thank you very much. -Rick

Dipping a cautious toe in the exciting waters of structured documentation; or, rather, trying my hand at using structured FrameMaker instead of / as well as my usual DITA IDE.First minor question:The Courier font is not availableThe Zapfdingbats font is not availableQuite right; they aren't! so, how do I persuade structured FM to use something else, from now on and for ever? I'll probably have more interesting questions later ;-}

Since my system is English the locale sort does not provide any benefit. sNamen = ['Käfer', 'côte', 'Bären', 'küssen', 'Kasimir','coté', 'analog', 'Ähnlich', 'Äpfel']; $.writeln (sNamen.sort()); $.writeln (sNamen.sort(function (a, b) { return a.localeCompare(b)})); Results in Bären,Kasimir,Käfer,analog,coté,côte,küssen,Ähnlich,Äpfel Bären,Kasimir,Käfer,analog,coté,côte,küssen,Ähnlich,Äpfel On a German or French system I expect a different order in t he second result lineCan someone with such a locale prlease test?And do you know how I should extend the sort function to get the uppercase and lowercase letters together: A, Ä, a, ä, B, b, C, c, ç, ... ?

So … I have a whole bookmap's worth of valid DITA files I've developed with XML Mind, and it seemed to me they would be a good starting point if I want to explore using structured FM for DITA.The first thing that hits me when I open any of these files in FM10 is that FM (naturally) applies its own page layouts and paragraph styles. Purely logical, since I haven't defined anything else. Keeping my fingers well away from ths structure, I use the familiar paragraph designer to update the styles FM has applied and soon have a pleasing combination of DITA structure and FM layout … until I save and re-open the document, and find all my formatting has been discarded.Deceptively simple – can of worms perched on tip of iceberg – question: what do I have to do to update the layout/styles? I realise there may be many more styles defined than elements used by my simple DITA files, and (even) that the inheritance we miss in unstructured FM may suddenly spring in to complicate matters in structured:

Hello.I'm handling a ditamap file with FDK.I would like to know the selected file name when I exceutes a context menu command at the ditamap pod.I added my code below. #define GET_FILE_NAME 1 VoidT F_ApiInitialize(IntT initialization){   F_ObjHandleT specialMenuId;/* Get the ID of the special menu. */specialMenuId = F_ApiGetNamedObject(FV_SessionId, FO_Menu, (ConStringT)"!DitamapContextMenu");/* Define the commands and add them to the Special menu. */F_ApiDefineAndAddCommand(GET_FILE_NAME , specialMenuId, (ConStringT)"GetFileName", (ConStringT)"Get File Name", (ConStringT)"");} VoidT F_ApiCommand(IntT command){  switch (command)  {    case GET_FILE_NAME :       F_ApiAlert((ConStringT)"The file name is...!", FF_ALERT_CONTINUE_NOTE);      // I want to get the selected file name here.    break;  };} Thanks. 

 ** My FrameMaker is a trial edition. When I clicked "Topic" in XML's tab, the message above popped up. Then pop up internal error and the FrameMaker goes off. What should I do for solving this problem?

I am using doc.Import to import a text file into FrameMaker. The text file is encoded in UTF-8. Is there a UTF-8 Constant for importing text files in FrameMaker? Here is my function: TTC_MB.importFile = function (filename, textLoc, doc) { var importProps, retProps, i; // Get default property list for importing documents. importProps = GetImportDefaultParams (); // Get a property list to return any error messages. retProps = new PropVals (); // Set specific import property values to import the document. i = GetPropIndex (importProps, Constants.FS_AlertUserAboutFailure); importProps[i].propVal.ival = false; i = GetPropIndex (importProps, Constants.FS_HowToImport); importProps[i].propVal.ival = Constants.FV_DoByCopy; // Attempt to import the document. doc.Import (textLoc, filename, importProps, retProps); };  

    Dear all,A crucial detail seems to be that the script to be run/debugged must be from the opened folder. Otherwise I get messages concerning missing/notfound targt although FM is open and the targt is addressed in the script by //@target framemakerFor scripts not needing the connection to FM the folder is not a requirement.My setup of launch.json: { "version": "0.2.0", "configurations": [ { "type": "extendscript-debug", "request": "launch", "name": "Run current file", "program": "${file}", "stopOnEntry": false } ] } FindingsWhen Debug is not active F11 switches the display to full screen. Obviously we are in a browser window and F11 triggers the kiosk mode ...It is not possible to step into the script with F10/F11 - this ... see above. To step into a script it is necessary to have at least one break point. From there on I can step with F10/11and continue with F5.I have not yet tested whether"stopOnEntry": true​would

I noticed that Esc f i o does not work in v2020. (Esc f i f does....) I hate using mouse-driven menus and want all of my memorized shortcut keys to work when I upgrade versions. Is there a workaround? Or do I have to wait for Adobe to create a patch? Does anyone know of any other shortcuts that don't work?

Hi community,I´m quite new to FM and so searching some beloved word features...I like to make styles based on other styles so that maintenance is easier - updates need less time.- In MS Word you have the possibility to set-up style templates hierarchical via the "based on" setting in the "designer" (German Formatvorlage basiert auf).When doing it clever, its quite effortless changing e.g. your base font type (if CD has to change) How do I manage that in FM, I have not found a similar option (my version is 2019)If this is not possible, wht?s the best practice? Any advice?  

I have created a bug report with Adobe (FRMAKER-9478 ) for this bug. I have copied the problem description from there for reference. When F_ApiGetTextForRange and F_ApiGetText return text containing mdash and ndash characters, with the flags FTI_String | FTI_TextObjId and encoding set to FrameRoman, they are returned as \x14 and \x13, instead of \xd1 and \xd0. If the flag is FTI_String, they are returned correctly as \xd1 and \xd0. The bug occurs with both 2019 and 2020, but not in 2017. The bug report lists workarounds, the use of UTF-8 encoding is the one I have implemented. Please note that other special characters may be affected and/or other FDK calls. I have verified the two mentioned above fail. I would appreciate it if you would vote for this rather bizarre bug to be fixed by Adobe. Thanks Jon.

Auf einen Laptop mit Windows 10 läuft seit mehreren Monaten eine aktivierte Version von Framemaker 11. Seit einigen Tage verlangt Framemaker nun beim Start nach der Seriennummer und wenn man die - gültige und bereit seit Monaten auf diesem Rechner genutzte - Seriennummer eingibt erfolgt die Rückmeldung, dass diese Seriennummer bereits auf zwei anderen Rechnern aktiviert sei, was definitiv nicht der Fall ist.Hat jemand eine Idee?Vielen Dank schon einmal für Eure Hilfe.HeinerB887

1. <title>2. <table>3. <note>4. <p>5. <note>6. <p>  For your information: Portrait, Korean langauge, Korean font, FM 2019 This is a rotated table. No.3 and No.5 warning (admonishment) text is rotated properly. But, texts in No.4 and No.6 paragraph under No.3 and No.5 warning element are not rotated properly. Can you give a little hint how to solve this problem (Korean texts in paragraph under <note> element are not rotated properly)? For your information, when I see this page in FM, all texts are rotated well. But, after publishing in PDF, a text rotation issue occurred in PDF file.

As you can see the above image, a period mark moves to the next line.Can you give a hint how to solve this problem (hanging punctuation mark: period, comma, closing parenthesis)? For your information: Korean language, Korean font, FM 2019