It's a long time since I've used fontlint, but from memory, it is a utility that is installed as a part of the fontforge package. It is Linux/Unix software. To run it on Windows, you must use CygWin to give a Unix-like environment. Other font validators are available; for example, the Microsoft Font Validator. Whichever font validator you use, my main point stands. Determine whether a fault is reported for the font, and if so, ask the developer to fix it. ... View more

The error message is telling you that the font is faulty. According to the message, the font uses the StemSnapV hint operator, but the interpreter is not finding a value for it. This is most likely because the value is missing from your font. However, it might be missing for other reasons. For example, the PostScipt code that you are distilling might have destroyed the value, before then trying to use it. To start with, use a font validity checker such as fontlint. This might confirm that the font is at fault. I'd also see if you can replicate the issue using from a more common application. Print to a PostScript file, then open that file in Distiller. If the font is indeed faulty, the only person who can fix this is the font's creator. You can contact him at mark@marksimonson.com​. If you do so, give as much information as possible, including version numbers of the Proxima Nova fonts and of any application you are using.Best of all would be instructions for replicating the problem with commonly available applications. As an aside, the StemSnapV value should be a list of average vertical stem widths for different types of chanarcter. At small point sizes, the interpreter uses this width for any stems that have a similar width. This avoids rounding creating noticeable but unintentional differences in stem widths. At larger point sizes no rounding is done, preserving any subtleties in the design. ... View more

I'd start by verifying that you really are using the same .sts file, book files, and FrameMaker application files. This includes any personal settings in \Users\<username>\AppData\Roaming\Adobe\FrameMaker\<version> . Ensure all files are on a local hard disc. This will remove any discrepancies caused by the caches that fileservers use. Wipe any existing output. Generate new output, and verify the datestamps are for now. Use something like the Microsoft File Checksum Integrity Verifier tool, or a file comparison tool, to compare all relevant files on the two machines: source files configuration files application files output files. ... View more

