Printing polish characters on form
I added some polish text in a standard textfield.
For example:
Ilość
Numer zamówienia zakupu
Podpis wystawiającego fakturę
This polish text is perfectly visible on Adobe Forms design view.
But during runtime, the polish characters are not visible anymore (instead an empty space is shown).
I tried with different fonts (Arial, Verdana) and different formats (Plain Text Only, Rich text), but nothing seems to work.
What could be the problem ?
Thanks
Hi Martin,
another thought to solve the issue is to translate the form to pl in your system. I got a similar issue some time ago.
I developed the form in DE and translated it just to English, because we wanted to set always English.
Problem was, that french characters didn't show up in a proper way in print-preview. We solved the issue by translating the form also in FR and IT.
It seemed, that the formlanguage passed just the native charactersets for this language.
Maybe you are having the same issue. Otherwise would be nice, if you can share your solution if there is another one here
~Florian
Similar Messages
-
Problem with printing Polish characters on paper printouts.
Scenario..1
Text Module TM being used in smartform. TM uses a style which has font ARIAL.
TM is translated into 2 languages English and Polish.
The English version contains Polish characters too, since a couple of Person names have to be printed.
When the form is printed in Polish language : The Polish characters are previewed and printed correctly
When the form is printed in English language : The Polish characters are previewed correctly but not printed correctly
Both the above use the same printer having support for Polish fonts.. so i am asssuming the printer is not the issue here.. i could be wrong.
Kindly advice.Hi!
In which way is the output transferred?
Something like:
a)
ESC 'times new roman'
My text
b) already converted into a picture with a specific resolution (e.g. of 300dpi)?
Case a) -> Your printer needs an installed font times new roman / it's using the first installed font or something in this way. Then you need to download a special (user-) font with polish characters. (That's a quite common way. Sometimes already then vendor installs an user font as preparation for some countries.)
Case b) -> No idea, when print preview is already OK, then output should be OK, too.
Regards,
Christian -
Printing Polish characters # output instead of "
Hi all,
Please can you assist.
I have been setting up mutliple printers for the business in Poland. The printers are all operating fine apart from the fact they output # instead of ".
All printers are using the recomended device type I2HP4, code page 1416.
All the information i could find suggests that the # symbol is used when the correct character is missing from the code page. I have however checked code page 1416 and the " symboll does exist with sequence U+0022.
In case its relevant the print method is U.
Any ideas where the problem may be?
Thanks
Grahamxmltype
(<Model_ID><![CDATA[' ||'U252'||C.SEGMENT1||']]></Model_ID>') -
Printing Polish from Unicode ECC system
Hi,
to print Polish characters as SAPscript, ABAP-list or SmartForms from a ECC 6.0 already converted in Unicode, is it right way cascading fonts, SAPWIN, SAPSprint, ecc. ?
Or... can I use "classic" HPLJ4000 device type with access method D?
My ECC system:
SAP_ABA 700 0014
SAP_BASIS 700 0014
PI_BASIS 2006_1_700 0004
ST-PI 2008_1_700 0001
SAP_BW 700 0016
SAP_AP 700 0012
SAP_APPL 600 0012
SAP_HR 600 0022
EA-IPPE 400 0011
EA-APPL 600 0011
EA-DFPS 600 0011
EA-FINSERV 600 0011
EA-GLTRADE 600 0011
EA-HR 600 0022
EA-PS 600 0011
EA-RETAIL 600 0011
FINBASIS 600 0011
ECC-DIMP 600 0011
ERECRUIT 600 0011
FI-CA 600 0011
FI-CAX 600 0011
INSURANCE 600 0011
IS-CWM 600 0011
IS-H 600 0012
IS-M 600 0011
IS-OIL 600 0011
IS-PS-CA 600 0011
IS-UT 600 0011
LSOFE 600 0011
SEM-BW 600 0011
ST-A/PI 01L_ECC600 0000
Kernel Patch number : 227
Thank you.
Regards.Hi,
you can use
1) standard device type I2HP4 (for polish only - does not work, if you e.g. have mixed data e.g. from Western and Eastern europe)
2) standard device type I2SWIN (for polish only - does not work, if you e.g. have mixed data e.g. from Western and Eastern europe)
3) HPUTF8 or LEXUTF8 (you will need specific Unicode capable printers for these device types)
4) Cascading Fonts as outlined in SAP note 812821 (mainly if you want to print data from multiple old code pages)
5) Check SAP note 1097990 for your printer vendor - whether Eastern European data is supported.
Usually, point 1. and / or 2. is the easiest way to print latin-2 data.
Best regards,
Nils Buerckel
SAP AG -
Sapscript and Standard Text - Polish Characters not printing
Hi,
I have created an English Sapscript and translated it to Polish via transaction SE76.
Changing my PC Region and Language settings to Polish allowed me to enter Polish Characters into Hardcoded text in the Sapscript and Standard Text via s010.
I have two problems:
1) With my PC Region and Language settings set to Polish, when I create my sapscript output some of the polish characters that I have entered via SE76 and SO10 do not appear and are replaced by others e.g.
ę is dispalyed as ê
ć is displayed as æ
ń is displazed as #
2) I have a business requirement to be in England Logged with PC Region and Language set to English but to print a sapscript output in Polish. Is this possible.
We are currently on non unicode SAP system.
Please can anyone advise.
RegardsHello,
SAP discourages mixed code page or MDMP systems and with good reason. If there is any possibility of you upgrading to a Unicode system in the near future you should try to wait for it. Supporting multiple languages in Unicode is easy, in MDMP it can be quite tricky. And MDMP makes the move to Unicode more difficult.
That said, your BASIS team can enable Polish and you can print in Polish while your PC is set for English. The SAPScript/Form must be in Polish or using an INCLUDE that is LANGUAGE 'PL' to let SAP know which code page to use when printing.
Seriously, look at moving to Unicode, you need to do it eventually anyways.
Michael -
Polish characters on print preview are not correct, printing works well
Hi gurus,
i've got a problem with smartform print preview. Our programmer developed form, which is used in polish and english version. In polish version everything works fine - print and print preview has polish characters (ąłćźń etc). In english version, print preview has no polish characters in address paragraph, but when I print it, everything is on his place.
Unfortunetly, system is non-unicode. I tried changing font to other (but in polish version with the same font, print preview is correct), changing size, even charset of printer. Works badly on I2SWIN, HP-PCL, and any other printer type.
What should I do now? Removing polish letters or changing them into "normal" is not acceptable solution, especially that printing works fine (on I2SWIN and HP PCL type also).
Polish is of course installed on the system.
Thank you for your help.
SAP ECC 6.0
SAP_AP 700 013Hi Martin,
another thought to solve the issue is to translate the form to pl in your system. I got a similar issue some time ago.
I developed the form in DE and translated it just to English, because we wanted to set always English.
Problem was, that french characters didn't show up in a proper way in print-preview. We solved the issue by translating the form also in FR and IT.
It seemed, that the formlanguage passed just the native charactersets for this language.
Maybe you are having the same issue. Otherwise would be nice, if you can share your solution if there is another one here
~Florian -
Printing Turkish Characters in SAP Script Form
Hi I want to print a Form where I need to Print Turkish characters from Database. Its Print Preview is coming absolutely right but there is some problem while printing. I shows # symbol in places of Turkish Characters. I have checked the printer and drivers and they are absolutely fine. Printer is printing other documents in Turkish Language but not the form. System has Turkish fonts installed. Kindly help. Thanks in advance.
Hi
See this OSS note for your problem
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
<b>
Reward points for useful Answers</b>
Regards
Anji -
Printing of special polish characters
Hello,
We have a requirement where in some of the Polish characters are not getting printed. To correct this we have to apply a OSS note.
SAP Application Release we are using is 4.7 & existing support package SAPKH47026.
We have found out one OSS note related to this & the note is 588724.
Please let me know if any of you have come across such issue & suggest me if this is the correct OSS note.
Best regards,
SathyanarayanaHi,
Thanks for your answer,
I am sorry i did not mention this, but the actual problem is during PDFconversion. Printing is working fine.
Regards,
Sathyanarayana -
Printing Chinese Characters in Smart Forms
Hi,
Iu2019m trying to print Chinese characters via smart forms. However during print preview or print, all Chinese characters are showing as # symbols.
I have researched and implemented for some possible solutions posted in the forum like:
a.) Setting the regional language control panel.
b.) Activating the multi-byte function in I18N.
c.) Checked the output device is SWINCF.
d.) Control parameter language is ZH (Chinese).
Unfortunately it still doesnu2019t solve the problem. Any input is highly appreciated.
With regards,
MarcRemark following basics:
Forms:
Language of the form must be: "ZH".
Due to a SAPNOTE only font family CN* (CNSONG etc.) is mapped.
For frontend print, you must install chinese true type on you local PC and print via "CNSAPWIN" .
For backend print, you must install neccesaary fonts in your printer to the resident fonts. You must use a printer like "CNHPL4" or so.
For PDF archiving, you must upload truetype fonts to application server -> basis guys.
Cascading Fonts:
If you mix different subfonts to unicode areas, you must use CNSAPWINCF.
Until now, only frontend printing is available.
Note:
Spool created for back end print with print preview is only a simulation of getting a picture of the output created with front end technology. So it can differ, when the printer does not have the resident fonts.
Regards,
Christian -
Oracle Report, How to Display Polish Characters in a PDF Output
Environment :
Oracle Application Server version 10.1.2.0.2 on Red Hat 4 Enterprise (Kernel 2.6.9-42.0.3 , 32 bit) Oracle Database Version 10.2.0.3.0 Our character set of database is UTF8
I have trouble to display polish characters in Reports Output. We develop on Windows XP machines. I can see the Polish Caharacters in the Reports Builder using several fonts (arial, arial unicode, Times new roman, verdana...) during design time or when running with the paper layout. But when the report deployed to application server running on the linux, the polish characters are replaced by symbols.
Even under Windows, when I select 'generate to a PDF' file option, the characters are not displayed correctly (When I open the generated PDF file with Acrobat reader and go to Document Properties / Fonts, I see the Fonts are always replaced with Adobe Sans MM)
Using the Forms Applications running on the same application server we have no trouble dealing/displaying with the characters (Ąą ĆćĘę Ł ł ŃńÓóŚ ś Ź ź Ż ż ß Đ đ € )
NLS_LANG setting is AMERICAN_AMERICA.UTF8 on the Linux Box and AMERICAN_AMERICA.WE8MSWIN1250 is on the Development machines. (have tried a number of different NLS_LANG settings on the development box as well with no luck).
Any direction would be appreciated.Hi,
You have several different approaches to fix this problem. First of all, you would be able to generate the PDF output with Font Subsetting setup and be able to see the Polish characters correctly when running the output with destype=cache&desformat=pdf. The following metalink documents would guide you with this setup :
Note.207711.1 "How to Use Font Subsetting in Reports 9i and 10g for PDF Output"
As at design time you use many different Windows specific fonts, I also advice you to check the following document :
Note.356221.1 "A Practical Methodology on Porting Reports from Windows to Unix with Different Fonts"
Once the PDF output is generated properly with correct characters, then if you need to use "destype=printer" for direct print, rather than "destype=cache" to display the output in browser, then you can use the "PDFPrint" pluggable destination, which is located in :
http://www.oracle.com/technology/products/reports/pluginxchange/index.html
Regards,
-Bulent -
Printer has been setup in one server but it's printing Junk characters
Printer has been setup in one server but it's printing Junk characters
Pdf file's sent from server and from local machine are printing fine..But prints sent from Oracle Reports are not getting printed, instead it is printing some garbage contents.Forgot to mention it's 10gAS (10.1.2.3) forms & reports
-
How to print bullet in smart form
Hi Experts,
I have a requirement in smart form where different points of texts should come under a bullet.
Can you please tell me how to print bullet in smart form.
Note : I have to use Standard text
Thanks in advance
Bikashi
good
We can create bullets in smartforms.
For this change the editor to text editor and then
goto insert->characters->SAP Symbols and select the
symbol you want.
This may help your requirement.
You cannot see the bullets in print preview, it'll
appear only on a hard copy.
reward point if helpful.
thanks
mrutyun^ -
Polish characters are garbled during PDF conversion
Hi,
I am facing problem with polish characters while converting spool to pdf in smartform. I have configured the new printer with device type I2SWIN with respective codepage. The preview of pdf in SAP is fine but when it is sent as an attachment in email or converted through program RSTXPDFT4, the polish characters are garbled.
I have already searched SDN for this but didnt find any soolution pertaining to my problem.
Please suggest a solution.
Regards
Abhimanyu.Hello,
Is your system a unicode system?
If so perhaps the Cascading Fonts might be useful for you (see SAP note 812821).
Cascading Font means that the PDF converter checks each character
of the text. For each character it determines the Unicode
character range, to which the character belongs. After this
it checks the SAP font name and determines, which PDF font
shall be used for this SAP font and the Unicode character range.
(see SAP note 999712)
You should get and install the device type SWINCF from note 812821, as
it is described in note 812821 (you must first apply the latest code
correction of note 812821).
Regards,
David -
Printing Turkish Characters in SAP Script
Hi I want to print a Form where I need to Print Turkish characters from Database. Its Print Preview is coming absolutely right but there is some problem while printing. I shows # symbol in places of Turkish Characters. I have checked the printer and drivers and they are absolutely fine. Printer is printing other documents in Turkish Language but not the form. System has Turkish fonts installed. Kindly help. Thanks in advance.
Hi, How did you manage to get this done?
-
Acrobat SDK 9.1 - custom plugin - Polish Characters issue
Hi,
I hope any of you will be able to help me out as we are having small issue. We are developing a plug-in that will digitally sign only XML prior to posting via webservice. This plug-in is developed for Adobe Reader 9.1 and we are using Adobe Acrobat SDK 9.1 to develop it. This plug-in needs to support Polish characters, so the plug-in will be compiled with _UNICODE directive. We are running into a Polish Character issue where Polish Characters are not being displayed in the plug-in popup. Would you be able to tell us how is the Acrobat SDK dealing with this (as it is using std:string and not any type of wide string format), what type of params will get simple functions (like AVAlertNote).
We are also using the JS bridge to export data from the fdf form (using exportXFAData).
Any help would be greatly appreciated!
Thank you,
Jan KropiwnickiYou should be using ASText objects when working with Unicode.
Maybe you are looking for
-
Calendar events not showing up in widget for NC?
Hi! Well I have a question about the calendar widget. Yesterday on my today view of the notification center I saw (in my tomorrow summary) that there is an all day event scheduled for today(The Veterans Day ) and when today I opened the calendar and
-
Restrict GR date prior to PO creation date.
Dear experts, The Present configuration allows GR date prior to PO creation date. The system allows users to post Goods receipt (MIGO), even if the GR date is prior to the PO creation date. How to restrict this? Is there a standard customization in M
-
Frozen Windows 7 install at DOS cursor with Boot Camp 5.0
Hello, I am installing windows 7 (32 bit) on a mid 2012 Mac Book Air (13 in) using install version of windows 7 DVD from external superdrive and boot camp 5.0. After boot camp partitions I go to a black screen with blinking DOS cursor and nothing h
-
Use a second computer as a 3rd display?
Hi there! Is it possible to use a second computer (my laptop in this case) to receive video as a 3rd display, through firewire? I think all I need is just a driver or program on the receiving computer to let be recognized as a camera by the main comp
-
Certificates Not Visible in FireFox.
I am importing(installing) a few .pfx certificates with valid credentials in Window 7 system. After doing such activity, I am able to see installed certificates in IE and Google Chrome Browsers. But the list is blank in case of Mozilla Firefox. Means