Hello, I think it would not be telling the full story if you just focus on how UTF-16 takes double the size for standard ASCII, and therefore uneconomic. and I am not speaking because UTF-16 actually takes less space than UTF-8 for Japanese text.
one must take into account that standard Windows API (wide characters) and macOS API (NSString) both use UTF-16, as does the file system (paths). so its make sense that 4D uses UTF-16 for internal string representation, since it can be used directly with native APIs. if UTF-8 was used for storage, then the data file may be smaller, but 4D would have to do the conversion back to UTF-16 before loading it to memory. > 2017/07/12 9:03、David Adams via 4D_Tech <[email protected]> のメール： > In 4D, I think you're always > using UTF-16, is that right? ********************************************************************** 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:[email protected] **********************************************************************
