Font Problems with 10.0.2

Ask a Question related to Macromedia Freehand, Design and Development.

  1. #1

    Default Font Problems with 10.0.2

    Since upgrading from FreeHand 11.0.1 to 11.0.2, our trademarks "?" and "?" are
    printing as a
    dingbat and quotation mark. This only happens when using the Mac OS 10.3.2
    system's Helvetica font.
    These printed fine prior to the upgrade. We have two machines with the same
    problem.

    lewid Guest

  2. Similar Questions and Discussions

    1. Font problems when converting into PDF
      Subject: Font problems when converting into PDF Bonjour, I am working in In-Design CS2 - OSX. I am working in French language which includes...
    2. Font problems with .pdf's
      Laurence: I only way I know of to edit text in Acrobat and keep the whole paragraph editable is with a third party plug-in like Pitstop from...
    3. Font Problems Font Problems Font Problems
      Hello, Doesn't illustrator open PDF's with embedded fonts as editable objects? I thought so but now have a PDF that opens fine in Acrobat...
    4. font aspect problems
      I have real trouble finding a font that looks good in flash with a 10 or 12 size.... Something looking like Arial would be very nice. please have a...
    5. Crossplatform font problems with Dir 8.5
      I am experiencing problems with font tracking on certain fonts that were embedded in MacOS and then ported to Windows where a projector is created....
  3. #2

    Default Re: Font Problems with 10.0.2

    My office has been having severe problems with fonts in both 10 and 11.
    Our current workaround is to copy the text and paste it into MS Word or Text
    Editor (to strip out any text formatting done in FH) then copy it out of that
    and paste it back into FH.
    I haven't seen any trouble with ?s or ?s yet though, just odd kerning and
    leading problems.

    Is anyone at MM looking into these?

    BAD

    arrowd Guest

  4. #3

    Default Re: Font Problems with 10.0.2

    I am also experiencing symbol loss of the font MICR. This is a Postscript Type
    1 Font and my workaround is to open the text line in IllustratorCS, convert to
    paths and then bring it into Freehand.

    David

    davecc Guest

  5. #4

    Default Re: Font Problems with 10.0.2

    We've got the same problem in our office. I'm glad to hear we're not alone.
    Sounds like you've narrowed the problem down to the same cause we have. I went
    as far as to delete the "dfont" Helvetica in the system fonts and replaced it
    with an older postscript version managed through Suitcase X1. Not sure how this
    will work over time, but so far, so good. I let you know if we come up with
    anything else.

    ArtMonkey2 Guest

  6. #5

    Default Re: Font Problems with 10.0.2

    All:

    I just wanted to confirm that the Option + 2 (TM) and the Option + r (R) are
    the symbols that you are referring to.

    John J Nosal
    Product Team Liaison - FreeHand
    Macromedia Tech Support

    "lewid" <webforumsuser@macromedia.com> wrote in message
    news:c277fu$sb8$1@forums.macromedia.com...
    > Since upgrading from FreeHand 11.0.1 to 11.0.2, our trademarks "?" and "?"
    are
    > printing as a
    > dingbat and quotation mark. This only happens when using the Mac OS
    10.3.2
    > system's Helvetica font.
    > These printed fine prior to the upgrade. We have two machines with the
    same
    > problem.
    >

    John J Nosal Guest

  7. #6

    Default Re: Font Problems with 10.0.2

    John,

    Yes it's the option 2 and option R keystrokes. Everything looks fine on the
    screen, it's after the document is printed that these symbols show up (the ?
    looks like a " and the ? looks like a ladybug). Converting the text to paths
    solves the problem also quiting FreeHand, relauching and reprinting has been
    successful. My earlier attempt to remove the Helvetica system font didn't work.
    I've been working from templates set up in FreeHand 11.0.1. I'm going to try
    setting up a template from scratch in 11.0.2 and see if the problem persists.
    Still doesn't help with older documents though

    ArtMonkey2 Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139