the character set used for non-unicode mode is actually locale-specific, but for most users it should be MacRoman (even on Windows).
the legacy internal character set (a.k.a. non-unicode mode) is "Mac" on both platforms, which is why the corresponding constant for TEXT TO BLOB is named "Mac text without length" (exception is the Japanese version, which uses a pair of special lookup tables) if you want to be absolutely sure, you could loop over all characters between 0x00 and 0xFF, compare the byte values from blob-based receive packet passed to BLOB to text. > 2018/01/03 21:23、Ken Daniel via 4D_Tech <4d_tech@lists.4d.com> のメール： > Miyako, since Receive Packet respects Use Character Set, is there a > particular character set I could set in v16.3 (Windows 32-bit Unicode mode > checked) that would match what was working when using Receive Packet with > unicode mode unchecked? Ken ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
