POCSAG/DAPNET still issues with ROT1 encoded messages and "umlauts"

boris75

POCSAG/DAPNET messages are still not fully "decoded" if they are encoded with ROT1 with latest beta firmare.

Example:
Incoming - 1*Qfhfm.Mplbm - stays encoded in the openspot backend

Umlaut-Encoding seems not to work (I don't know if this is an encoding-issue with UTF8 or whatever),

outgoing msg from the backend: aou äöü ÄÖÜ will be transferred to aou - {|} []

HA2NON

POCSAG does not support UTF8, only plain ASCII

boris75

Hm, ok. Some hardware-vendors are replacing the characters for the umlauts like here, maybe this is interesting for you to fix the umlaut problem if the customer is for german market:

https://github.com/DecentralizedAmateurPagingNetwork/Core/issues/143

incoming character for german device setup (idea):

Mapping table:

@ §
[ Ä
\ Ö
] Ü
{ ä
| ö
} ü
~ ß

Any plans for better ROT1 decoding? I assume that DAPNET may play a bigger role in the near future and Openspot is a perfect device for it.

Thanks for your time I really appreciate that.

Tyrbiter

POCSAG is a 1981 spec, developed from 1976 on. UTF-8 didn't exist until 1992 so making DAPNET compatible with it is not at all easy, it would need escape sequences for non-ASCII characters and a means of specifying a codepage.

Sounds like a fun project, animated GIFs are next!

boris75

ISO 8859-1 or so?