pike.git/ lib/ modules/ Calendar.pmod/ TZnames.pmod

2000-08-11

2000-08-11 08:48:39 by Mirar (Pontus Hagland) <pike@sort.mirar.org>

• 2c3cdd4f434a9020fab0d2257d8e919212ef8788 (12 lines) (+7/-5) ^{[ Show | Annotate ]}
  Branch: 7.9

docfix

Rev: lib/modules/Calendar.pmod/Event.pmod:1.4
Rev: lib/modules/Calendar.pmod/TZnames.pmod:1.3
Rev: lib/modules/Calendar.pmod/YMD.pmod:1.7

21:   //! <i>[...]</i> }),   //! </pre>   //! - //! note: - //! Loading all the timezones can take some time, since - //! they are generated and compiled on the fly. + //! Please note that loading all the timezones can take some + //! time, since they are generated and compiled on the fly.      mapping zones=   ([
117:   //! <i>[...]</i> }),   //! </pre>   //! - //! note: - //! Just because it's noted "CST" doesn't mean it's a + //! Note this: Just because it's noted "CST" doesn't mean it's a   //! unique timezone. There is about 7 *different* timezones that   //! uses "CST" as abbreviation; not at the same time,   //! though, so the DWIM routines checks this before
127:   //! For most timezones, there is a number of region timezones that for the   //! given time are equal. This is because region timezones include rules   //! about local summer time shifts and possible historic shifts. + //! + //! The <ref>YMD.parse</ref> functions can handle timezone abbreviations + //! by guessing.      mapping abbr2zones=   ([