Lines Matching full:readers

244 Readers that understand only Version 1 must ignore
261 This guideline helps obsolescent version 1 readers
262 agree with current readers about timestamps within the
265 supporting obsolescent readers use a
271 time, TZif readers should either refuse to process
284 When reading a version 2 or higher file, readers
288 Readers should calculate the total lengths of the
292 When a positive leap second occurs, readers should append an extra
302 older readers.
307 pitfalls in older or buggy TZif readers,
309 to help TZif readers avoid common pitfalls when reading
323 new-version data useful even for older-version readers.
326 readers.
331 Some readers examine only version 1 data.
338 Some readers designed for version 2 might mishandle
344 mishandled by version 2 readers.
346 Some readers designed for version 2 do not support
364 Some readers designed for version 2 or 3, and that require strict
368 Some readers ignore the footer, and instead predict future
373 Some stripped-down readers ignore everything but the footer,
385 Some readers do not use time type 0 for timestamps before
391 Some readers mishandle timestamps before the first
393 Readers that support only 32-bit timestamps are likely to be
400 Some readers mishandle a transition if its timestamp has
404 Some readers mishandle TZ strings that
416 Many readers mishandle time zone abbreviations that contain
420 Some readers may mishandle time zone abbreviations that
428 Some readers mishandle TZif files that specify
431 These readers do not support locations like Ireland, which
444 Some readers generate ambiguous timestamps for positive leap seconds
447 a positive leap second 78796801 (1972-06-30 23:59:60 UTC), some readers will
457 are listed here mostly as warnings to developers of readers.
460 Some readers do not support negative timestamps.
464 Some readers mishandle timestamps before the first
466 Readers that do not support negative timestamps are likely to
469 Some readers mishandle time zone abbreviations like
476 Some readers mishandle UT offsets that are out of the
481 Some readers mishandle UT offsets in the range [\-3599, \-1]
486 Some readers mishandle UT offsets that are not a multiple