Font or text rendering problem :(

Hello!
I have a problem in Numbers with text rendering or something like that.
Some characters have wrong representation right in cells. And when I export document to PDF all characters which cross the cell border have white lines.
I already tried to rebuild font cache without luck.
Can anyone help to figure this out?
Thank you!
P.S.
Numbers 2.1, Mac OS X 10.7.2, here is a snapshot:

You already know that but it may be interesting for others.
(1) the OP's document behave the odd way on my machine.
(2) When I insert similar characters in a complementary table in the original document, it behave flawlessly.
Now are new informations.
(3) I copied the content of your tables and pasted values in tables of a blank new document.
With the font set to Helvetica everything was OK.
I tried several fonts.
Avant Garde --> OK
Baskerville --> OK
Calibri --> OK
Arno Pro --> OK
Cochin --> OK
Garamond Premier Pro --> OK
Minion Pro --> OK
Warnock Pro --> OK
Arial --> Odd behavior
This odd behavior doesn't strike in TextEdit or Pages.
So there is clearly a problem between Numbers and Arial
Yvan KOENIG (VALLAURIS, France) lundi 30 janvier 2012
iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
My Box account  is : http://www.box.com/s/00qnssoyeq2xvc22ra4k

Similar Messages

  • BUG: text rendering problems after keyboard firmware update

    Hey all!
    Just letting you know that today, after installing the keyboard/mouse firmware update 1.0, the font rendering in many applications become weird, letters may overlap, see some screenshots:
    http://artemio.net/tmp/apple/bug1.png
    http://artemio.net/tmp/apple/bug2.png
    My system is iMac Intel Core Duo 17", 2 GB RAM, 250 GB HDD, Mac OS 10.4.6.

    Just to clarify, that was a software update, not a firmware update. I don't think the keyboard has any resident firmware.
    Since this is a new update from Apple, and there have been very few posts about problems after it was installed, (I have seen a couple here) I think that you should call and speak directly with an Apple Customer Service rep. That way Apple knows some have issues with the update and they may have suggestions.
    Let us know what they say.

  • ADE 2.0 text rendering problem

    I've been using ADE 1.7 with epubs on my PC. Yesterday I updated to 2.0, but it seems to have some kind of a problem displaying text.
    http://i.imgur.com/ZihT8.png
    As you can see, the text has some kind of a resolution problem.
    When I adjust the window's size, the text seems to be shifting with it too, the pixel-jumble changing with the every pixel I move the panel's border. Justified or aligned text, it doesn't matter, neither the font size I choose in ADE (bigger font sizes look better, but they still have this problem). Cover pictures are pixelated as well.
    It looks as if it's resizing every line or something.
    I've got an ATI HD5670 video card, with the latest driver, if that helps. Desktop resolution is set to 1440x900.
    Any tips? What could be the problem?

    I'm afraid my universal response to problems with ADE 2.0 is to replace it with the earlier version that works.
    Maybe Adobe will test v2.1 before they release it?
    Version 1.7.2, it is a little difficult to find, available on Adobe site for Windows and for Mac.
    http://helpx.adobe.com/digital-editions/kb/cant-install-digital-editions.html
    The forum software is sometimes corrupting the link above.  There shouldn't be a blank in 'editio ns.html'.  The following redirects to the same page: http://tinyurl.com/diged172

  • Safari 5.1.7 and OSX 10.6.8 (Snow Leopard) - Text rendering problem with Zoom

    After updating to Safari 5.1.7, all of my web pages do not render properly when I use zoom feature of OSX 10.6.8.  I am nearsighted, and like to increase the size of web pages.  Until this update, Safari was fine--zoom, and the page zooms properly (e.g., text fits in address bar, pictures/text are not cut off, etc.).  After this update, Safari opens up text in smaller font, running in a narrow line down the page, and doesn't use the full screen, as does Firefox for example.  I like Safari, and would like to remedy this.  Any suggestions?

    I fixed this by unchecking "Zoom Text Only" in Safari > View menu.

  • Text rendering problems in Safari

    I am using Vista so I don't know if you will be able to help me, but I have this problem using both Safari and Chrome:
    Some random web pages display like that, as do the 'Trending Topics' and 'Who To Follow' sections on Twitter. I have tried changing the encoding on both browsers to no avail. This problem does not exist in IE, but has been happening for me in both Safari and Chrome for over a year. Completely stumped!

    HI,
    Try Safari maintenance.
    From the Safari Menu Bar, click Safari / Empty Cache. When you are done with that...
    from the Safari Menu Bar, click Safari / Reset Safari. Select the top 5 buttons and click Reset.
    Mac OS: Web Browser Quits Unexpectedly or Stops Responding
    Safari add-ons can cause performance issues or other situations
    Carolyn

  • Diagnosing Arabic font rendering problem

    I have an application that is localized into Arabic. On three machines I have access to to test on (Windows Vista, OS X, and Fedora 9), when the locale is set to Arabic, the UI is rendered correctly - menus, buttons, etc. all have their text rendered in Arabic and look fine.
    The person that translated the text into Arabic, however, doesn't have the same results. He's running Linux (can't remember what flavor) and when he runs the application, the Arabic text all comes out as boxes. He says this is the case for any LookandFeel he tries (Metal that hideous GTK, Nimbus).
    Since I can verify that the application does look okay on some machines, I feel comfortable in thinking that it's an issue on his specific machine. My question is - how can we diagnose what the problem actually is?
    His machine's default locale is Arabic, and other (non-Java) applications render Arabic text fine.
    He's using Sun Java 1.6 (not sure what minor release though), not GNU Java.
    (Possibly?) relevant info:
    I noticed that several UI keys such as "Menu.font" and "Button.font" are using a Deja Vu font on my Vista system when rendering Arabic. He says his system does have Deja Vu fonts installed, but when he's getting his boxes displayed, it seems these properties are set to some other Bitstream Vera font.

    Sorry, I haven't a clue regarding a possible solution, but I thought I'd share this:
    BoBear2681 wrote:
    I noticed that several UI keys such as "Menu.font" and "Button.font" are using a Deja Vu font on my Vista system when rendering Arabic. He says his system does have Deja Vu fonts installed, but when he's getting his boxes displayed, it seems these properties are set to some other Bitstream Vera font.According to [this page|http://linux.wareseeker.com/Desktop-Environment/dejavu-fonts-2.19.zip/314962]
    The DejaVu fonts are a font family based on the Bitstream Vera Fonts
    db

  • Font / text edit problem in photoshop CS6

    Hi there,
    I have a strange text edit problem in Photoshop CS6 running on Mavericks.
    Every time I use the text-tool in PS, write a sentence, mark it and change something like color, font size etc., the marked text vanishes.
    I have to "undo" the last step and the changed text appears again.
    Every time!
    I have a clean installed CS6 with no plugins and no other than system fonts installed.
    Everything on a new Mac Pro with OS X 10.9.5
    Any clues? Thanks.

    Do you have the latest updates for photoshop cs6?
    You can use Help>Updates from within photoshop cs6 to check if there are any available.
    Also, if you go to Help>System Info from within photoshop cs6, you can see the Photoshop Version in the top line.
    You should be on version 13.0.6
    See if turning off Dictation solves the issue.
    Go to System Preferences ---> Dictation and Speech -----> select OFF radio button .

  • Arial font rendering problem in AIR

    Hi,
        I am new to flex. I have a problem in rendering arial font in Label in AIR application.
    I have attached the screen shot.The letter W has been cutted.
    Regards,
    Jayagopal.

    OK, I eventualy discover that Java uses its own font configuration, and look for the fonts in /usr/share/fonts/TTF. As I use Bohoomil bundle fonts, which does not install fonts in this directory, Java wasn't finding the right fonts.
    Copying the DejaVu family in /usr/share/fonts/TTF solved the problem.

  • Staff? Text rendering incompatibility  Safari 7.06 and Muse 2014.1.1.6     Websafe fonts render issue

    Text rendering incompatibility
    Safari 7.06 and Muse 2014.1.1.6
    Websafe fonts render poorly when on top of a
    ‘Browser Fill’  has ‘Image added’  and ‘scrolling’ check box left unchecked’
    or when
    Any ‘composition is set below the text and composition is set to ‘pin’
    Comparison Web safe fonts render
    Chrome = all good
    Firefox = all good
    Safari running on ‘non-retina’ displays = bad
    As mentioned these are websafe font / also occurs with self/hosted fonts
    unfortunately client is viewing on Ipad that is non retina and uses Safari.
    Any work around?
    Thanks
    Milton

    Hi Zak
    Thank you for your prompt response.
    I have been reviewing this issue on a number of screens an Browsers – I realise the huge hassle of compatibility comments.
    Below links and further explanation and screen shots
    Thanks again
    Milton
    Web safe fonts (e.g. helvetica / arial) render poorly when:
    Any ‘composition’ is set below the text and the 'composition' is set to ‘pin’
    See first scroll page at www.edehorton.com
    The top slideshow is 'pinned' and it is this action that creates the issue for text on the whole page.
    It also occurs when text is on top of a ‘Browser Fill’  that has an ‘Image added’  and ‘scrolling’ check box left unchecked’
    See first scroll page a www.edehorton.com/judaica.html
    creates the issue for text on the whole page.
    I can remedy these  situations by ‘unpinning' the 'compostion’ or placing the ‘pinned' 'composition' above the text
    or in the second instance by turning the ‘scrolling’ radio check button in ‘Browser fill’  on.
    Screen snap shots below
    Comparison 'Web safe font - Helvetica' plus 'Webfont' render
    Chrome = all good / Firefox = all good /Safari running on ‘retina’ displays = all good Safari 5.06 on' non-retina' = all good
    Safari 7.06 running on ‘non-retina’ displays = bad

  • 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>

  • Since numbers 3.1 rendering problem in output

    Since I upgraded to Numbers 3.1 all printed output is no more crispy, it looks like a rendering problem. My Number documents consist of normal text elements and tables, sometimes some charts. Scaling on printout is not activated. On the Mac display the problem does not exist, everything seems to be fine, also in large zoom factors. But printing the document produces some kind of unrendered, pixely output, comparable to a screenshot, by far not that crisp as in Numbers 3.0.1. Other applications such as Pages, Word, Excel are not affected, printouts are fine.
    What I did so far:
    - uninstall and reinstall numbers
    - changing, reinstalling the printer driver (HP Color LaserJet 2025 Series), I use the Postscript driver
    - converting the Number documents to Numbers '09 and opening them again
    - playing and testing with numerous zoom factors
    - changing fonts in the Numbers document
    ... all without any success.
    What helped me was:
    - Installing Numbers 3.0.1 again using TimeMachine, installed it parallel to Numbers 3.1
    - In Numbers 3.1 exporting the Numbers document to Numbers '09
    - Opening that document in Numbers 3.0.1
    - Printing the document in Numbers 3.0.1 --> Output ist fine and perfect.
    It seems to be a rendering problem, only in Numbers 3.0.1. The problem appears in all existing and new Numbers documents on Numbers 3.1.
    Here is my infrastructure:
    MacBook Air Mid 2013, OS X Mavericks 10.9.1
    Numbers 3.1 (1769)
    HP Color LaserJet CP2025dn using PostScript
    Many thanks for your help!
    speckch

    Perhaps you can see the problem in this version. This is a PRINTING problem. You cannot see it on screen in the pdf.
    This is a single Numbers document, printed directly from Numbers (3.1). The font is identical in both lines. The box color is identical (black) and the width of the line is identical (0.5 pt). It was printed on an HP Color LaserJet CP2025.
    The upper text is jagged. It may look fine on your screen, but it's not.
    This is very obvious if you look at the larger image that is linked to the image above. (Remember, a computer screen is only 72 dpi and this image is optimized for that. Printed text is much higher resolution. So, to get an accurate view on your screen of how jagged the text is when printed, you need to look at it magnified. Right-click on the image above to open the image in a new tab, and you should get the full size.)
    Also, the because the upper image is lower resolution (jaggies), the narrow line cannot print accurately. Thus, it appears blueish. When you look at the full-size image, you can see how jagged the line is and the mix of dots (red and blue, predominantly) that was output by the printer. In contrast, the lower text box is smooth and black.
    I don't know where the problem lies, but I have not experienced anything like this on any other program I currently use. It's a postscript printer, and I suspect that something's gone wrong in the postscript output associated with tables and the printer is printing the screen view, not the higher resolution printer data. But that's just a guess. And as far as I know, it's not something anyone other than Apple can fix.
    And, of course, since you can't see this problem on screen in the pdf, no matter how much you "zoom" in, you won't know if your files will print badly until you test it. Or, worse, your client does.
    Bummer.

  • How to specify fonts in text in SVG file?

    I've got an Edge Animate composition that includes a bunch of SVG files which specify (inside the svg files themselves) that a particular font should be used. So for instance, there's text in the SVG that's set to render in Arial. If I view that SVG by itself in the browser, the text is rendered in Arial. But when that SVG is part of an Edge composition, the text in that SVG reverts to some other default font.
    The same problem happens when I try to specify a custom web font inside the SVG. The web font shows up fine when viewing the SVG independently, but when it's part of an Edge composition, it reverts to a default (Some serif font: Times, I think.)
    Let me stress this is NOT about specifying the fonts in Edge itself (by adding the web font to the edge composition, and then styling text from within the Edge Animate interface): this is about text that has been specified in the SVG file in Illustrator. That font specification is ignored when the SVG is brought into Edge.
    This text in the SVG shows as Arial when I'm in the Edge Animate interface, but when I view the whole composition in the browser, that's when it reverts to a different font.
    Any ideas what's going on here?

    Thanks for the reply. Yes, I've given up on fonts embedded in SVGs for now. I tried using SVGs with all text converted to outlines. That solved the type problem. But it of course made all the SVGs very large. I'm now having a problem with the Edge composition not fully loading.
    It throws some javascript errors that indicate that al the libraries haven't loaded. Or, sometimes it just pulls up a blank page and nothing ever shows up, even when there are no javascript errors. The errors are mostly this:
    Uncaught ReferenceError: jQuery is not defined byod_edgeActions.js:191(anonymous function)byod_edgeActions.js:191
    Uncaught TypeError: Object #<Object> has no method 'okToLaunchComposition' byod_edgePreload.js:27
    edgeCallbackbyod_edgePreload.js:27
    (anonymous function)byod_edgePreload.js:15
    tbyod_edgePreload.js:11
    dbyod_edgePreload.js:10
    I.b.onreadystatechange.b.onloadbyod_edgePreload.js:10
    So I'm thinking the loader is trying to move on to execute code when it hasn't loaded what it needs. This was happening on Firefox and Chrome. So now I've converted some of the larger SVGs to PNGs, which brought their file size down considerably. This eliminated the error on Firefox, but I'm still getting it in Chrome. I think it's just taking too long to load all my animations. It's a pretty big composition: an infographic that's 548 px wide by 3100 px tall. It has 8 animations in it, each as a symbol. There are perhaps 80 individual graphic elements in total that are involved in the animations.
    Even when those graphic files are as small as I can make them, Chrome still errors out before displaying anything.
    If it just turns out that this is too big a composition to be done in Edge Animate, I'm in big trouble, as a client has already paid for this.
    I'm hoping I can find a way to slow down the loader and make it wait until everything is loaded before moving on. But it's tough, as the edgePreload.js file wasn't meant to be tampered with, and is minified. I don't mind having a preload image appear for a while with a "loading..." message. But if it never loads...
    Not sure how to proceed, really.

  • Some web fonts are not rendered

    When I visit some sites that use web fonts, the web fonts are not rendered. It does not render with the wrong font - the text is completely invisible.
    On other sites, web fonts work just fine, and I cannot understand why some web fonts work and some don't.
    Examples of non-working sites:
    http://blog.mailchimp.com/ (headers shown, article text missing)
    https://www.sbab.se/ (huge top header missing)
    http://onlinepizza.se/ (headers and button texts missing)
    Examples of working sites:
    http://www.google.com/fonts
    http://www.typetester.org/
    On the Network -> Fonts tab in the inspector, no downloads are shown on the broken sites. Is there a font cache that I can delete?
    I have tried uninstalling firefox, deleting all profiles and installing it again. Nothing changes.

    Works fine here on Linux.
    Right-click > "Inspect Element" > Font shows:
    *http://blog.mailchimp.com/ Copyright (C) H&FJ | typography.com (Whitney SSm B) & Copyright (C) H&FJ | typography.com (Whitney SSm A)
    *https://www.sbab.se/ SBABSansStencilBeta-Bold
    *http://onlinepizza.se/Stockholm/ MuseoSans-700
    Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
    *Do NOT click the Reset button on the Safe Mode start window.
    *https://support.mozilla.org/kb/Safe+Mode
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
    Reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.
    *Hold down the Shift key and left-click the Reload button
    *Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
    *Press "Command + Shift + R" (Mac)

  • Dynamic text rendering in Cp4

    I'm having an issue with an embedded AS2 SWF that spawns a MovieClip containing a dynamic text field populated with ActionScript. When I publish/preview the Captivate movie with externalized animations, the dynamic text renders fine. However, when I do NOT externalize animations, the dynamic text appears garbled.
    I'd go ahead and externalize animations in this project, but there are other embedded SWFs in the project that work correctly only when they are not externalized.
    Anyone have experience with this or a similar issue?

    I just had a similar problem and fixed it by embedding the font into the Flash SWF and also embedding uppercase and lower case characters.
    Not sure why this was needed since I never had to do that with Captivate 3, but that was the only thing that corrected the problem.
    /Michael
    Click here to visit the www.captivate4.com blog

  • {text-rendering : optimizeLegibility} turns off google webfont in DW CS6 live preview (suddenly)

    I'm currently working on two websites for the UN, based on Wordpress, child themes based on twentytwelve and twentythirteen.
    I started to work a certain time ago on the child theme for 2012 which uses "Open Sans" fonts.
    I don't remember having any problem with this site: everything was working ok, I made a few changes but nothing important.
    I turned to the nd website based on 2013-theme, it works perfectly and DW CS6 is a real time saver for creating a child-theme, nonetheless...
    This morning I turned back to the 2012-based wordpress site: every text was simply not displayed anymore... only in live preview in DW...
    Even with the parent theme, the text was siply not displayed (so don't suggest my css code is bugged or what...)
    After a while, I figured out it was not really a problem regarding the font itself, but with the CSS property "text-rendering" with value set "optimizeLegibility".
    Commenting out this declaration solved the problem. Nonetheless...
    1 month ago there was no problem. Then suddenly...
    Is there a problem with the live preview mode and this CSS property? (indeed there is a problem)
    Can we have a fix for this? I mean, an update for DW CS6  (not for DW CC) ?
    TIA

    Hello Nancy!
    Normally, according to https://developer.mozilla.org/en-US/docs/Web/CSS/text-rendering Gecko could take it in charge too, but seems to override this setting (a thing I can understand, Gecko is using a fast rendering engine). So you're right: at this time, it can impact only webkit/chromium engines. Which, as far as I know is the underlying engine(s) behind "Live Preview". And it does impact readibility in DW CC (it improves it).
    Personnally I'ls better stick to the real CSS properties for kerning, alternative uppercases and ligatures, BUT the wordpress team seemed to think it was a good idea to use it (along with many other strange ideas such as using rem unit for the layout).
    The real thing here is: some weeks ago, when I started to tune the 2012-based theme I use for this site, I'm pretty sure I was able to read the text in Live Preview in DW CS6. I wouldn't have chosen to use this theme with such an annoyance, else. So basically, it's really strange that suddenly this property has such an impact on the "live preview" mode of DW CS6. What I would really appreciate here is a small update/bugfix to DW CS6: I don't need this property to be taken in charge in DW CS6 as it is done in DW CC, I'ld just want this property not to impact the live preview.
    Last : I mentionned an update of DWCC being possibly a culprit for this. How relevant could be this statement ? Are "live preview" modes shared by DW CC and DW CS6 ? (Even if, of course, this "bug" is not happening with DWCC).
    PS: Thanks a lot Nancy to pay attention to my posts as I often yell a lot here.

Maybe you are looking for