Back

If your email is not recognized and you believe it should be, please contact us.

Forum Replies Created

Viewing 8 posts - 16 through 23 (of 23 total)
  • Author
    Posts
  • in reply to: Apply color to all tracked changes in Story Editor #93880

    Just exported a test .pdf with Kai’s script and it does export with the yellow highlight.

    Also, tried to run the one liner script, but it errors out. :(

    View post on imgur.com

    in reply to: Apply color to all tracked changes in Story Editor #93877

    Hello Kai,

    you are indeed a master of your craft. I’ve been reading your posts for quite some time and you provide excellent scripts. Thank you for replying.

    Your sample script is almost too well done, because I can’t find a way to remove the yellow highlight if I want to. This is why I usually changed the font color from black to magenta, so the manual override could be reverted at any time with ease.

    In terms of what to track, the most important is the added text, since that’s what’s showing when the layout is done. If they want to check in depth I can always provide an InCopy .pdf that shows everything.

    But if it’s easier to script so it adds magenta to everything (deleted and added text) it’s no problem at all.

    Thank you again for your invaluable help!

    in reply to: Apply color to all tracked changes in Story Editor #93873

    This is how I do it now. I typeset documents with lots of modifications that come from InCopy files, and I have to mark them in some way so the editor sees them in .pdfs. I make them magenta as a local override, but it takes a lot of time for 2000 pages books to go through each modification manually and set that color. (Open story mode, find next modification [Ctrl+Page Down], apply magenta. Repeat).

    That’s why I thought that if I can do that, a sort of script/macro could do it faster.

    Unfortunately colors can’t be assigned to a keyboard/mouse shortcut like para/char styles. I could work some macro on that.

    in reply to: Apply color to all tracked changes in Story Editor #93870

    Thanks for the reply!

    Setting character styles is out of the question since most of the text will already have a character style applied to it, be it italic, bold or other (nested) combinations.

    Thank you again for your suggestion! Seems that only a complex script will solve the problem.

    Thank you very very much for taking the time to write this up. I have tested it using your .idml file and it works wonderful, with an effective panel where you can select the layers.

    Unfortunately, the format of my chapter numbers is [§1:01 First section in chapter 1] instead of [1:01 First section in chapter 1], and that little § seems to break the whole script since it doesn’t find anything in a random chapter I’ve selected. Could you leave an e-mail address? I want to send you one of my book chapters and see ‘live’ what’s going on.

    Also, after the basics are fixed, I’d like to know if adding several chapter styles to search at once is doable and other small tweaks.

    Again, thank you so much for your hard work.

    Regarding your first question, exactly. The body of the chapter/section has a different style applied to it. The RUNNING HEADER style is only for the chapter/section titles. The usual format is, for example, 1.01^tIntroduction
    If I understood you correctly, yes, the script should get all chapter/section numbers where a case is present, and put them in the format I presented above.

    Regarding your last idea, some cases can be encountered just once in the whole book. Other ones reoccur in the exact same form in multiple chapters, or they even occur in different forms. This shouldn’t matter much, as long as all are identified and attributed the right chapter/section they are in.

    Thank you for the reply Matthew!

    Knowing that this kind of script can be attempted is a big leap forward. As you mentioned, the script has to be written based on how the document is set up, so here are some specifics:

    The master page of the book that handles the chapters has two text variables (one on each page, in the header) that handle the running headers. The one on the left has on the ‘Use:’ setting section ‘First on Page’ and the one on the right has ‘Last on Page’. So the section numbers appear on every single document page.
    The text frame containing the running headers never get overridden.

    The thing is that I don’t think the script can take the section number in the header and put all the cases on that page with that header since on a page there are, for example, section 1.05, 1.06 and 1.07, but the Running Header shows 1.05 (when on the left side page) or 1.07 (when on the right side page).

    So, on a very unspecialized, basic level of design, the script should identify the CASE TABLE and start verifying backwards, each paragraph, until it hits the first RUNNING HEADER style and that would be the one that the case belongs to.

    Let me know if you need any more info.

    Thank you!

    Thank you very much for the reply, Masood!

    The links you gave me are really useful for creating Indexes and I thank you, they will really come in handy one day.

    The script that I’m looking for is a bit more simple (or is it?) than that: I don’t want the script to select just a list of words that have a certain style, I want it to take every group of consecutive characters that have that particular style, and specify their corresponding chapter/section number.

    To give you an example, on a page that has two chapters there are two cases in different blocks of text: VanDyke v. SKI Ltd., 67 CA4th 1310 (1998) in section §1:01 and Curties v. Hill Top Developers, Inc., 14 CA4th 16 51 (1993) in section §1:02. These cases have a Character Style named CASE TABLE and the sections have a Character Style named RUNNING HEADER.

    I am looking for a script that can look for these two styles and order them in a list (alphabetically or not) that would look something like this:

    VanDyke v. SKI Ltd., 67 CA4th 1310 (1998), §1:01
    Curties v. Hill Top Developers, Inc., 14 CA4th 16 51 (1993), §1:02

    So the script idea (I have no idea about scripting so I’m just getting this on a logical pattern) would be something like:
    [CASE TABLE], corresponding [RUNNING HEADER]

Viewing 8 posts - 16 through 23 (of 23 total)