Language of smartforms

Hello,
i have created two smartforms to print activities from CRM. If the activity has the Object Type BUS2000125 smartform 1 is used and if the activity has the Object Type BUS2000126 smartform 2 is used.
When I print the smartform 1 the smartform is printed in the language according to the language which is saved at the customer. The smartform 2 is printed in the language which I have selected in my personal portal settings.
I can´t find the difference between these both smartforms.
Can someone explain me in which cases which language is used and where are these settings when I want to change them?
Thanks!
Regards
Philipp

Hi,
Thanks a lot for the reply!
Well, I tried your steps, but, in the Target language, there is no Hindi. There are around 41 languages, which are eventually found in T002.
But, no HI.
Now, if we are able to install the Hindi language, I guess we can get the HI option in the Target language. Can you tel me how to install Hindi Language?
Thanks again....
PS: Meanwhile, in the Object Name section, if we give the name of the Smartforms, one error is displaying: Object not found. May be, we need to create a Text Module in place of Smartforms?

Similar Messages

How to change the language in smartform?

hi
how to change the language in smartform?

Hi,
U can't change the language in the smartform, the main language of the smartform is the language used to create it (so the language used for SAP log on.
But u can translate it (by trx SE63) and if u need to print in a new language u have to indicate it when the smartform is called.
U can transfer the language to be used for the print in the parameter CONTROL_PARAMETERS, like structure SSFCTRLOP, here u can indicate the language in the field LANGU.
see this..
Use transaction SE63, after activate your smartform, to translate.
In the First Page of your Smart Forms click on Global Settings under that click Form Attributes
now in the Right side screen Go to Subscreen Language Attributes.
select the Radiobutton Translate To all Languages
from the Translate subscreen out of three radio buttons.
rewaards if useful
regards,
nazeer

Problem in Translating the language in SMARTFORMS to English to Chinese

Hi ALL,
I have requirement to Change / Translate the language in SMARTFORMS to English to Chinese.
kindly tell the procedure to do that.
In SE63 , i tried to translate it. but it is throwing an error " INCORRECT CODEPAGE".
What does that mean?
How to handle this ?
Waiting for your replies.
Thanks .
Suki.R

Hi,
first Check whether codepage for Chinese language is installed or not?
Then follow below steps carefully
Step1 :
T/Code > Smartform>Global Settings -->genreal attributes Tab > Set flag (Radio Button)transaltionTo all languages/ Restricted languages
Please set this flag.
STEP2:
Translation:
Use T/code SE63>Translation(Menubar)>R3 enterprise> Other Long Texts>select " SSF"-->Enter Smartform name and from language and destination language.
STEP3:
Transporting translations :
Please execute the following program for transporting translations : RS_LXE_RECORD_TORDER
Target language = * or Target transalation lang.
Object type = SSF
Then Press Create Transport Request button. Create Request.
Then include all your translations to that request.
I hope this will solve ur problem.
Regards,
Anirban

Text should appear both in chinese and english language in smartform-Urgen

Hi All,
In my requirement in smart form, the standard text and values to be printed should appear both in english and chinese language.
When my login language is EN(English), I cannot able to see the chinese text , but only the english text.
If login in Chinese language, I can able to see the both the Chinese and English text in print preview, even then in printout the chinese text is missing.
Please let me know what will be the problem.
What printer i can use to get both chinese and english text.
Thanks in advance
Saravana

Hi
See the attached 2 OSS notes for your problem
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
reward if useful
regards,
ANJI

Text Modules translation to logon language in Smartforms

I have created a text module and included it in my smartform. Now what i want is to translate the form as well as the text module in the Logon language.
In the general attributes for the smartform i have already selected Translate-> To all languages.
Please help. Thanks in advance

Hi.
You can easily translate the text module using transaction SE63.
Just select Translation->ABAP Objects->Transport Objects
and fill it like for a smartform
R3TR SSFO <Name of text module>
Choose the language and here you go.
Regards,
Timo.

Change language in smartform layout

HI all,
I want to change the language of text in smartform.
4 it i go to SE-63 and Translation->Long texts-->smartforms.
But the problem is that in target language thre is no hindi language.
and also none of these available languages is changable.
points r assured.

hi sanket,
u want to print someting in hidi on your report,
there r two conditions 1 is your data (that is u r fetching from table) is in english and the second is the data is written (according to the character sequence) in hindi,
if u'r data is in hindi just create a smart style with hindi font and apply this on the text u want to print in hindi....
and if u want to change the whole language (hindi) then u have to crate a english to hindi converter.....that is used internally when u change the langage.
thanx
reward if helpfull

