forums.silverfrost.com

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

We try to make use of UTF-8 encoded character strings in wini0@ calls and in write statements using ftn95 version 7.10.

We have observed the following problems.

1) The German character "ö" is not displayed correctly in a winio@ call displaying a menu item. However, the German characters "ä","ü","Ä","Ü" and "Ö" are displayed correctly in the same situation. In the error case of character "ö" blanks are displayed in the menu item.

2) We run into problems when trying to make use of write statements displaying UTF-8 characters, if no winio@ call has been executed before the write statement. In case of having executed a winio@ call before the first write statement the write statements work fine.

Please use the url following to get an image with more informations

http://www11.pic-upload.de/06.10.14/akw991qhnde.jpg

Regards,
Dietmar

PaulLaidler · Posted: Mon Oct 06, 2014 7:03 pm Post subject:

I have logged this for investigation.

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

Paul,

how do you proceed with the investigation?

We are interested in moving our complete code basis to UTF-8 code but as long as these bugs exist we will not do so.

Do you have an idea when we could expect an update where these UTF-8 problems are fixed?

Kind regards,
Dietmar

PaulLaidler · Posted: Tue Dec 02, 2014 1:23 pm Post subject:

Dietmar

We are working flat out on the port to 64 bit at the moment,
so I am not able to give you a firm date for this.
Hopefully it will all be sorted before the end of the first quarter of 2015.

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

Paul,

we observed another problem in this context:

we would like to enter UTF-8 characters using the winio format string %rs.
We currently enter the UTF-8 characters by Copy &Paste from another document. In our example we use Chinese characters for copying to the %rs box. The buffer of the %rs box will contain characters '?' for the Chinese UTF-8 characters copied. We would have expected that the buffer contains the UTF-8 code of the Chinese UTF-8 characters.

We have created a picture you may refer to by the link:

http://www11.pic-upload.de/19.12.14/gt1ljpr8tj9m.jpg

The first and second line of this picture refer to the %rs box after copying the Chinese characters. The first line contains the contents of the buffer (no Chinese characters) whereas the second line contains Chinese characters int the %rs box. For control reasons we have added a test string "test" left to the Chinese characters.

We have read in the UTF-8 documentation about problems in this context concerning the %eb box, but nothing concerning %rs boxes.

Do we have a chance to bypass this for %rs boxes or is there a general problem concerning user supplied UTF characters to %rs boxes, as well?

Regards,
Dietmar

PaulLaidler · Posted: Mon Dec 22, 2014 8:09 pm Post subject:

I don't have an immediate answer to this query. I will try to find some time to look into it.

PaulLaidler · Posted: Wed Jan 21, 2015 4:07 pm Post subject:

Dietmar

I have looked briefly at these issues today and it would be a great help if you could supply some short sample programs, one for each issue raised.

PaulLaidler · Posted: Wed Jan 21, 2015 4:21 pm Post subject:

The following program works OK for copying characters from the "Character Map" utility.

PaulLaidler · Posted: Wed Jan 21, 2015 4:56 pm Post subject:

It turns out that you don't need the call to enable_utf8@ in the above sample.

ClearWin+ just uses the standard Microsoft edit control and pasting is done by the API. This means that it is basically a Microsoft issue.

If I can find any further information on the Internet then I will let you know.

mecej4 · Joined: 31 Oct 2006 Posts: 1886

Paul wrote "but there are no Chinese characters in this utility". In order to get some characters displayed properly in CharMap, you need to first select (inside CharMap) a font that contains those characters. For example, choosing Arial Unicode MS will enable you to select Chinese PinYin characters which, when copied and pasted into the box displayed by running the example program shown above, are displayed correctly.

PaulLaidler · Posted: Wed Jan 21, 2015 10:38 pm Post subject:

Many thanks for the information.

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

Paul,

the code following is an example of what goes wrong to our opinion. It is your example slightly modified.

PaulLaidler · Posted: Thu Jan 22, 2015 4:11 pm Post subject:

Thanks for the sample. I can now see what is expected.

PaulLaidler · Posted: Thu Jan 22, 2015 5:33 pm Post subject:

I have not found a way to copy Chinese characters from the input edit box to the read-only edit box. ClearWin+ uses WM_GETTEXT which is equivalent to GetWindowText and this works fine for other UNICODE characters but not for Chinese characters.

Can you explain the wider context of what you want to do? There may be some other way to get the characters. For example, they may be accessible directly from the clipboard.

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

Paul,

our intent was to show that buffer txt does not contain the Chinese characters although we thought it should. Instead txt contained 2 characters '?'. This is the first line of the picture referred to by the web link of our previous post. We need the correct Chinese UTF values in the buffer because in our main application which we want to move from ASCI to UTF characters we would like to process the UTF characters in further parts of the code.

Here is another example which writes a text file containing the buffer txt without Chinese characters after having pasted the Chinese characters to the edit filed.