Your ItemL3 has an ancestor named ItemL3, but you also use an element named ItemL4?   I think the wrinkle is in trying to display the attribute of an ancestor that has the same element name and attribute name of the current element.   Try testing your syntax with other elements and attributes that don't overlap names/labels with your active element.   ... View more

It's not easy to follow, as you have both an element and an attribute named TAILS.    As written, it looks like you are asking to display the Tails attribute value(s) on an ancestor element named ItemL3. Does it work if you rewrite it as  Prefix: Tails: <$attribute[Tails]>   For more detail, see the last example on p123 of FrameMaker - Structured EDD Development Workbook   ... View more

Please share the attlist   ... View more

Excellent. I suggest posting the tracker link so other French authors and localization (localisation!) folks can upvote it and speed up its fix   ... View more

So, it sounds like the feature is working, but not providing the result you need.  Occasionally, Adobe employees like @pulkitn will drop in with a thought. I've included him here to perhaps get perspective. Have you reported this via the tracker.adobe.com system? That's the official way to get an Adobe bug looked at for possible correction in future versions.     ... View more

Hi Andrea,  If Fm thinks you have a MiniTOC in there, you can use Find/Change in two different ways to locate the offending MTOC. First, search for Marker of Type: Hypertext Then, if that doesn't solve the issue, check your reference pages for a MTOC page. On that page, check the paragraph tags, and then search your doc for the Paragraph Format(s) shown. In my case, it's showing a Heading1MTOC paragraph style is in use. You might also look at your Paragraph Catalog to identify any MTOC entries. Here's what mine looked like     Here's a video to explain https://www.youtube.com/watch?v=VPM76rZj6rU   ... View more

Hi Stephen, sorry to hear you're having destructive crashes! I have only seen that a few times in Fm 2022, but I have seen it.   Using Autosave options in the Preferences can be helpful and setting Backup on Save can be helpful but creates a lot of extra files to wade through. However, when you try to reopen your file after a crash, I would expect to see a message about the crash recovery file (.recover) that you can open and save off as a file to potentially save that hour of work that you did. However, it sounds like you're getting files with gibberish extensions. When I've had those in the past, I've copied my content into a new doc and abandoned the one that keeps crashing.   ... View more

I don't speak French, but it certainly looks like that's the Smart Quotes feature setting. You'll need to enable Smart Quotes and set them up as you wish in your Preferences. Deselecting Smart Quotes will disable your quote settings, and it appears you've already discovered this on your own.   ... View more

Did you view the New Feature video I created for the language-specific smart quotes feature? Choosing the correct character in your spelling preferences should get you straightened out.   https://www.youtube.com/watch?v=1yRuon3tb3E     ... View more

There are around 30 replies in various threads, so here's a recap to get things in the right direction: Your subject and description aren't 100% accurate. While the EPS may have an embedded size, your XML doesn't specify a size, so you might consider editing the subject/description to read "Not scaling to desired size" You have a number of paths you can investigate: Editing the EDD to provide default formatting for your graphics elements that are missing formatting attributes and values Using read/write rules to provide formatting upon XML import Using Find/Change on the XML to add the attributes you want for formatting Scripting on the imported XML in FrameMaker (as suggested by @frameexpert ) Please keep us posted!   ***Also, I don't believe FrameMaker 11supported XML as a working file format...are you opening XML or .fm docs? ... View more

Ok, per your sample, there are no attributes or values on your graphics, so you'll want to set defaults in your EDD, or set a value via your read/write rules.  I'd guess that setting defaults in the EDD would be the easier route.   ... View more

Is the fm property import size value being properly handled? If not, focus on that.   Is a default value defined in the EDD? If so, try something like this element "graphic" { is fm graphic element; attribute "XXXX" implied value is "YYYY"; }    ... View more

Please share the original XML representation prior to import to Fm   ... View more

