-={ fredag, 02 oktober 2015, 11:56:37 +0200 }=-

Hey Holger!

 HG> A list of variables is included in the manual, but not as
 HG> comprehensive as the one you included.

It depends on the compiler, library and headers as well as how long ago the
program was compiled.  time.h doesn't stand still for no man.  :::snicker:::

In my particular case I am using glibc-2.22 for libs and headers which is as up
to date as it can be at this writing.  time.h is where the function strftime is
derived from and as far as I am aware is the same for many other platforms and
languages (C in my case) since the earth's crust first cooled early in the
Precambrian.  Heck even Python has a strftime function built into it to assist
the bogoLinux types such as the Debian crowd.  :::evil grin:::

 HG> To my knowledge only Sweden and Denmark use yyyy-mm-dd.

Nope.  It is a universally acceptable format especially when %T and %z are
tacked onto it.  In fact the RFC-3339 format encorporates yyyy-mm-dd (aka %F)
which is popular in email headers etc. for well over a decade now.  For example
my above date in RFC-3339 format would have been;

-={ 2015-10-02 11:56:37+02:00 }=-

Of course language makes no difference to the above format which helps when
debating universality and can be successfully used in all sorts of digital
communications these days without ruffling anyone who matters feathers any no
matter where in the world they are.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.3.42(1)-release (x86_64-unknown-linux-gnu)