(Created page with "<seo title="Directly Edit EBCDIC Text Files | vEdit" description="EBCDIC text files can be directly edited in vEdit without having to translate them so they can be transferred...") |
(→How to Directly Edit an EBCDIC Text File) |
||
| Line 4: | Line 4: | ||
EBCDIC text files can be directly edited in VEDIT, without having to translate them. This is best for EBCDIC files which will subsequently be transferred back to the mainframe computer. | EBCDIC text files can be directly edited in VEDIT, without having to translate them. This is best for EBCDIC files which will subsequently be transferred back to the mainframe computer. | ||
| − | + | ==How to Directly Edit an EBCDIC Text File== | |
#Open the file in the usual manner, e.g. with <kbd>FILE</kbd> > <kbd>Open</kbd>. | #Open the file in the usual manner, e.g. with <kbd>FILE</kbd> > <kbd>Open</kbd>. | ||
EBCDIC text files can be directly edited in VEDIT, without having to translate them. This is best for EBCDIC files which will subsequently be transferred back to the mainframe computer.
You can now directly edit the EBCDIC file. Although the EBCDIC file itself has not been translated or changed in any way, it now appears normal and can be edited in vEdit like a normal file.
In “EBCDIC” mode, vEdit acts just as if you were editing the file on a mainframe computer. When you save the file, it is still an EBCDIC file which can be uploaded back to a mainframe. It is so easy to directly edit an EBCDIC file in vEdit that you might be wondering what the fuss is all about.
To let you easily edit EBCDIC files, vEdit performs invisible translations:
Since ASCII and EBCDIC have somewhat different character sets, not all characters will translate correctly. Therefore, if you translate a file to EBCDIC and then back again to ASCII, you may not have the same file again. Some punctuation, e.g. “[”, “]”, “|”, and many control and graphics characters will have changed.