ISO 8601 formatting in 2.3.17: will it be OK this way?
Since 2.3.17 is due within 22 hours or so, this is the last chance to
tell your requirements regarding this.
See the ?iso... built-ins below (this is the test case BTW).
- The meaning of things after iso_... are:
- utc: use UTC "time zone"
- local: use the value of the time_zone setting of FreeMarker
- ms: millisecond accuracy (the default is second accuracy).
This will show "fraction seconds", not really milliseconds.
So 00:00:00 plus 200 ms looks like "00:00:00.2",
00:00:00 plus 230 ms looks like "00:00:00.23",
00:00:00 plus 0 ms looks like "00:00:00", etc.
- m: minute accuracy (the default is second accuracy)
- h: hour accuracy (the default is second accuracy)
- nz: don't show time zone (UTC offset, actually). Note that
date-only formats never show the time zone, since ISO
8601:2004 doesn't mention that it's allowed (right?).
- If `d` below was a javax.sql.Date or javax.sql.Time, the ?date or
?time part would be redundant, as FM will detect what it is.
- `javaUTC` and `javaGMT02` are java.util.TimeZone objects dropped into
the data-model, not strings.