[aprssig] Unicode in APRS messages
andrewemt at hotmail.com
Sun May 11 08:17:33 CDT 2014
YAAC supports UTF8 and Unicode, and I18N (internationalization); if the user types in a message string using characters not in the base 7-bit ASCII character set, YAAC will send it as UTF8, and decode received UTF8 properly (callsigns are restricted to 7-bit ASCII due to the AX.25 specification). Note that this should even work if you are using AGWPE as the TNC for YAAC (since YAAC is what is actually rendering the strings, not the AGWPE server daemon).
Alas, I don't speak any other languages well enough to actually create the alternate localized (L8N) prompt string files for YAAC. :-(
Andrew Pavlin, KA2DDO
author of YAAC ("Yet Another APRS Client")
> Date: Sun, 11 May 2014 08:10:19 +0200
> From: info at sartrack.co.nz
> To: aprssig at tapr.org
> Subject: [aprssig] Unicode in APRS messages
> I am currently adding internationalisation to my SARTrack program (
> http://www.sartrack.co.nz ), and have volunteers in various countries
> doing translations for me.
> Up to this point, I never attempted to use Unicode for APRS messaging
> during transfer via APRS servers.
> I have now added UTF8 encoding/decoding to the TCP interface... And this
> works perfectly when I use my own program, while testing on a 'aprsc'
> based server. Russian and other languages with 'funny' characters now
> come out correctly on the other side.
> However, when I tested it with the APRS client 'AGWTracker', garbage
> came out.
> I would like to know how other APRS clients deal with this issue, and
> what Encoding (if any) is being used to transfer Unicode APRS packets
> over TCPIP.
> And how this type of data is dealt with, when it must be transfered over
> the radio, as this is obviousely ASCII/ANSI based...
> Bart ZL4FOX / PA2FOX
> SARTrack Developer and CEO
> aprssig mailing list
> aprssig at tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aprssig