Also, that would explain why it works on 4.2 but not 4.0. 4.2 and later versions of 4.1 handle BOMs, but 4.0 does not. You might want to schedule an update of that 4.0 system....
-Danny From: [email protected] [mailto:[email protected]] On Behalf Of Mike Sokolov Sent: Monday, October 17, 2011 10:15 AM To: General MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] Encoding error during document loading It looks as if you have a BOM (byte order mark) at the beginning of the file, as you figured out. One thing you can do is just to remove it, but some editors (Notepad being one, I guess) will hide it from you. This link has a number of suggestions how to remove it: http://stackoverflow.com/questions/295472/how-do-i-remove-the-bom-character-from-my-xml-file On 10/17/2011 11:53 AM, Neil wrote: Hi, I am getting a weird encoding issue when importing documents. While my local copy of MarkLogic has NO problem loading a document, when I try to load the same document on a remote server the following error is raised: [1.0-ml] XDMP-DOCROOTTEXT: xdmp:document-load("C:\TestFile.html", (), <options xmlns="xdmp:eval"><database>16453038828028925603</database><modules>0</modules><de...</options>) -- Invalid root text "" at C:\TestFile.html line 1 The document loads OK in IE, which reports that the document is "Unicode- UTF-8" encoding, and opens OK in Oxygen too. When I open the document in Notepad I do not see any unusual characters on line one, but did not really expect to. I recall that characters FE and FF are used in Unicode to indicate whether the bytes are lower- or higher-byte first (but is that just in Unicode 16?). I tried add <encoding> options to xdmp:document-load() but none of the values I tried helped any. My local configuration is: Architecture: i686 Platform: winnt Host: neil-pc MarkLogic Product Edition: Standard MarkLogic Product Version: 4.2-5 The server configuration is: Architecture: amd64 Platform: winnt Host: dgdbsrv1.dg.local MarkLogic Product Edition: Enterprise MarkLogic Product Version: 4.0-3 So the obvious question is whether differences between 4.0 and 4.2 account for me not seeing the error locally, and the error appearing on the server? If so is the only solution to upgrade the server version? Or is there an easy way I can convert the documents into a format that WILL load into the earlier version of ML? Regards, Neil. _______________________________________________ General mailing list [email protected]<mailto:[email protected]> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
