[Info-vax] Alpha Community licenes.
Jan-Erik Söderholm
jan-erik.soderholm at telia.com
Tue Sep 20 03:54:13 EDT 2022
Den 2022-09-20 kl. 04:14, skrev Steven Schweda:
>> I do not know why you are taking this personaly...
>
> What's personal? I'm simply bewildered by your apparent
> unwillingness to admit that the only problem here is a failure to use
> widely available tools in a way which avoids the problem.
And that causes the issues that I have described.
I have never said that it can't be avoided.
>
>> I often *do* have issues reading text files (like read-me files
>> or source code) from zipped VMS kits. In many cases this is due
>> to that the original files had variable-length records.
>
> Without knowing how these unspecified "zipped VMS kits" were made,
I never expected you to know that. Cool down... :-)
> or
> how you handled them,
I just opened it as any other ZIP file on my laptop.
Windows explorer opens and displays ZIP files just fine.
But it knows nothing about VMS-specific file/record formats.
> I can't say why you had trouble. I would note,
> however, that Info-ZIP UnZip on non-VMS systems has long had a
> "VMS_TEXT_CONV" option (enabled by default -- See "unzip -v"), which is
> supposed to deal helpfully with such files. If you rely on other unzip
> programs which lack such a feature, then you might complain to their
> authors. (If you see Info-ZIP UnZip misbehaving, then feel free to
> complain to me.)
>
No, I have never said anything like that. I still do not know why
you think that I'm complaining to you or on your work. Weird...
>> I do not understand why you have a problem with that...
>
> It's simply irrelevant to the problem with the recent VSI-generated
> *_COMMUNITY_LICENSE_PAK.zip archives. (Whose files contained no such
> variable-length records.)
Yes! Absolutely correct. Those file worked just fine.
That is why made my comment that this is not always the case.
More information about the Info-vax
mailing list