Printing Font Problem

Dear Team,
Whne I am giving Printing . Its giving BIG Font Printing.but Two days back it was working fine.Whats the Problem? and How I check ? and where?
Thanks
manu

Hi manu,
Its giving BIG Font Printing
1.check Windows driver for the printer is correct
2. you can select check fonts with SE75 ...also check this
note: 323460
How I check ? and where?
you can check with SPAD & SP02 t-codes
regards,
majamil

Similar Messages

System.printing font problem with numbers

I hope I'm putting this question in the correct forum as the issue covers a lot of ground.
I have a C#.net 4 web service on an IIS 7.5 box (call it box 1) that creates XPS documents and stores them in an SQL database.
I have a second C# .net 4.5 (tried .net 4 too and it makes no difference)web service on a separate box (box 2) that pulls documents out the database and sends them to print server queues on separate boxes, say this is box 3, using System.Printing which
is pretty bog standard code except for the XML tray designation code.
This works and the documents are rendered correctly except...
If the font installed on box 1 (IIS 7.5 on server 2008 R2) that is used to create the documents is also installed on box 3 (Times New Roman for example on the print server which is also server 2008 R2) then the documents text comes out
in Times New Roman as you would expect, but any numbers within that text come out in some unknown bold san serif font (e.g abcde
12345). If I put a text character directly in front of a number it renders correctly.(e.g abcde x12345) If the font isn't installed on box 3 then it comes out correctly, numbers and all. If I print the documents from XPS viewer
then they print correctly. The font versions makes no difference. I've tried changing the printer settings (print directly, advanced feature off, client rendering etc) and this makes no difference. The documents are properly formatted right down to each
paragraph now (trying to get rid of this problem) and still it persists.
This issue only appears if both boxes have the same font and you are printing from code.
I've got around the problem by using an equivalent Linux TTF that'll never appear on both servers, but I'd love to know where this problem is. Any takers on answering this?