Multi-language in smartforms

Hi Experts
I have an requirement in smartforms in which I have to use more than a Language. ie., My logon language is EN and I want to Display a smartform with ENGLISH and THAI, without changing the logon language. If anyone has done / got a solution please do reply.

Thanks Folks,
I see your logic, thanks.
What I did after my posting is something like this:-
Translated my text elements to different language Chinese in SE63( I am passing Text elements to Smart form FM from print program). If my Multi-langu flag is on, then I read the non Latin text elements by setting SET LANGUAGE lg.
After reading my text once again set the language back to EN to read remaining text SET LANGUAGE as EN. pass the text elements (lets say TXT-Chinese) and TEXT-english to the Smart form FM.
Important thing is to set the output language parameter in control options of Smart form = "Chinese" = '1'. Call the SF and output you will see both English and Chinese data.
The english text is printed if there is no Chinese translated values.
If I want to print "Product" I will set Txt-101 = Product and I also want to print chinees translated stuff "XXXXXX" so I translate it in SE63.
In my print program I read the same text element 2 times one by seting language as EN and other time by setting lang as Chinees.
Store these text elements read data in 2 variables and pass it to Smart form, also set the smart form language as Chinees in the control structure and pass to FM. It will print both.
I know this is not perfect solution but it works for Chinese. Now the new issue I am facing is it does not work for Thai. I mean it works but the whole smartform output goes beyond the page limits and also the formatting is gone. it doesn't look close to the expected page.
Any suggestions ??

Change display language of smartform from within the smartform itself

Hi!
The smartform is invoked to display from the standard with some language, which we want to change.
We can't change calling code (because it's standard).
Is it possible to change the displaying language of a smartform from within the smartform. Say, "Initialization" section?

Hi Concern,
We can change language at run time. With following way.
1.    Define a variable and allocate language u want to langu fields.
DATA lV_CT_PARA TYPE SSFCTRLOP.
Here LV_lang contain the language u want to assign.
LV_CT_PARA-LANGU = LV_LANG.
2. Pass it to smart form.
CALL FUNCTION FM_NAME
    EXPORTING
ARCHIVE_INDEX              =
ARCHIVE_INDEX_TAB          =
ARCHIVE_PARAMETERS         =
   CONTROL_PARAMETERS         = LV_CT_PARA
MAIL_APPL_OBJ              =
MAIL_RECIPIENT             =
MAIL_SENDER                =
OUTPUT_OPTIONS             =
USER_SETTINGS              = 'X'
Itu2019s working for me.
Regards
Swati.
Edited by: Swati Namdev on Apr 28, 2010 7:06 PM

Language in smartform

hello guyz,
i wanna develop a smartform in norwegian ..how can i do it..
plz advise..
regds

DEVELOP U R SMARTFORM IN ENGLISH.....AFTER DEVELOPMENT ...ACTIVATE THE SMARTFORM......
IN FORM ATTRIBUTES TAB .........U WILL LANGUAGE ATTRIBUTES BELOW...[TRANSLATE]..
SELECT THE RADIOBUTTON TO TO SELECTED LANGUAGE ...GIVE THE LANGUAGE U WANT ....SO IT WILL TRANSLATE IN TO RELAVENT LANGUAGE ......
FROM THE LOG ON PAD ...LOG IN TO U R RELAVENT LANGUAGE...
REWARD POINTS IF HELPFUL...

Language translation - Smartform

Dear readers,
Please help me out in translating a smartform from language FR (French) to EN.
I have a smartform which was initially written in FR (french) and now it needs to be translated to EN.
Please let me a full procedure to translate a smartform, including the Tcodes and the step-by-step procedure for the same.
Thanks in advance.
Regards,
Pawan.

Hi All,
I do have an issue while converting a SMARFORM using se63.
I was trying to convert my EN Smart form to FR (French) .
I followed the below mentioned steps ;
_Logged in EN (English)
-->>_Gone to se63
-->gone to translation->abap obj->other long text->select ssf sap smartform
-->gave the SMART FORM name
-->given translation are :999999 (abap system)
--> Source language (English) & Targe Language (French)
--> clicked on EDIT
when i follow these and click on EDIT i am getting this ERROR " Form or text yfipayment does not exis_t" (Message no. SMARTFORMS200). but actually the smarform really exists but its showing error as does not exist.
Then,
i *tried loggin in using FR (French)* and followed the same procedure and got
a warning saying "Objet non trouvé" (N° message SAPMTRAN010)
can anyone help me on this issue..
Regards,
Saravanan
Edited by: Saravanan Easwaran on Mar 31, 2009 5:53 PM
Edited by: Saravanan Easwaran on Mar 31, 2009 6:06 PM
Edited by: Saravanan Easwaran on Mar 31, 2009 6:09 PM

