× 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.



Hi,

as answer to Joep's and Wim's questions :

* Word cannot open (because file contains invalid characters)
* in 5250, file looks ok (accents are shown like it should)
* Qccsid (and job ccsid = 65535)
* Qchrid = 697 500

Hope you can help me looking at this additional info ... .

Kr,
Dirk.

Dirk Mari?n

Toyota Motor Europe
60 Avenue du Bourget,
1140 Brussels, Belgium

Ph: +32 (0) 2 745 2581

www.toyota-europe.com



From: j.beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx
To: "RPG programming on the IBM i \(AS/400 and iSeries\)"
<rpg400-l@xxxxxxxxxxxx>,
Date: 21/01/2014 15:32
Subject: Re: Another code page - character set issue ?
Sent by: rpg400-l-bounces@xxxxxxxxxxxx



Dirk,

Questions:

- How do you see the strange characters? MS Word? XML-SPY?
- How does the file look like through DSPF?
- What is the source of your data? Can you verify it contains valid
characters in the CCSID you are converting from (usually the job CCSID;
specifying 0 for conversion id)?

Joep Beckeringh


Dirk.Marien@xxxxxxxxxxxxxxxxx

Re: Another code page - character set issue ?

I've now tried both options.

Coded character set is now 1208, but I still get strange characters in
my
XML :

<goodsDescription>"Peintures:base de polym?s synth?ques+naturels
modifi
砼/goodsDescription>

The XML's without é, è, à, ... are going great ... .

Any ideas left ?

Kr,
Dirk.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.