Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

font sapscript

Former Member
0 Likes
3,885

I have a new form for delivery processing.  in the window Main I have a line with a paragraph format (ZL) that uses font Courier 9.  When I process this output in DEV, everything is lined up as I would want.  I moved everything to TST and now the font is different and item data is not lined up properly.  I have the same sapscript, same program.  Originally I was using another form and it would not work, so I copied it into a new sapscript and a new output type - same result.  Any suggestions on where to look next?  I just am perplexed as to what I have missed?

Susan

9 REPLIES 9
Read only

Former Member
0 Likes
3,310

Are you using the same printer in TST as DEV? Is the font installed in TST?

Rob

Read only

0 Likes
3,310

same printer

Read only

0 Likes
3,310

And the font??

Rob

Read only

0 Likes
3,310

Courier is a font in SAP DEV and TST.  The only difference I see is in DEV I have a courier 020 where I do not have the 020 in TST.  The font in the paragraph format is courier 9.0, which does not show specifically in DEV or TST in SE73.

Read only

Former Member
0 Likes
3,310

I am still stuck on this.  I was using courier 9.0 at the paragraph format at line item of window main.  Works fine in DEV, but when moved to TST is another font in TST that is also is not lining up properly.  Had Basis update font family for Courier in TST.  Ran output again and the same issue.  now I just changed the paragraph format in DEV to Courier 10 and it prints fine in DEV.  Transport to TST and font changes and alignment is still off.  Using same printer in DEV and TST.  We need this form.  I have never run into this and am at a loss on what the issue is?

Read only

0 Likes
3,310

Hi,

Have you already tried the deleting SapScript text load trick - using program RSTXDELL (see also 1567036 - Font problems in SAPScript or Smartforms due to SAPScript buffer)?


cheers

Jānis


Read only

0 Likes
3,310

I tried this.  I am at home so cannot print here but did ask for a repeat output and then displayed it on the screen.  It does not seem to have changed anything.

Read only

0 Likes
3,310

Hi,

It is in no way guaranteed in SAP Spool system that what you see in preview will be output on paper and vice versa...

Just to be sure - when you say "Courrier" - is that SAP System Font (preinstalled font visible in SE73 under System Fonts) or is it installed additionally as "True Type" font?

What device type is used for output? What Host spool access method is used in the Output Device? My next suggestion would be to transport both the SAP Device type in question and the Output device from DEV to TST.

Just to narrow down possible causes, I would also suggest to create a tiny test form containing nothing but one variable/text formatted using system font COURIER, and compare raw spool contents (OTF) in both systems - whether or not they are identical.

I don't expect these two steps to change/reveal anything, but this kind of problems requires systematic approach...

If the OTFs are identical, SAP Script side of "solution" is more or less OK. If the problem persists with test form too, it's time to turn on the "test mode" on output device in SPAD:

and instruct Spool System to retain the temporary file that gets sent to printer:

This will make it so that you can access (download) this file in SP01 under finished Output Requests. Take away this in Spool Request:

and, after printing, go to output request display and get the file here:

Compare the files on both systems, it should reveal something, I hope... This is why it's important to create small test form, so one can still understand something in those files...

Just let me know if you have trouble with any of this stuff, I'll try to give better instructions... Don't forget to turn off the test mode on the Output device after done testing.

cheers

Janis

Message was edited by: Jānis B

Read only

0 Likes
3,310

Susan,

can you prepare a little test of the form/paragraph in your DEV and TST systems: use SO10, create a standard text using your form, use your paragraph format, and output a string of text in your desired font (COURIER 10 ?).

Now create a spool request (no IMMEDIATE PRINT!) from that SO10 text in both systems, use the same printer as for your real document.

Now go to SP01, and enable "OTF display", which shows you the internal format for SAPscript/Smart Forms spool requests. Start SP01, output the list of jobs, and now menu "Goto-Display requests-Settings". There, set display mode to "Raw", ENTER.

Now display the spool request you have created from SO10.  What you see now are the OTF commands in the spool request.

The first line should contain an OTF command similar to

//XSWINCF      0750 00000+00000+

Here, SWINCF is the device type of the printer that I used. For your test, this device type should be the same one in DEV and TST  ! It is the device type which determines which printer fonts are actually available.

Now search for lines that start with FC (font call) command. This shows you which actual printer font (i.e. font defined in SE73 under "printer fonts" for a given device type) was used for output. For example

FCCOURIER 120X 00144 %CFNT     410300144EXX

is the OTF command that tells the printer driver to switch to font COURIER 120 BOLD of devtype SWINCF.

Does that help in determining what is different between DEV and TST?

Regards.

  Alex