[Info-vax] Making sure Character Encodings dont't break between workstation and OpenVMS

[John E. Malmberg]

On 9/10/2019 4:34 AM, Tapland wrote:
> On Tuesday, September 10, 2019 at 11:26:02 AM UTC+2, Marc Van Dyck wrote:
>> Tapland presented the following explanation :
>>> I am a beginning software developer for OpenVMS on a Windows workstation. I
>>> previously used Notepad++ and it's NppFTP plugin to browse, download and
>>> upload file to the OpenVMS-machine.

You may want to look at Visual Studio Code instead of Notepad++.

I do not know if it will help with your character encoding issue.

Unfortunately UTF-8 support for terminal output is pretty much limited 
to terminal emulators.  The UTF-8 output by the one of the Perl self 
tests can really mess up a DECterm.

https://wiki.vmssoftware.com/VMS_IDE_Developing

https://marketplace.visualstudio.com/items?itemName=VMSSoftwareInc.vms-ide

https://marketplace.visualstudio.com/items?itemName=tomesparon.openvms-syntax

> Yes, it absolutely is when there isn't a lot of new development or creation of new files.
>    
> I think I found a handy way. I set ISO 8859-1 as default and fallback
> in my editor. Opening files from OpenVMS I will now see if they open
> with another encoding, and by default the editor will save in 8859-1.
> Using WinSCP for SFTP, which works, and will try to figure out the
> built in FTP-clients later.

I have Cygwin (32 bit) installed on Windows and have it serving files 
via NFS, which are mounted on the OpeVMS system.

The last time I looked a few years ago, Cygwin 64 bit did not have an 
NFS server package.

I also have a fedora system serving NFS files.

In both cases I had to enable NFS V2 and V3 as I am mounting those files 
on VAX/VMS 7.3, OpenVMS Alpha / Itanium 8.4.

Regards,
-John
wb8tyw at qsl.net_work