We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi there,
today I tried to replace Rockets gmake with ZOT equivalent. Unfortunately I'am unable to use vanilla USS files (untagged/1047) as a Makefile.
If my file is untagged and in IBM-1047 gmake can't read it. When tagging this file with the appropriate tag, things are going well.
Untagged files in IBM8859-1 where read just fine. (tagged too)
So in my opinion the default behavior is to read untagged files as ISO8859-1. I don't think that's the right choice.
But what do you think about this?
Best, Mike
The text was updated successfully, but these errors were encountered:
Any update here?
Sorry, something went wrong.
Yes, untagged and IBM-1047 will work:
toe Makefile # convert to EBCDIC chtag -r Makfile # make it untagged ls -lT total 32 - untagged T=off -rw-rw-r-- 1 ITODORO BASIC 871 Sep 12 08:16 Makefile t ISO8859-1 T=on -rw-rw-r-- 1 ITODORO BASIC 959 Sep 12 08:16 process_data.pl [ITODORO@ZOSCAN2B ~/podman_makefile]$ make Cleaning up... rm -rf data.txt risk_analysis.txt Cleanup complete. Downloading data file using curl... ...
No branches or pull requests
Hi there,
today I tried to replace Rockets gmake with ZOT equivalent.
Unfortunately I'am unable to use vanilla USS files (untagged/1047) as a Makefile.
If my file is untagged and in IBM-1047 gmake can't read it.
When tagging this file with the appropriate tag, things are going well.
Untagged files in IBM8859-1 where read just fine. (tagged too)
So in my opinion the default behavior is to read untagged files as ISO8859-1.
I don't think that's the right choice.
But what do you think about this?
Best, Mike
The text was updated successfully, but these errors were encountered: