Djac
685 pts. | Feb 28 2008 2:38PM GMT
What printer are you printing to? If it’s a HP LJ2015P then I don’t think you’ll have much luck whatever you do. They have very limited PCL5e font support so can’t print a very wide range of accented and special characters.
Rodymary
25 pts. | Feb 29 2008 4:35PM GMT
I’m on lexmark optra printers T614, T642, so T6xxx
here’s what I did and how is my config
- as/400 QCCSID 65535
- data keyed in thru a client access setuped in turkey host code page turkey (1026)
- job which generate my spool in turkish CCSID
- when i look my spool, all turkish special char. are ok on display
- my spool description tells me turkey ccsid
- i changed the code page from the DEVD *PRT with the turkish one
- i sent the spool to my lexmark printer thru LPR…
- char. are wrong
which font is used on the printer ? i don’t know, my DEVD *PRT is using Font 11… what does it means ?
am I missing something ?
thanks
Rodymary
25 pts. | Mar 7 2008 10:53AM GMT
hi all
FYI, i’ve solved my problem
it was just a missing setup in the printer, which had to be changed to turkish code page
so, the way to print turkish is simple :
- have turkish text in data base (must be keyed in thru a turkish client-access session, code page 1026)
- set the turkish CCSID EBCDIC 1026 on the PRTF then create your spool
- send your spool to a well setuped turkish printer (code page ASCII 857)
I thought that the printer was able to analize the data it received and automatically set the appropriate code page, but in my case, a simple *SCS spool, the original code page information is not transmitted
Rod
TomLiotta
7550 pts. | Oct 30 2009 1:25AM GMT
it was just a missing setup in the printer, which had to be changed to turkish code page
That is troublesome, but maybe it just isn’t clear. Did you have to “install” the Turkish code page or did you merely change the printer configuration to print Turkish as the default or something similar? If you simply changed the default, then that might have been unnecessary. It’s probably an excellent idea — just maybe not needed.
What would concern me is this:
- - as/400 QCCSID 65535
That setting tells the system not to convert characters, handle data as binary. In a multi-language environment, that’s troublesome to put it mildly. In 21 years working with AS/400s at many sites, I’ve yet to find one that should be set with QCCSID 65535. (Except for systems explicitly intended to test CCSID issues.) Worse, it’s unusual to find systems that aren’t set at 65535. Even simple transfers to ANSI/ASCII systems (e.g., PCs) bring grief.
Tom






