Exporting field contents and removing unicode

[Cabinetman]

I am downloading a web page using troi url to get it into a text field - received data - that comes in as Unicode. I then export using field contents to save as an HTML file for stripping.

The Unicode is causing havoc! Seems I have some UTF-16 in the field.

I don't see any options available using the export field contents to specify the "output file character set"

Any ideas without going to a plug-in? I want to get rid of everything that isn't your standard HTML and text.

This needs to be automated so manually copying and pasting won't work...

[Søren Dyhr]

Use instead Send Event and build the string for the command via a calculation - this way:

"cmd /c echo " & yourField & " > temp.txt"

This will give an x-byte file if your field contain exactly x chars, it's as short as it gets!

--sd

[Cabinetman]

I tried the send event and maybe had something wrong because I couldn't find the file created...

"cmd /c echo " & table::received data & " > testpage.txt" .... using the calc section of the send event.

Solved anyway though! Or at least very close.... haven't filled all the gaps yet

I named the web viewer as odject "web page ie"

I then created a calc field using GetLayoutObjectAttribute("web page ie" ;"content")which diplays the html.

Exported this and all seems well........

The only problem I see so far is it only recalculates if the record changes. I need to create some sort or refreshing

There is only 1 record in this table so even if I go to a different page in the viewer or the content of the page changes I still have the same data in the field I export contents from.

Hhhhuuuuummmmmmmmmmmmmmmm

Edit: I had the field set to Global and changed it... may be the answer.

Edited August 20, 2008 by Guest

[Søren Dyhr]

maybe had something wrong because I couldn't find the file created...

Then make sure to include the absolute path for delivery:

../ - followed by precise path, gives an offset in the root-directory!

--sd

[Cabinetman]

Thanks.

I think I'm sticking with the easier (for me) of the 2 which is to use the export field contents.

Since I have found another way to get the source without having to use a plug-in I don't have a problem with the data in the field.