Subj : JS Object save_msg()
To   : Digital Man
From : deon
Date : Wed Dec 18 2024 15:42:12

  Re: JS Object save_msg()
  By: Digital Man to deon on Tue Dec 17 2024 05:36 pm

Howdy,

 > What do you have set in SCFG->System->Local Time Zone? This is the default
 > time zone information used by MsgBase.save_msg() and stored in the message
 > header (if not otherwise specified in the message header object).
 >
 > It should be storing whatever you have configured in SCFG->System->Local
 > Time Zone.

OK, it is UTC in there.

So this just is confusing, and IMHO messed up. I must have the wrong impression of Syncs timezone handling.

If you dont supply a datetime stamp (via any of the header save attributes that have a date/time), and Sync "figures it out" why cant it figure out the timezone of that time it gets as well?

Sync obviously knows the time zone - given that it displayed that message, that it saved 3s earlier with a "UTC" timezone as "11 hrs from now". Its not using that System->Local->Time Zone when displaying the message?

I think it can be improved, but if I'm wrong, I'd like to understand why my
thinking is wrong...

Oh, and there *is* a problem with strftime(), but it may not be SBBS related.

2-3 hrs ago, my test script:

writeln(strftime("%a, %d %b %Y %I:%M:%S %z",time()));

was returning a correct date/time and timezone information - had me baffled, especially after I posted yesterday.

Now, its out again by 12 hrs:
> date
Wed Dec 18 15:26:39 AEDT 2024

> jsexec ansitex/tools/test-strftime.js
Wed, 18 Dec 2024 03:27:19 +1100

Its out by 12 hrs, as it should be Wed, 18 Dec 2024 15:27:19 +1100

> php tools/test-strftime.php
Wed, 18 Dec 2024 03:27:19 +1100

This has got me stumped.


....лоеп

---
 ю Synchronet ю AnsiTEX bringing back videotex but with ANSI
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.