Hello everybody!

According to the 3.00 doc's you can set a timezone, but when I try it catches it as an error. Is there a way to set the timezone?

Thanks,
RickV


--- SBBSecho 3.37-Win32
* Origin: Live Wire BBS [livewirebbs.com:1025] (1:154/110)

Hello RickV!

21 Apr 26 11:19, you wrote to All:

According to the 3.00 doc's you can set a timezone, but when I try it catches it as an error. Is there a way to set the timezone?

Using kludge (you see).

In bash I have something like:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

Hi Karel,

On 2026-04-22 14:55:24, you wrote to RickV:

According to the 3.00 doc's you can set a timezone, but when I try it
catches it as an error. Is there a way to set the timezone?

Using kludge (you see).

In bash I have something like:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3

I don't think that is necessary. On Linux and Windows, golded just gets the info directly from the OS...


Bye, Wilfred.

--- FMail-lnx64 2.3.3.1-B20260417
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

22 Apr 26 15:33, you wrote to me:

I don't think that is necessary. On Linux and Windows, golded just
gets the info directly from the OS...

This was not the question.

There are several reasons why it could be needed. (in my example, keeping OS in Datacentre somewhere, but using just Golded from Czech Republic)

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

Hello Wilfred!

22 Apr 26, Wilfred van Velzen wrote to Karel Kral:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3

I don't think that is necessary. On Linux and Windows, golded just
gets the info directly from the OS...

The line above IS the setting for the OS.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Karel!

23 Apr 26, Karel Kral wrote to Wilfred van Velzen:

There are several reasons why it could be needed. (in my example,
keeping OS in Datacentre somewhere, but using just Golded from Czech Republic)

I don't understand. No matter where the datacentre is, no matter where your golded runs, if you post a mail "now" the displayed time should be "now" and is the same. As a result the displayed time on a third system is the same.

Alas timezone handling isn't easy and there are still issues even in "latest" calendar software.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hi Kai,

On 2026-04-24 13:53:08, you wrote to me:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3

I don't think that is necessary. On Linux and Windows, golded just
gets the info directly from the OS...

The line above IS the setting for the OS.

In linux the timezone for the system is configured by /etc/localtime, which is symlink to /usr/share/zoneinfo/Europe/Amsterdam on my system.

You don't need the TZ variable, although that might still work for applications to overrule the system settings.


Bye, Wilfred.

--- FMail-lnx64 2.3.3.1-B20260417
* Origin: FMail development HQ (2:280/464)

Hello Kai!

24 Apr 26 14:01, you wrote to me:

I don't understand. No matter where the datacentre is, no matter where your golded runs, if you post a mail "now" the displayed time should
be "now" and is the same. As a result the displayed time on a third
system is the same.

In different words: I want to know - how "old" the message is.

Do not care about TimeZone of Sender, do not care about TimeZone of Operation system (usualy GMT or real placement) - I do care about my TimeZone.

I see then when message was created "at my time" - and read "at my time".

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

Hello Wilfred!

24 Apr 26 17:15, you wrote to Kai Richter:

You don't need the TZ variable, although that might still work for applications to overrule the system settings.

As we are in GOLDED echo = still works in Golded+ app.

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

Hello Wilfred!

24 Apr 26, Wilfred van Velzen wrote to Kai Richter:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3

I don't think that is necessary. On Linux and Windows, golded
just gets the info directly from the OS...

The line above IS the setting for the OS.

In linux the timezone for the system is configured by /etc/localtime, which is symlink to /usr/share/zoneinfo/Europe/Amsterdam on my system.

$ tail -n 1 /usr/share/zoneinfo/Europe/Amsterdam
CET-1CEST,M3.5.0,M10.5.0/3


Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Karel!

24 Apr 26, Karel Kral wrote to Kai Richter:

I don't understand. No matter where the datacentre is, no matter
where your golded runs, if you post a mail "now" the displayed
time should be "now" and is the same. As a result the displayed
time on a third system is the same.

In different words: I want to know - how "old" the message is.

Do not care about TimeZone of Sender, do not care about TimeZone of Operation system (usualy GMT or real placement) - I do care about my TimeZone.

I see then when message was created "at my time" - and read "at my
time".

