|
I didn't say it's a Windows/Notepad problem. I said that if you're
doing a "save as" from Notepad before importing it into the real
application, then you need to examine how Notepad is encoding the data,
because in that case the entire file is being re-written by Notepad.
I also said (in the same message) that you could supply a BOM at the
start to control how Notepad interpreted it.
But, whatever... why am I bickering with you?
On 6/25/2012 10:04 AM, John Yeung wrote:
My guess (and it's definitely possible that I'm off the mark -- it's
just a guess) is that the first file contains something that is
triggering Notepad to believe that it is UTF-8, whereas the
others do not have that.
Exactly my point. You originally said "it's a Windows/Notepad
problem, not an i/RPG problem". But if the encoding of the first file
is *detectably* different from the others, when the intention was for
all the files to have the same encoding, then doesn't it seem that
it's due to (and fixable from) the i?
Well, since apparently my way of phrasing and explaining things is not
helpful enough for you, I'll just bow out of this conversation.
Look, I'm not the one asking for help. I don't have your expertise on
the i (frankly, very few people do). If you have a problem with me,
that's fine. Don't penalize the OP or the rest of the list by
withdrawing. Just put me in a kill file or set up a filter or
something.
John
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
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.