Re: [Xlog-discussion] Import from Logger32.adi

[JACrux]

Thanks for that Arne

I think your message did not go to the Xlog group so I include it below.
Why does anyone need to log time in seconds  ??? .... I have never used 
seconds because my watch and my pc clock are never that accurate; I need to 
check against the atomic standard time from MSF. Then I reset the pc time. 
(My shack pc runs 24/7.)

Maybe my previous analysis was not very clear. I checked again and
Logger32 always outputs six digits for the TIME part of the ADIF file. I can 
see that when I look at the exported file structure. I do not know how to 
change that because Logger32 does not have any built-in option to change the 
exported format from six digits to four. If it did, there would be no 
problem. 
(Also if Xlog could be asked to ignore the last two time digits, there would 
be no problem, but I think it is better to be able to make the choice in the 
ADIF log source programme.)
 
Logger32 can be setup to display TIME as 2359, or 23:59. But you can also 
choose to display a six digit time, including seconds. 23:59:15 would be 
acceptable, or 2359:15, or 235915. But if you do decide to display only a 
four digit time like 2359, Logger32 still adds 00 seconds to every four digit 
HHMM time when it exports the log in ADIF format. 2359 is always exported as 
235900. (That does not look good to me in a logbook; 23:59:00 would be easier 
to understand.)

Xlog sees the added 00 seconds and displays them as part of a six digit time 
display, with no punctuation, as 235900.  
The only easy answer is to edit the Logger32 ADIF file,  by substituting 
<TIME_ON:4> for <TIME_ON:6>  for every TIME entry in the entire log.  Then 
Xlog sees the time format is only 4 digits long and it ignores the last two 
digits in the Logger32 ADIF TIME data.  It works for me anyway.
 
The all-black callsign column is much less easy to work around.  
The really good news is that Xlog works so well and that it is only a weird 
UTF8 language problem that makes things difficult on my dual boot Win2k/SuSE 
9.3 machine. 
73 John G3JAG

 
On Friday 26 August 2005 11:48, you wrote:
> Hello Xlog group
>
> ADIF spec for TIME
>
> A time specification. May be 6 characters long (HHMMSS) if seconds are
> included, 4 characters (HHMM) if seconds are not included. Time is in
> 24-hour format, from 0000 to 235959. A zero-length field or omission of the
> field indicates an empty time value.
>
> Most of the hams in EU are using 24-hour format. 6 characters
>
> I think the problem is that Xlog dont accept more than 4 characters during
> import.
> Xlog must follow the ADIF spec. What you see in the log is a different
> thing.
> Logger32 is using the correct standard. Most of the problem is export and
> import
> between different logging program. They dont use the ADIF standard.
>
> 73 de Arne/SM5CNQ
>
>
> ----- Original Message -----
> From: "JACrux" <address@hidden>
> To: <address@hidden>
> Sent: Friday, August 26, 2005 8:15 AM
> Subject: [Xlog-discussion] Import from Logger32.adi
>
> > Thanks for the advice regarding the six digit time format used in the
> > ADIF file exported from Logger32.  I cannot find any way to make Logger32
>
> export
>
> > exactly what is used in the Logger32 TIME columns - it always exports 6
> > digits even if you select the "2359" time display format.
> > So I edited the entire 22000 QSO ADIF file with WordPad, replacing
>
> TIME_ON:6
>
> > by TIME_ON:4. Then I replaced TIME_OFF:6 by TIME_OFF:4. It took quite a
>
> long
>
> > time ...... but now xlog reads the ADIF file and displays the 4 digit
>
> time.
>
> > Updating the log will be easier; I need only edit the new QSO data
>
> exported
>
> > from Logger32 before merging the logs.
> > I don't think this is a UTF8 problem. At present, Logger32 cannot be set
>
> up to
>
> > adjust the exported TIME column width to reflect the time format selected
>
> by
>
> > the user.
> >
> > Now I suggest that xlog (perhaps only for me !) would look nicer if
> > GMTEND
>
> can
>
> > be changed to OFF, so the column width is the same as GMT ..... maybe not
> > good for everyone. Note: here in UK we are supposed to log QSO end time.
> > Also, can the UNKNOWN entries be customised (or even left out) ??
> >
> > Yes, the UTF8 problem that causes that black callsign column is still
>
> there. I
>
> > need to find out how to fix it and I have not much idea where to start.
> > Maybe I need a brain import ?
> > 73 John G3JAG
> >
> >
> >
> > _______________________________________________
> > Xlog-discussion mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/xlog-discussion