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



On Tue, Jun 19, 2018 at 1:21 PM, Soucy, Michael <MSoucy@xxxxxxxxxxx> wrote:
I tried changing the attributes using the CHGATR command. When I do that it removed the BOM from the file, but now the program I wrote using Scott Klement's CSV parsing utility won't work.

The CHGATR command should not remove anything. Indeed, it should not
affect the contents of the file at all. If you look at the file in
hex, I'm confident you will see that the BOM is still there. It will
show up as the following three bytes: x'EFBBBF'. This is a strong (but
not foolproof) indication that the contents of the file really are
UTF-8, in which case 1208 is the proper CCSID.

Buck gives some good diagnostic advice, which you should definitely
try, but I just wanted to clarify that CHGATR does not touch the bytes
within the file. It only alters metadata.

John Y.

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.