It looks like you have a zip file that incorporates changes that weren't in the 
distribution.

There is a new version of XQDebug, 1.0.2, that will filter Apple and SVN 
changelog/archive files from a zip file.

You can get it from here: http://code.google.com/p/xqdebug/downloads/list

1.0.2 also allows window resizing (thanks to Michael Fagan), better support for 
MarkLogic system files and the Database Explorer allows you to explore the 
directories and files and view permissions without needing a URI Lexicon on the 
database.

Please let me know if you still have any problems with this new revision.

Keith Breinholt
[email protected]


-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Jason Hunter
Sent: Monday, October 25, 2010 3:03 PM
To: General Mark Logic Developer Discussion
Subject: Re: [MarkLogic Dev General] XQDebug fails to install

Well MarkLogic treats the file as text based on its file extension. It's 
apparently not utf-8 so thus the issue. 

Perhaps the resource fork isn't really supposed to be there. Try removing it 
from the zip before installing?

Sent from my iPhone

On Oct 25, 2010, at 4:32 PM, David Sewell <[email protected]> wrote:

> We're trying unsuccessfully to install the open source XQDebug tool,
> 
> http://xqzone.marklogic.com/code/xqdebug
> 
> on our development server (Red Hat Linux). Running the install script 
> fails with a server error indicating some real oddness in the 
> interaction between script and zipfile, suggesting maybe that the 
> source zipfile was corrupted at some point?
> 
> XDMP-DOCUTF8SEQ: xdmp:zip-get(fn:doc("/code/xqdebug/xqdebug.zip"), 
> "__MACOSX/xqdebug/assets/scripts/editarea_0_8_2/._change_log.txt") -- 
> Invalid UTF-8 escape sequence at 
> __MACOSX/xqdebug/assets/scripts/editarea_0_8_2/._change_log.txt line 1 
> -- document is not UTF-8 encoded in 
> /xqdebug/install/install-functions.xqy, on line 26,
> 
> etc. etc. In other words, for some reason the program is reading in an 
> OS X resource fork dotfile, ._change_log.txt (i.e. one of the metadata 
> files that gets created when you run an OS X zip program) and trying 
> to interpret it as a text file, which it's not (it's binary data).
> 
> Any ideas, anyone?
> 
> DS
> 
> --
> David Sewell, Editorial and Technical Manager ROTUNDA, The University 
> of Virginia Press PO Box 400314, Charlottesville, VA 22904-4314 USA
> Email: [email protected]   Tel: +1 434 924 9973
> Web: http://rotunda.upress.virginia.edu/
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general


 NOTICE: This email message is for the sole use of the intended recipient(s) 
and may contain confidential and privileged information. Any unauthorized 
review, use, disclosure or distribution is prohibited. If you are not the 
intended recipient, please contact the sender by reply email and destroy all 
copies of the original message.


_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to