Proposal for coding in UTF-8
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
Signature · 3 lines
Key ID: 0xF6768208 Key fingerprint = B16D 0A7C 5B29 A334 CE6A 71F6 EAF8 3D88 F676 8208 Key server: hkp://wwwkeys.eu.pgp.net
Is this also compatible with CQRlog as well?
(Linux, MS, and maybe Apple, not sure.)
Quoted 30 lines · Pino Zollo
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
Signature · 14 lines
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!Il sabato 11 luglio 2009 16:17:44 kd4e ha scritto:
Quoted 2 lines
Is this also compatible with CQRlog as well?
(Linux, MS, and maybe Apple, not sure.)
I don't know....
If a logger receives an UTF-8 adif file and does not how to handle it will bounce a lot of errors...
If a logger receives an ISO-8859-1 adif file and ignores the tag all will be OK .
At present only DBLog knows what to do of the ENCODING tag.
73
Pino ZP4KFX
Quoted 37 lines
Quoted 35 lines · Pino Zollo
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/Linuxhttp://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
Signature · 3 lines
Key ID: 0xF6768208 Key fingerprint = B16D 0A7C 5B29 A334 CE6A 71F6 EAF8 3D88 F676 8208 Key server: hkp://wwwkeys.eu.pgp.net
New FBB 7.04r2 release
In reply to Pino ZolloHi FBB sysops and users,
I published a modified version of FBB BBS 7.04r2 with
small changes to reduce both debug verbose output /var/log/fbb.log (optional) and more importantly, CPU load.
Observed xfbbd CPU load was 7-14%, sometime peeking
even higher.
It is now less than 1%.
This patch has been backported to versions 7.04o2 and 7.04p2
Here are two important recommandations : boot kernel in
single processor mode (online grub command : nosmp) On 64 bit systems, add N 1 parameter in forward script to preclude forward compression.
Read more here : http://rose.fpac.free.fr/MINI-HOWTO/
FBB source package may be downloaded from :
http://f6bvp.free.fr/logiciels/BBS-f6fbb/xd704r2-src.bz2
Version 7.04 is still under debugging phase, with latest intermediary versions 7.04s.nn
73 de Bernard, f6bvp