A
Al Meadows
Have a weird one. The application works fine on some printers, doesn't on
others. The problem is that I have a one page report which uses several
fonts and fonts of varying size. The only one I am having trouble with is
the OCR font (see code below). On some machines, when they print to their
local printer. it comes out looking like Arial or something similar. These
are a combination of local attached printers (mostly) and some network ones.
For example. one model of HP works, another doesn't.
I can't duplicate it locally.
The print routines are performed with VS2005 using C#. The specific line
where the problem occurs is as follows:
private void printLine(PrintPageEventArgs e, Font printFont, Brush brush,
float left, float top, string text, bool adjustFrom)
{
......
e.Graphics.DrawString(text, printFont, brush, left, top,
StringFormat.GenericTypographic);
......
}
Where all the variables are supplied. All printing, regardless of font,
size, location, or text being printed passes through this one single
statement. The only line that appears to have a problem is when the
variable printFont is as follows:
Font printFontOCR = StatInfo.createFont("OCR A Extended", 12);
where StatInfo.createFont is as follows:
public static Font createFont(string fontName, Int32 size)
{
Font printFont = new Font("Arial", 10);
try
{
printFont = new Font(fontName, size, style);
}
catch (Exception e)
{
MessageBox.Show("A font substition was necessary. Please
ensure you have the latest fonts installed. The Bad Font is:" + fontName);
ErrorTracker et = new ErrorTracker();
et.ExtraInfo = "createFont:" + fontName + " - " +
printFont.ToString();
et.postManagedError(e.Message, "A font substition was
necessary. From " + fontName);
printFont = new Font("Arial", size, style);
}
return printFont;
}
As you can see... I included this Font Instantiation procedure in order to
handle a situation where a desired font cannot be created within the
application. Note that when we have the problem, we are NOT triggering an
exception.
Additionally...
I added these lines of code around the DrawString line.
Application.DoEvents();
if (printFontOCR.Equals(printFont))
{
text = "OCR Font: " + text;
}
e.Graphics.DrawString(text, printFont, brush, left, top,
StringFormat.GenericTypographic);
Application.DoEvents();
in order to perhaps catch timing problems with the DoEvents method and also
having it check the value of the variable printFont to insure that it was
EQUAL to what I defined as printFontOCR. In all cases, both good printers
and problem printers, it correct equates printFont to printFontOCR.
This program is a replacement of an older VB6 program that creates the same
report however in the case of the VB6 app, we are using the printer object
that is part of VB. When these desktops with attached printers who are
having problems now print form the older VB6 app... it works PERFECT.
In addition, creation of a word document that includes a number of font
samples that also include the problematic font "OCR A Extended" also works
perfectly when printed.
As a final test to see what might be happening, I added a PrintPreviewDialog
to the project in order to get a preview of what the printed result should
look like. What was seen is that even in the PrintPreviewDialog display...
the OCR Font is 'wrong'.
One final, less importantr question relating to the PrintPreviewDialog .
When I use this, it is displaying correctly on the screen however the
document is ALSO being printed regardless which sort of makes using the
print preview kind of worthless. Any ideas why this is happening?
others. The problem is that I have a one page report which uses several
fonts and fonts of varying size. The only one I am having trouble with is
the OCR font (see code below). On some machines, when they print to their
local printer. it comes out looking like Arial or something similar. These
are a combination of local attached printers (mostly) and some network ones.
For example. one model of HP works, another doesn't.
I can't duplicate it locally.
The print routines are performed with VS2005 using C#. The specific line
where the problem occurs is as follows:
private void printLine(PrintPageEventArgs e, Font printFont, Brush brush,
float left, float top, string text, bool adjustFrom)
{
......
e.Graphics.DrawString(text, printFont, brush, left, top,
StringFormat.GenericTypographic);
......
}
Where all the variables are supplied. All printing, regardless of font,
size, location, or text being printed passes through this one single
statement. The only line that appears to have a problem is when the
variable printFont is as follows:
Font printFontOCR = StatInfo.createFont("OCR A Extended", 12);
where StatInfo.createFont is as follows:
public static Font createFont(string fontName, Int32 size)
{
Font printFont = new Font("Arial", 10);
try
{
printFont = new Font(fontName, size, style);
}
catch (Exception e)
{
MessageBox.Show("A font substition was necessary. Please
ensure you have the latest fonts installed. The Bad Font is:" + fontName);
ErrorTracker et = new ErrorTracker();
et.ExtraInfo = "createFont:" + fontName + " - " +
printFont.ToString();
et.postManagedError(e.Message, "A font substition was
necessary. From " + fontName);
printFont = new Font("Arial", size, style);
}
return printFont;
}
As you can see... I included this Font Instantiation procedure in order to
handle a situation where a desired font cannot be created within the
application. Note that when we have the problem, we are NOT triggering an
exception.
Additionally...
I added these lines of code around the DrawString line.
Application.DoEvents();
if (printFontOCR.Equals(printFont))
{
text = "OCR Font: " + text;
}
e.Graphics.DrawString(text, printFont, brush, left, top,
StringFormat.GenericTypographic);
Application.DoEvents();
in order to perhaps catch timing problems with the DoEvents method and also
having it check the value of the variable printFont to insure that it was
EQUAL to what I defined as printFontOCR. In all cases, both good printers
and problem printers, it correct equates printFont to printFontOCR.
This program is a replacement of an older VB6 program that creates the same
report however in the case of the VB6 app, we are using the printer object
that is part of VB. When these desktops with attached printers who are
having problems now print form the older VB6 app... it works PERFECT.
In addition, creation of a word document that includes a number of font
samples that also include the problematic font "OCR A Extended" also works
perfectly when printed.
As a final test to see what might be happening, I added a PrintPreviewDialog
to the project in order to get a preview of what the printed result should
look like. What was seen is that even in the PrintPreviewDialog display...
the OCR Font is 'wrong'.
One final, less importantr question relating to the PrintPreviewDialog .
When I use this, it is displaying correctly on the screen however the
document is ALSO being printed regardless which sort of makes using the
print preview kind of worthless. Any ideas why this is happening?