On 25 Feb 2016 4:43 AM, Bobby Johnson wrote:
Yep, I have been chipping away at it. May take a while. My main objective was
to let people know that some and maybe all of the extended ascii characters will
not go through a zip/unzip operation in tact.
I would have thought that this was a Windows restriction and not a Legacy
problem. Windows has a list of disallows characters and your Alt-0150 is not on
that list. It does say that not all filename strings are valid on all file
systems. This becomes important when moving files between, say, Windows and a Mac.
This paragraph might cast some light (from
<https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396>)
Use any character in the current code page for a name, including Unicode
characters and characters in the extended character set (128–255), except for
the following:
The following reserved characters:
< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)
Your Alt-0150 might only be really valid on a pure Unicode system.
One question though: What software did you use for the ZIP/UNZIP? Software that
expects 'normal' filenames might have problems with 'exotic' characters.
--
Regards,
Mike Fry (Jhb)
_______________________________________________
LegacyUserGroup mailing list
[email protected]
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
