Configure Numbered and Bulleted Styles in CSS

I have searched and read a lot of postings re:Numbered and Bulleted styles/lists in the CSS setup and still have no clue how this was changed in the most recent build of RoboHelp HTML or the correct way to apply and get to work.
In X5 of RoboHelp HTML, I had a CSS style sheet with 5 paragraph styles with bullets. I did not create a list - I simply bulleted the style. When I apply one of these styles to a paragraph it adds a bullet.
I upgraded to RoboHelp HTML X8.0.2.208 and my bulleted styles are a total mess. The styles are still in the CSS, but when applied there is no bullet - it adds a number (then I have to click the Bullet icon button on the toolbar to apply a bullet). I have tried to find release notes or some documentation explaining the change and can find none. I have reviewed Peter Grange's site information about lists and multilevel lists, but see no reason why I cannot just apply a bullet directly on a style without using the list or multilevel list.
I guess the issue may be my stupidity on the configuration and use of lists and multilevel lists. Is there any documentation from Adobe that outlines the change that occurred as of this most recent build? I am looking for an explanation of how a list corresponds to a style and how to get the style to work correctly. Ironically, the online help has been no help at all.
As always, thanks to any feedback or direction.
Michael F Weart

OK - sorry have not posted my solution and it works for me...
This is what I did to create a single level bulleted style using bulleted list:
(1) Create a MultiLevel List Style called BulletedList
I have only defined Level 1 of the MultiLevel List
For that Level 1 - I DID NOT specify a Paragraph Style
For that Level 1 - I selected List Style of DISC
For that Level 1 - I defined the Edit Style as <x>
Saved this MultiLevel List style with a name of BulletedList
(2) Created a Paragraph Style called NBullet
Font is set to Arial 10pt
Spacing/After is set to 6pt
From Indents line - clicked the AutoNumber icon button
This opens the List for Autonumbering dialog and I set the following:
Checked the box for Inherit Numbering Property from Multilevel List
Selected BulletedList from the List Class drop down
Selected List Level as "1"
Clicked OK to apply and return to Paragraph Style Setup dialog
On Paragraph Style Setup dialog clicked the Format drop down button
Selected Paragraph formatting
Defined Left Indentation of .5in
Defined Special Indentation of Hanging .25in
(3) Clicked OK to save the Paragraph style called NBullet
When I look at the drop down list of styles within a topic, the style name appears as "1 NBullet". Don't let the "1" fool you - when I apply that style the "disc" bullet is applied and NOT a number (it just displays a number in the style name for some reason that escapes me).
I now have my bulleted style back and it works fine.
NOTE:  I do not like to reformat anything, so I set up an NBullet (Spacing After set to 6pt), NBulletSpace (Spacing After set to 12pt) and NBulletLast (Spacing After set to 18pt).
I also set up "bullet continuation" paragraph styles so I can lead with a bulleted line of text and then follow with "additional information" paragraph that aligns to the text in the bulleted lead paragraph line - that paragraph style is NBulletContinue defined with NO autonumber setup and the Format/Paragraph set to Indent/Left .75in (which aligns the text to the text of the bulleted paragraph).
I set up the same paradigm of NBulletContinue, NBulletContinueSpace and NBulletContinueLast.
=============
Aside from the Style name appearing in the Style list when working in a topic as "1 NBullet", "1 NBulletSpace" and "1 NBulletLast" the formatting works and looks great (and note - the style name when I go into CSS formatting does not have the leading "1").
Also note, if I use the Increase Indent option when working in a topic on the NBullet styled paragraph, the Level 2 bullet list format is applied. I HAVE NEVER and WILL NEVER use the Increase or Decrease Indent functionality (either in Word or RoboHTML).
All of my CSS styles match the naming convention used in my Word template - making it easier to push content back and forth between Word and RoboHTML.
=============
My approach may be non-standard and may not be within the spirit of this functionality, but it works for me and I get the formatting I need.
One last note on the comment of the "sluggishness of the product" for x8 - I had the same problem and then I applied the two patches that were made available. The difference in the response time was VERY noticeable in a GOOD way. Search for and apply both fixes to RoboHTML x8 and you will see a pronounced difference. I also got my boss to approve ordering a new PC and now there is not sluggishness at all in the performance.
Thanks to all --
Michael F Weart

