|
Hello Paul, If you change the CCSID tag to the correct ascii CCSID prior to opening the file (using CHGATR on V5R1 or the Qp0lSetAttr API) - how does the implicit conversion then work? Best regards, Carsten Flensburg ----- Original Message ----- From: "Nicolay, Paul" <paul_nicolay@merck.com> To: <rpg400-l@midrange.com> Sent: Thursday, March 14, 2002 1:33 PM Subject: POP server direct access > Hi, > > I'm writing a program that should process incoming mails. While a sockets > connection to the POP server is maybe the recommended method, I'm currently > reading directly from \QTCPTMM\MAIL\<mailbox> > > When reading the file (with the C open/read() functions) from such a mailbox > however, I get a few translation issues. First of all, unlike for example > my HTML files the content doesn't get translated to EBCDIC (because the SMTP > server seems to tag those mail files with CCSID 37). Instead the file > remains ASCII... which I tried to solve by doing the translation myself > (based on QEBCDIC table). > > While this works for almost all characters, it doesn't for 'I', 'O' and 'Z' > ??? I can understand that special characters would be an issue, but not > something in the range from A to Z ? > > Why is the C function acting this strange... and why is viewing the file via > NetServer or EDTF going perfect ? > > Thanks in advance, > Paul > > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. >
As an Amazon Associate we earn from qualifying purchases.
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.