I can use "Convert Text" for "ASCII to UTF-8" action.
But how can I make "UTF-8 to ASCII"? I can`t find such possibility.

Error in previous message...

Please read it as:

I can use "Convert Text" for "UTF-8 to ASCII" action.
But how can I make "ASCII to UTF-8"? I can`t find such possibility.

When you save a text source as UTF-8 any ASCII is automatically converted to UTF in the save process.
Is that what you mean?

Tijn

I try to work with "Convert Text" action in "Text Formatting".
I have text variable in ASCII
How can I convert text variable from ASCII to UTF-8?

Why would you want to convert the variable?

Djuggler is Unicode, meaning a variable is always double byte. UTF-8 is a more extended charset then ASCII, so if had an action that converts a variable from ASCII to UTF-8, nothing would change in the variable content.

ASCII or UTF-8 within Djuggler is only meaningful when saving to disk.

I think the main reason is representation of my native language letters (russian).
Now I can see my native language letters only in comments.
But I can NOT see native language letters in Actions (when UTF-8).
Instead I see: Куплю: Электротехническое
It's UTF-8

But if I convert "UTF-8 to ASCII" I see all native letters well and work with them as usually.

And therefore sometimes I need to convert from ASCII to UTF-8

It's not a very big problem for me, but may be it would be more comfortable see my native letters in actions too

Can you attach a simple example, with the difference between a comment and an action? The interface should always display the correct characters.
DS

http://s19.radikal.ru/i192/1007/4c/b6b35aaa3834.jpg

Thanks for the screen-shot.
We tried to replicate the situation but without luck.
Can you mail the djs file to supportteam@dj..com

thanks
Djuggler Support

Email sent

But may be this script have to execute at appropriate language version of Windows.

Thanks for the email.

We have found the problem. It only occurs when using HTML source instead of DOM source.
Apparently the HTML source is not always read as Unicode, depending on the original source of the page.
We will take the problem under investigation and aim for a solution in the next major release.

Thanks again for putting this to the attention of the development team.
Support Team.