Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Pino Zollo <pinozollo@gmail.com>
To: ADIF <adifdev@yahoogroups.com>
Cc: ham-linux@mailman.qth.net,
	Linux Hams <linux-hams@vger.kernel.org>,
	Debian Hams <debian-hams@lists.debian.org>
Subject: Proposal for coding in UTF-8
Date: Fri, 10 Jul 2009 16:16:25 -0400	[thread overview]
Message-ID: <200907101616.26422.pinozollo@gmail.com> (raw)

Hi de ZP4KFX

I propose to include into the standard the following tag for the header:

<ENCODING:5>UTF-8 

ENCODING can be absent or can be <ENCODING:10>ISO-8859-1

This is already implemented in my DBLog...see http://www.qsl.net/zp4kfx/Linux


http://www.qsl.net/zp4kfx/Linux/TestUTF8.html

http://www.qsl.net/zp4kfx/Linux/DBLog/Shot-QSO%20List-utf8-%20test.png

DBLog works on Linux and stores data's on PosgreSQL, both of which are UTF-8 
compliant.

DBLog can export both in ISO-8859-1 or in UTF-8.

Importing, if it  finds into the header <ENCODING:5>UTF-8  then does not do 
any coversion.
If it  finds  <ENCODING:10>ISO-8859-1 or no ENCODING tag, then converts into 
UTF-8.

The difference is mainly for the accented vowels (from 128 to 256) that come 
mainly by N1MM or Logger32 ADIF files.

Also other loggers could follow this method or be aware of the ENCODING tag to 
avoid errors.

Best 73 de

Pino ZP4KFX

-- 
Key ID: 0xF6768208 
Key fingerprint = B16D 0A7C 5B29 A334 CE6A  71F6 EAF8 3D88 F676 8208
Key server: hkp://wwwkeys.eu.pgp.net

             reply	other threads:[~2009-07-10 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10 20:16 Pino Zollo [this message]
2009-07-11 20:17 ` [Ham-Linux] Proposal for coding in UTF-8 kd4e
2009-07-11 21:38   ` Pino Zollo
2009-08-11 13:08 ` New FBB 7.04r2 release Bernard Pidoux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200907101616.26422.pinozollo@gmail.com \
    --to=pinozollo@gmail.com \
    --cc=adifdev@yahoogroups.com \
    --cc=debian-hams@lists.debian.org \
    --cc=ham-linux@mailman.qth.net \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox