From: kd4e <doc@kd4e.com>
To: pinozollo@gmail.com
Cc: ADIF <adifdev@yahoogroups.com>,
ham-linux@mailman.qth.net,
Debian Hams <debian-hams@lists.debian.org>,
Linux Hams <linux-hams@vger.kernel.org>
Subject: Re: [Ham-Linux] Proposal for coding in UTF-8
Date: Sat, 11 Jul 2009 15:17:44 -0500 [thread overview]
Message-ID: <4A58F368.5030802@kd4e.com> (raw)
In-Reply-To: <200907101616.26422.pinozollo@gmail.com>
Is this also compatible with CQRlog as well?
(Linux, MS, and maybe Apple, not sure.)
Pino Zollo wrote:
> 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
>
--
Thanks! & 73, doc, KD4E
FS/Swap/Wanted: http://kd4e.com/swapn.html
Free OS : http://www.PuppyLinux.com
Personal: http://kd4e.com
|_|___|_|
| | & | |
/\ {|
/ \ {|
/ \ {|
/ @ \ {|
| |~_|~~~~|
| -| | |
============\ # KD4E
Have an http://ultrafidian.com day!
next prev parent reply other threads:[~2009-07-11 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 20:16 Proposal for coding in UTF-8 Pino Zollo
2009-07-11 20:17 ` kd4e [this message]
2009-07-11 21:38 ` [Ham-Linux] " 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=4A58F368.5030802@kd4e.com \
--to=doc@kd4e.com \
--cc=adifdev@yahoogroups.com \
--cc=debian-hams@lists.debian.org \
--cc=ham-linux@mailman.qth.net \
--cc=linux-hams@vger.kernel.org \
--cc=pinozollo@gmail.com \
/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