Standard Finishing
4Over

Announcement

Collapse
No announcement yet.

Screen Fonts issue

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Screen Fonts issue

    Hi All,
    Does anyone know a quick method to preflight files that only have screen fonts collected or detect missing printer fonts (FlightCheck isn't consistent doing this)? This is an annoying problem when designers aren't aware of what they are using.

    Thanks.

    Edited by: Tech on Oct 26, 2007 2:31 PM

  • #2
    Re: Screen Fonts issue

    Acrobat's Documents Properties Fonts tab will tell you if the fonts are embedded. Is that what you are asking about?

    Comment


    • #3
      Re: Screen Fonts issue

      Nope, I triple check our designer's layouts in various stages... what isn't so easy is we also received or work with much older files... pre-PDF day stuff. We are talking about a mix used of true type/post script and now OTF. It's just too easy to overlook something and not catch what is loading and what isn't in native files.

      Today for instance, a font called Meta loaded in FontXplorer and looks fine in Quark 6&7, it even flightcheck correctly. The strange part is in FontXplorer only screen font is loaded and with our vendor not being able to load this typeface, it's safe to assume 1) they didn't try hard enough to load the font; 2) the font they received is corrupted; 3) only screen font is ever used in this project but no one knew printer font is missing.

      BTW, anyone here tried TransType? Anyone use this to convert older true type or postscripts into OTF for printing?

      Comment


      • #4
        Re: Screen Fonts issue

        I'm confused...

        The concept of "screen font" vs. "printer font" hasn't existed in Mac OS
        since Mac OS X (and possibly a bit before in 9.x)...What you see is what
        you get - period! Doesn't matter if it's Type 1, TTF or OTF.

        Can you give us some more information about what the REAL problem is?

        Leonard

        Comment


        • #5
          Re: Screen Fonts issue

          I feel your pain! The thing is, that Meta crap font is very problematic. It in its self is the problem. It just doesn't work right. Add all the Meta fonts you can find in your font management software of your choice, then add those bastards in Font Book also, and re-start your Mac. That's what works for me. I HATE Meta. . . Meta, Meta Plus, Meta Plus Headache after headache!!!

          Comment


          • #6
            Re: Screen Fonts issue

            > {quote:title=leonardr wrote:} The concept of "screen font" vs. "printer font" hasn't existed in Mac OS since Mac OS X (and possibly a bit before in 9.x)...What you see is what you get - period! Doesn't matter if it's Type 1, TTF or OTF.

            Leonard{quote}



            I'm confused now as well...

            we, to this day, still get old fonts from clients that have a screen and printer version and if you don't have both halves, you can't use it (and these are Type 1 fonts, Truetype fonts and Open type fonts only have one part).

            Comment


            • #7
              Re: Screen Fonts issue

              It seems unless you experience this like Danny and I have, it's hard to believe old postscript type 1 fonts can cause such problem. Keep in mind, Meta is an old multiple master font (with multiple parts) and from what I read these fonts stinks when it comes to publishing.

              What I'm trying to say is, current font management programs will load these multiple font(s) and identify it as screen type only. It loads and prints fine from Quark/InDesign until it reached our vendors, who can't always load and print them.

              Comment


              • #8
                Re: Screen Fonts issue

                I agree, the Multi Master fonts will work on occasion, and not on others.
                I've had them load into Suitcase, but then you couldn't get them out. I had to toss the prefs and database to clear Suitcase out so I could load other fonts.

                Comment


                • #9
                  Re: Screen Fonts issue

                  > {quote:title=leonardr wrote:}{quote}
                  > I'm confused...
                  >
                  > The concept of "screen font" vs. "printer font" hasn't existed in Mac OS
                  > since Mac OS X (and possibly a bit before in 9.x)...What you see is what
                  > you get - period! Doesn't matter if it's Type 1, TTF or OTF.

                  Lotsa' Type 1 fonts still being employed. OSX hasn't changed the necessity for having screen and printer fonts for output of Type 1 fonts, has it?

                  rich

                  Comment


                  • #10
                    Re: Screen Fonts issue

                    Rich,

                    In a word - no (which you knew that). At least us prepress techs know that cause we have to deal with them daily.
                    Just cause OpenType may be what's being pushed today to be used, most times I still get Type 1 fonts.

                    Don

                    Comment


                    • #11
                      Re: Screen Fonts issue

                      Yes, and Mac OS X contains a NATIVE Type 1 font rendering engine.

                      AFAIK, it doesn't use the "bitmap/screen" fonts that Mac OS 9 used to -
                      it only deals with outline font data. As such, it won't even bother to
                      look at those bitmaps just sitting around wasting space on your disk.

                      Leonard

                      Comment


                      • #12
                        Re: Screen Fonts issue

                        Just to follow up on myself...

                        The following URL from Apple's website may help.

                        <http://docs.info.apple.com/article.html?artnum=25251>

                        Leonard

                        Comment


                        • #13
                          Re: Screen Fonts issue

                          > {quote:title=leonardr wrote:}{quote}
                          > Yes, and Mac OS X contains a NATIVE Type 1 font rendering engine.
                          >
                          > AFAIK, it doesn't use the "bitmap/screen" fonts that Mac OS 9 used to -
                          > it only deals with outline font data. As such, it won't even bother to
                          > look at those bitmaps just sitting around wasting space on your disk.
                          >
                          > Leonard


                          then why do we have problems when we don't have both parts and you try to .ps out?


                          quote from the Apple link about Type 1 fonts that Leonard posted:

                          PostScript Type 1 (with double-byte support). Adobe PostScript fonts launched the desktop publishing industry and are used today by publishers, corporations, and government agencies for high-quality output to laser printers, imagesetters, and platesetters. Each PostScript font requires two files, one for the screen and one for use by the printer's RIP (raster image processor). Mac OS X is the only operating system that provides native PostScript Type 1 font support.

                          So we do have two parts and Apple supports them?

                          and about MM fonts:

                          Multiple Master. This special type of PostScript font allows variation of one or more font parameters (such as weight) to create a large number of custom styles, also known as instances. Mac OS X can activate already created instances of Multiple Master fonts.
                          (this one I have trouble with cause they just don't work with the apps, not the OS, but the Apps, like Quark for one and Suitcase for another).

                          Comment


                          • #14
                            Re: Screen Fonts issue

                            I did more digging and I'm testing FontDoctor right now. This might be the solution for our workflow—scan > detect problem fonts at initial design stages should be the best method to prevent font issues downstream. If we can identify bad fonts early on, we can replace them early and wonder why printer are sending bad proofs to us.

                            Thanks everyone for replying.

                            Comment


                            • #15
                              Re: Screen Fonts issue

                              > {quote:title=Tech wrote:}{quote}
                              > I did more digging and I'm testing FontDoctor right now.



                              we use Font doctor and it works great...

                              it tosses all the type 1 fonts out that don't have both halves, and others fonts that are corrupt and un-repairable...


                              most of the time.


                              (I'm being facetious here, I have recently had more than my share of trouble with suitcase and I am currently researching font management alternatives.)

                              Comment

                              UltimateDuploSmartsoft (Presswise)Standard FinishingKBA4Over
                              UltimateDuploStandard FinishingKBAKBA GTIChili publish4Over

                              What's Going On

                              Collapse

                              There are currently 3990 users online. 90 members and 3900 guests.

                              Most users ever online was 6,151 at 11:36 AM on 11-17-2017.

                              Working...
                              X