Dual Languages in SMARTFORM

Hi Gurus,
I am working on a smart form related to SD. My requirement is - according to the sold to party country on the form the language of the smartform needs to be changed. Eg. If the sold to country is Bazil, the form needs to be printed or output in Spanish..if its US the form needs to be printed in english. I tried to pass the language in the FM calling the form but it doesnt work. I have translated the from to Spanish using the utilities on form attributes. Can anyone please help.
Thanks,
Dante

Hi all,
Thank you for the responses. I tried the solutions but was not able to get it. Here is what I did.
I translated the Smart from into Spanish on the general attributes tab and passed the language key as 'S' in the control parameters when calling the FM in my print program. I passed the language key in debugging mode as 'S'. It still prints the form window header texts in English.
Do I have to manually maintain the Header texts on the windows in Spanish...if yes then what is the use of translating the form.
I was thinking that you maintain the headers in English and when I select the translate option it automatically translates into the languages.
I also tried to translate using SE63 but I am not familiar with the TCODE and its confusing..It displays all window names and header texts and when I double click on them it says no proposal found.
One more thing - I dont want the layout or format changed...all I need is when the country key of sold to is Brazil, the form (Header texts on the Form) needs to be printed in Spanish other wise in English.
Anyone been in the same situation...any valuable suggestions will be rewarded.
Thanks
Dante.

Displaying smartform output in logon language.

Hi All,
I have a requirement in which I create a smart form in English language. If i logon in a different language, The smartform o/p or layout should be displayed in that logon language.
I have checked se63 but not able to figure out based on logon language
Thanks in advance,
Gopinath

Firstly, you need to design the smartform in english and make sure the form is avialable in all languages.... and do the necessary translations using SE63 transaction code. ...
transalation steps:
1) SE63 <- tcode
2) translation> abap objects> other long texts
3) Pop-up, double click on forms and styles, and double click on SAP smartforms and do the translations to respective target language from source language.
coming to your second question.
Do necessary changes to the control parameter of the smartform to
cs_control_param-langu = SY-LANGU.
make sure, this changes are done in print program.
If parameter cs_control_param-langu = nast-spras then it takes the language form the message type, which does not suits your requirement.
I hope above information will help you to close the thread.
Regards,
SaiRam

Smartform language translation

Hi all,
I am working with a Purchase Order smartform. My requirement is depending on the Vendor language the Smartform should be printed in that particular language. For example if the Vendor language is FI, the smartform should be printed in Finnish language. In the smartform I have several Hardcoded Lables and texts in English language. How can I go for the translation of the smartform.
Waiting for replies. Thanks

Hi,
Now if the language of the Vendor to which this Purchase Order is to issued is Finnish
at this time ,did you get language into any variable ?
if yes , as Ravi suggested , change the standard text language with variable like below
or capture the language into a variable and include it in standard text
Example:
/: INCLUDE z_txt OBJECT TEXT ID txt LANGUAGE &Variable&
Name: z_text
Object: Text
Text id: Txt (Text id from SO10)
Language: variable
In the smartform I got the language into a variable and according to what you have explained I need to go with standard texts in SO10 and use the required language standard text in the form depending on the langauge in the variable. Please correct me if I understood something wrong. - yes you are correct
And again my question is cant I use SE63 translated Finnish form instead of the standard texts
No , use standard texts only .Translation will be used in case of different language logins,but standard text has to be created in different languages
Regards
Appana
Message was edited by: L Appana

Smartform output showing another language rather than english

Hi Experts,
in my system if any of the smartform/script output want to see it showing another language.it's not showing in english language.same smartform in my friend's system it is showing english only.
Please suggest me the solution.
Thanks in advance,
Venkat.

Hi
See the attached 2 OSS notes for your problem
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
Reward points
Regards

Arabic language Smartform given Wrong Output format.

Hi,
I have developed Arabic Language smartform and tested in Print Privew mode working fine .
Problem with smartform Converted into PDF format and downloded to PC given wrong format.
Pl let me know any changes required.

Sorry I do not have answer to your question. But can you share with me how you managed to display Arabic language in Smartform?

Language of smartforms

Similar Messages

Maybe you are looking for