Hello Dear OMs,
Here is the first step in the project of internationalising the outback comms series of apps (AndPskmail, RadioMsg and jPskmail).
The RadioMsg app was already capable of handling (as in transferring) the UTF-8 character set, but not AndPskmail, and jPskmail was only partially handling it.
The next step will be to internationalise the GUI texts in the apps themselves. This is already done in the Java app jPskmail, but not in the Android apps.

In the mean time if you could test the matched pairs of beta apps listed below it will help validate the changes:

1. AndPskmail for Android now handles messages, emails headers and bodies and web pages containing UTF-8 characters. It also means that emojis can now be transferred and displayed. The app to install is at the following link: https://bitbucket.org/VK2ETA/andpskmail/downloads/

2. jPskmail for Windows/Linux. The beta file is not a full install file. So assuming you have already installed jPskmail with the version 3.1.7 installer, just download the beta file and rename it to jPskmail.jar. Copy over the current file located in the installation folder. Web location: https://bitbucket.org/VK2ETA/javapskmailserver/downloads/

Changes:
Transfer and display of the full UTF-8 character set, in both compressed and un-compressed methods.

Note: in AndPskmail the compression flag is set in Settings/Data Exchange/Compressed Data Exchange. In jPskmail it is set in Preferences/Configuration Tab/Compressed Data. The client dictates if the exchange is compressed or not.

All the best.

73, John (VK2ETA)

Following the list of issues documented by Dr Ievkov, there is a new version of jPskmail: V3.1.8.4

Web location: https://bitbucket.org/VK2ETA/javapskmailserver/downloads/

The beta file is not a full install file. So assuming you have already installed jPskmail with the version 3.1.7 installer, just download the beta file and rename it to jPskmail.jar. Copy over the current file located in the installation folder.

Issues addressed:
A. Bug fix: "I don't understand "~SEND" reply when requesting Grib files

B. Bug fix: When using virtual mail boxes, grib file replies would not be visible to the requester due to the reply coming from a different email address.

C. Bug fix: Endless reties of some data frames due to the presence of control characters not processed on the Rx side ("0x0D" is ignored). This also resulted in corrupted multibytes UTF-8 characters in emails and web pages.

Issues 3,4 and 9 have not yet been looked at yet (multiple QTC 0+ requests, Email Delete not keeping local header list synchronised and server not sending its own APRS beacon)