Character encoding in output from external commands

Having trouble installing Oxygen? Got a bug to report? Post it all here.
cwittern
Posts: 4
Joined: Sat Feb 26, 2005 3:28 am

Character encoding in output from external commands

Post by cwittern »

Hi there,

I just succeeded in submitting a XQuery to the eXist XML Database by defining an "external command", which works nicely, however: Somehow Oxygen seems to mangle the encoding of the returned output. eXist returns to me UTF-8, but Oxygen seems to interpret it as MacRoman and shows me garbage.

I am working on Mac OS X with Oxygen 5.1. The default encoding in the preference pane (for non XML files) is set to UTF-8.

Any help appreciated,

Christian
george
Site Admin
Posts: 2095
Joined: Thu Jan 09, 2003 2:58 pm

Post by george »

Dear Christian,

The encoding used for the external tools output is the platform encoding.
Can you direct the output to a file and open that in oXygen? Is this workaround satisfactory?

Best Regards,
George
cwittern
Posts: 4
Joined: Sat Feb 26, 2005 3:28 am

Post by cwittern »

george wrote:Dear Christian,

The encoding used for the external tools output is the platform encoding.
Can you direct the output to a file and open that in oXygen? Is this workaround satisfactory?

Best Regards,
George
No, not really. The Platform encoding then is probably MacRoman if I am working on the Mac? I do all my work in UTF-8 and also set this at the default encoding in Oxygen, but this does not help.

In addition, if I have a result in the result pane and then save it to a file I do have the same problem: All my characters get garbled (e.g. turned into ??). The only work around I found so far is copy-and-paste from the result pane to a new file. This does work, but is not very elegant. I would prefer if you could look into a solution.
george
Site Admin
Posts: 2095
Joined: Thu Jan 09, 2003 2:58 pm

Post by george »

Hi Christian,

I added an enhancement entry to associate also an encoding with an external tool.

The results are saved using the following procedure:
-- assume the result is XML and try to determine the encoding from the header
-- if the above fails then use the encoding for non XML files specified in Options->Preferences on the Global page.

Best Regards,
George
Post Reply