wader/fq
1
1
Fork 0
mirror of https://github.com/wader/fq.git synced 2024-12-28 08:02:28 +03:00
Code Issues Projects Releases Wiki Activity
4b0018f70a
fq/format/tzif/testdata/GMT-3.fqtest

58 lines
5.8 KiB
Plaintext
Raw Normal View History

support tzif (time zone information format)
2022-12-01 15:44:57 +03:00
$ fq -d tzif dv GMT-3
interp: Change bit ranges to use exclusive end All other ranges and slicing uses exclusive end so i think it make sense to make it consistent. Update docs and add additional example for non-byte-aligned field. Also fixes issue showing zero bit ranges as start-NA.
2023-10-20 16:08:14 +03:00
|00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f|0123456789abcdef|.{}: GMT-3 (tzif) 0x0-0x75 (117)
| | | v1header{}: 0x0-0x2c (44)
0x00|54 5a 69 66 |TZif | magic: 0x545a6966 (valid) 0x0-0x4 (4)
0x00| 32 | 2 | ver: "2" (0x32) (valid) 0x4-0x5 (1)
0x00| 00 00 00 00 00 00 00 00 00 00 00| ...........| reserved: raw bits 0x5-0x14 (15)
support tzif (time zone information format)
2022-12-01 15:44:57 +03:00
0x10|00 00 00 00 |.... |
interp: Change bit ranges to use exclusive end All other ranges and slicing uses exclusive end so i think it make sense to make it consistent. Update docs and add additional example for non-byte-aligned field. Also fixes issue showing zero bit ranges as start-NA.
2023-10-20 16:08:14 +03:00
0x10| 00 00 00 00 | .... | isutcnt: 0 0x14-0x18 (4)
0x10| 00 00 00 00 | .... | isstdcnt: 0 0x18-0x1c (4)
0x10| 00 00 00 00| ....| leapcnt: 0 0x1c-0x20 (4)
0x20|00 00 00 00 |.... | timecnt: 0 0x20-0x24 (4)
0x20| 00 00 00 01 | .... | typecnt: 1 0x24-0x28 (4)
0x20| 00 00 00 04 | .... | charcnt: 4 0x28-0x2c (4)
| | | v1datablock{}: 0x2c-0x36 (10)
| | | transition_times[0:0]: 0x2c-0x2c (0)
| | | transition_types[0:0]: 0x2c-0x2c (0)
| | | local_time_type_records[0:1]: 0x2c-0x32 (6)
| | | [0]{}: local_time_type 0x2c-0x32 (6)
0x20| 00 00 2a 30| ..*0| utoff: 10800 (valid) 0x2c-0x30 (4)
0x30|00 |. | dst: 0 (valid) 0x30-0x31 (1)
0x30| 00 | . | idx: 0 (valid) 0x31-0x32 (1)
| | | time_zone_designations[0:1]: 0x32-0x36 (4)
0x30| 2b 30 33 00 | +03. | [0]: "+03" time_zone_designation 0x32-0x36 (4)
| | | leap_second_records[0:0]: 0x36-0x36 (0)
| | | standard_wall_indicators[0:0]: 0x36-0x36 (0)
| | | ut_local_indicators[0:0]: 0x36-0x36 (0)
| | | v2plusheader{}: 0x36-0x62 (44)
0x30| 54 5a 69 66 | TZif | magic: 0x545a6966 (valid) 0x36-0x3a (4)
0x30| 32 | 2 | ver: "2" (0x32) (valid) 0x3a-0x3b (1)
0x30| 00 00 00 00 00| .....| reserved: raw bits 0x3b-0x4a (15)
support tzif (time zone information format)
2022-12-01 15:44:57 +03:00
0x40|00 00 00 00 00 00 00 00 00 00 |.......... |
interp: Change bit ranges to use exclusive end All other ranges and slicing uses exclusive end so i think it make sense to make it consistent. Update docs and add additional example for non-byte-aligned field. Also fixes issue showing zero bit ranges as start-NA.
2023-10-20 16:08:14 +03:00
0x40| 00 00 00 00 | .... | isutcnt: 0 0x4a-0x4e (4)
0x40| 00 00| ..| isstdcnt: 0 0x4e-0x52 (4)
support tzif (time zone information format)
2022-12-01 15:44:57 +03:00
0x50|00 00 |.. |
interp: Change bit ranges to use exclusive end All other ranges and slicing uses exclusive end so i think it make sense to make it consistent. Update docs and add additional example for non-byte-aligned field. Also fixes issue showing zero bit ranges as start-NA.
2023-10-20 16:08:14 +03:00
0x50| 00 00 00 00 | .... | leapcnt: 0 0x52-0x56 (4)
0x50| 00 00 00 00 | .... | timecnt: 0 0x56-0x5a (4)
0x50| 00 00 00 01 | .... | typecnt: 1 0x5a-0x5e (4)
0x50| 00 00| ..| charcnt: 4 0x5e-0x62 (4)
support tzif (time zone information format)
2022-12-01 15:44:57 +03:00
0x60|00 04 |.. |
interp: Change bit ranges to use exclusive end All other ranges and slicing uses exclusive end so i think it make sense to make it consistent. Update docs and add additional example for non-byte-aligned field. Also fixes issue showing zero bit ranges as start-NA.
2023-10-20 16:08:14 +03:00
| | | v2plusdatablock{}: 0x62-0x6c (10)
| | | transition_times[0:0]: 0x62-0x62 (0)
| | | transition_types[0:0]: 0x62-0x62 (0)
| | | local_time_type_records[0:1]: 0x62-0x68 (6)
| | | [0]{}: local_time_type 0x62-0x68 (6)
0x60| 00 00 2a 30 | ..*0 | utoff: 10800 (valid) 0x62-0x66 (4)
0x60| 00 | . | dst: 0 (valid) 0x66-0x67 (1)
0x60| 00 | . | idx: 0 (valid) 0x67-0x68 (1)
| | | time_zone_designations[0:1]: 0x68-0x6c (4)
0x60| 2b 30 33 00 | +03. | [0]: "+03" time_zone_designation 0x68-0x6c (4)
| | | leap_second_records[0:0]: 0x6c-0x6c (0)
| | | standard_wall_indicators[0:0]: 0x6c-0x6c (0)
| | | ut_local_indicators[0:0]: 0x6c-0x6c (0)
| | | footer{}: 0x6c-0x75 (9)
0x60| 0a | . | nl1: 10 (valid) 0x6c-0x6d (1)
0x60| 3c 2b 30| <+0| tz_string: "<+03>-3" 0x6d-0x74 (7)
support tzif (time zone information format)
2022-12-01 15:44:57 +03:00
0x70|33 3e 2d 33 |3>-3 |
interp: Change bit ranges to use exclusive end All other ranges and slicing uses exclusive end so i think it make sense to make it consistent. Update docs and add additional example for non-byte-aligned field. Also fixes issue showing zero bit ranges as start-NA.
2023-10-20 16:08:14 +03:00
0x70| 0a| | .| | nl2: 10 (valid) 0x74-0x75 (1)
Reference in New Issue Copy Permalink