I believe you must edit this statement in main.css: @media screen and (min-width: 81em) { table.headertable td.logo img {                               vertical-align:middle;                               max-height:4em; } I determined this by using the DOM Inspector from my browser's Developer Tools. Clicking on the logo reveals its HTML source, the CSS rules applied (and their location), its computed size and how that was calculated, and so on. I couldn't see any other relevant CSS statements applied to the logo or its parents, but I might have missed something. Oh, and the above is from FM12. I guess FM2015 will be similar, but you never know. ... View more

Choose Format > Document > PDF Setup. In the Include Paragraphs list, select your heading1 paragraph tag. Use the Bookmark Level >> button to indent this bookmark. Repeat for other formats (e.g. ​heading2​) as needed. ... View more

This behaviour can also be caused by virus checking software. If you can temporarily disable any such software, see if that makes a difference. ... View more

Have you tried using FrameMaker 11 to open the FrameMaker 7 files? It might just work. If FrameMaker 7 fails to open them, you can also try a "heroic open": https://forums.adobe.com/search.jspa?q=heroic%20open ... View more

> For some reason, this is how tabs are represented when you get text from a document with the API. The reason is that FrameMaker's original Standard character set encoded a tab as \x08. A strange decision that has caught me out before. Here is that encoding's idiosyncratic use of the control-character space: Hex code Standard character set \x04 discretionary hyphen \x05 suppress hyphenation \x08 tab \x09 forced return \x0a end of paragraph \x10 numeric space \x11 nonbreaking space \x12 thin space \x13 en space \x14 em space \x15 nonbreaking hyphen Some of the above might have changed with the introduction of Unicode support. For example, the various spaces might now be encoded with their correct Unicode value. But the tab weirdness appears to persist... ... View more

Your DNS server is not converting the hostname help.adobe.com into an IP address (for example 23.205.220.88). You can check this by opening a command prompt, and typing this command: nslookup help.adobe.com You should get output similar to this: > nslookup help.adobe.com Server:  dns.mydomain.com Address:  12.34.56.78 Non-authoritative answer: Name:    a630.b.akamai.net Addresses:  23.205.220.88           23.205.220.105 Aliases:  help.adobe.com           help.wip4.adobe.com           help.adobe.com.edgesuite.net           help.adobe.com.edgesuite.net.globalredir.akadns.net I'd expect you're instead seeing an error, perhaps something like this: > nslookup help.adobe.com Server:  dns.mydomain.com Address:  12.34.56.78 *** dns.mydomain.com can't find help.adobe.com: Non-existent domain You might also verify that a different DNS server can successfully resolve the address. For example, using Google's server at 8.8.8.8: > nslookup help.adobe.com 8.8.8.8 Server:  google-public-dns-a.google.com Address:  8.8.8.8 Non-authoritative answer: Name:    a630.b.akamai.net Addresses:  23.205.220.88           23.205.220.105 Aliases:  help.adobe.com           help.wip4.adobe.com           help.adobe.com.edgesuite.net           help.adobe.com.edgesuite.net.globalredir.akadns.net Refer this issue to your sysadmin and/or ISP. If necessary, change which DNS server you are using. A web search will tell you how to do this. ... View more

You can define a specific page or named destination in a URL: http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/pdf_open_parameters_v9.pdf For example: http://example.org/doc.pdf#page=3 http://example.org/doc.pdf#nameddest=foo Perhaps you can open a URL as a workaround? ... View more

Nothing to add to the excellent response from Russ, except just to confirm that if the underlying object is not an FO_Pgf, it is a text line in a graphic, instered using the text tool. ... View more

That should do what you want. yes. ... View more

Read the section Getting and setting the insertion point or text selection in the FDK Programmer’s Guide. The code below is from memory, but should give you the idea of what is required. You should add error checking, and test it. F_ObjHandleT activeDoc; F_TextRangeT textRange; activeDoc = F_ApiGetId(0, FV_SessionId, FP_ActiveDoc); textRange = F_ApiGetTextRange(FV_SessionId, activeDoc, FP_TextSelection); /* * textRange.beg.objId is the ID of the paragraph or text line at the start of the current selection * textRange.end.objId is the ID of the paragraph or text line at the end of the current selection */ if (F_ApiGetObjectType(activeDoc, textRange.beg.objId) == FO_Pgf) {      // we have a paragraph } else {      // we have a text line } ... View more

Sorry, but an Internal Error message does identify the actual error. Below is an explanation, if you are interested. I'd repost, explaining what actions of yours are causing FrameMaker to crash. 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 the FrameMaker application and the DLLs that it uses. This varies between machines, and even on the same machine, and so these numbers also do not indicate the actual 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

It's also mentioned in these posts and their replies: FM12 incorrect selection on clicking list items Pod scrollbox issue It's in Adobe's bugbase at Bug#3798506 - Choosing a cross-reference in the cross-reference pod. First reported against FM 11.0.1. Not fixed in FM 12, and I'd expect still not fixed in FM 2015. ... View more

There's some simple JaavScript code in this thread that just searches the PDF for various regular expressions: https://forums.adobe.com/thread/289547 ... View more

AFAIK: embedded figures are an Inset object the image data is stored as one or more facets each facet is a named property of an Inset object the name typically represents the format or type of data (e.g. OLE, WMF, PNG). The above is extrapolated from the C API, with which I am more familiar. But I've not used insets very much, so I'd trust the manuals over anything I say. ... View more

You can also create a Character Format to position a diacritical, but you have to use MIF to do so, because no GUI is provided: Open a new empty document. Type the character that you want to combine with the diacritical, the diacritical, and a following character Use micropositioning to adjust the position of the diacritical so it correctly combines: select the diacritical hold down the Alt key, and use the arrow keys to position the diacritical Change the Spread to adjust the position of the following character: select the diacritical adjust the value of the Spread in the Character Designer, typically to a negative amount Save the file as MIF. Find the text. It will usually be near the end of the file, and look something like this: <Para   <Unique 999266>   <PgfTag `Body'>   <ParaLine    <String `B'>    <Font     <FTag `'>     <FDX  -41.66%>     <FDY  -27.77%>     <FDW  -20.0%>     <FLocked No>    > # end of Font    <String `’'>    <Font     <FTag `'>     <FLocked No>    > # end of Font    <String `C'>   > # end of ParaLine > # end of Para Use a text editor to create a small MIF file. This MIF file defines a single character format that sets the same <FDX> and <FDY> micropositioning values and the <FDW> Spread value. Chaneg the FTag to an appropriate name. No other content is needed: <MIFFile 12.0> <FontCatalog <Font   <FTag `my_character_format_name'>   <FDX  -41.66%>   <FDY  -27.77%>   <FDW  -20.0%>   <FLocked No> > # end of Font > # end of FontCatalog # End of MIFFile Open the MIF file using FrameMaker. Import the Character Format from the newly opened MIF file into your templates. You can then use the Character Format to position the diacritical, and any others of similar size. Because the values are percentages, and so relative to the fnt size, you can use it in different contexts. ... View more

No direct experience, but some suggestions: An Inset object has a set-only InsetSaveFacetToFile property. This might do what you need. There's not much documentation for it in the Scripting Guide. I'd start by trying values of "OLE" or "WMF" for the facet name. Other facets might exist as named properties of the Inset, so list all the properties, and examine them. The libraries for the FDK (FrameMaker's C API) expose symbols for functions named F_ApiExport() and F_ApiGetExportDefaultParams(). These are undocumented, but I believe they do the reverse of F_ApiImport() and F_ApiGetImportDefaultParams(). There might be corresponding JavaScript methods: GetExportDefaultParams() is documented, but I don't see any documentation for Export(). Again, these might do what you need, if they exist. Finally, the FDK documentation sometimes has more informatioin than the Scripting Guide, so might give some further suggestions that can be re-engineered using JavaScript. ... View more

Mike-Hardy wrote: Tried adding the above to the bug database, but it won't let me: I've now succeeded in adding my contribution as a note on your bug, so hopefully this will give Adobe something to go on. ... View more

Maybe there is some control character or other weirdness in there. See if the right arrow key moves the cursor over the word as expected. Or just re-type it, then spell check again. Restarting FrameMaker and/or Windows might also help. ... View more

Tried adding the above to the bug database, but it won't let me: "Sorry this operation could not be completed at this time, please try again later." Sigh... ... View more

I've used the ImageMagick command line to report how these JPEG files are encoded: identify -verbose <filename> Most fields were identical, or could be explained by tiny differences in RGB values after Paint has done a lossy decode/re-encode of the image data. But the orientation- and geometry-related fields differ significantly. Here are the relevant bits of the output: >identify -verbose four.jpg Image: ...\four.jpg   Geometry: 4128x2322+0+0   Print size: 57.3333x32.25   Page geometry: 4128x2322+0+0   Orientation: RightTop   Properties:     exif:Orientation: 6    >identify -verbose fourR.jpg Image: ...\fourR.jpg   Geometry: 2322x4128+0+0   Print size: 32.25x57.3333   Page geometry: 2322x4128+0+0   Orientation: TopLeft   Properties:     exif:Orientation: 1 The faulty images use RightTop orientation: the 0th row of the image data is the right edge of the image the 0th column of the image data is the top edge of the image but the good ones use TopLeft orientation: the 0th row of the image data is the top edge of the image the 0th column of the image data is the left edge of the image. (The numeric values of the exif:Orientation fields also encode this same orientation.) I suspect that FrameMaker has problems with images that use the RightTop orientation.It might be using a library with such issues; some have been reported. I'd suggest using a JPEG-specific tool that can re-orient the file to TopLeft without data loss, such as a combination of  jhead and  jpegtran. It would be easy to script this change. For the record, there were some other minor differences, mostly offsets to data within the file. These are almost certainly irrelevant. Interestingly, Paint hasn't updated the recorded orientation of the thumbnail, which remains as RightTop. It's also added a single new field to the properties: Image: ...\four.jpg   Properties:     exif:InteroperabilityOffset: 4942     exif:thumbnail:JPEGInterchangeFormat: 5102     exif:thumbnail:JPEGInterchangeFormatLength: 26355     exif:thumbnail:Orientation: 6 Image: ...\fourR.jpg   Properties:     exif:InteroperabilityOffset: 4920     exif:thumbnail:JPEGInterchangeFormat: 5118     exif:thumbnail:JPEGInterchangeFormatLength: 3351     exif:thumbnail:Orientation: 6       unknown: -4126 The change is file size is probably because Paint has decoded and re-encoded the JPEG data, and it is a lossy process. ... View more

This feature was introduced in FrameMaker 2015. See: http://www.adobe.com/uk/products/framemaker/features.html https://helpx.adobe.com/framemaker/tutorials/generate-mobile-apps-video.html For a list of FrameMaker features and their availability in different versions, see: http://wwwimages.adobe.com/content/dam/acom/en/products/framemaker/framemaker_2015/pdf/FM_2015_VERSION_COMPARISION.pdf ... View more

The code you have supplied should be doing the following: Take a length parameter Separate it into variables named number and units Use those variables to set a lenght-in-mm variable Format the length-in-mm with two decimal places. The error message you are getting is "Arithmetic operator is not defined for arguments of types (xs:string, xs:decimal)". This is because you are passing a string to an arithmetic operator, but the operator is expecting a number. I suspect the statements where the number variable is used to set the length-in-mm variable. for example:         <!-- Output the length, translated into mm -->         <xsl:variable name="length-in-mm">             <xsl:choose>                 <xsl:when test="$units='cm'">                     <xsl:value-of select="$number * 10"/> If $number is a string, it would generate the error you are seeing This is the code that sets the number variable        <xsl:variable name="number" select="normalize-space(translate($length, '+-0123456789 abcdefghijklmnopqrstuvwxyz', '0123456789'))"/> It incorrectly does the following: translates a + character to a 0 (zero) translates a - character to a 1 (one) translates the digits 0-7 to the digits 2-9 respectively (i.e. adds 2) discards any 8, 9, space, or lowercase a-z An alternative version of this line is commented out:         <!--xsl:variable name="number" select="normalize-space(translate($length, '+-0123456789.abcdefghijklmnopqrstuvwxyz', '+-0123456789.'))"/--> This strips any lowercase a-z and is more likely to be correct. I'd suggest backing up your current version, and then trying the following change at the start: <xsl:template name="Get-size">         <xsl:param name="length"/>         <!-- Get the number part by blanking out the units part and discarding white space. -->         <xsl:variable name="number" select="normalize-space(translate($length, ' abcdefghijklmnopqrstuvwxyz', ''))"/>         <!-- Get the units part by blanking out the number part and discarding white space. -->         <xsl:variable name="units" select="normalize-space(translate($length, ' +-0123456789.', ''))"/>         <!-- Output the length, translated into mm --> It does essentially the same, but is easier to understand and maintain. ... View more