And there is one of the problems with timezone handling - other people may want to know at which local time the message was created. It would feel strange to me if someone is writing his mails always between 0200 and 0500 in the night. ;-)

But your way is the actual recommended way for internatinal standards as i found on

https://www.w3.org/TR/timezone/

I'm not deep into the FTS and don't know which timestamps (of which timezone) are required to be set by FTS software.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hi Kai,

On 2026-04-25 12:20:02, you wrote to me:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3

I don't think that is necessary. On Linux and Windows, golded
just gets the info directly from the OS...

The line above IS the setting for the OS.

In linux the timezone for the system is configured by /etc/localtime,
which is symlink to /usr/share/zoneinfo/Europe/Amsterdam on my system.

$ tail -n 1 /usr/share/zoneinfo/Europe/Amsterdam CET-1CEST,M3.5.0,M10.5.0/3

So? My point is still valid, you don't need to set the TZ environment variable yourself...

Bye, Wilfred.

--- FMail-lnx64 2.3.3.1-B20260417
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

25 Apr 26 18:03, you wrote to Kai Richter:

Hi Kai,

On 2026-04-25 12:20:02, you wrote to me:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3

I don't think that is necessary. On Linux and Windows, golded
just gets the info directly from the OS...

The line above IS the setting for the OS.

In linux the timezone for the system is configured by
/etc/localtime, which is symlink to
/usr/share/zoneinfo/Europe/Amsterdam on my system.

$ tail -n 1 /usr/share/zoneinfo/Europe/Amsterdam
CET-1CEST,M3.5.0,M10.5.0/3

So? My point is still valid, you don't need to set the TZ environment variable yourself...

Bye, Wilfred.

I agree, but also the TZ is no longer available in GoldED.

RickV


--- SBBSecho 3.37-Win32
* Origin: Live Wire BBS [livewirebbs.com:1025] (1:154/110)

Hello Kai!

25 Apr 26 12:23, you wrote to me:

I'm not deep into the FTS and don't know which timestamps (of which timezone) are required to be set by FTS software.

Neither me. As FTS was there after TimeZone, I do believe that handling of zone is correctly prepared (in fido).

In Golded: still have one FidoPoint running in oracle's OCI Console (for free!) where TimeZone as a such can not be changed (easily). But you can always export TZ

In general: (my experience) - usualy I have there limits until when is expected to send answer. It helps me to know these points recalculated in one timezone (created, received, answered). Somehow got used to it.

To shared article: nice to read it. From my experience - the best was one Canadian-South Korean-Czech project. Where Canadian collegue claimed early morning calls, Korean-one late work (sometimes, ok - once ;-) - I was fine, eating lunch and listening

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

Hello Karel!

26 Apr 26, Karel Kral wrote to Kai Richter:

I'm not deep into the FTS and don't know which timestamps (of
which timezone) are required to be set by FTS software.

Neither me. As FTS was there after TimeZone, I do believe that
handling of zone is correctly prepared (in fido).

I have no idea what's going on in real. ;-)

Wasn't fido born before the public internet age?

My first contact with BBS around 1980 was via modem line and restricted to the local area due to modem/phone call costs. There was basically no need to take care of the timezone nor charset because the computer was simply set to the local ones and data never leaved the system. I can't remember i ever had to select my timezone when in logged into a BBS so i think they operated with their local time. Then there was fido and BBS started exchanging fido mail between timezones and as a part of progression the timezone handling was needed for fidonet software.

Today i don't want to bother anyone but i doubt that all fidonet software can handle timezones corretly.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Wilfred!

25 Apr 26, Wilfred van Velzen wrote to Kai Richter:

set TZ=CET-1CES,M3.5.0/2,M10.5.0/3

The line above IS the setting for the OS.

In linux the timezone for the system is configured by
/etc/localtime, which is symlink to
/usr/share/zoneinfo/Europe/Amsterdam on my system.

$ tail -n 1 /usr/share/zoneinfo/Europe/Amsterdam
CET-1CEST,M3.5.0,M10.5.0/3

So? My point is still valid, you don't need to set the TZ environment variable yourself...

I haven't installed an OS lately so i don't know if the TZ is set by geo-IP location now. As far as i remember i always had to tell an OS during installation which timezone it is and that way i set the TZ variable via the installer zoneinfo setup.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)