Lines Matching refs:date
2203 # some sort of date code instead of the two zero bytes at 6 and 7
2276 >>8 byte&0xF0 0x30 \b, root type: date
2868 >22 string X -- out of date
5718 # on 11th line date inside c-comment like: Thu Jun 4 22:25:19 2015
7258 # f_timdat - file time & date stamp only for little endian
8191 # TODO: Release date, device information, region code, others?
8217 # TODO: Release date, device information, region code, others?
9462 >>>>>>>>>>>>1 ubyte x \b, update-date
9463 >>>>>>>>>>>>1 use xbase-date
9492 >>>>>>>>>>>>>>1 ubyte x \b, creation-date
9493 >>>>>>>>>>>>>>1 use xbase-date
9494 >>>>>>>>>>>>>>44 ubyte x \b, update-date
9495 >>>>>>>>>>>>>>44 use xbase-date
9586 # test and print the date of xBase .DBF .MDX
9587 0 name xbase-date
10227 >22 string X -- out of date
10969 #>4 date x stamp %s
10974 #>4 date x stamp %s
14557 # quarantined date
16481 # skip invalid date 0 like in linearSRGB.icc
16788 # date
19949 >>>>>&0 bedate x \b, date=%s
21331 # additional check for creation date after 1 Jan 1970 ~ 7C25B080h
21394 # creation date in seconds since MacOS epoch start. So 1 Jan 1970 ~ 7C25B080
21397 >91 ubelong <0x7c25b080 INVALID date
21399 # last modified date
21673 # only the creation date is local time, all other timestamps in HFS+ are UTC.
21867 # TZ=GMT date -d '1989-12-31 0:00' +%s
21935 >0x39 use garmin-date
22021 # display date stored inside Garmin maps like yyyy-mm-dd h:mm:ss
22022 0 name garmin-date
22049 >>>0x0E use garmin-date
22061 >>>0x0E use garmin-date
22099 >>>0x0E use garmin-date
22110 >>>0x0E use garmin-date
22136 >>>0x0E use garmin-date
22226 # build date like: Oct 25 1999, Oct 1 2008, Feb 23 2009, Dec 15 2009
22566 >>&32 string x \b, date %15.15s
22570 >>&32 string x \b, date %15.15s
22574 >>&32 string x \b, date %15.15s
22578 >>&32 string x \b, date %15.15s
22582 >>&32 string x \b, date %15.15s
22586 >>&32 string x \b, date %15.15s
22590 >>&32 string x \b, date %15.15s
22594 >>&32 string x \b, date %15.15s
22598 >>&32 string x \b, date %15.15s
23798 # date of last change MM/DD/YY
23800 # creation date MM/DD/YY
24572 # date stamp for file
24573 #>10 uleshort x \b, date 0x%x
24676 # plausibility check for date
24998 >>>>>>>>>>>>>>>0x002B ubyte&0x70 0x00 \b, date format=Y-M-D
24999 >>>>>>>>>>>>>>>0x002B ubyte&0x70 0x10 \b, date format=M-D-Y
25000 >>>>>>>>>>>>>>>0x002B ubyte&0x70 0x20 \b, date format=D-M-Y
26643 # date is supposed to be big-endian seconds since 1 Jan 1904, but many
27488 # containing version, creation date, and purpose
29886 # \001c date and time created 87/09/23 08:09:20 by ian
29991 # uppercase letters. However, examples have been seen without the date string,
32367 >12 byte >0 Revision date %02x
33382 # it. The interesting value is the cvs date (8 digits decimal).
33750 # check and then display version and date inside MS Windows HeLP file fragment
33751 0 name help-ver-date
33770 # GenDate often older than file creation date
33794 >>>>>&0 use help-ver-date
33798 >>>>>>>&0 use help-ver-date
33801 >>>>>>>>>&0 use help-ver-date
33804 >>>>>>>>>>>&0 use help-ver-date
33807 >>>>>>>>>>>>>&0 use help-ver-date
33810 >>>>>>>>>>>>>>>&0 use help-ver-date
33814 >>>>>>>>>>>>>>>>>&0 use help-ver-date
35106 # Then the build-date
