× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



OK, this should be an easy one...

I have some text in AS/400. Transfering it to a folder with CPYTOPCD or
using CPYTOSTMF, no problem during the transfer to a flat file "xxx.txt"

We had some problems with our national language chars, accented vowels,
spanish n-tilde lower and uppercase, but all these got solved using
adequate translate table.
The problem comes with the "euro" sign:
I type euro in the AS/400. No problem.Also changed translate table to
translate our EBCDIC euro sign X'9F' to ASCII X'80'.
When I put the text data from AS/400 to the flat XXX.txt file, then I AM
ABLE TO SEE the euro sign using Wordpad in the PC, so I know translation
was correct.

But if I try to see it with MS Word, euros signs only show as blank
square boxes... Curious enough, even if using MS Word itself  I add new,
additional, euro signs to the document, I can see them while I'm in
Word, but if then save the document and reopen it with same Word... both
initial euro signs and the new ones aded just before, all show as blank
square boxes! Strange!
This mess just comes from the need to send out some faxes from AS/400,
using a product called ZetaFax which works quite nicely, but the
question of the euro sign is driving us crazy.

I think the problem may come from the fact that the flat XXX.txt file
I'm creating for each fax to be sent has its own CodePage, coming from
the AS/400, and that CodePage WORD will not recognize (but why would
Wordpad do recognize it ???) .

CPYTOPCD does not allow to specify a destination CodePage
CPYTOSTMF does allow such a parameter, but I've tried with all different
values I could think of, and still Wordpad will recognize our translated
euros, but WORD will not.

Anybody knows what CodePage WORD uses when opening a flat " *.TXT  "
file? I guess the key is importing FLAT DATA with a different codepage
than the one Word is supposed to use...
In the old times, Win95, somewhere in CONFIG.SYS or AUTOEXEC (don't
remember ...) you could specify code page 437 (for US) or 850,... but
with WinNT that's gone !
How can I CPYTOPCD/CPYTOSTMF to a flat file with adequate codepage for
MSOffice?

Any one has a bright idea?
We are using AS/400 with version 4.5    .  PC side is NT Server 4.0,
ServicePack 5, and Office97
--
-------------------------
Antonio Fernandez-Vicenti
afvaiv@wanadoo.es




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.