Re: AS400 codepage to MS Office -- MIDRANGE-L

Just some guesses -

I assume you have the euro-enabled fonts for Windows and
Office?

Have you tried STMFCODPAG(*PCASCII)? That's supposed to
be the one for Windows.

Is your 400 set to code page 1140? I saw something that
says that is the extension for 37 that has the euro.

Could there be a problem with Unicode in NT?
> 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
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>