> On Aug 30, 2017, at 6:31 PM, Justin Carr via 4D_Tech <[email protected]> > wrote: > > Also I'm pretty sure if you use TEXT TO DOCUMENT to produce UTF-8 (or any > other charset that has a BOM specified for it), 4D will insert the BOM in the > document.
Yes, and this makes TEXT TO DOCUMENT less useful than it should be for UTF-8. There is no option to leave it out and most other systems don't expect it to be there. As Justin said, the only option is to use BLOB TO DOCUMENT instead. https://en.wikipedia.org/wiki/Byte_order_mark > The Unicode Standard permits the BOM in UTF-8,[3] but does not require or > recommend its use.[4] Byte order has no meaning in UTF-8,[5] so its only use > in UTF-8 is to signal at the start that the text stream is encoded in UTF-8, > or that it was converted from another stream that contained an optional BOM. John DeSoi, Ph.D. ********************************************************************** 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] **********************************************************************