Similar Messages

  • XML assign style for numbered and bullet lists

    Hi,
    This is kinda a continuation from my previous thread. I understand that XSLT has to be used to transform the previous elements to be able to use ID paragraph styles. I would think the same would have to be acoomplished for lists.
    Is it possible with paragraph styles to generate the same results as a list in HTML? Or would I have to create individual paragraph styles for each nested list?
    I hope I'm making sense.
    Like:
    <h5>Nested unordered list</h5>
    <li1>bullet list</li1>
    <li1>bullet list</li1>
    <li2>bullet list</li2>
    <li2>bullet list</li2>
    <li3>bullet list</li3>
    <li3>bullet list</li3>
    <li4>bullet list</li4>
    <li4>bullet list</li4>
    Sample HTML:
    <h5>Nested unordered list</h5>
    <ul>
    <li>bullet list</li>
    <li>bullet list</li>
    <ul>
    <li>bullet list</li>
    <li>bullet list</li>
    <ul>
    <li>bullet list</li>
    <li>bullet list</li>
    <ul>
    <li>bullet list</li>
    <li>bullet list</li>
    </ul>
    </ul>
    </ul>
    </ul>
    <h5>Nested ordered list</h5>
    <ol>
    <li>ordered list</li>
    <li>ordered list</li>
    <ol type="a">
    <li>ordered list</li>
    <li>ordered list</li>
    <ol type="i">
    <li>ordered list</li>
    <li>ordered list</li>
    <ol type="A">
    <li>ordered list</li>
    <li>ordered list</li>
    <ol type="I">
    <li>ordered list</li>
    <li>ordered list</li>
    </ol>
    </ol>
    </ol>
    </ol>

    I think the best way is to create a new paragraph style for each nested level.
    Example:
    Create a new style for each sub level.
    Text here
    Text here
    Sub level 1
    Sub level 1
    Thanks...

  • Outlines in Word Processor, numbers and bullets don't mix?

    I'm writing a meeting adenga in an outline form. I want the main topics to be numbered, sub-topics to be bulleted, and sub-subtopics to have diamond bullets.
    For some reason, the following (as an example) happens. I've created a list of 7 main topics. I add subtopics to topic # 5, which are by default also numbered instead of bulleted. As soon as I change the label style on these subtopics to bullets, topic # 6 is re-labeled # 1, topic # 7 becomes # 2, etc.
    I need to make my sub-topics bulleted without affecting the numbering of the main topics. What's happening?

    When you add a label (eg. Number) to a paragraph, you are setting a Style for that paragraph. The Style is inherited by subseqent paragraphs until a new style is set.
    When you change the label, you are resetting the Style of the selected paragraph(s). This change breaks the chain of 'subsequent paragraphs', and the count is reset.
    Rather than a Paragraph style (such as Number or Bullet), you could use one of the three Outline styles (Harvard, Diamond, or Legal) which do allow marking subtopics without affecting the numbering of the main topic list. Unfortunately, none of the three will give the topic marking pattern you want.
    You can get (almost) what you want by not creating new 'paragraphs', and by manually inserting the bullets and diamonds.
    AppleWorks considers every return character to mark the end of a paragraph, and any character following a return (other than another return, and probably a small set of other characters) to be the first character of a new paragraph.
    To start a new line without starting a new 'paragraph', use a line feed (soft return), made by pressing shift-return.
    Follow the shift-return with a tab to indent the subtopic, then option-8 for the bullet.
    For the second level of subtopics, use shift-return, tab, tab, shift-option-V.
    Regards,
    Barry

  • Numbered List and Bulleted List w/ Custom Style Sheet

    Hi,
    I am a new user to RoboHelp 7, and must say I find it useful
    but also painful to use. Currently I’m trying to solve
    something that feels like a bug in RoboHelp 7, but before I give in
    and accept defeat I wanted to check with the forum.
    I have FrameMaker 8, and import the files to RH where I use
    them to create WebHelp projects.
    Here’s a short procedure:
    1. I Import my files with a predefined style sheet matching
    the FM styles.
    2. I also check the Convert to HTML list option and set all
    numbering and bullet styles to User defined.
    - After import RH does the usual thing and creates a bunch
    of style sheets on its own
    3. I select all the files from the Topic List pod and apply a
    new custom style sheet. This enables me to have one style sheet for
    all the HTML files with the right layout and formatting
    4. I generate the output, and RH uses the new style sheet
    reference
    The resulting HTML files shows that the output is not the
    same as the generated HTML shown in RH’s HTML editor view
    - Editor view: <li class=”style”>
    - Browser view: <li>
    6. If I make a change (e.g. add a space) and save the HTML
    file, and generate the project again the HTML is correct in the
    browser
    One could argue that it’s not a big problem; however,
    with a large project this is starting to look more like a nightmare
    Does anyone know of this problem, and if so can it be fixed?
    Kind regards,
    Jon

    Is this the time when I get really angry at Adobe for creating the worst FrameMaker/RoboHelp integration ever? No! However, I must admit that I'm amazed that they are unable to solve an important feature as conversion of lists from a FrameMaker document to a RoboHelp WebHelp project. When I say conversion I mean a clean conversion with minimal interference from RoboHelp that allows me to use CSS to its full extent.
    Here's the problem, and this was also the problem with RoboHelp 7 and FrameMaker 8. BTW, I use standalone versions (not TCS 1 or 2).
    Figures: First image depicts FrameMaker 9's Paragraph Designer and the Autonumber format for a paragraph named VizNumbered. Second image depicts the RoboHelp 8's conversion setting.
    FrameMaker uses Autonumbering in front of paragraphs to create lists. This means that you in RoboHelp need to manage two formats, the autonumber and the paragraph style.
    RoboHelp does of course not (by default) use Autonumbering in front of paragraphs because a RoboHelp WebHelp project is HTML based, and list tags in HTML can perfectly handle any formatting of text etc.
    RoboHelp will convert, when "Convert Autonumber to HTML List" is selected, the Autonumber in FrameMaker to a list tag (LI). By default this will generate a list with a lot of margin, font and other CSS properties that tries to simulate the way the list is laid out in the FrameMaker document. In addition to the list tags it will convert the FrameMaker paragraph to a P tag which it inserts within a list tag. The issue you will experience with this is that indentations with the paragraph tag does not align properly between line 1 and 2. At the same time the WebHelp project will not look the same in IE, Firefox or Chrome. That is, Chrome and Firefox will look the same, and IE different. IE has the WYSIWYG feel, but it does not comply well with W3C standards (i.e. using P tags enclosed by LI tags is not a good idea ...).
    Selecting "Convert Autonumber to RoboHelp List" does something similar, but is not recommended at all!
    So, here's the big question. How can I make sure RoboHelp understands that I ONLY need to define a list tag with a CSS class attribute attached to it?
    Today I basically only get the following:
    <li><p class=""></p></li> or,
    <p class=""></p>
    What I want is the following:
    <li class=""></li>
    Can this be solved with today's versions, can anyone help me, or do I have to wait for the Adobe development team to realize this and to fix it?

  • Bullet style defined as "disc" in CSS is inserted as "circle"

    We use RH9 with RSC. I've been wondering about this problem for a few weeks and maybe someone here has an idea why it's happening...
    The bullet style is defined as "disc" in our CSS, yet when I insert a bulleted list (using the button on the RH toolbar), my bullets end up as "circle" style. I don't use any other formatting on the bullets (the HTML I get is just <ul style="circle"><li>blahblah</li</ul>). The weird thing is that's it's only happening for me. My coworker opened the same project and she's getting "disc" bullets correctly.
    It's not a major problem, I just go in the HTML and fix the bullets manually, but it's really bugging me. Is there a global setting in RH (or Windows?) that I messed up? Did I somehow set "circle" bullets as my default and that's overwriting the CSS?

    I am guessing this is not source control related but because of the way you have defined lists.
    In older versions of Rh you could define a paragraph style as a list. Since Rh8 lists have to be defined as list styles but you can superimpose a paragraph style for characteristics such as as font size and colour for the text. See Lists on my site and the link to Upgrading.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Help with bullet style in external CSS

    I'm learning Dreamweaver after using Frontpage. I'm also kind
    of new with external stylesheets. And am stuck on formatting
    bullets. I can't seem to figure out the code for a bullet style and
    only find code for inline style sheets.
    More importantly, I can't create leading between the bullets.
    In FrontPage, I just set paragraph spacing before and after (for
    instance, 6 pt). Would it be margin-bottom? Anyway, here is the
    code I have, but when I apply it, no bullets appear.
    .bullet {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 12px;
    color: #000000;
    text-align: left;
    list-style-position: outside;
    list-style-type: disc;
    Thanks, Susan

    The CSS rule is the same whether it is use inline, in the
    <header> part
    of the document or an external stylesheet.
    In your CSS sample below, you defined a class with the proper
    declarations, but most likely you did not apply that class to
    your list
    in the HMTL.
    <ul class="bullet">
    <li>......
    If every list is styled the same way, you can simply
    (re)define the ul
    tag in your stylesheet.
    ul {font-family....}
    If you want leading between the bullets there are several
    different
    possibilities like applying padding, margin using line-height
    but in any
    case you have to apply it to the list items - <li>
    To go with your example, the CSS would be:
    .bullet li {padding: 6pt 0}
    Be careful with using pt as a measure on screen though.
    Although you are
    permitted to doing so, it is more advisable to use pixels or
    event
    better a relative measure such as em.
    Anurag
    s3r3nity1 wrote:
    > I'm learning Dreamweaver after using Frontpage. I'm also
    kind of new with
    > external stylesheets. And am stuck on formatting
    bullets. I can't seem to
    > figure out the code for a bullet style and only find
    code for inline style
    > sheets.
    >
    > More importantly, I can't create leading between the
    bullets. In FrontPage, I
    > just set paragraph spacing before and after (for
    instance, 6 pt). Would it be
    > margin-bottom? Anyway, here is the code I have, but when
    I apply it, no bullets
    > appear.
    >
    > .bullet {
    > font-family: Verdana, Arial, Helvetica, sans-serif;
    > font-size: 12px;
    > color: #000000;
    > text-align: left;
    > list-style-position: outside;
    > list-style-type: disc;
    >
    > Thanks, Susan
    >

  • After updating numbers and pages I can no longer copy multiple cells from numbers and paste and match style to pages.

    After updating numbers and pages I can no longer copy multiple cells from numbers and paste and match style to pages.  I used to be able to select multipule cells in a row (such as company name, address, etc.) then paste and match style on to a pages letter. I found the paste and match style option in the edit menu, however it will only work one cell at a time. Before the update is was working great.

    For diagnosing purpose thy the procedure in a new user account and see if it works there. You create a new user account in the System Preferences > Accounts. If it works in the new account it is probably a corrupt plist file that needs to be deleted.

  • Bullet and number styles different when viewed

    I'm using RoboHelp 6 to produce a WebHelp project.
    It seems like the bullet and number styles behave differently
    than the other styles. There is an automatic indent, even though
    Left is set to 0, and a tab. I have been able to get the View
    Selected Item to look the way I want (with a hanging indent that
    aligns under the tabbed text) even though it looks very different
    in the WYSIWYG Editor.
    With the Number style, the font size seems much larger in the
    View Selected Item than it does in the WYSIWYG Editor. Is there a
    way to know what the font size will be/look like to the Help user?
    The number size also seems to be different if I use the Create a
    Number List button or use the Number style. What is the difference
    between using the style and using the button? Can I control the
    number and bullet font and size?
    I'm still learning.
    Thanks

    Bummer!
    RH doesn't always remove every piece of code when you, for
    instance, select bolded characters and click the Bold toolbar
    button; it often adds another SPAN tag for normal inside or outside
    the bold tag!
    The surest way I know to completely purge content is to
    filter it through a plain text editor like Notepad:
    1. In the RH topic, select the content (some paragraphs or
    the entire topic).
    2. Cut it (Ctrl+X).
    3. Paste it into Notepad (Ctrl+V).
    4. In Notepad, select and cut the content.
    5. In the RH topic, paste the purged content where the old
    content used to be.
    Each paragraph will only get P tags assigned to it, allowing
    you then to style your way through them. Of course, this
    slash-and-burn method eliminates all hyperlinks, pop-ups, etc., so
    plan accordingly.
    Good luck,
    Leon

  • Spry Menu Bar 2.0 (1.0) - Handling of widget generated CSS, placement and rendering problems in CSS

    Hello:
    I wanted to repost my question to re-frame the issue based on what I have learned thus far.
    I am working on a website that has been developed using the Spry Menu Bar Framework UI (2.0) I.0, that has some peculiar rendering problems that affect IE 6 in particular.  The CSS is reprinted below.
    In particular, when I post the widget generated CSS in the head as it is orginally situated by the framework, the menu bar works fine.  However, it seemed to me that I should be able to reduce page weight (an important consideration considering my target population) by placing it in the general style sheet governing the entire site.
    When I place the styles at the beginning of the style sheet the menu doesn't render at all in any of the browsers (IE 6+, Firefox, Opera, Safari, Netscape, etc.) as it conflicts with the general rules governing links that appear later in the style sheet.  When I place the styles specific to the Menu bar at the end of the style sheet, then the menu bar renders properly in all browsers except IE 6.
    The odd thing is that the only way to ensure that the menu bar works in IE 6 is to keep the menu related styles in the head of each page.  This raises problems related to page weight (not an insurmountable consideration if no other solution can be found) but still an issue.  Likewise I need to support IE 6, again given the target audience/population.  The issue obviously has something to do with specificity, but I am not certain that is the only consideration at work here.  I have not tried the !important selector in regard to the menu, as IE 6 seems to only partially support this.
    Thanks in advance for any advice or insight that can be provided.  Thanks in particular to Martin for his contributions to my earlier question related to this issue.
    Steve Webster.
    The CSS governing the horizontal menu bar is as follows:  (currently the following CSS is embedded in the head of the web page)
    <style type="text/css">
    /*  -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles --  */
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
       these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
       .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
       You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
       with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:transparent;
       font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 17px;
        font-style: normal;
        padding:0;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 10px 10px 10px 4px;
        background-color:#000088;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
        background-repeat:repeat-x;       
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none none none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:center;
        line-height:1.4em;
        color:#ffffff;
        background-color:transparent;
        padding: 0px 18px 0px 5px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: bold;
        font-size: 15px;
        font-style: normal;
        background-color:#000088;
        padding:0px 2px 0px 0px;
        border-width:0px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: none;
        padding: 0px;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 0px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: none none none none;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 10px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:transparent;
        color:#ffffff;
        padding: 10px 10px 10px 10px;
        width: 240px;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #2E35A3;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
        background-repeat:repeat-x;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    #MenuBar .SubMenu .MenuItemHover {
        background-color:#2E35A3;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: transparent;
       min-width:0%;  /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                       0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: transparent;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
    * all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
    * The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    /* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
    </style>
    The CSS governing the site generally is reproduced below:  (my belief is that it is the a:link, a:visited,  a:hover, a:active styles that may be in conflict).
    @charset "utf-8";
    body  {
        font: 100% Verdana, Arial, Helvetica, sans-serif;
       min-height: 0; /* This is necessary to overcome the "haslayout" bugthat is found in Windows 7 in conjuction with IE8.  For Moreinformation see: URL -- http://reference.sitepoint.com/css/haslayout.html */
        margin: 0; /* it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
        padding: 0;
        text-align:center; /* This allows for the centering of the container and overcomes a bug inherent in IE 5 */
        color: #000000;
        list-style-image: none;
        background-color: #FCFCFC;
    h1,h2,h3,h4,h5,h6 {
    color:#000066;
    a:link {
        color: #151A96;
        text-decoration: underline;
    a:visited {
        text-decoration: underline;
        color: #1B8DCD;
    a:hover {
        text-decoration: none;
        color: #F30A0A;
    a:active {
        text-decoration: underline;
        color: #151A96;
    #container {
        width: 960px;   
        margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
        text-align: left; /* this overrides the text-align: center on the body element. */
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Midsection %20_960.png);
        background-repeat: repeat-y;
    #header {
           padding: 0;  /* this padding matches the left alignment of the elementsin the divs that appear beneath it. If an image is used in the #headerinstead of text, you may want to remove the padding. */
            width:960px;
            height:332px;
            background-image:
            url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Header_960 .png);
            background-repeat:no-repeat;
    #header h1 {
        margin-right: 0px; /* zeroing the margin of the last element in the #header div will avoid margin collapse - an unexplainable space between divs. If the div has a border around it, this is not necessary as that also avoids the margin collapse */
        padding: 0; /* using padding instead of margin will allow you to keep the element away from the edges of the div */
        display:none;
    #header img {
        display: none;
    #Main_nav_contents {
        padding: 0;
        margin-top: 0px;
        height: 39px;
        width: 950px;       
        padding-top: 275px; 
        padding-left: 39px;
        z-index: 3; 
    #MenuBarVertical {
        margin-bottom: 50px;
        padding-top: 50px;
        padding-bottom:200px;
        padding-left: 15px;
        padding-right: 15px;
    .mainContent_left {
       margin: 0;/* the right margin on this div element creates the columndown the right side of the page - no matter how much content thesidebar1 div contains, the column space will remain. You can removethis margin if you want the #mainContent div's text to fill the#sidebar1 space when the content in #sidebar1 ends. */
        padding-left:30px;
        padding-right:20px; /* remember that padding is the space inside the div box and margin is the space outside the div box */
        width: 600px;
        float: left;
    .sidebar_right {
        float: right; /* since this element is floated, a width must be given */
        width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
        margin-top: 30px;
        margin-left:0;
        margin-right:10px;
        font-size:90%;
    .mainContent_right {
        margin-left: 10px;
        padding-left:30px;
        padding-right:20px;
        width: 600px;
        float: right;
    .sidebar_left {
        float: left; /* since this element is floated, a width must be given */
        width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
        margin-top: 30px;
        margin-left:30px;
        margin-right:0;
        overflow: hidden;
        font-size:90%;
    .main_content_centered {
        width: 650px;
        margin-left: 155px;
    .main_content_centered_header {
        margin-left: 75px;
    .sidebar_textbox {
        margin: 0px;   
        width: 260px;
        padding: 2px;
    .sidebar_textbox_header {
        width:255px;
        height:58px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Header.png);
    .sidebar_textbox_background_middle {
         width: 255px;   
        padding-top: 12px;   
        padding-bottom: 10px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Middle.png);
        background-repeat: repeat-y;
    .sidebar_textbox_content {
       /* The width and padding are set as follows to accomodate quirks inbrowser rendering and to ensure that text is contained within thebackground of the text box */
        width: 230px;
        padding-left: 20px;
        padding-right: 40px;
    .sidebar_textbox_footer {
        width:255px;
        height:64px;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Port rait%20Textbox%20Footer.png);
    #issues_menu a:link {
        color: #151A96;
        text-decoration: none;
        font-weight:bold;
    #issues_menu a:visited {
        color: #151A96;
        font-weight:bold;
        text-decoration: none;
    #issues_menu a:hover {   
        color: #F30A0A;
        font-weight:bold;
        font-style: oblique;
        text-decoration: none;
    #issues_menu a:active {
        color: #151A96;
        font-weight:bold;
        text-decoration: none;
    #archives {
        padding-top: 15px;
        padding-right: 15px;
        padding-bottom: 20px;
        padding-left: 0px;
    .landscape_textbox {
        width: 500px;
        margin-right: 0px;
        margin-left: 30px;
        padding-top:35px;
        padding-bottom: 25px;
        font-style: normal;
        font-weight: normal;
    .landscape_textbox_hdr {
        width:500px;
        height:38px;
        margin:auto;
        padding:0;
        background-image:
    url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Landscape%20Textbox%2 0Header.png);
    .landscape_textbox_middle {
        width:auto;
        margin:auto;
        padding-top: 12px;
        padding-bottom: 12px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/lan dscapte%20Textbox%20Middle.png);
        background-repeat:repeat-y;
    .landscape_textbox_content {
        width:450px;
        padding:25px;
    .landscape_textbox_ftr {
        width:500px;
        height:44px;
        margin:auto;
        padding:0;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Lan dscape%20Textbox%20Footer.png);
    #footer {
        padding: 0; /* this padding matches the left alignment of the elements in the divs that appear above it. */
        width: 960px;
        height: 222px;
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Footer%20_ 960.png);
        background-repeat:no-repeat;
    #footer p {
       margin: 0px; /* zeroing the margins of the first element in the footerwill avoid the possibility of margin collapse - a space between divs */
        padding:0px; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
        text-align:center;
        margin-left: 50px;
        margin-right: 50px;
        padding: 10px;
        font-size: small;
    #footer h5 {
    text-align:center;
    .fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
        float: right;
        margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page */
        float: left;
        margin-right: 8px;
    .clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
        clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    .dropcap {
        display: block;
        float: left;
        line-height: 80%;
        font-size: 250%;
        font-weight: bolder;
        color: #000066;   
        padding: .03em .1em 0 0;
    .red_arrows {
        list-style-position: outside;
        list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Arrow%20Large.png);    
    .blue_bullets {
        list-style-position: outside;
        list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Bullet%20Medium%20Fu ll.png);   
    .attention {
        color: #F30A0A;
        font-size:x-large;
        font-family: Georgia, "Times New Roman", Times, serif;
        font-style: italic;
        font-weight:900;
    .attention_small {
        color: #F30A0A;
        font-size:large;
        font-family: Georgia, "Times New Roman", Times, serif;
        font-style: italic;
        font-weight:900;
    .table {
        table-layout:fixed;
    .blue {
        color: #00F;
    #container .mainContent_left p .blue {
        color: #0303A0;

    Hi Nancy:
    The specific code that I am referring to is the CSS code governing the styling of the spry menu widget that only works in IE 6 if, and only if, it remains in the head of the web page.  If removed and placed in a stylesheet, the IE plugins fail to compensate for the IE 6 "gap" bug.  As I said, it doesn't make sense to me that, assuming specificity is addressed, that these can not be included in an external style sheet.  I am looking for a) an explanation why they must remain embedded in the web page; and 2) any means by which I might be able to export them.
    I will reproduce the specific css style (code) below:  it should also be visable through reveal source --
    Thanks again, Steve Webster.
    The CSS governing the horizontal menu bar is as follows:  (currently the following CSS is embedded in the head of the web page)
    <style type="text/css">
    /*  -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles --  */
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
       these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
       .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
       You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
       with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:transparent;
       font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 17px;
        font-style: normal;
        padding:0;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 10px 10px 10px 4px;
        background-color:#000088;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
        background-repeat:repeat-x;       
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none none none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:center;
        line-height:1.4em;
        color:#ffffff;
        background-color:transparent;
        padding: 0px 18px 0px 5px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: bold;
        font-size: 15px;
        font-style: normal;
        background-color:#000088;
        padding:0px 2px 0px 0px;
        border-width:0px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: none;
        padding: 0px;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 0px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: none none none none;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 10px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:transparent;
        color:#ffffff;
        padding: 10px 10px 10px 10px;
        width: 240px;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #2E35A3;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
        background-repeat:repeat-x;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    #MenuBar .SubMenu .MenuItemHover {
        background-color:#2E35A3;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: transparent;
       min-width:0%;  /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                       0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: transparent;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
    * all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
    * The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    /* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
    </style>

  • How to apply style sheet (.css) in Weblogic directory listing

    Hi,
    We are migrating a directory listing application from Apache to Weblogic.
    Earlier we did this by Apache httpd.conf entry like below :
    <Directory "/opt/apache/httpd-2.1.9/htdocs/Myreportfolder">
    IndexOptions FancyIndexing FoldersFirst NameWidth=* XHTML
    IndexOrderDefault Descending Date
    IndexStyleSheet "/css/style.css"
    </Directory>
    /opt/apache/httpd-2.1.9/htdocs folder has all it's usual resource files.
    We were able to see documents in "Myreportfolder".
    Now we have moved to Weblogic and using virtual directory mapping as below and we are trying to achieve the same thing:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <wls:weblogic-web-app xmlns:wls="http://www.bea.com/ns/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd">
    - <wls:container-descriptor>
    <wls:index-directory-enabled>true</wls:index-directory-enabled>
    <wls:index-directory-sort-by>LAST_MODIFIED</wls:index-directory-sort-by>
    </wls:container-descriptor>
    - <wls:virtual-directory-mapping>
    <wls:local-path>/Myreportfolder</wls:local-path>
    <wls:url-pattern>/*</wls:url-pattern>
    </wls:virtual-directory-mapping>
    <wls:context-root>/getreports</wls:context-root>
    </wls:weblogic-web-app>
    We are able to view the reports but we do not get look-and-feel of Apache like directory listing.
    but we encounter below issues:
    1) File/Folder icons are not visible - we want to use style sheets in http header from the response that is returned from weblogic server
    2) Filename is limited to 29 characters when it is showing
    3) Files are not sortable as Descending order - we sorted using tag <wls:index-directory-sort-by>LAST_MODIFIED</wls:index-directory-sort-by> but the latest file is shown at the last
    We are thinking that Weblogic must be having some configuration like Apache httpd.conf where we can apply style sheets (css ).
    We would appreciate af anyone can provide better insight into the issue.
    or is it possible to extend weblogic.servlet.fileservlet class to serve this purpose.
    Thanks & regards,
    Rabi

    Hi Vikash,
    Check the below links which will you idea on the same.
    Stylesheet for WDA without integrating in SAP Portal
    Apply custom css to WebDynpro application
    Thanks
    KH

  • How do I move the numbers or bullets closer to the list?

    Oh Dreamweaver sages...How do I move the numbers or bullets closer to the list?  Please look at this  http://www.stii.us/whatisst.html  and tell me what you recommend.  Thank you!

    With CSS margins and padding.
    #mainContent li {
      margin-left:10em;
      padding-left:0;
    Also remove the <p> tags from all your <li> tags.
    <ol>
         <li>this is a list item</li>
         <li>this is a list item</li>
         <li>this is a list item</li>    
    </ol>
    Nancy O.

  • How can I add a new Template to My Templates in Pages? I've read most of the discussions on the subject but it doesn't work for me. By the time I reach the Templates folder, I only see templates for Numbers and not for Pages. Need help, please.  Thanks

    How can I add a new Template to My Templates in Pages? I've read most of the discussions on the subject but it doesn't work for me. By the time I reach the Templates folder, I only see templates for Numbers and not for Pages. Need help, please.  Thanks

    Si vous avez utilisé la commande Save As Template depuis Pages, il y a forcément un dossier
    iWork > Pages
    contenant Templates > My Templates
    comme il y a un dossier
    iWork > Numbers
    contenant Templates > My Templates
    Depuis le Finder, tapez cmd + f
    puis configurez la recherche comme sur cette recopie d'écran.
    puis lancez la recherche.
    Ainsi, vous allez trouver vos modèles personnalisés dans leur dossier.
    Chez moi, il y en a une kyrielle en dehors des dossiers standards parce que je renomme wxcvb.template quasiment tous mes documents Pages et wxcvb.nmbtemplate à peu près tous mes documents Numbers.
    Ainsi, quand je travaille sur un document, je ne suis pas ralenti par Autosave.
    Désolé mais je ne répondrai plus avant demain.
    Pour moi il est temps de dormir.
    Yvan KOENIG (VALLAURIS, France)  mercredi 23 janvier 2011 22:39:28
    iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
    My iDisk is : <http://public.me.com/koenigyvan>
    Please : Search for questions similar to your own before submitting them to the community

  • Is there a 'macro' to convert a Word style to CSS tag?

    The text in my source (Word) has a named character style applied to selected words/phrases throughout the text.  I want to detect that specific character-style spec. in the source (pasted from Word into a DW target page) and have a way to translate what was a Word style-spec. into a specific CSS style for that same piece of text in the HTML. 
    For example, say the Word style is a character style named "boldBlue" (which, when applied to the text, makes it appear in ... bold and blue).  In CSS, I have a style named "BB" -- I want the HTML to have the same text tagged correctly using the CSS spec. for "bold blue" (BB), without needing to assign that CSS tag over and over and over to each case.
    Is there some 'macro' (or 'batch') way to accomplish this in CS6?

    Honestly, the best thing you can do is strip out all Word generated code. Word is a horribly writer of html and css and will increase the headache factor of your project by an order of magnitude. DW has a feature built into it specifically to strip out all Word generated gibberish simply because it is so terrible...
    Commands > Clean Up Word HTML
    To change code from something like class="BoldBlue" to class="BB", you can open the page in source view and use the Find & Replace feature to replace all instances of BoldBlue with BB.
    Ctrl + F or Edit > Find and Replace
    When the dialogue window pops up, choose Current Document and Source Code from the drop downs. Put the exact text, spaces and all into the Find field and the new info in the Replace, then click Replace All.

  • Character Styles in CSS Properties Panel are not correct

    I am using Adobe Illustator CC.
    I am trying to export all of the charter styles as CSS. However the CSS panel is not generating the correct style.
    Right now, in the Character Styles Panel and CSS Properties Panel I have 3 styles (Default, h1, h2)
    This is how they are defined in the Character Styles Panel:
    1. [Normal Character Style]:Helvectic Neue LT Std, 55 Roman, 16px
    2. h1: Helvectic Neue LT Std, 25 Ultra Light, 35px
    3. h2: Helvectic Neue LT Std, 45 Light, 18px
    HOWEVER
    When I go to the CSS Properties panel the code is not showing the Font Style:
    This is how they are defined in the CSS Properties Panel:
    1. [Normal Character Style]:
    .NormalCharacterStyle
      font-family : Helvetica Neue LT Std;
      font-size : 16px;
      color : #19131F;
      color : rgb(25, 19, 31);
    2. h1:
    .h1
      font-family : Helvetica Neue LT Std;
      font-size : 35px;
      letter-spacing : 0.53px;
      color : #FFFFFF;
      color : rgb(255, 255, 255);
    Missing:  25 Ultra Light
    3. h2:
    .h2
      font-family : Helvetica Neue LT Std;
      font-size : 18px;
      text-transform : uppercase;
      color : #FCFCFC;
      color : rgb(252, 252, 252);
    Missing:  45 Light
    Am I not doing somethign correctly? Is it a problem with my font or with Illustrator?
    Also, in case it makes a difference, I only have the default paragraph style defined. It's style is; Helvectic Neue LT Std, 55 Roman
    Thanks!

    CSS cannot render typographical multiple weight fonts simply because that's just not how it works. All CSS does is reference a physical font file and its properties and while it's possible to use the font-weight and font-style attributes to make standard fonts lighter or bolder it does not compare to anything you would do with the font in a real design environment. That and of course you still need to define fallback/ substitution options - the Helvetica Neue you are referencing is exclusively available on Apple systems only and even if what you are trying worked off the bat, it would be useless on alternate devices that have no access to the font.
    Mylenium

  • The Response Group application was unable to transfer the call to the configured destination and no fallback exists

    Hey,
    I get this error message when calling into an unassigned number which redirects to a response group:
    From user URI:
    sip:[email protected];gruu;opaque=srvr:Microsoft.Rtc.Applications.Acd:RS6nRGV9DlmpNsLtmz5qeQAA
    To user URI:
    0220198611;phone-context=DefaultProfile
    From user agent:
    RTCC/4.0.0.0 Response_Group_Service Announcement_Service
    Diagnostic header:
    26005; reason="The Response Group application was unable to transfer the call to the configured destination and no fallback exists."
    Interestingly "To user URI: 0220198611;phone-context=DefaultProfile" is the number off the caller not the destination. I wonder is this a bug? So is the response group trying to transfer to this number and failing because of course it doesnt exist?
    As you can see the below the number I am calling is not 0220198611: 
    From phone number: 0220198611;phone-context=DefaultProfile
    To phone number: +6493760053 From mediation server: onzlyncfe1.domain.co.nz To mediation server: From gateway: 192.168.100.70
    To gateway:
    Disconnected by: +6493760053
    Does the calling party's number have to be normalised? If so how can I do this because the global normailisation rules dont seem to apply
    in this situation. These rules do work when when calling into a users DDI. 
    Also to be clear....
    +6493760053 is an unassigned number which is setup to redirect to a response group.
    If I assign +6493760053 to a user then it works.
    Additionally this works perfectly when the gateway sends the call to our legacy 2007r2 mediation server then on to Lync. If the gateway sends the call directly to the co-located Lync mediation server I get the error described.
    I hope I make sense. If you are confused let me know :)
    Help is appreciated.
    Thanks,
    Andrew

    Hi ANdrew
    Kindly advise how you transfered the unassigned numbers to a specific user, i used the below command but it failled, the message displayed but the call never routed:
    New-CsAnnouncement -Parent service:ApplicationServer:LyncFE.squareone.local -Name "SQ unassigned number announcement" -TextToSpeechPrompt "You entered an invalid extinsion you will be forwarded to the operator" -Language "en-US" -TargetUri "sip:[email protected];user=phone"
    While [email protected] is the sip uri in my lync for the operator
    could you advise what is my issue?

Maybe you are looking for