Hi Ghost...
If you're talking about the Linux TTF, it works just fine, unfortunately it's not an exact match, so in order to get Times New Roman to work as advertised I might have to put some rather "dubious" code in, i.e. hunt down any text that "starts with"
number or find space + 0-9 and then stick an "i" in front in white..that sort of "dubious" thing.
The Time New Roman problem (and other fonts that are on both the IIS 7.5 box where the documents are created and the print servers where they are spooled) is quite baffling.
These are examples of the issue.
2 people went to market...the text comes out in Times, the number comes out in some bold san serif.
I went to the market on 12/12/2012 to see some pigs...shows the same problem
I went .2 the market on .12/12/2012......shows the same problem
I went t2 the market on i12/12/2012...all renders as Times.
In a nutshell, if the char preceeding the number is a-z the numbers are rendered correctly, otherwise they come out as bold san serif.
If I use, say for example Garamond (which isn't on the print server) then the whole everything renders correctly in Garamond. Same thing with all other fonts I tried. if both are on both servers then you get the problem. We have a mix of printers from
various manufacturers hanging off the print servers and the same thing happens on all of them so it's not a printer driver problem.
Everything renders correctly from a print out from the XPS viewer.
The exact architecture is that browser Ajax requests are fired at the doc builder service on an IIS box which builds the documents, puts them in an SQL database as byte arrays and returns success. Depending on the user's location and printer
spec, a new Ajax request is then sent to another IIS box (which is either local or remote to a print server) to print out the documents on location specific printers. The reason for doing it this way was to avoid Kerberos issues that would occur in a double
hop to a remote print server. Note: this is not my domain and I have no control over maintenance, but a Kerberos failure would result in badness, so it's been avoided. Therefore jobs that don't need an exact user, use a domain app pool account and jobs that
do require a specific user go to a service on the print server. Either way the same issue arises.
I though the problem was with my code, but the MS example XPS documents show the same issue.
XPS creation is by GemBox.Document from docx templates and Gembox saw the same issue on their servers when I brought this problem up with them. They put a fix in that partially resolved the matter from their standpoint, but it didn't make any difference
in my architecture.
HTH

Printing/Font problem Indesign CS4

I am hoping someone can help me figure out an issue I'm having with Adobe Indesign CS4 and printing.
A few weeks ago I upgraded from CS3 to CS4. I had just sent a CS3 document to my printer and it looks great. I decided to update all the files I was working to CS4 (Indesign) since I knew I'd be working on them within the next few months. I upgraded and printed out one of the files to my xerox 6200 phaser and now parts of the document (a 4 page document) prints out of my printer like it's missing the font. Not all of the fonts change to a strange courier slanted italic font, just some of them. I've tried just about everything and am driving myself crazy trying to get it fixed. I can't attach a sample because it only does it when printing. I have checked for errors in preflight and I have none. The fonts I'm using are cronos mm and cronos mm italics. My operating system is snow leopard 10.4.11.
These are what I've tried:
1. I printed from the indesign 3 file before conversion and it prints fine.
2. Made a pdf of the indesign 4 file and no errors and looks great on screen and prints from the printer and looks great.
3. I've printed out individual pages, one at a time, and when printing individual pages no weird fonts, but when I send the job to printing the whole document is when I get the weird fonts.
4. Tried to save it as an .indx file and print from it and it still has the same issue.
5. Exported the text and saved it as plain text from text edit and placed it in a fresh file and reapplied the fonts and it still prints weird. I only did 1 and a half pages of it to see if just bringing in clean text and redoing it but it didn't work.
6. I'm using Font Agent Pro 3.3.2 and I deleted the fonts from the system and reimported the fonts from a backup file. Verified the fonts and found that some of the cronos fonts (expert) couldn't be verified and deleted them, but those weren't the ones that I was using.
7. Cleaned the font cache using Tweak Freak.
8. Deleted the adobe plist preference thing
9. Deleted my printer, downloaded a new driver and font management thing for my printer and reinstalled it
10. Restarted numerous times and reopened the file and printed and it's still printing weird.
11. Done a save as several times and gotten the same results.
12. I've opened other files that use the same fonts as this file and they've printed fine after upgrading to cs 4.
13. Printed from another person's computer who has everything that I have on my system and his system does the same thing.
14. Spent countless hours looking online and can't find a solution. I'm afraid if I do anymore I will screw up my computer or indesign or fonts so I thought I'd email this list to see if there's a solution. Any help would be appreciated.
Rosie

Peter,
Thanks so much! It worked! I changed it to subset and it printed perfect. I had tried everything else in that box, such as binary instead of ascii, level 2 instead of 3, but never changed from complete to subset. I really appreciate your help! And I do still have some hair left. I didn't pull it all out
As a side though, it's weird that in CS 3 with the same settings - complete - it would print fine, but when upgrading it changed it. I also exported it as a pdf to make sure it looked good on screen and printed out great. Thanks again. I appreciate your help. You are brilliant!
Rosie

Font Problem: Zebra label print

Hi,
I'm designing label print with Zebra Z4MPlus, I can rotate the text in 90 degree, but the problem is the printed font is so ugly and letters are twisted together, I take the font 'HELVE', it should be all right, how can I solve it?!
Any suggestion will be appreicated!

I've try to find font HELVE in zebra web site to upload in Z4MPlus printer, but I couldn't find ? how can I?

How can I print a LabView report using the printer font (not a windows font)?

My printer is connected via a com interface. For speed reason I have to use the font of the printer. I use the report generation VIs to generate my report. With the VI "Set Report Font.vi" its possible to choose a font but I think only windows fonts are accepted.
Printing from "WordPad" using printer fonts is no problem, just select font "15 CPI" for example. But how does it work with LabView?

Have you already tried this in LabVIEW? What results did you receive when you tried it?
J.R. Allen

Font problem in Classic

I posted this over in the Classic forum...but it's rather dead over there and I fear it may not be seen for a while...so here's the problem...
I'm running Quark 4 in Classic and having trouble with fonts. Though the fonts are on my computer, and in the OS 9 fonts folder, they won't print correctly. If I use the same printer and print from Quark on my old iMac (running OS 9) the fonts print and look fine.
I read another thread in this forum that mentioned the fonts must be OS 9 fonts (and must not have been run through suitcase or a similar managing program???). So, on the off chance that my husband or I just took OS X fonts and copied into the OS 9 folder, I copied the OS 9 fonts from the iMac (I just grabbed everything in the Frutiger family, as it was one that I had an issue with) and then dumped them into the OS 9 fonts folder on my iBook. I restarted Classic mode in order to make the fonts available to the OS and then printed again. The font still prints all pixeled-looking.
Can anyone tell me what I'm doing wrong? Do I need to find the original font disc and install them from the disc?
Any help would be most appreciated!!!!!

Hi Diane,
Glad that the tip helped to "solve" the font problem!
Not sure why you are printing the file info at the bottom of the page. It does sound as if it is a print setting somewhere though. Hopefully someone has a clue for you.
Again, thanks for the "solved" star and if I can think of something else for you to try I'll post back. Let us know if you figure it out.
good luck,
littleshoulders
edit:
"In lieu of an answer...I tried changing the paper size to legal and it's not on the last copy I printed."
Ooops, I misread your reply, and see that by changing the paper size it corrected the issue.
Message was edited by: littleshoulders

Why ist the printed font size smaller then the choosen font size in pages

Hi,
sorry about my english it´s a lot of years agoo i used it.
since a cuple of months i choosed a mac mini to be used as my favorit pc-system. Now i am using pages to create letters and stuff like greeting cards, posters, flyers and so on.
In this i´ll find a problem between the choosen font sizes and the printed paper.
If i choose a font and size like arial 12, and start the print job of the lettert with my Printer (Samsung 3170 MFC or Samsung 315), the size of the printed font is very smaller than the in pages choosen font (seen on the screen.
If i use MS offce it is the right size on the screen as on the printet paper.
What do i wrong?
Greetings from Hamburg Germany

Maybe because your document isn't displayed at 100% but at 120% on your screen.
On my iMac, to get the same size on screen and on paper, the zoom factor must be 142% which can't be done thru the available interface.
Yvan KOENIG (VALLAURIS, France) dimanche 3 juillet 2011 12:43:09
iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8
Please : Search for questions similar to your own before submitting them to the community
To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

PDFMaker font problem

Can anyone offer any advice on how to debug a font problem?
I am using a (shareware) symbol font on my Windows XP system. It works great in FrameMaker, and comes out perfectly in Frame-generated PDF files.
Unfortunately, I also have to convert Excel spreadsheets to PDF, using the same font. When I generated those PDF files with PDFMaker, the font characters all show as little squares. I checked MS Word as well, and it has the same issue.
I've checked the font properties in the generated file using the TouchUp Text tool in Acrobat - the font is recognised and embedded. If I try to make changes, I get this error message:
"Some of the characters in the current font are not available, the missing characters will be replaced by place holder characters (maybe dots '.').
"A work around to this is to select another font which contains the characters in the TouchUp Properties dialog.
"Proceed with replacement?"
I'm using Office 2007 under Windows XP Professional. The font is shareware and unsupported. I'd bet my bottom dollar that the problem isn't in PDFMaker, but I don't know a whole lot about fonts, and I'm not sure how to debug this.
Can anyone offer any advice?

If you go to the general tab in the Adobe PDF printer properties, there is a button for printing preferences. Select that and go to the Adobe PDF Settings tab. There should be a check box for leaving the log file intact there. You can also simply print to the Adobe PDF printer with print to file selected. Then open the file in Distiller and watch the messages created (these steps are automated if you do not print to file).
You can also check the fonts in the PDF (use ctrl-D, font tab). If they are embedded, that information is stated in parentheses. If there is no statement of embedding, then it did not get done. That is not necessarily an error if the job settings are not set to embed the font.

Smartform-PDF-Printer fonts

Hi Folks,
Here we have designed a Invoice-smartform and converted it into PDF which is by default storing in c-drive as mentioned in the code.When we open the Pdf it is displaying it fine but when given a printout except the logo nothing is getting printed,I mean it is showing all junk characters.May I know what is the problem and how to rectify the same.
Points will be given.
K.Kiran.

Hi Kiran, see the OSS notes: 960341 and 776507.
I downloaded and copying here, Hope this will be helpful
OSSNote:960341
Symptom
In some device types (e.g HPLJ4, HPLJ5) you experience non-uniform character spacing in the PDF document after the PDF conversion of SAPscript or Smart Forms documents, using HELVE or TIMES fonts. You want to know the reason.
Other terms
CONVERT_OTF, SAPscript, Smart Forms
Reason and Prerequisites
The problem is not due to an error in the PDF converter but due to the fact, that the printer font, underlying the device type (e.g. Univers or CG Times in PCL-5 device types), is not available for the PDF converter and is either not available in Adobe Reader. The PDF converter has to try to simulate the layout of the printer font by means of a font which is predefined in Adobe Reader. This is done by assigning the letter widths of the printer font to the font used in Adobe Reader.
The PDF file contains a table with letter widths, used by Adobe Reader in the output of text, for each used printer font (except PostScript fonts).
Example:
%Charwidth values from HP4300 HELVE 060 normal
/Widths
[ 278 333 500 633 633 1000 758 333 333 333 633...
Adobe reader converts this width table, by modifying the space between each character, so that the specified letter width (= space between the current and the next letter) is kept.
This 'Simulation' of printer fonts results in the sometimes visible irregular spaces in PDF.
The PDF converter always uses the Helvetica Adobe PostScript font for the display of HELVE and the Times Roman Adobe PostScript font for the display of TIMES. However, for these Adobe PostScript fonts, Adobe Reader often uses a Windows TrueType font, which differs slightly from the original PostScript font.
Solution
Workaround: Use the POST2 PostScript device type or the PDF1 PDF device type for the PDF conversion of documents in the Latin-1 character set. They both use the Adobe PostScript fonts Helvetica or Times Roman for the HELVE/TIMES printer fonts.
Header Data
Release Status: Released for Customer
Released on: 30.06.2006 12:44:06
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s):            Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR                      ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000    0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000    0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE   120 00109XSF100SF101110000067E X
Header Data
Release Status: Released for Customer
Released on: 22.08.2005 09:57:20
Priority: Recommendations/additional info
Category: Customizing
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
BC-SRV-SSF Smart Forms
regards,
Anji

PDF Font Problems

I am exporting an Adobe InDesign file to a PDF. When I take the PDF file to computers other than my own to print, fonts get messed up and lost. How can I correct this problem?

Not sure about where to find this in InDesign but when converting a Word document to PDF you need to go into File > Options > Save > Embed fonts in the file.
I would imagine that InDesign has a similar setting.

OCR Font Problem

Post Author: jeromehou
CA Forum: .NET
I am working on a web application using asp.net 2.0. I have a report using crystal and exporting it into a pdf file. The problem I have is the OCR font. The OCR font can be displayed well while running the application on my local box. But when I put the web app in the production box, the OCR font is not displayed properly. My question is do I need to embedded the OCR font in the report? Thanks THanks

Hi Naresh,
we worked with OCR-B font on cheques with SAPscript (on 4.6c and on 6.0). The bank was not completely satisfied with the result but they finally accepted it (they told us that it was not exactly 12 point large although we set it to 12 point in SAP).
Have you checked the print preview in SAP? Can you see OCR-B there? Maybe your printer has problems with this font.
Please try the following: Set one paragraph to ARIAL or TIMES (for example) and one to OCR-B and print the cheque. Check if you can see a different font for both paragraphs. If no, please check again the settings for the used paragraph format.
Best regards,
Peter

Leopard and font problems

I have had my fonts default to courier when
printing, just like the others who have posted notices in recent
weeks. I wish I had never installed Leopard because I use FH
daily-- I don't understand Illustrator even though I have it. I
THINK in Freehand. I know I can change all my fonts to paths or
print form the PDF preview mode BUT I don't want to have to do
that. Anyway, I have another issue. I do a newsletter once a month
and the editor sends me the articles cut and pasted into eMails. I
have copied, cut and pasted the articles into FH beautifully up
until Leopard. Now I get all those crazy weird characters.
Apostrophes become "i"s, quotation marks become exclamation marks
and spaces get crosses in them. I am ready to scream! I don't want
to reinstall Panther but I will if I can't fix these issues.
Anybody got any answers? is calling Adobe Customer Support a waste
of time?

For the garbled font problem you might try removing font
cache files.
FontNuke will do the job. You can download the latest version
here.
http://www.macupdate.com/info.php/id/21536
Judy Arndt

"font" problems when converting InDesign file to negative

the printing service we use for our college newsletter, which is done in InDesign CS3, says he is having "font problems" when he turns the file into a negative (the master used for printing paper copies of the newsletter). I use only a standard font, "Times," in various sizes.
he did not have this problem with InDesign CS2, and he is as yet unable to explain exactly what the problems are but said there are 3 pieces of equipment involved that each contribute to the problem: old vs new operating systems (OS) in RIP unit and workstation to newest applications and older RIP unit. (I haven't a clue what any of this means...)
he has asked we create an "outline" of the InDesign file before sending it and believes doing that may help. however, when I create an outline of the document, all of the font turns bright red-- is this what is supposed to happen or am I doing something wrong?
can anyone help me figure out how to help the printer?
FA NEWS editor
(linda)

The .sitx file extension is a Stuffit executable, a way of compressing files so that they take less time to transfer. This has nothing to do with your problem.
What I'm recommending is that you Export PDF (File > Export > Adobe PDF). Choose the Press Quality preset and send the resulting PDF to your printer. Scott's suggestion will give you a PDF with outlined type, but before you go that route, try a Press Quality PDF, which will have live type and embedded fonts.
The best reason for sending PDF to your printer is to avoid font problems.
Ken

X11 printing font controls

I continue to have problems controlling my printer from some OS X applications (emacs and xemacs, to be specific). While I can print from emacs without apparent difficulty, xemacs is, at the moment, at lost cause. My latest bete noire for emacs is my inability to alter the default printing font, which appears to be a 14 point monospaced font. Since it is printing a page that is composed in 11 point monospaced font, there is no way for programs, their headers, or anything else to come out correctly. By contrast, in a program like vim, also running under X11, the display font is exactly the same as the printing font and so the text appears on the printed page exactly as it does on screen. While I understand this to be an emacs problem, I'm 100% convinced of this. As proof, if I lpr the file directly outside of emacs or vim, the file prints in 14 point monospace type. I have the default font for OS X applications set to be 11 point True-type font and I can control that directly from the Printer Setup or Page setup panel within any OS X application.
There HAS to be a default font setting buried deep in the bowels of the Unix configuration (.bashrc, .profiles printer.conf, somewhere) but I've been unable to locate the precise place to change this so that my X11 applications all print through lpr in a uniform 11 point font.
Any suggestions on where to start drilling for font oil?

Please contact Manhatten Assoc. for supporting their software.

How to uninstall Snow Leopard? major font problems in iWork, iLife

All iWork and iLife apps have shocking font problems... so much so that I need to uninstall Snow Leopard and wait for Apple to sort it out. Does anyone know the best way? And how is it possible that these problems are occurring with Apple's inhouse software? Other stuff seems to be working OK so far for the most part. For a bit more detail on my problems, including sample images:
http://bit.ly/309G0o

Snow lizard cost me $27.000.00 in unusable fonts. We installed snow lizards (what I'm calling it now) and lost 934 fonts. Say 40 were bad fonts and 896 were type 1 postscript. When I explained to the tech person how big this was to the print community, he had no clue. - I'm still waiting to hear back. I have a case number but now I read from another post they knew Snow Lizard would do this. At 30.00 per font that is almost $27,000 to replace what they thought wasn't important. But in the print world of design this is huge. Every layout and ad that needs an update - which take a few minutes is a whole rework. They have no clue what business a mac computer is in or they don't see us as important.
I did find if I load those fonts or the font missing into the InDesign font folder I can get the old ad to make it to pdf. But photoshop and illustrator, I'm screwed. And if I didn't outline the type in illustrator - it's gone. I asked the tech guy if I can go back, and undo this slimy lizard and he said probably not if we do backups. We do backups every hour - this is the print business. I feel forsaken. I've been with apple for so many years.

Printing Font Problem

Similar Messages

Maybe you are looking for