This function doesn't seem to convert text to encoded HTTP at all, instead it URL-encodes text. Is this others' experiences?

If this is true, it would be nice to have a true Text to Encoded HTTP function (keeping this URL encoding function separately).

Hi,

I think you are right, it's a URL encode and not a HTTP encode. Wrong label.
We will put the Text to Encoded HTTP on the list for the Convert text function.

Could you give us an example for typical use?
DS

Sure, because there is not a great function in the software (yet) to turn HTML to formatted text (retaining line breaks, etc) I instead am saving raw HTML to a database (via a stored procedure). There are errors trying to save large chunks of data with characters like ' in them, so I instead need to HTTP encode the text before saving it. URL encoding the text then decoding it on the other end gives some side-effects that are not optimal.

In general, because Djuggler's strengths don't seem to be in transforming data (yet)-- like date conversions and formatting, text formatting, numeric conversions and formatting-- my idea is to do as much of that work as possible outside of the tool and have DJuggler only grab raw HTML.

I hope I can prove the concept of what I am trying to do within the trial period then I will happily purchase the product

Thank you

A new version 2.2.11 has been released with HTTP Encode and HTML encode in the Convert Text action. The old HTTP encode has been renamed to URL encode.

Version 3 of Djuggler will have much more transform options for dates, numbers and text. It will also be complete Unicode.

Thank you for your input.
DS

I should thank you for being so responsive and attentive!

I can't wait for version 3, as it will be nice to be able to extract dates from the web like "Wednesday January 2nd 2009" or "01/02/2009" (or whatever) and transform them into datetime types suitable for databases :)

Thank you again for your quick responses and actions