Hello, August Abolins - Martin Foster.
On 9/28/20 12:19 AM you wrote:

Thanks for pointing that out. I recently paid closer attention to
what my online banking system uses, invoices, and what the gov't
prefers. Bank = dd/mm/yyyy. Statments = mm/dd/yyyy Gov't =
yyyy/mm/dd

Strange. In the US, most people and places use mm/dd/yyyy. In the
military, we used dd/mm/yyyy. I got used to it, which helped me later.
I worked in the oil and gas industry for years, and had communicated internationally a lot. Dates could have been confusing there.

If anything, we are conditioned to keep guessing what our reality
is. :( No wonder I am confused.
--
../|ug --- OpenXP 5.0.46 * Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)

--
Best regards!
Posted using Hotdoged on Android

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

Hello Chuck!

*** Tuesday 29.09.20 at 22:15, Chuck Pierson wrote to August Abolins:

[snip]

Strange. In the US, most people and places use mm/dd/yyyy. In the military, we used dd/mm/yyyy. I got used to it, which helped me later.
I worked in the oil and gas industry for years, and had communicated internationally a lot. Dates could have been confusing there.

Although I've lived in the UK all my life and was brought up to use the British date format(dd/mm/yyyy), I now much prefer to use the European
date format(dd.mm.yyyy).

Regards,
Martin

--- OpenXP 5.0.47
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** On Wednesday 30.09.20 - 09:18, Martin Foster wrote to Chuck Pierson:

Although I've lived in the UK all my life and was brought
up to use the British date format(dd/mm/yyyy), I now much
prefer to use the European date format(dd.mm.yyyy).

The "." vs "/" makes no difference to me. Albiet, I am partial
to the "." when illustrating a phone number (See the very top
of my biz website: https://ashlies.ca

When I worked in industry where the client was primarily the
military, the spec documents and other correspondences used
what I call the odemeter arrangement for the date:

yyyy mm dd, or yyyymmdd

That made the most sense for me. It was super easy to sort
files and instantly see the proper order of things.

--
../|ug

--- OpenXP 5.0.46
* Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)

Hello August!

*** Saturday 27.04.19 at 19:22, August Abolins wrote to Martin Foster:

For your perusal and comments/additions/corrections:
https://kolico.ca/fidonet/echos/points/

Thank you very much indeed for putting that up, much appreciated.
Where should we post our comments/additions/corrections :)

Oh.. this echo is probably fine for that. Or.. a netmail with "PRO" or "CON" somewhere in the Subject would get my attention too.

Can you please add the following:

Addition
========

[APoint] PROS
-------------
Supports Styled Text(Bold, Italic, Underlined)

Regards,
Martin

--- OpenXP 5.0.46
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** On Tuesday 22.09.20 - 14:02, Martin Foster wrote to August Abolins:

Addition
========

[APoint] PROS
-------------
Supports Styled Text(Bold, Italic, Underlined)

DONE.

The footnote [*8] has been added with your fix.

And I adjusted the date format on that table to dd/mm/yyyy

https://kolico.ca/fidonet/echos/points/


--
../|ug

--- OpenXP 5.0.46
* Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)

Hello August!

*** Sunday 27.09.20 at 09:21, August Abolins wrote to Martin Foster:

Addition
========

[APoint] PROS
-------------
Supports Styled Text(Bold, Italic, Underlined)

DONE.

Thanks for that.

The footnote [*8] has been added with your fix.

And for that.

And I adjusted the date format on that table to dd/mm/yyyy

https://kolico.ca/fidonet/echos/points/

Thanks for that also but take a close look at the month :-))

Regards,
Martin

--- OpenXP 5.0.46
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** On Monday 28.09.20 - 09:35, Martin Foster wrote to August Abolins:

And I adjusted the date format on that table to dd/mm/yyyy

https://kolico.ca/fidonet/echos/points/

Thanks for that also but take a close look at the month :-))

888888ba .88888. dP dP dP
88 `8b d8' `8b 88 88 88
88 88 88 88 88aaaaa88a 88
88 88 88 88 88 88 dP
88 .8P Y8. .8P 88 88
8888888P `8888P' dP dP oo


Thanks for pointing that out.

I recently paid closer attention to what my online banking
system uses, invoices, and what the gov't prefers.

Bank = dd/mm/yyyy.
Statments = mm/dd/yyyy
Gov't = yyyy/mm/dd

If anything, we are conditioned to keep guessing what our
reality is. :( No wonder I am confused.

--
../|ug

--- OpenXP 5.0.46
* Origin: ----------Do Not Fold, Spindle or Mutilate.---------- (2:221/1.58)

Hello Chuck!

** On Tuesday 29.09.20 - 22:15, Chuck Pierson wrote to August Abolins:

Thanks for pointing that out. I recently paid closer attention to
what my online banking system uses, invoices, and what the gov't
prefers. Bank = dd/mm/yyyy. Statments = mm/dd/yyyy Gov't =
yyyy/mm/dd

Strange. In the US, most people and places use mm/dd/yyyy. In the military, we used dd/mm/yyyy. I got used to it, which helped me later.
I worked in the oil and gas industry for years, and had communicated internationally a lot. Dates could have been confusing there.

I think yyyy/mm/dd makes the most sense. It resembles the way an odometer works or how any other click counter works, or how the incremental numbering system works in general.

I've worked with the MIL-STD docs for the Standard Electronic Modules Program (SEMP). That is where I first noticed the consistent and sensible use of dd/ mm/yyyy. (like an odometer in reverse)

Looking at some of those MIL-STD docs brings back a lot of memories. My work pertained to the electrical requirements of the modules. Start with MIL-STD 1389C and begin the journey of standard pointing to standard pointing to standard pointing to standard... (arghh)

--
../|ug

--- OpenXP 5.0.48
* Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)