Hi all,
I'm new to CQRLOG. I'd like to test and compare it with my nowadays log program jLog and I have several questions about it:
1- In CQRLOG I can't see any QSO field about contest like ADIF-compliant jLog field CONTEST_ID (i.e. EA-DME). I only see a contest window but I'm afraid it's for hot contest work and not for include contest info about a QSO entry after contest finished. How can I do this here?
2- There's USERDEFn fields in ADIF to define your own fields but I don't know if CQRLOG supports them.
3- I'm trying to import an ADIF file exported with jLog and CQRLOG can't do very well: it reports that only 3 records were imported but nothing appears imported. I'm afraid that jLog ADIF files contain lowercase tags and CQRLOG maybe expects uppercase tags, isn't it or maybe a bug?
Thanks all. 73.
Hi,
as far as I know recent version of cqrlog has contest_id field.
CQRLOG uses user defined ADIF fields to store it's own data. Common user defined fields are not supported. It's really hard to think about UX, because CQRLOG is getting more complex and we have to take care about UX.
Could you send me the adif file, please? CQRLOG can handle tags in uppercase or lowercase, the problem will be with something else. My email is petr@ok2cqr.com.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Thanks for your help. I've sent you the conflicting ADIF file by mail.
Regards.
Hi!
1) When you open "contest" window you should see "extension" in NewQSO window (make it wider) were the contest information is shown.
How ever NewQSO window is not meant for entering contest qsos. It is there if you need to edit already logged contest qsos.
The contest ID (we call it contest name) is shown there, and also in "contest" window itself.
If you have tried to type into "Contest name" you find out that it offers several contests built in but that this field is a free type field and you can put what ever you prefer there. It will be exported using CONTEST_ID tag in adif import.
2) if you desperately need an adif tag that does not exist you can enter your values to "Comments to qso" field and after adif export open the adi file with text editor and replace tag name "COMMENT" with text editor's replace command (witout touching the lenght of tag ":nr" I.E : <COMMENT:4>Test )
--
Saku
OH1KH
Thanks for your replies. I'd try to answer you when my time lets me.
Here is a screenshot of a test with contest info but I can't see any "extension" of contest information in NewQSO window ... I entered some info about a contest in the Contest window and I exported later into ADIF file but I can't see any CONTEST_ID info. Maybe I have a missconcept about contest info can entered into a QSO record.
Thanks.
File:
Hi!
From picture I can see that you are running 2.3.0(001). That is very old.
Please install the latest version 2.4.0.(001) then we are talking about same things.
--
Saku
OH1KH
Thanks again for your help.
First of all I installed 2.4.0 release (I'm working on Debian Testing and I like to work with official repository releases of software but in this case I need contest functionality that it doesn't come with 2.3.0 releases).
From "SQL console" in CQRLOG I have to extend "remarks" field in MySQL database from 200 to 500 characters (for example) to import correctly (thanks to OK2CQR).
Now I've observed another some issues when importing ADIF:
- "contest_id" ADIF tag is imported succesfully into "contestname" database field but "credit_granted" or "credit_submitted" ADIF tags cannot be seen in database (they supposed to be "stx", "srx", "stx_string" and "srx_string" in database). So I can't find them in Contest section from a QSO window.
- Some "name" and "qth" fields are misteriously 1, 2 or 3 characters right-trimmed but I can't see any import database issues about that and these fields are correct in ADIF file.
Thanks in advance. Regards, 73.
Hi!
If you have extended "remarks" and imported qsos be aware that you need to change also "NewQSO/Comment to qso" field MaxLength and recompile cqrlog.
Otherwise if you ever edit and save your imported qso your "comment to qso" ("remarks" in database) will be cut to 200 characters !
Please read again specifications https://adif.org/310/ADIF_310.htm#QSO_Fields
"credit_granted" or "credit_submitted" has nothing to do with contest tags. They are tags "stx", "srx", "stx_string" and "srx_string" in adif specifications as in database columns, too.
This is mentioned in HELP/OPERATION/NewQSO:
If you open "contest" window then you will see contest messages also in "NewQSO" window. They may be under "DXCC info" part, so make NewQSO window wider horizontally.
The contest part of NewQSO is meant only for editing already logged qsos if needed. (for some unknown reason !?)
Do not try to use it for logging contest qsos. It works, but is not user friendly in any way.
Right trimming may be caused (perhaps?, just a guess, never seen that...) when name or qth has some special character like üõ or similars.
--
Saku
OH1KH
Hi,
I'll take into account the "remarks" field lenght to avoid compile CQRLOG but I'm afraid that I have to do it.
About contest fields I'll try to put in order my ideas and missconcepts about contest information in an ADIF file. jLog exports contest information in a different fashion and I'll try to adapt it to CQRLOG to import correctly. Sorry for my confusion.
About characters right-trimming is effectively happen when a field contains characters like ñáéíóú or simmilar. It maybe happens due to UTF-8 conversion. I'll try to review it.
Thanks again for your support.
Regars, 73. Vic. EA4GRG.
Hi Vic!
Also with extended remarks:
In NewQSO you can not even see the part that goes over 200 chrs without setting new value of MaxLength. How ever extended part staus there in database if you do not save NewQso again (edit view).
With ADIF we have tried to follow the specification from adif.org
Right trimming seems to happen only in ADIF import. I did not get it happen, but importing those special chars caused extra "<" for me. I will open issue from this.
--
Saku
OH1KH
Hi,
I've downloaded source code and modify it to extend 'remarks' until 500 chars max in form control, comment and database create table sentence. I installed it and import and works fine (I'd like to generate a deb package too but I don't know how to make it).
About right trimming I realize that also happen in 'Comment to QSO' field also QTH and Name fields and it apparently happens at import time. I note there are the same missing right characters as many special characters in the field like ñáÁéÉ ...
For example:
Original ADIF tag: "Hola más ñoño saludos y gracias"
In CQRLOG: "Hola más ñoño saludos y grac"
Thanks again. 73.
Ok!
Now you can use Comment to qso/remarks without worries. How ever it is not standard and so logs are not transferable to other cqrlogs.
But that is the great thing in open source software; You can modify it by your own needs.
Importing special characters is a problem. And it will exist on all fields of cqrlog.
There is no other well working way than user check before import.
Fortunately linux has tool for that. https://www.shellhacks.com/linux-check-change-file-encoding/
Cqrlog expects UTF-8
First check adif file with "file -bi in.ADI" then change it to utf-8 if needed with "iconv -f utf-8 -t YourCharCode -o out.ADI in.ADI"
To make things easier in future it could be good to change system character code to utf-8 if it is not.
--
Saku
OH1KH
Hi,
jLog exports adif file in iso-8859-1 encoding. I converted it with iconv command also KWrite save-as-encoding command. In both cases the converted adif file is in utf-8 encoding and it's perfectly readable in any text reader application but CQRLOG import cuts ending characters notwithstanding it shows special characters fine.
Regards.
Hi!
Could you send a short export (1-3 qsos) that include those name/qth that are causing problems. Either upload with your message here (change .ADI to .txt) or send to my email.
mycallsign at sral fi.
We do not have those characters in Finnish (just äöå) and I would like to test a bit with original iso-8859-1 export that is known to cause problems.
--
Saku
OH1KH
Ok,
I'm sending you both ADIF files with a test fake QSO by mail. We have several special characters in spanish too: ñÑáÁéÉíÍóÓúÚüÜ
If I import in iso-8859-1 into CQRLOG spanish characters appears like <?>
Thanks.
Thanks!
I will study them.
In brief test I noticed that cqrlog will cut as many characters from end as there are those special characters.
How ever if I open qso for edit and add dropped characters back, save qso, do export with cqrlog, delete qso and import it back again everything works perfect without cutting.
The difference lays here
jlog: <qth:19>El Campello (Ávila) <
cqrlog:<QTH:20>El Campello (Ávila)<
jlog leaves 1 space to end of tag string, cqrlog does not. That does not matter.
But cqrlog counts tag having 20 chars as jlog counts them as 19. That matters !
jlog counts true visible charcters to length of tag. Cqrlog counts bytes in string where Á represents then as 2 characters.
Fixing this causes all cqrlog exported adifs fail to load back if they have special characters somewhere and this would be fatal for many users.
Adif standard must be studied to see what it says about this.
More tests should also be done what happens when cqrlog exports to LoTW or other places. Can they accept less characters then tag length says?
--
Saku
OH1KH