| The questions in .1 still apply.
Some application, even if it was just a text editor created the file.
That program used particular codes for particular characters.
If it used National Replacement Character Set codes for characters
not in the usual ASCII set, and the printer was set to use ISO Latin 1
or DEC MCS, then characrer mismatches will occur.
If you can post a representative file, we might be able to resolve the issue.
- tom]
|
| Okay, thanks for such a simple text case.
This is the content of the one line test file:
Das ist ein Test � AE � UE � OE
This is its hex dump:
65 54 20 6E 69 65 20 74 73 69 20 73 61 44 00 1F ..Das ist ein Te 000000
4F 20 D6 20 45 55 20 DC 20 45 41 20 C4 20 74 73 st � AE � UE � O 000010
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 45 E............... 000020
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 000030
(Note that the AE, UE, and OE characters are not failed ligatures,
but separate character pairs.)
As I see this on my screen, I see upper case A umlaut, upper case U umlaut,
and uppser case O umlaut for the three characters that precede the AE, UE,
and OE.
When I print the file to a DEClaser 5100 using DCPS and the ANSI translator,
I see the same characters in print that I see on my screen.
However, when I print the file to the 5100 using its native PCL mode,
the printed output shows as lower case a accent, upper case E accent, and
lower case slashed letter o.
My printer says that its PCL character set is set to "font number 0,"
as was mentioned in the base note. (My printer also has the ROMAN-8
symbol set selected - wat does yours have in its PCL state?)
There is only one black square character in that set, hex code FC.
I'm guess that the UCX$TELNET symbiont is activating the PCL interpreter
for this file and perhaps re-selecting a font number or character set.
- tom]
|