Bug 46915

Informational

GemStone/S 64 Bit

3.5.5, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3

All Platforms

Files created using GsFile using String containing non-ASCII characters not accessible

Prior to GS/64 3.3, there was a bug in GsFile (44786) where on a unix environment using a UTF-8 locale, if a file was created using a filename that was a String containing non-ASCII characters, the resulting file would have a corrupted filename that was not a valid UTF-8 string.  Since 3.3, these files are now not directly accessible from GsFile.  Attempts to read/append them using the same String will fail with a file not found error.

Workaround

Rather than using:

GsFile open:  <stringContainingNonAsciiChars>

use:

GsFile open:  (Utf8 withBytes: <stringContainingNonAsciiChars> asByteArray)


Last updated: 5/30/17