Watermark linked to a table or anchored frame

Hello
I'm having a problem. I have a table wich has a watermark. I created two more master pages with the watermark and applied to the pages containing the table.
The problem comes when I add or remove some pages before this tables. The master page still applied to the same number page and the tables pages not.
I tried to insert the watermark into an anchored frame positioned 'Outside column' but it overlaps the table content.
How can I solve the problem?
Thank you in advance
Best regards.
Raúl

You should be using the Master Page mapping to tie a specific paragrah (i.e. the one used to anchor the table) to a custom Master Page.
See:
http://www.adobe.com/print/tips/frm7masterpage/index.html or download the PDF at: http://www.adobe.com/print/tips/frm7masterpage/pdfs/frm7masterpage.pdf
http://rjacquez.com/how_to_apply_master_pages_auto/
http://tv.adobe.com/watch/tips-and-tricks-for-technical-communicators-to-maximize-producti vity/master-page-mapping-tables/
http://wiki.scriptorium.com/tiki-index.php?page=Mapping+paragraph+tags+to+master+pages
http://www.aptsolutions.com/pdf/MasterPageMaps.pdf

Similar Messages

  • Accessibility: Reading order of tables and anchored frames

    I am creating accessible, tagged (section 508 compliant) PDFs in FrameMaker 9. The reading order for tables and frames is not correct.
    When I view the PDF reading order using Adobe Acrobat Professional or another screen reader, anchored items such as tables and anchored frames are  placed last in the reading order, regardless of where they appear in the document flow or page layout. The reading order skips over all tables and frames, reading all paragraphs on a page first, then reading the tables and frames as the last objects on the page. This logically doesn't make sense to skip over tables/frames as they generally apply to the content that preceeds it.
    For example, the following document structure:
    <Paragraph 1>
    <Table 1>
    <Paragraph 2>
    <Anchored Frame 1>
    <Paragraph 3>
    <Anchor Frame 2>
    <Paragraph 4>
    is being read by assistive technology as:
    <Paragraph 1>
    <Paragraph 2>
    <Paragraph 3>
    <Paragraph 4>
    <Table 1>
    <Anchored Frame 1>
    <Anchor Frame 2>
    I want the document structure to be read correctly as intended.
    In otherwords, the PDFs generated by FrameMaker 9 are not completely accessible because of incorrect reading order output by default. This information is not listed in the VPAT for FrameMaker 9.
    I want to avoid any post processing using Acrobat's Touch Up Reading Order tool. Is there a way to automate updates to reading order?
    Can FrameMaker 9 logically place tables and anchored frames into the correct reading order? How do I adjust these settings?
    Thanks in advance!

    As mentioned above, tables and anchored frames are inserted into thier own paragraph style "Frame". The paragraph style "Frame" is tagged. To my knowledge, there are no options for tagging or not tagging tables or anchored frames.
    Regardless of which paragraph type the table or anchor frame is inserted into, and what that paragraphs tagging settings are, it is still last in the reading order.
    I've tried a variety of options: tagging the "Frame" paragraph style as a sibling, child, and parent of my other paragraphs; I've even tried omitting it from the reading order. None of these options present anchored frames (and tables) in the logical reading order.
    Even images that are inline (within a paragraph; not in thier own paragraph) are not being read as part of the paragraph.  Inline images get skipped over by screen readers and get read at the end of the page, which makes no sense whatsoever.
    All tables and images end up at the end of the reading order (after ALL paragraphs) regardless of the tagging settings.
    Refer to my previous screenshot for a clear diagram of what is happening to the reading order. Each of those anchors is in it's own paragraph style. I want tables and anchored frames to be sequential in the reading order along with paragraphs. (1,2,3,4,5,6 not 1,4,2,5,3,6.)
    I'm using the Tags tab of the "PDF Setup" dialog to adjust these settings. Is there somewhere else I should be making changes to the reading order?
    This is a bit disturbing because FrameMaker touts creating accessible documents and this severe reading order issue impares my ability to do so. I would not consider documents that jump around the page in an illlogical, fixed order, to be accessible. I'm very suprised that no one else has encountered this issue (at least that I can find...)

  • How to link a text box to an anchor frame in the master pages?

    Ok, as the title states, we are trying to figure out if it is possible to link a text box to an anchor frame in the master page. When you look at our Master Page layout, we have a text box in the upper left hand corner of the left hand page, this is used for our machine serial numbers. Then we have an anchor frame that automatically fills out the figure number. Let's say I have pages 2 & 3 (left & right), they have a S/N at the top of the page for the machine, then pages 4 & 5 have a different S/N. If I have to add more pages in between pages 2 & 3 (bumping the current 4 & 5 to 6 & 7), the anchor frame bumps to the next page, but the S/N text box doesn't. Is there a way to fix it so that they both move to the next page? Thanks for the help.
    P.S. I can include images and other info if needed.

    I have included a two pictures that should help me explain.
    Master Page:
    This is the master page set up, the "Page Text Box" has the flow set to "B" while the S/N text box has the flow set to "A". This setup is for our parts manuals, the left page is usually an illustration while the right page is usually a parts list. The text box, anchored frame & paragraph tag are empty in the master page set up. The "page text box" has a flow of "B" and the "S/N text box" has a master flow of "A".
    Body Page 1:
    When we create new pages, the paragraph tag automatically fills in the figure title on the left page, then we add an anchor frame within the text box to hold the illustration. You will notice that I added in a "test" serial number at the top of the page. Now if I need to go back and add two pages before this, the anchor frame, illustration and parts list will move to a new page, but the S/N text box will not. The "Before S/N TBD" would stay on the original page.
    This is what happens, the text box containing the illustration and the parts list "bump" to the next page, but the S/N text box does not. So the question we have is there a way to link that text box to the page so when we create new pages the S/N text box moves with the illustration.
    Does this help?
    Thanks for the assistance Error7103.

  • Anchored Frames and Inserted Tables

    Something has happened.....
    It used to be that I could insert a table (there is an anchor at the insertion point) and follow that with an anchored frame for a graphic and they would display according this order.
    Now, when I do the same sequence, the anchored frame for the graphic always displays before the table.
    Does anyone have a fix for this? Is there a setting somewhere that I need to change to get them to display in the order that I've placed them?
    I installed the 8.0.2 patch, did that break something?
    Dennis

    Sheila,
    The anchored frame for the graphic is set to "Below Current Line" which is what I've always used.
    On rare occasions I have used "At Insertion Point" where I've inserted an icon that I'm describing. Using the "At Insertion Point" requires you to put in a negative number for the Distance above Baseline field. I would rather not do this for all my graphic images.
    My Table Designer properties (Basic tab) are set with Start: Anywhere. Again, this is what I've always used.
    Thanks for your suggestion. If others have experienced the same, please let me know.
    Thanks,
    Dennis

  • Finding anchor frame for broken links to graphic

    I have a document that when opening wants a new link to a graphic that has been deleted from the file. I have looked on the body pages, master pages, reference pages, everywhere I can think of to locate where the graphic the file is looking for could be located. Can anyone suggest additional places in file to look?
    Thanks

    If the file isn't part of a book, make it one, then:
    Add > List of > Figures
    and you'll find out what page it's on (if LOF catalogs missing imports, which it may not).
    You can also save as MIF and look in the MIF for the object name. You need to learn a little about MIF to decipher where that maps to in the document.
    Import references can hide in all sorts of places, including but not limited to:
    beyond edge of anchored frame (had 2 of those just today)
    hidden behind an opaque something you can see
    conditional text currently turned off
    text flowed out of sight on disconnected page
    in plain sight, but hidden by Color Views
    Worst case scenario: create a 1x1 pixel white object and give it the name of the rogue.

  • Best Practice for Image placement and Anchored Frames for use in Robohelp 9

    Hi,
    I'm looking for the best practices in how to layout my images in Framemaker 10 so that they translate correctly to Robohelp 9.  I currently have images inside of Anchored frames that "Run into" the right side of my text. I've adjusted the size of the anchored frame so that my text flows correctly around the image. Everything looks good in Framemaker! Yeah! The problem is that when I link my Framemaker document to Robohelp, the text does not flow around my image in the same manner. On a couple of Robohelp screens the image is running into the footer. I'm wondering if I should be using tables in Framemaker in order to get the page layout that I'm looking for. Also, I went back and forth...is this a Framemaker question or is this a Robohelp question. Any assistance would be greatly appreciated.

    I think Jeff is meaning this section of the RoboHelp forums:
    http://forums.adobe.com/community/robohelp/robohelp_framemaker

  • Best Practices for image layout and positioning using anchored frames in Framemaker 10

    Hi,
    I'm looking for the best practices in how to layout my images in Framemaker 10 so that they translate correctly to Robohelp 9. I currently have images inside of Anchored frames that "Run into" the right side of my text. I've adjusted the size of the anchored frame so that my text flows correctly around the image. Everything looks good in Framemaker! Yeah! The problem is that when I link my Framemaker document to Robohelp, the text does not flow around my image in the same manner. On a couple of Robohelp screens the image is running into the footer. I'm wondering if I should be using tables in Framemaker in order to get the page layout that I'm looking for. Also, I went back and forth...is this a Framemaker question or is this a Robohelp question. Any assistance would be greatly appreciated.

    I wish I could offer some advice, rather than simply adding to your question. I think there is something odd that happens with anchored frames.
    I have been going through fits trying to figure out why the placement of my graphics shifts when I run them through Frame 10-to-RoboHelp 9 conversion. The placement in our books is flush left to the body text area. However, when they convert, some are flush left, some are centered, and a very few are flush right. My boss is very unhappy with me, as I have been unable to figure out why this is happening. I didn't create these files, so I don't know if it's something that goes back to how the graphics were initially imported. But I can't figure out why everything looks right in Framemaker, with the frame attached to an anchor tag, etc. but the placement goes hinky when they convert.
    Any insights are appreciated. I'm wondering if it's going to come down to deleting them and recreating the graphic frame.

  • How does one assign change bars to the contents of an anchored frame?

    Assigning change bars to text in FrameMaker 10 appears to give inconsistent results. Sometimes I can select the contents of an anchored frame and assign a change bar to it. Other times, only the marker is assigned a change bar and not the contents of the anchored frame.
    Also, sometimes I can select a table and assign a continuous change bar to it. Other times, a separate change bar is assigned to individual rows of the table.
    Are there any workarounds for this inconsistency?

    .

  • How can I create "drop caps" Anchored frames tool: "Run into Paragraph" in a text document, and at the same time be able to feather the text to the bottom of the pages? I´m using FrameMaker 10.

    @

    Presumably you are doing the DC as a single letter inside an Anchored Frame run-in from left.
    Back when FM had a manual, this was the method discussed in the manual. The manual, however, also said "Framemaker does not feather text in a text frame in which text runs around graphics."
    That was FM7.0. I don't know if FM has enhanced DC or feathering since then.
    If I had the requirement, I might look at putting the whole lead paragraph in a borderless table.

  • Using Anchored Frame Object Attributes to "Store" Art Numbers

    Good Morning, Everyone,
    I have been using FrameMaker for over 15 years now, and as a tech writer who has inherited LOTS of graphics-intensive documents from previous writers, I have often struggled with identifying source files for embedded graphics. (I prefer to embed graphics in my documents, but that is a topic for another discussion ;-) ) More often than not, graphics have been named something that made sense to the original author at the time, but is nothing more than cryptic code to me now.
    As a result, over the years, I have developed a personal "system" for naming my graphics files that identifies/names each file as the document number in which it resides followed by a sequential number. For example, if a document number is UM345-123, then my graphic files are named UM345-123_0001, UM345-123_0002, etc.  I then include a small (hopefully unobtrusive) 8-point text frame in the lower right-hand corner of the graphics frame that indicates the file name for the base graphic. I create an Art# tag that includes an autonumber for the Document Number (e.g., UM345-123,) which is then inserted into the text frame, and I assign the next sequential number to the graphic/file. The advantage to this is that in the future, files are easily identified if someone wants to use my graphic and all they have is a pdf copy of my document - anyone can easily locate the source file and either update it or forward it on.
    One disadvantage is that in some situations, fitting the text frame/graphic number into the graphic frame is tough - to the point where it detracts from the graphic itself.  I am now wondering if it is possible to somehow utilize Anchored Frame Attributes to store the graphic number in these situations. Perhaps create a new attribute specifically for the Art Number? Has anyone else done something similar?
    Thanks in advance for your help!!!
    Nancy

    > ... include a small (hopefully unobtrusive) 8-point text frame in the lower right-hand corner of the graphics frame ...
    We do this as well, either as a text frame, or in the caption table below, with the reference ID set to a non-obnoxious gray. The main issue with doing this is that the ID is hand-typed, and can easily be incorrect, but usually only when it matters .
    We also have other metadata, that the end users don't see, such as file type, scale and rotation, and this is text with a color set, at rendering, to Invisible by Color Views.
    What you really want, however, is metadata that can't be incorrect, and shows the complete provenance of the object. For this, use text in the original art that is several mm above the art/table/chart extents. Clip it after import with the top edge of the anchoring frame or graphic frame within. End users never see it, but future document stewards can either slide the image down, or pull the frame edge up, to reveal the trail of crumbs leading back to the object's place of birth.
    Caution: that out-of-frame metadata may survive into the PDF, depending on Distiller vintage and settings. You can remove it via Examine Document in Acrobat Pro.

  • Hel with modifying cs5/6 script...create anchored frames from text

    hello
    I have one great time saver script for cs5 for create anchored frames from text tagged with/or charachter style/paragraph style. This work in cs6 but have some "bugs" for me. Script need to be compatible with InDesign CS6.
    1. script in original (look bellow) create text frame which is fitted to lenght of the text. I make change and change 466 line:
    AnchoredTextFrame.fit(FitOptions.FRAME_TO_CONTENT);
    now frame is wide as I write in check box, good. But frame not resize to lenght of the text so I add after above lines 466-470:
        var FO = FitOptions.FRAME_TO_CONTENT,
        tfs = ([]).concat.apply([], app.activeDocument.stories.everyItem().textContainers),
        t, i = tfs.length;
    while( i-- ) (t=tfs[i]).overflows && ( t.locked || t.fit(FO) );
    now all is ok but is here better way to make this to work? Simply, i want to spec text frame width in dialog box, frame will resize only verticaly in direction to amount text in frame. I dont want any overset text.
    2. One "bug". For some reason script alter paragraph style of other text which is not subject to be cutted in anchored frame.
    How to resolve this?
    #targetengine "session"
              Automating anchored object creation
              Version: 2
        Script by Thomas Silkjær
              http://indesigning.net/
    Модификация Б. Кащеев, www.adobeindesign.ru
    Скрипт предназначен для создания привязанных фреймов из текста, отформатированного
    каким-либо абзацным или символьным стилем. Эти стили задаются пользователем в диалоговом
    окне скрита. Там же необходимо задать объектный стиль для привязанного фрейма, в котором
    пользователь должен заранее задать оформление и параметры привязки. Далее необходимо
    указать ширину привязанного фрейма, а его высота будет рассчитана автоматически исходя из
    объема текста. При вводе дробных значений ширины привязанного фрейма в качестве
    разделителя целой и дробной части следует использовать не запятую, а точку, следуя западным
    стандартам разработчиков программы  Adobe InDesign. Первоначально идея и скрипт по созданию
    привязанных фреймов принадлежит Thomas Silkjær для версии ID CS4. C появлением версий CS5
    и CS5.5 скрипт перестал в них выполняться, да и в версии CS4 не всегда корректно работал.
    Анализируя недочеты скрипта в данной его версии были исправлены ошибки и внесены
    функциональные дополнения исходя из понимания задачи автором модификации. Добавлена
    возможность выбора стилей, если они они находятся в группах (папках), возможность выбора
    единиц измерения из выпадающего списка, изменены GREP-выражения для поиска текста,
    область действия скрипта ограничена материалом (Story), а не документом.
    var myMeasureUnits = ["Milimeters","Centimeters","Points","Inches", "Picas", "Ciceros"];
    var selectUnits;
    var pStyleIndex = null;
    var cStyleIndex = null;
    var oStyleIndex = null;
    var myH, myW;
    function main()
        app.scriptPreferences.userInteractionLevel = UserInteractionLevels.interactWithAll;
              if (app.documents.length == 0)
                        alert ("Document is not open. Open document first");
                        return;
        var myParaStyleList = myGetParagraphStyleNames();
        var myCharStyleList = myGetCharacterStyleNames();
        var myObjStyleList = myGetObjStyleNames();
        if(app.selection.length && app.selection[0].hasOwnProperty("baseline"))
            var myStory = app.selection[0].parentStory;
            var myWin = myDialog(myParaStyleList, myCharStyleList, myObjStyleList);
            if ( myWin.show()  == 1 )
                var myDocument = app.activeDocument
                with (myDocument.viewPreferences){
                    // Сохраняем старые единицы измерения в переменных myOldXUnits, myOldYUnits
                    var myOldXUnits = horizontalMeasurementUnits;
                    var myOldYUnits = verticalMeasurementUnits;
                    // Устанавливаем новые единицы измерения
                    switch(selectUnits)
                        case 0:                   
                            horizontalMeasurementUnits = MeasurementUnits.millimeters;
                            verticalMeasurementUnits = MeasurementUnits.millimeters;
                            break;
                        case 1:
                            horizontalMeasurementUnits = MeasurementUnits.centimeters;
                            verticalMeasurementUnits = MeasurementUnits.centimeters;
                            break;
                        case 2:
                            horizontalMeasurementUnits = MeasurementUnits.points;
                            verticalMeasurementUnits = MeasurementUnits.points;
                            break;                  
                        case 3:
                            horizontalMeasurementUnits = MeasurementUnits.inches;
                            verticalMeasurementUnits = MeasurementUnits.inches;
                            break;
                        case 4:
                            horizontalMeasurementUnits = MeasurementUnits.picas;
                            verticalMeasurementUnits = MeasurementUnits.picas;
                            break;
                        case 5:
                            horizontalMeasurementUnits = MeasurementUnits.ciceros;
                            verticalMeasurementUnits = MeasurementUnits.ciceros;
                            break;
                        default: break;
                    } // switch
                if(cStyleIndex == null)
                {/*поиск по стилю абзаца*/
                    var pStyle = getParagraphStyleByName(myParaStyleList[pStyleIndex]);
                    resetGREPfindChange();
                    app.findGrepPreferences.appliedParagraphStyle = pStyle;
                    app.findGrepPreferences.findWhat = NothingEnum.nothing;
                else //
                    // поиск по стилю символов
                    var cStyle = getCharacterStyleByName(myCharStyleList[cStyleIndex]);
                    resetGREPfindChange();
                    app.findGrepPreferences.appliedCharacterStyle = cStyle;
                    //app.findGrepPreferences.findWhat = ".+";
                    app.findGrepPreferences.findWhat = NothingEnum.nothing;
                var foundItems = myStory.findGrep();
                if(!foundItems.length) {
                    alert("Found the text to be placed in a linked frames"); exit();
                //alert(foundItems.length);
                //alert (foundItems[0].contents)
                //alert (foundItems[1].contents)
                var oStyle = getObjectStyleByName(myObjStyleList[oStyleIndex]);
                for(var i = foundItems.length-1; i >=0; i--)
                    //alert (foundItems[i].contents)
                    createAnchoredFrame(foundItems[i], oStyle);
                with (myDocument.viewPreferences){
                    try{
                        horizontalMeasurementUnits = myOldXUnits;
                        verticalMeasurementUnits = myOldYUnits;
                    catch(myError){
                        alert("Unable to return to the original unit");
            } //if ( myWin.show()
        } //if(app.selection.length && app.selection[0].hasOwnProperty("baseline"))
        else
            alert("Place the cursor in the text and run the script again")
    } // main
    function myGetParagraphStyleNames()
    // Получаем список стилей абзацев
              var curGroup;
              var curGroupName;
              var curNameInGroup;
              var myParagraphStyleNames = app.activeDocument.paragraphStyles.everyItem().name;
              myParagraphStyleNames.shift(); // удаление стиля No Paragraph Style
              var paraGroups = app.activeDocument.paragraphStyleGroups;
              var paraGroupsLen = paraGroups.length;
              for(var i = 0; i < paraGroupsLen; i++) {
                        curGroup = paraGroups[i];
                        curGroupName = paraGroups[i].name;
                        curGroupStyleNames = curGroup.paragraphStyles.everyItem().name
                        for (j=0; j< curGroupStyleNames.length; j++)
                                  curNameInGroup = curGroupName +":"+ curGroupStyleNames[j];
                                  myParagraphStyleNames.push(curNameInGroup);
              return myParagraphStyleNames;
    function myGetCharacterStyleNames()
    // Получаем список символьных стилей
              var curGroup;
              var curGroupName;
              var curNameInGroup;
              var myCharacterStyleNames = app.activeDocument.characterStyles.everyItem().name;
              myCharacterStyleNames.shift(); // удаление стиля None
              var charGroups = app.activeDocument.characterStyleGroups;
              var charStyleGroupLen = charGroups.length;
              for(var i=0; i < charStyleGroupLen; i++)
                        curGroup = charGroups[i];
                        curGroupName = charGroups[i].name;
                        curGroupStyleNames = curGroup.characterStyles.everyItem().name;
                        for (j=0; j< curGroupStyleNames.length; j++)
                                  curNameInGroup = curGroupName +":"+ curGroupStyleNames[j];
                                  myCharacterStyleNames.push(curNameInGroup);
              } //for
              return myCharacterStyleNames;
    } // fnc
    function myGetObjStyleNames()
        var curGroup;
              var curGroupName;
              var curNameInGroup;
              var myObjStyleNames = app.activeDocument.objectStyles.everyItem().name;
        myObjStyleNames.shift();
        var objGroups = app.activeDocument.objectStyleGroups;
        var objStyleGroupLen = objGroups.length;
        for(var i=0; i < objStyleGroupLen; i++)
                        curGroup = objGroups[i];
                        curGroupName = objGroups[i].name;
                        curGroupStyleNames = curGroup.objectStyles.everyItem().name;
                        for (var j=0; j< curGroupStyleNames.length; j++)
                                  curNameInGroup = curGroupName +":"+ curGroupStyleNames[j];
                                  myObjStyleNames.push(curNameInGroup);
              } //for
        return myObjStyleNames;
    } // fnc
    function myDialog(myParaStyleList, myCharStyleList, myObjStyleList)
        var myDialog = new Window('dialog', 'Create anchored text frames');
        this.windowRef = myDialog;
              myDialog.orientation = "column";
        myDialog.alignChildren = ['fill', 'fill'];
        // добавляем панель 1 с элементами управления
        myDialog.Pnl1 = myDialog.add("panel", undefined, "Move the text in linked frames");
              myDialog.Pnl1.orientation = "column";
        myDialog.Pnl1.alignChildren = "left";
        myDialog.Pnl1.pstyle = myDialog.Pnl1.add('checkbox', undefined, "Text with the paragraph style");
        myDialog.Pnl1.pstyle.value = false;
        myDialog.Pnl1.dropdownParaStyle = myDialog.Pnl1.add("dropdownlist", undefined, myParaStyleList);
        myDialog.Pnl1.dropdownParaStyle.title = "Select the paragraph style ";
        myDialog.Pnl1.dropdownParaStyle.minimumSize = [250,20];
        myDialog.Pnl1.dropdownParaStyle.enabled = false;
        myDialog.Pnl1.dropdownParaStyle.selection = 0;
        if(myCharStyleList.length)
            myDialog.Pnl1.сstyle = myDialog.Pnl1.add('checkbox', undefined, "Text with character style");
            myDialog.Pnl1.сstyle.value = false;
            myDialog.Pnl1.dropdownCharStyle = myDialog.Pnl1.add("dropdownlist", undefined, myCharStyleList );
            myDialog.Pnl1.dropdownCharStyle.title = "Select the character style ";
            myDialog.Pnl1.dropdownCharStyle.minimumSize = [250,20];
            myDialog.Pnl1.dropdownCharStyle.enabled = false;
            myDialog.Pnl1.dropdownCharStyle.selection = 0;
            myDialog.Pnl1.pstyle.onClick = function()
                if(this.value) {
                    myDialog.Pnl1.dropdownParaStyle.enabled = true;
                    myDialog.Pnl1.dropdownCharStyle.enabled = false;
                    myDialog.Pnl1.сstyle.value = false;
                else
                    myDialog.Pnl1.dropdownParaStyle.enabled = false;
                    myDialog.Pnl1.dropdownCharStyle.enabled = true ;
                    myDialog.Pnl1.сstyle.value = true;
            }// fnc
            myDialog.Pnl1.сstyle.onClick = function()
                if(this.value)
                    myDialog.Pnl1.dropdownCharStyle.enabled = true;
                    myDialog.Pnl1.dropdownParaStyle.enabled = false;
                    myDialog.Pnl1.pstyle.value = false;
                else
                    myDialog.Pnl1.dropdownCharStyle.enabled = false;
                    myDialog.Pnl1.dropdownParaStyle.enabled = true ;
                    myDialog.Pnl1.pstyle.value = true;
            }// fnc
        }//  if(myCharStyleList.length)
        else
            myDialog.Pnl1.pstyle.onClick = function()
                if(this.value)
                    myDialog.Pnl1.dropdownParaStyle.enabled = true;
                else
                    myDialog.Pnl1.dropdownParaStyle.enabled = false;
    //  Вторая панель
        myDialog.Pnl2 = myDialog.add("panel", undefined, "Parameters of the text frame");
              myDialog.Pnl2.orientation = "column";
        myDialog.Pnl2.alignChildren = "left"; 
        myDialog.Pnl2.dropdownObjStyle = myDialog.Pnl2.add("dropdownlist", undefined, myObjStyleList );
        myDialog.Pnl2.dropdownObjStyle.title = "Select an object style ";
        myDialog.Pnl2.dropdownObjStyle.minimumSize = [250,20];
        myDialog.Pnl2.dropdownObjStyle.enabled = true;
        myDialog.Pnl2.dropdownObjStyle.selection = 0;
        myDialog.Pnl2.Group1 = myDialog.Pnl2.add( "group" );
        myDialog.Pnl2.Group1.stxt1 = myDialog.Pnl2.Group1.add("statictext", undefined, "The width of the text frame");
        myDialog.Pnl2.Group1.etxt = myDialog.Pnl2.Group1.add("edittext", undefined, "40");
        myDialog.Pnl2.Group1.etxt.characters = 10;
        myDialog.Pnl2.Group1.dropdownMeasurementUnits = myDialog.Pnl2.Group1.add("dropdownlist", undefined, myMeasureUnits );
        myDialog.Pnl2.Group1.dropdownMeasurementUnits.maximumSize = [80,20];
        myDialog.Pnl2.Group1.dropdownMeasurementUnits.selection = 0;
        //myDialog.Pnl2.Group1.stxt2 = myDialog.Pnl2.Group1.add("statictext", undefined, "mm ");
        /*myDialog.Pnl2.Group2 = myDialog.Pnl2.add( "group" );
        myDialog.Pnl2.Group2.stxt1 = myDialog.Pnl2.Group2.add("statictext", undefined, "Высота привязанного фрейма  ");
        myDialog.Pnl2.Group2.etxt = myDialog.Pnl2.Group2.add("edittext", undefined, "30");
        myDialog.Pnl2.Group2.etxt.characters = 10;
        //myDialog.Pnl2.Group2.stxt2 = myDialog.Pnl2.Group2.add("statictext", undefined, "mm ");*/
        myDialog.Pnl2.stxt1 = myDialog.Pnl2.add("statictext", undefined, "Attention! When you enter fractional values as");
        myDialog.Pnl2.stxt2 = myDialog.Pnl2.add("statictext", undefined, "the decimal part, should be used");
        myDialog.Pnl2.stxt3 = myDialog.Pnl2.add("statictext", undefined, "point, not comma.");
        myDialog.Pnl2.stxt1.graphics.foregroundColor = myDialog.Pnl2.stxt1.graphics.newPen (myDialog.Pnl2.stxt1.graphics.PenType.SOLID_COLOR, [1, 0, 0, 1], 1);
        myDialog.Pnl2.stxt2.graphics.foregroundColor = myDialog.Pnl2.stxt2.graphics.newPen (myDialog.Pnl2.stxt2.graphics.PenType.SOLID_COLOR, [1, 0, 0, 1], 1);
        myDialog.Pnl2.stxt3.graphics.foregroundColor = myDialog.Pnl2.stxt3.graphics.newPen (myDialog.Pnl2.stxt3.graphics.PenType.SOLID_COLOR, [1, 0, 0, 1], 1);
        // --------- кнопки --------------
        var myGroup = myDialog.add( "group" );
        myGroup.orientation = 'row';
        myGroup.alignChildren = ['fill', 'fill']; 
        myGroup.okButton = myGroup.add( "button", undefined, "OK" );
        myGroup.okButton.onClick = function()
            if(myCharStyleList.length) // есть символьные стили в документе
                if(!myDialog.Pnl1.pstyle.value && !myDialog.Pnl1.сstyle.value)
                    alert("You must select a paragraph style or character style");
                    return ;
                if(myDialog.Pnl1.pstyle.value) { pStyleIndex= myDialog.Pnl1.dropdownParaStyle.selection.index; cStyleIndex = null;}
                else {cStyleIndex = myDialog.Pnl1.dropdownCharStyle.selection.index; pStyleIndex=null; }
            else // нет символьных стилей
                if(!myDialog.Pnl1.pstyle.value)
                    alert("You must select a paragraph style");
                    return;
                pStyleIndex = myDialog.Pnl1.dropdownParaStyle.selection.index;
                cStyleIndex = null;
            } //  else // нет символьных стилей
           oStyleIndex = myDialog.Pnl2.dropdownObjStyle.selection.index;
           if(myDialog.Pnl2.Group1.etxt.text =="")
               alert("Enter the width of the text frame");
               return;
            else
                myW = myDialog.Pnl2.Group1.etxt.text;
                myH = myW;
            /*if(myDialog.Pnl2.Group2.etxt.text == "")
                alert("Введите высоту привязанного фрейма");
                return;
            else
                myH = myDialog.Pnl2.Group2.etxt.text;
           selectUnits = myDialog.Pnl2.Group1.dropdownMeasurementUnits.selection.index;
            myDialog= this.window.close( 1 );
        myGroup.cancelButton = myGroup.add( "button", undefined, "Cancel" );
        myGroup.cancelButton.onClick = function() { myDialog = this.window.close( 0 ); }
        myDialog.Pnl3 = myDialog.add("panel", undefined, "");
        myDialog.Pnl2.alignChildren = "left";
        myDialog.Pnl3.stxt = myDialog.Pnl3.add("statictext", undefined, "(с) Thomas Silkjær        (с) Борис Кащеев, www.adobeindesign.ru ");
        return myDialog;   
    } // fnc
    function getParagraphStyleByName(myStyleName)
              var DocParaStyles = app.activeDocument.paragraphStyles;
              var DocParaGroups = app.activeDocument.paragraphStyleGroups;
              myStyleName = ""+myStyleName;
              var pos = myStyleName.indexOf(":")
              if(pos == -1)
              // стиль не в группе
              var myStyle = DocParaStyles.item(myStyleName);
                        return myStyle;
              } //if
              else
                        var myGroupAndStyleNames = myStyleName.split(":")
                        var myGroupName = myGroupAndStyleNames[0];
                        var myStyleName = myGroupAndStyleNames[1];
                        var myGroup =DocParaGroups.item(myGroupName);
                        return myGroup.paragraphStyles.item(myStyleName);
    } // fnc
    function getCharacterStyleByName(myStyleName)
              var DocChStyles = app.activeDocument.characterStyles;
              var DocCharGroups = app.activeDocument.characterStyleGroups;
              // Есть ли в имени полученного символьного стиля двоеточие? (двоеточие разделяет название группы стилей и название стиля)
              myStyleName = String (myStyleName);
              var pos = myStyleName.indexOf(":");
              if(pos == -1)
              // стиль не в группе
                        return DocChStyles.item(myStyleName)
              } //if...
              else
              {// Стиль в какой-то группе
                        var myGroupAndStyleNames = myStyleName.split(":")
                        var myGroupName = myGroupAndStyleNames[0];
                        var myStyleName = myGroupAndStyleNames[1];
                        var myGroup = DocCharGroups.item(myGroupName);
                        return myGroup.characterStyles.itemByName(myStyleName);
              } // else
    } // fnc()+
    function getObjectStyleByName(myStyleName)
        var DocObjStyles = app.activeDocument.objectStyles;
        var DocCObjGroups = app.activeDocument.objectStyleGroups;
        myStyleName = String (myStyleName);
        var pos = myStyleName.indexOf(":");
        if(pos == -1)
              // стиль не в группе
                        return DocObjStyles.item(myStyleName);
              } //if...
        var myGroupAndStyleNames = myStyleName.split(":");
        var myGroupName = myGroupAndStyleNames[0];
        var myStyleName = myGroupAndStyleNames[1];
        var myGroup = DocObjGroups.item(myGroupName);
                        return myGroup.objectStyles.itemByName(myStyleName);
    } //fnc
    function resetGREPfindChange()
        app.changeGrepPreferences = NothingEnum.nothing;
        app.findGrepPreferences = NothingEnum.nothing;
        app.findChangeGrepOptions.includeFootnotes = false;
        app.findChangeGrepOptions.includeHiddenLayers = false;
        app.findChangeGrepOptions.includeLockedLayersForFind = false;
        app.findChangeGrepOptions.includeLockedStoriesForFind = false;
        app.findChangeGrepOptions.includeMasterPages = false;
    function createAnchoredFrame(myText, myObjStyle)
        var myGeometricBounds = [];
        var myInsertionPoint = myText.insertionPoints[0];
        myInsertionPoint.select;
        var AnchoredTextFrame = myInsertionPoint.textFrames.add();
        myGeometricBounds = AnchoredTextFrame.geometricBounds;
        //alert(parseFloat(myH) + " " + parseFloat(myW))
        myGeometricBounds[2] = myGeometricBounds[0] + parseFloat(myH);
        myGeometricBounds[3] = myGeometricBounds[1] + parseFloat(myW);
        AnchoredTextFrame.geometricBounds = myGeometricBounds;
        AnchoredTextFrame.anchoredObjectSettings.anchoredPosition = AnchorPosition.anchored;
        myText.move(LocationOptions.before, AnchoredTextFrame.texts[0]);
        AnchoredTextFrame.appliedObjectStyle = myObjStyle;
        AnchoredTextFrame.fit(FitOptions.CONTENT_TO_FRAME);
        var FO = FitOptions.FRAME_TO_CONTENT,
        tfs = ([]).concat.apply([], app.activeDocument.stories.everyItem().textContainers),
        t, i = tfs.length;
    while( i-- ) (t=tfs[i]).overflows && ( t.locked || t.fit(FO) );
    } //fnc
    main();

    Hi Cari,
    I did create a new user account (admin level) and InDesign works like a charm.
    When I went back to the other account, plug-ins gone, I deleted the prefs and caches, restarted and still everything is crashing as before.
    At least I am working on one account and I will contiue to troubleshoot on the other account. And at some point either the new account will crash or the old account will work and I will go from there.
    Thanks for the info about Mac remembering info. Always trying to be helpful these Macs.
    And thanks for getting at least into a workable space!!! I am supremely grateful!

  • Indesign Bug with Auto-Size and fitting in Anchored frames

    Hi,
    Steps to reproduce:
    1. Create a text frame with 2 Anchored text frames with the same width.
    2. Make the anchored frames Auto-Size --> Vertical only
    3. insert text to the first frame, when type enter to the next line the frame become higher but the next frame remain in the same position. just after typing the first character in the second line the next frame adjust in the right position.
    4. The same happen when pasting text that make the frame bigger.
    5. The same happen without Auto-Size when fit frame to content.
    Does anyone knows about it?
    Any idea how to bypass?
    Thanks

    This is a user to user forum with "some" Adobe staff participation, report bugs at this link
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform for bugs or feature requests

  • Converting All Figures in Anchored Frames With Callouts

    I need to take a few hundred linked graphics in anchored frames that have FrameMaker callouts,save them as PNG files with the callouts embedded (yes, I know I won't be able to edit the callouts later) using different names (or another location), and relink to the new graphics. Doing this one by one is doable, but suboptimal.
    I'm not sure if I need a script, some other tool, or if there is some easy way I am missing. Anyone else have to do this and can give me a pointer or two?
    Thanks,
    Marc

    This isn't a full solution, but does reduce the workload.
    Using Acrobat Pro (possibly Standard, probably not Reader),
    use the Document > Split Document feature set to:
    (*) Number of Pages [ 1 ]
    and:
    Output Options:
    [*] Use Label [ Page ]
    The file names won't be your image IDs, however.
    This gives you the original PDF as single file per page, which dramatically enhances options for batch processing with other apps.
    For example, you could use PhotoShop to batch convert those .pdf's to .png's, with full control over res. Illustrtator can also do this (File > Export), with res control.
    You could actually re-import those page images back into the FM doc, using Graphic Frames (clipping paths) to hide all page content except the desired images.

  • Fm9p237, probs with Save As PDF, turns *some* anchored frames blue

    I am using Save As PDF because have to create CMYK PDF. I know how to do that. The issue now is that FrameMaker is sticking blue boxes around only *some* of the graphics.
    They are all EPS graphics imported by reference into anchored frames. These boxes do not appear in the FM file.
    The boxes clearly are the anchored frame bounding boxes.
    Any ideas? Any switch I should set? Any ritual incantations that will appease the FM Postscript generator?
    Thanks for your help, Becky

    Hi Bernd  and Art,
    Yes, I am using spot colors. I did some more testing and here is what I found:
    Use Save As PDF in FM-->all colors except for spots are correctly converted to CMYK. Bitmap screenshots are also converted to CMYK. If I convert the  spot colors to CMYK SWOP  in Acrobat 9, using its preflight tool, the spots are all converted to the same CMYK values that they were assigned in Frame. BUT there are  random  blue boxes in the doc, clearly where FM for some reason colored the bounding box of an anchored frame or a table cell.
    Print to Adobe Printer instance in FM with the Press Quality job options-->All colors come out CMYK, including spot colors and bitmapped
    and there are no random blue boxes BUT the CMYK conversions of the spot colors are wrong.
    My choice: Save As PDF. I will just remove the blue boxes with Acrobat.
    I considered PitStop Pro and downloaded the trial copy,  but its userdoc is terrible and I can't figure out how to batch-convert the incorrect CMYK colors t. Can't find any good help on line either. Too much bother.
    Sigh. Adobe, are you listening? It's ridiculous that the company that produces Photoshop can't make CMYK color conversion work in Frame.
    TThank you, Bernd and Art. I appreciate your feedback very much.
    --becky

  • Anchors above anchored frames

    Hi all,
    I'm developing some templates for computer software manuals. I need a nice neat generic method for adding images and their titles. I need the figure titles to be positioned in the side heading, aligned with the top of the figure beside it.
    For tables I use a TableTitle side heading paragraph format that has a Table paragraph format after it with a negative space after value. The table format has a negative space before value, so when inserted it lines up nicely with the top of the table title.
    I would like to do something similar for figures, but I can't seem to find a method of positioning the anchored frame that works. 'Below current line' would be ideal, if that didn't leave me with the line holding the anchor above it, which the side heading is then aligned with instead. Is there a way to apply a paragraph format to the anchored frame that would allow me to enter a negative space before value like i do with the table? Or is there some other way to align the anchored frame with the top of the title beside it?
    Thanks very much to anyone who can help,
    Kat

    Kat,
    I hope I understand your problem correctly.
    The paragraph containing the figure title is positioned in the side head with alignment set to Top Edge. Then that paragraph is followed by another paragraph, which of course is in the main text column, empty, and aligned at the top with the side head.
    With the insertion point in the second paragraph, import the image file. This puts the image below the line. Select the image, not the anchored frame, and scale it if necessary. If not created at the correct size, you probably want to scale it down to fit the width of the text column. Now press the key sequence Esc, m, p (note m and p are lowercase). The anchored frame shrinks to fit tightly around the image and changes it position to At Insertion Point. If you turn on Text Symbols, you will see the end-of-paragraph symbol at the lower right edge of the image, and the top of the anchored frame will align with the TOP of the side head text.
    You also have to be sure the line spacing of the paragraph holding the image is NOT fixed or Frame will move the image up.
    Hope this is what you need,
    Van

Maybe you are looking for