Thanks, John. > On Jul 3, 2018, at 8:48 PM, John DeSoi via 4D_Tech <[email protected]> > wrote: > > The extra characters are the Byte Order Mark (BOM) - see the documentation. A > BOM is useless with UTF-8, but there is no way to prevent 4D from inserting > it when using TEXT TO DOCUMENT. > > I use this method instead: > > > C_TEXT($1;$2) > C_BLOB($blob) > > TEXT TO BLOB($1;$blob;UTF8 text without length) > BLOB TO DOCUMENT($2;$blob) > > John DeSoi, Ph.D. > > > >> On Jul 3, 2018, at 10:31 PM, Robert McKeever via 4D_Tech >> <[email protected]> wrote: >> >> TEXT TO DOCUMENT($MyDocs1{$n};$MyReplacedDoc;"UTF-8";0) >> >> Seemed to work. Except each modified file has three extra leading >> characters, so the java scripts won’t run.If I remove the weird characters, >> the scripts run fine. The documents were created with UTF-8. >> >> In hex, the characters are ‘EFBBBF’. How do I prevent the characters from >> being added? > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > **********************************************************************
_________________________________________ Bob McKeever http://www.mswl.com <http://www.mswl.com/> McKeever's Software Wizardry Port Coquitlam, B.C. [email protected] ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
