Styles Are Referencing Unwanted Style Sheet

Hi, I resaved a style sheet with a new name then created a new page and attached the new style sheet to it. But for some reason some of the text in the new page is still referencing an old style sheet and I don’t know how to get tit to only reference my new style sheet.
Here is the message I get when I select the type in the page and hover over the rule in the CSS styles panel.
this rule is defined in file “light_new.css” with specificity 0,0,0,1

And, isn't "light_new.css" the name of the new stylesheet? If not, what *is* the name of the new stylesheet?

Similar Messages

Easily removing unwanted styles

I could have sworn this was already covered on these forums,
but a search of "remove style" and "delete style" did not yield
anything for me. So, I apologize if this has indeed been covered
and I'm simply too dense to find it on my own.
I inherited a project where many cooks spoiled the broth, and
now it is chockful of styles. While our standards call for about 10
styles, there are dozens upon dozens of styles in this
project--most are similar to each other, such as many variations of
Bullet-List-1/List-Bullet-1. Fortunately, they all are attached to
one CSS, but that CSS is just a bloody mess.
I could, of course, go through the Styles dialog box and
delete each unwanted style. That is a bit tedious but doable. I
would be happier with a method for deleting multiple styles. If
someone has wisdom in this category, I'd love to hear it.
This opens a different can of worms. The big problem is that
I have several paragraphs attached to styles that I want to delete.
Deleting the styles results in a formatting nightmare if I don't
identify each of these paragraphs first and apply the appropriate
styles. Is there an easy way to see what styles are in use and in
what topics? I checked the Reports, but the best I can get is which
topics are attached to what CSSes. I could, of course, use the
Multi-File Find and Replace feature, and I'm not above that, if
it's the best option (sadly, FAR is not an option for me at this
company, though UltraEdit is).
Any insight from the pros? Am I on the right track? Is this
task simply as daunting and overwhelming as I think?
Kevin

Hi Kevin. I believe that if you delete a style from the style
sheet all the text that uses it reverts back to the "based on"
style used when it was created. For example if you create "Style1"
based on the "Normal" style, text reverts back to the "Normal"
style if "Style1" is deleted. This may hopefully help with your
tidy up although I don't know of a way to delete multiple
styles.

Styles are missing when publishing to ePub in RoboHelp 9

