Have just upgraded from 5.52 to 6.5 (Win2000). Have a nice little IWPERL script that 'writes back' some info to my DCRs (with DCRFILEHANDLE) after they have been submitted and deployed. This used to work like clockwork, but with the new upgrade I find that after submitting my files I can no longer open them in TeamSite, i get the delightful error - Root cause:
Couldn't parse DCR bytes into DOM [unable_to_parse_dcr ]:Invalid byte 1 of 1-byte UTF-8 sequence.<br>
The reason for this is of course that 'something' has written a UTF-8 Byte Order Mark (BOM) at the beginning of the file. The only thing that has touched the file is my IWPERL script where I opened and wrote back the file using DCRFILEHANDLE. Hmmmmm. <br>This poses several questions - <br> 1. Does anyone know of a way of turning off the writing of the BOM that DCRFILEHANDLE seems to now be doing? <br>2. If there is no way of turning it off the BOM mark then why have Interwoven in their infinite wisdom enabled this when TeamSite is still (for some unkown reason) unable to deal with it.
Any help, as always, greatly appreciated :-)
Edited by nichporter on 05/10/05 00:35 AM (server time).