Offhand, I see that you don't have specific reader or writer rules. If you're not saving back out to XML for a deliverable, you may have luck with a specific reader rule to import the graphic, without having to account for the value when saving out to XML.   It looks like (many years ago) the default behavior of Fm 11 parsed your attributes and values in a way  acceptable to your needs. Fm 17 seems to have different default behavior, so you may need to explicitly explain what you need done with the values. I'm not clear on the specifics of your graphics (pixel count, etc.) so you will likely need to analyze the differences between the "working" graphics and the "non-working" graphics. You mentioned that you're working with XML; does that mean your Fm documents can use the XML view and you can see the underlying code? If so, compare the raw XML representation to the Fm XML View of a properly formatted image to the XML View of an improperly formatted image. This comparison may give you insight into what you need to do.   ... View more

Also, are you saving as .fm or some other format like dita XML or sgml? if so, the issue could be with one or more template files applied when you open the doc.   ... View more

It can, and certainly doesn't hurt to try.   ... View more

I believe you need sub rules for values    ... View more

It sounds like you're already using a read/write rules file in your structapp. Have you set up read/write rules to specify fm properties for the scale of the graphics?   ... View more

Just as Adobe hopes that helpful users will answer your questions here in this user-to-user forum, Adobe hopes that really attentive people like you will file these items in the tracker, especially for things that are critical to your workflow. https://tracker.adobe.com/#/home   FrameMaker 2020 and earlier bug trackers are not likely scrubbed by engineers for issues that still exist in the current product. If no current version (Fm 2022) tracker item yet exists, I would be surprised if the bug is addressed any time soon. I'd happily vote for that item...What is/are the Fm 2022 (v17) tracker link(s) related to your issue(s)?   ... View more

The next time you update Fm, change the preferences folder name from 17 to 17x (or similar) prior to updating. This will preserve your preferences, including a Workspaces directory, and should allow you to add your workspace file from the 17x directory back into the 17 directory after updating. Here is a short video to show you how it works. https://www.youtube.com/watch?v=yrr3iaXM778 ... View more

Just for anyone reading this thread... @Robert at ID-Tasker  is describing a quirk in InDesign, not FrameMaker. Doing Save As in FrameMaker has no value in speeding things up. In fact, using Save As would likely break all the referencing between documents that FrameMaker is so good at.   ... View more

Hi Ran, how've you been? It sounds like you're seeing something I've noticed with TOC and IX for years: When adding a new generated file to a book, the generated file opens up in its own window when first opened. After that, and perhaps after consolidating into the tabbed docs in the UI, it seems always to open into the tabs as expected.   Are you perhaps seeing that all files in your books have this behavior?   I'd test it myself, but can't update my working copy until a client is able to update from 17.0.4 in a few weeks.   ... View more

You'll need to disable/remove autonumbering in the title.1 paragraph style in your template. Since you're working with a set of Book with Components files, you might want to save off a chapter of your book as Template.fm or similar, make the change, then import your paragraph styles back into the appropriate .fm files. NOTE: Your 1.9.6 numbering appears to be typed into the doc, or is otherwise acting as content. This may cause issues if you are authoring in your Book with Components set of files.   ... View more

I wonder if you'd get better results asking this question in the Id forum, where folks are looking for things Id doesn't do (or do well) For myself, I like Fm's ability to manage content across VLB (Very Large Books) and InDesign's ability to microdesign a specific page.   ... View more

Both likely solve your problem, but without detail it is hard to tell which would be preferable. Perhaps you could take a few minutes to create a lorem ipsum example instead of the yellow box.   ... View more

Out of curiosity, why won't the MiniTOC suffice for your list?   ... View more

Just didn't want Derick wandering off in the wrong direction!   ... View more

For clarity, I think @Jeff_Coatsworth  was thinking about a List of Elements and Paragraphs as shown below. The List of References is great for other things, but (unless my coffee hasn't kicked in yet) I don't think the LOR would collect your heading style as you described it.     ... View more

Hi Kimberly,  My thoughts are in a different direction...are you looking to link a graphic produced by a 3D application like SolidWorks? If so, look to place a U3D image, which allows you to generate all manner of hotspots, links, tables, views, animations, to the extent those named things have been created in the modeling application. https://www.youtube.com/watch?v=C_s8SRWu2_M   ... View more