Good afternoon,
We are developing content for Android Tablets and have learned the customary format that we used is, well, unusable.
A few posts suggest that ePub is really the only way to go with Android Tablet Help.
http://blogs.adobe.com/techcomm/2010/04/robohelp_script_to_generate_epub_format_content_fo r_mobile_d.html
http://forums.adobe.com/message/3629956
http://blogs.adobe.com/techcomm/tag/mobile
http://blogs.adobe.com/techcomm/2010/12/epub-industry-standard-file-format-for-reflowable- content.html
So, I have published using the ePub format, but I have noticed the existing styles are ignored. In another post, it was noted to ensure that the tags are lower case. I edited the css file and made sure the tags are lower case, but this did not make any difference.
Any suggestions for what may be happening here? My best guess is there is an issue with the CSS file.
Best Regards,
Eric Buterbaugh
Here is the style sheet:
/*created with adobe robohelp 9.*/
h1 {
    margin-bottom: 5pt;
    margin-top: 0.5pt;
    color: #ffffff;
    font-weight: bold;
    font-style: normal;
    font-family: arial, sans-serif;
    font-size: 18pt;
    background-color: #3f5f94;
li.h1 {
    color: #ffffff;
    font-weight: bold;
    font-style: normal;
    font-family: arial, sans-serif;
    font-size: 18pt;
h2 {
    font-weight: bold;
    margin-top: 9.5pt;
    margin-bottom: 0.5pt;
    font-size: 11pt;
    font-family: arial, sans-serif;
li.h2 {
    font-weight: bold;
    font-size: 11pt;
    font-family: arial, sans-serif;
h3 {
    font-weight: bold;
    margin-top: 9.5pt;
    margin-bottom: 3pt;
    font-family: verdana, sans-serif;
    color: #1e56b5;
    font-size: 8pt;
li.h3 {
    font-weight: bold;
    font-family: verdana, sans-serif;
    color: #1e56b5;
    font-size: 8pt;
p {
    margin-bottom: 4.5pt;
    font-size: 9pt;
    margin-top: 0pt;
    font-family: arial, sans-serif;
li.p {
    font-size: 9pt;
    font-family: arial, sans-serif;
a.expandspot {
    color: #008000;
    cursor: hand;
    font-style: italic;
    text-decoration: none;
span.expandtext {
    font-style: italic;
    font-weight: normal;
    color: #ff0000;
a.dropspot {
    cursor: hand;
    color: #008000;
    font-style: italic;
    text-decoration: none;
a.glossterm {
    color: #800000;
    cursor: hand;
    font-style: italic;
    text-decoration: none;
span.glosstext {
    font-style: italic;
    font-weight: normal;
    color: #0000ff;
p.bullet-hollow-indent {
    list-style: circle;
    margin-left: 18pt;
li.p-bulleted-indent {
    list-style: circle;
p.bulleted {
    list-style: rh-list;
    x-list-class: rl-p-bulleted;
    x-list-level: 1;
    margin-top: 4.5pt;
    font-weight: bold;
    margin-left: 48px;
    text-indent: -24px;
li.p-bulleted {
    list-style: disc;
p.note {
    font-style: italic;
    color: #0000ff;
    background-color: #cdc9b1;
    margin-bottom: 9pt;
    border-top-style: solid;
    border-bottom-style: solid;
    border-top-color: #000000;
    border-bottom-color: #000000;
    border-left-style: none;
    border-right-style: none;
    border-top-width: 1px;
    border-bottom-width: 1px;
    margin-top: 9pt;
    text-indent: 0.25in;
    margin-left: 54pt;
    margin-right: 224px;
li.p-note {
    font-style: italic;
    font-weight: normal;
    color: #0000ff;
    text-indent: -;
    list-style: url(blue_nav_index.gif);
h4 {
    font-size: 9pt;
    margin-top: 9.5pt;
    margin-bottom: 0.5pt;
    font-family: arial, sans-serif;
li.h4 {
    font-size: 9pt;
    font-family: arial, sans-serif;
p.tip {
    x-next-class: ;
    x-next-type: p;
    font-style: italic;
    font-weight: normal;
    color: #0000ff;
    border-top-style: solid;
    border-bottom-style: solid;
    border-top-color: #000000;
    border-bottom-color: #000000;
    border-top-width: 1px;
    border-bottom-width: 1px;
    background-color: #fefaa7;
    margin-left: 36pt;
    margin-right: 54pt;
    margin-top: 13.5pt;
    margin-bottom: 4.5pt;
li.p-tip {
    font-style: italic;
    font-weight: normal;
    color: #0000ff;
p.blue {
    font-size: 10pt;
    color: #ffffff;
    x-next-class: ;
    x-next-type: h4;
    margin-top: 9pt;
    font-weight: bold;
    font-style: normal;
    background-color: #87a3ed;
    margin-right: 0pt;
li.p-blue {
    font-size: 10pt;
    color: #ffffff;
    font-weight: bold;
    font-style: normal;
p.code {
    font-family: "courier new", monospace;
li.p-code {
    font-family: "courier new", monospace;
p.tasks {
    font-weight: bold;
    font-style: normal;
    margin-right: 0pt;
    font-size: 8pt;
    font-family: verdana, sans-serif;
    color: #1e56b5;
    background-color: #ffffff;
    line-height: normal;
    margin-top: 4.5pt;
    list-style: rh-list;
    x-list-class: rl-p-tasks;
    x-list-level: 1;
    margin-bottom: 4.5pt;
    x-next-class: aftertasks;
    x-next-type: p;
    text-indent: -0.23in;
    margin-left: 0.23in;
li.p-tasks {
    font-weight: bold;
    font-style: normal;
    font-size: 8pt;
    font-family: verdana, sans-serif;
    color: #1e56b5;
    list-style: disc;
    line-height: normal;
p.aftertasks {
    margin-top: 0pt;
    margin-bottom: 13.5pt;
    text-indent: -0in;
    x-next-class: tasks;
    x-next-type: p;
    margin-left: 18pt;
li.p-aftertasks {
p.normal-indent {
    margin-left: 18pt;
li.p-normal-indent {
h4.heading4-indent {
    margin-left: 18pt;
li.h4-heading4-indent {
li.h1-headingtop {
    font-size: 14pt;
rh-list.rl-p-bulleted {
    x-level-count: 1;
    x-lvl-1-format: "<x>";
    x-lvl-1-type: filled-circle;
rh-list.rl-p-note {
    x-level-count: 1;
    x-lvl-1-format: "<x> ";
    x-lvl-1-type: "folder open";
rh-list.rl-p-tasks {
    x-level-count: 1;
    x-lvl-1-format: "<x> ";
    x-lvl-1-type: filled-circle;
p.numbered-list {
    list-style: rh-list;
    x-list-class: rl-p-numbered-list;
    x-list-level: 1;
    margin-left: 18pt;
rh-list.rl-p-numbered-list {
    x-level-count: 1;
    x-lvl-1-format: "<x>.";
    x-lvl-1-type: decimal;
p.bulleted-dark-indent {
    list-style: rh-list;
    x-list-class: rl-p-bulleted;
    x-list-level: 1;
    margin-top: 4.5pt;
    font-weight: bold;
    text-indent: -24px;
    margin-left: 88px;

Hi,
I ran some more tests and did some reading up, and I constantly come across the limitations of the ePub format/readers. From the ePub specification:
The CSS-based style sheet constructs in this specification define required rendering functionality. To minimize the burden on Reading System developers and device manufacturers, not all CSS 2 properties are included. A few additional properties and values have been added to support page layout, headers, and footers. These, taken together, constitute the OPS CSS 2.0 required subset.
An example about using colour in a style sheet:
Current browsers support a host of keyword color names. XHTML 1.1 defines 16 named colors, as well as numeric values. OPS style sheets may use all CSS2 forms, however Reading Systems are not required to distinguish all these colors for rendering (otherwise monochrome devices would necessarily be non-conforming, which is not the intent).
Fonts are supported in the standard (the standard says that font-family and other styling must be supported). As far as I can make out, you may choose between two things:
Use generic font description: serif, sans-serif, monospace.
Use font names, such as Arial. This however would require you to use an open type font which needs to be embedded in the ePub.
See the following section in the specification: http://idpf.org/epub/20/spec/OPS_2.0.1_draft.htm#Section3.4
The answer I can give you goes contains multiple facets:
ePub does not support all the formatting you may be able to throw at it using style sheets. A list of all supported formatting is available in the specification.
ePub readers can perhaps ignore styling even though the ePub format supports it.
Some styling, such as specifying a font, may only work after manually optimizing the CSS through an external CSS editor.
I haven't read the complete specification, so I'm not in the position to tell you what will always work, what will never work, etc. The following page has some screenshots of the same ePub on different readers: http://rufus.deuchler.net/2010/10/css-and-xhtml-tags-for-epub.html That illustrates the problem.
Sorry I can't be more help, but it seems we will have to learn to live with formatting loss in ePub. It's not Robo's fault, but it's annoying none the less.
Greet,
Willam

Styles are broken in Pages 5

I just upgraded to Pages 5.
I opened a document that I'd been working on in the previous version of Pages. It has several styles, incuding a bulleted list style called "main bullet".
I attempted to apply that style to a section of text, and while it did indent the text properly, it did not add bullets. (Also, in the Style panel a bullet does not appear next to the "main bullet" style as it does in Pages 4. This was my first clue that something was wrong.)
So I went back in the text to a bulleted list that uses the "main bullet" style. I selected the text, then went to the Style panel and chose "main bullet" > update style. This did not seem to help. The "main bullet" style still has no bullet next to it in the Style panel, and when I tried again to apply it to some text, the bullet doesn't appear.
I decided to try a different style, in this case "body". I went to a section that has the "main bullet" style, selected it, and applied "body". The indentation changed, but it did not remove the bullet as it was supposed to.
Is this a bug, or do styles work differently in Pages 5?
It appears that styles do not include formatting like bullets, which, if true, is a huge problem.
I was also upset to learn that once I've opened a document in Pages 5, I can no longer open it in Pages 4. So I'm essentially stuck with Pages 5 whether I like it or not.

I have exactly the same problem but I found that Pages '09 was still installed on my system after the Pages/Mavericks update - search for Pages in Spotlight.
So, I just deleted the Pages 5 document that I had been working on and started all over again with trusty Pages '09.
You are correct styles are severely broken! How disappointing for this new, much vaunted, update.
I guess I'll carry on using '09 until Apple come up with a 5.1 version...
Other bugs I found:
1. Resizing an image so that it just fits on a page - when it jumps to the new page (because it's stretch too far) and you make it smaller to fit the space on the page, the preview stops updating so you have no idea how big it's going to be...
2. Headers and Footers don't carry over properly from an '09 document
3. Empty boxes have the word 'Text' in them rather than empty when you carry over from an '09 document
4. It is very slow to update headers...
5. Oh and did I mention styles are completely destroyed and are a BIG FAIL in Pages 5 IMO

Graphics(Styles) are not Affecting in HTML Format of Smart Form

Hi,
I have converted a Smartform from PDF format to HTML. but the Graphics ( Styles ) are not Affecting the out put.
Can any body Give me the solution.

Please suggest me ,how to convert from pdf to html workformat,if any program is available for that.Please send it

My existing object styles are not visible

My existing object styles are not visible in the object style panel- only via quick apply (so I know they exist)
Any idea how I can make this panel functional again?
Using CS6
Thanks!

@ Bob, I think you posted the response to a differnt question...
@ chandasz, see Replace Your Preferences

Styles are not showing in html mail

Hello all,
i have a servlet that sends a mail in html format. i have a string with all the html tags, and the first part of the string is as follows:
String htmlText = "<html><link href='styles/styles.css' type='text/css' rel='stylesheet'>....here gos the rest of the html tags.
i receive the mail properly, but seems that the styles are not working....any help?
Thanks

Because the link to your stylesheet is a relative URL, and in an e-mail there's no base URL for it to be relative to. Using a fixed URL like http://yourhost.org/styles/styles.css would probably work.

What styles are lost when importing/converting PS text to editable text?

In CS5.5, when I import a PSD file with one or more text layers (retaining layer styles and editable layer styles) some of the layer styles change upon import.
In addition, after import, in the Comp panel, sometimes there are no visual differences between that display and the display in PS. But in individual style layers in the Timeline panel, things have changed. Most typically, strokes with gradients are changed either to a solid color (gray or red) or to a simple white-to-black gradient. How is it the display can show a gradient when the stroke layer shows a solid color?
When the text layers are converted to editable text, those changed style properties kick in.
I'm guessing some or all of this has to do with AE text not being able to have a gradient for the fill or stroke? That being the case, is there a work-around?
If this goes beyond not being able to use a gradient for fill or stroke, what are the "rules"? What styles are lost/changed upon import and when converting to editable text?
Jeff Sengstack

> In addition, after import, in the Comp panel, sometimes there are no visual differences between that display and the display in PS. But in individual style layers in the Timeline panel, things have changed. Most typically, strokes with gradients are changed either to a solid color (gray or red) or to a simple white-to-black gradient. How is it the display can show a gradient when the stroke layer shows a solid color?
After Effects includes the entire Photoshop rendering engine, so any PSD and its layer styles should render fine (i.e., just like in Photoshop). If it doesn't, please submit a bug report.
But After Effects does not include the entire UI from Photoshop for creating and modifying layer styles.
The layer styles feature in After Effects exists primarily to provide fidelity between what you see in Photoshop and what you see in After Effects---not so that you can add and modify layer styles in After Effects. The UI in the Timeline panel is therefore a barebones implementation that doesn't include many of the features of layer styles in Photoshop. As you observe, there are many cases in which the representation in the Timeline panel is much more simplistic than what is in the Composition panel.
This separation between the UI and the ability to render with good fidelity is most apparent with pattern overlays. See this video for a good demonstration of how to use layer styles in After Effects by tapping into these features in Photoshop:
http://library.creativecow.net/articles/harrington_richard/photoshop_layer_styles_with_ae. php
> In CS5.5, when I import a PSD file with one or more text layers (retaining layer styles and editable layer styles) some of the layer styles change upon import.
How, exactly, do they change? A screenshot would be useful.
If it's what I'm suspecting, then the page that Mylenium points you to has the clue:
"When a layer style is applied to a vector layer—such as a text layer, a shape layer, or a layer based on an Illustrator footage item—visual elements that apply to the edges of the contents of the layer apply to the outlines of the vector objects, such as text characters or shapes. When a layer style is applied to a layer based on a non-vector footage item, the layer style applies to the edges of the layer’s bounds or masks."
When you convert between Photoshop text and editable text, you're changing the render order and also switching between raster images and vectors. This can affect appearance in many ways.

Styles are missing in contribute

Hi,
i have a problem that the styles on contribute 3 are missing
the styles are setted with dreamweaver on the template!
can somobody help me
thanks

I've confirmed that my CSS classes are showing up in the Apply CSS Class dropdown of the editor for Web Pages and for Site Editor (ICE), but NOT in the editor for a Web App item description. Initially, this was the only place I was checking which was why I thought it wasn't working at all.
Besides this, I've found that applying CSS classes in Site Editor does not work if the selection you are applying the class to is an anchor (for example, a selected class gets applied to heading tags once you deselect the text). If I have applied a class to an anchor from the admin editor or ftp then I select that anchor in Site Editor, the applied class appears as selected in the CSS dropdown, but if I try to change the class in Site Editor by selecting a different class, it does not set the class or have any affect on the existing class.
Has anyone else had these issues or found solutions?
-Jake

Styles are causing me to go nutz

Lets say I have a style (blue with backdrop)
When I put the curser on some text that is red, and try to apply the Blue with Backdrop, nothing happens.
I can not figure out what I am doing wrong, or what is the correct way to apply styles.
I have been looking at You Tubes and I believe I have bee following the directions correctly but so far not doing so hot.
In essense, if my style is blue color, and has a backdrop, maybe a bezil or what ever and 20 point Times new roman, I want to put my curser on any text that is red, not back drop or other special effects, and apply my blue style top it and it will change from red to blue, same size, same backdrops etc.
What am I doing wrong?
Bob

Yes, those are both distinct paragraphs, and each should have its own style. The styles should define EVERYTHING about the paragraph that wouldn't be "special" like an italicized word in the midst of roman text (though if you can predict where those things will fall you can use nested styles or GREP styles to handle them automatically as well). You want a paragraph style for every type of paragraph you use.
One style can be based on another when they share characteristics that you want to link. Changing the base style will change all the shared parameters in the based on style at the same time, but anything you've changed (point size, color, or some other feature) will remain as is.
Next style is used when the following paragraph will always be a particular style. An example would be a heading that is always followed by body text, but body text is not always followed by something different, so you set the heading to have a next style of body, and leave the body style set to next style same. In your menu it might make sense to have the item name style set with a next style of item description. If that description is always one paragraph, you might want to set its next style to be item name, so they will rotate automatically as you type. Next style is only applied when you actually type a hard return or in cases where the object style specifies to use next style, or you have made a selection of a block of text and right-clicked the style name for the first paragraph in the block and chose one of the Apply style and next style options (which is a very fast way to style an entire block of imported text).
Peter

How can I see where Paragraph / Character Styles are used?

I am editing a 40-page document and have many Paragraph styles. I have already deleted unused paragraph styles and now would like to see where are the remaining styles used to edit the text directly. IS there a way to see it? (InDesign CS4 or CS5)
Thanks,
Marina

Marine von Koenig wrote:
I am editing a 40-page document and have many Paragraph styles. I have already deleted unused paragraph styles and now would like to see where are the remaining styles used to edit the text directly. IS there a way to see it? (InDesign CS4 or CS5)
Thanks,
Marina
Save two copies of the file.
Close the original file. In a saved copy, [EDIT] use the paragraph style panel to [/EDIT] change the text color of every paragraph style to a new color whose swatch you name for the paragraph style. For example, Head1 paragraph style's text color becomes your newly-made swatch Head1color.
Every paragraph in the document will appear in the color you assigned. This should give you a picture of which paragraphs are which style.
Save the colored version of the file if you want to keep it.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices
Message was edited by: peter at knowhowpro

Changes to [No Paragraph Style] causing unwanted style overrides

Hi fellow InDesigners
I'm using InDesign CS6. I'm working with long documents that were originally created in previous versions (CS4 and possibly earlier). My standard workflow for these jobs is to do the bulk of the text formatting in a newly created, bare-bones, single column document. First, I load the paragraph and character styles from the template, and when I'm done I copy and paste the formatted text back into the template for final layout and typesetting. This used to work fine in CS4, but in CS6, all my paragraphs show the plus sign in the Paragraph Styles panel, indicating that they have been overridden. They should be identical, since I imported the styles from one file to the other. The overrides include drop cap alignment, and even more obscure things like 'IdeoSpaceBehavior' and 'Diacritic Positioning'.
It seems likely to me that this problem is due to Adobe having changed the definition of the mysteriously ubiquitous '[No Paragraph Style]' style between versions. The template file has carried over the definition from CS4, but the newly created working files have the new definition, and since [No Paragraph Style] is not included when importing styles from one document to another, the inconsistency remains. Copying and pasting text with no overrides in one document, shows overrides in the other.
So the simplest solution I can think of, would be to change the [No Paragraph Style] in the template to match the definition of new CS6 documents. Is this even possible? My Googling thus far suggests that [No Paragraph Style] is pretty much untouchable.
Is there nothing for it but to create the template files again as new documents in CS6?

No worries Michael. Yes, I vaguely remember the change too.
My understanding is, [No Paragraph Style] is very much a style—a paradoxically named style to be sure, but a style nonetheless. Check out the [Basic Paragraph] style definition by double clicking on it in the Paragraph Styles panel. It's style definition is: '[No Paragraph Style] + next: [Same style]'. That's it. Minion Pro 12 point, with auto leading—and every other conceivable paragraph attribute—all handled by [No Paragraph Style]. Adobe needed some defaults, and that's what [No Paragraph Style] is—just a default style. You can never escape it either, since every style, no matter what it's based on, has [No Paragraph Style] as its most senior ancestor.
So that's essentially my problem. Adobe has, in their wisdom, changed the [No Paragraph Style] style between versions, so that a document originally created in an earlier version and a document created in CS6 have different [No Paragraph Style] settings. I'm pretty confident this is the cause of my problems.
Lots of my paragraph styles inherit from other styles. Why would I not want that? My custom 'Paragraph' style has lots of other styles based on it—from typesetting variations, to quotes, lists, etc. But the 'Paragraph' style itself is based on [No Paragraph Style]. As I said, you can't really escape [No Paragraph Style].

Where are the paragraph style tools in Indesign CC2014?

Hi! I've just started using Id through Creative Cloud on a new computer (have been using CC CS6 for two years), and the installer gave me CC2014 rather than CS6. So this is a question only about CC2014.
Where has the paragraph styles window gone? Specifically, how can I edit, create and organise paragraph styles, and how can I get a window up on the main screen with all the styles laid out? All these things were easy to find in CS6, but I can't track them down in CC2014. The only thing I get (and that with a bit of customization). is a drop-down menu in the main toolbar, which allows me to choose from existing options on an existing document.
There is no Paragraph Styles option under Windows>Styles.
There is no Paragraph Styles option under Type.
The only Paragraph window which appears is designed for editing text as you go along, not for applying styles.
The Help options all point me back to the entry for CS6, and tell me to go to Type>Paragraph Styles (which doesn't exist).
I can't get a window up on the main screen to apply styles instantly from a list. I only get that dropdown menu, which has no further options.
Can anyone either point me to some up-to-date guidelines or explain where all the paragraph options have gone and how I can use them? Alternatively, can I revert to CS6? This was easy and intuitive before, and now it's neither...
Thanks!

Yes, that did it. All the old menu options have reappeared. I don't know why they were hidden in the first place - these were things I never needed to set up on either of my previous computers.
Thank you very much!

Problem with footer in table style not applying paragraph style... or just me?

I'm having a niggling problem making a table style with cell/paragraph styles for the header, body, and footer respectively. I want to make it as simple as possible for other users but one thing keeps tripping me up. I'll try and describe with screenshots. I'm using InDesign CS5 on Windows 7.
I have a table style set up with cell styles for the header, body, and footer, and paragraph styles for each as well. Say I'm converting a list of generic text to this table:
i convert it to my table style. The body style is a numbered list:
I convert the header to an, err, Header. The cell applies the header paragraph style as I should expect:
I convert the footer likewise, but it maintains the Body text paragraph style as an override!
So naturally I clear the override and it works fine. But of course, I'd rather it acted like the header row. I can't work out where the override on the footer comes from and why it operates differently in this respect to the header row. There is nothing different about how the styles are constructed. Have I made a mistake somewhere, or is this correct behaviour I'm misinterpreting, or something...?
edit: Here is the file, if that will help:
https://www.dropbox.com/s/4kzgui1itaskuvz/strip%20list%20test.indd

Hi,
I was able to reproduce the issue you are facing.
I will be logging a bug for this and it would be investigated.
Thanks a lot for reporting the problem!!
Javed

[JS CS3] JS method for Object Styles Break Link to Style

I have pages full of objects that are assigned the pesky "Basic Graphics Frame" object style. I need to do the equivalent of choosing "Break Link to Style" in the Object Styles panel on all the objects in many files.
I haven't been able to find anything equivalent to the "Break Link to Style" functionality in looking through the Object Browser. Finding all objects with [Basic Graphics Frame] object style and applying an object style of [None] doesn't do the same result. Any ideas?

hi:
//FindObjectPreference
myDoc = app.documents[0];
app.findObjectPreferences = NothingEnum.nothing;
app.changeObjectPreferences = NothingEnum.nothing;
app.findChangeObjectOptions.properties =
objectType: ObjectTypes.allFramesType, //graphicFramesType, textFramesType, unassignedFramesType
includeFootnotes: true,
includeHiddenLayers: true,
includeLockedLayersForFind: true,
includeLockedStoriesForFind: true,
includeMasterPages:true
//var graphicOStyleName = "[Normal Graphics Frame]";
app.findObjectPreferences.appliedObjectStyles = myDoc.objectStyles.item(1);
var dstStyle = myDoc.objectStyles.item(0);
var founds = myDoc.findObject(0);
var foundsLen = founds.length, i, found;
for(i = 0; foundsLen > i ; i++){
//app.select(founds[i]); alert(founds[i].appliedObjectStyle.name);
founds[i].applyObjectStyle(dstStyle, false, false);
<pre>
jxswm

Styles Are Referencing Unwanted Style Sheet

Similar Messages

Maybe you are looking for