35c35
< whose clocks all agree about timestamps that occur after the of the <a
---
> whose clocks all agree about timestamps that occur after the <a
56c56
< Athough some information outside the scope of the database is
---
> Although some information outside the scope of the database is
71c71
< Group Base Specifications Issue 7</a>, IEEE Std 1003.1-2008, 2016
---
> Group Base Specifications Issue 7</a>, IEEE Std 1003.1-2017, 2018
82c82
< It doesn't even really make sense to talk about a region's
---
> It does not always make sense to talk about a region's
95,96c95,96
< interface that explains the names; for one example, see the 'tzselect'
< program in the <code><abbr>tz</abbr></code> code.
---
> interface that explains the names; for one example, see the
> <code>tzselect</code> program in the <code><abbr>tz</abbr></code> code.
139a140,142
> Some names are further qualified to help avoid confusion; for example,
> '<code>America/Indiana/Petersburg</code>' distinguishes Petersburg,
> Indiana from other Petersburgs in America.
162c165,166
< E.g., prefer '<code>Brunei</code>' to '<code>Bandar_Seri_Begawan</code>'.
---
> E.g., prefer <code>Asia/Brunei</code> to
> <code>Asia/Bandar_Seri_Begawan</code>.
180,181c184,185
< For example, '<code>America/New_York</code>' precludes
< '<code>America/New_York/Bronx</code>'.
---
> For example, <code>America/New_York</code> precludes
> <code>America/New_York/Bronx</code>.
196c200
< don't bother to include more than one location
---
> do not bother to include more than one location
203,204c207,209
< prefer '<code>Costa_Rica</code>' to '<code>San_Jose</code>' and
< '<code>Guyana</code>' to '<code>Georgetown</code>'.
---
> prefer <code>America/Costa_Rica</code> to
> <code>America/San_Jose</code> and <code>America/Guyana</code>
> to <code>America/Georgetown</code>.
211c216,217
< E.g., prefer '<code>Paris</code>' to '<code>France</code>', since
---
> E.g., prefer <code>Europe/Paris</code> to <code>Europe/France</code>,
> since
216,218c222,226
< Use mainstream English spelling, e.g., prefer '<code>Rome</code>'
< to '<code>Roma</code>', and prefer '<code>Athens</code>' to the
< Greek '<code>����������</code>' or the Romanized '<code>Ath��na</code>'.
---
> Use mainstream English spelling, e.g., prefer
> <code>Europe/Rome</code> to <code>Europe/Roma</code>, and
> prefer <code>Europe/Athens</code> to the Greek
> <code>Europe/����������</code> or the Romanized
> <code>Europe/Ath��na</code>.
223,224c231,232
< e.g., prefer '<code>Shanghai</code>' to
< '<code>Beijing</code>'.
---
> e.g., prefer <code>Asia/Shanghai</code> to
> <code>Asia/Beijing</code>.
226,227c234,235
< location, e.g., prefer '<code>Rome</code>' to
< '<code>Milan</code>'.
---
> location, e.g., prefer <code>Europe/Rome</code> to
> <code>Europe/Milan</code>.
230,231c238,239
< Use the singular form, e.g., prefer '<code>Canary</code>' to
< '<code>Canaries</code>'.
---
> Use the singular form, e.g., prefer <code>Atlantic/Canary</code> to
> <code>Atlantic/Canaries</code>.
236,239c244,249
< E.g., prefer '<code>Cayman</code>' to
< '<code>Cayman_Islands</code>' and '<code>Guatemala</code>' to
< '<code>Guatemala_City</code>', but prefer
< '<code>Mexico_City</code>' to '<code>Mexico</code>'
---
> E.g., prefer <code>America/Cayman</code> to
> <code>America/Cayman_Islands</code> and
> <code>America/Guatemala</code> to
> <code>America/Guatemala_City</code>, but prefer
> <code>America/Mexico_City</code> to
> <code>America/Mexico</code>
248c258,259
< E.g., prefer '<code>St_Helena</code>' to '<code>St._Helena</code>'.
---
> E.g., prefer <code>Atlantic/St_Helena</code> to
> <code>Atlantic/St._Helena</code>.
253,254c264,265
< For example, don't change the existing name '<code>Rome</code>' to
< '<code>Milan</code>' merely because Milan's population has grown
---
> For example, do not change the existing name <code>Europe/Rome</code> to
> <code>Europe/Milan</code> merely because Milan's population has grown
321,322c332,335
< '<code> </code>' and '<code>?</code>', but these characters have a
< special meaning to the shell and cause commands like
---
> space and '<code>?</code>', but these characters have a
> special meaning to the
> <a href="https://en.wikipedia.org/wiki/Unix_shell">UNIX shell</a>
> and cause commands like
691c704
< Civil time was not based on atomic time before 1972, and we don't
---
> Civil time was not based on atomic time before 1972, and we do not
723c736
< and it's not clear how to apply it here.
---
> and it is not clear how to apply it here.
767c780
< Also, POSIX <code>TZ</code> strings can't deal with daylight
---
> Also, POSIX <code>TZ</code> strings cannot deal with daylight
877c890
< In POSIX, there's no tamper-proof way for a process to learn the
---
> In POSIX, there is no tamper-proof way for a process to learn the
976,977c989,990
< if such code is moved to "old" systems that don't
< provide <code>tzsetwall</code>, you won't be able to generate an
---
> if such code is moved to "old" systems that do not
> provide <code>tzsetwall</code>, you will not be able to generate an
981c994
< indirectly – and there's no <code>TZ</code> environment
---
> indirectly – and there is no <code>TZ</code> environment
983c996,998
< behavior since it's not the way SVR2 systems behave.)
---
> behavior since it is not the way <a
> href="https://en.wikipedia.org/wiki/UNIX_System_V#SVR2"><abbr>SVR2</abbr></a>
> systems behave.)
1043c1058
< package; it's impossible to reliably map <code>timezone</code>'s
---
> package; it is impossible to reliably map <code>timezone</code>'s
1055c1070,1072
< The <abbr>4.2BSD</abbr> <code>gettimeofday</code> function is not
---
> The <a
> href="https://en.wikipedia.org/wiki/History_of_the_Berkeley_Software_Distribution#4.2BSD"><abbr>4.2BSD</abbr></a>
> <code>gettimeofday</code> function is not
1064c1081
< for places that don't use <abbr>UT</abbr>.
---
> for places that do not use <abbr>UT</abbr>.
1158,1161c1175,1178
< An excellent resource in this area is Nachum Dershowitz and Edward M.
< Reingold, <cite><a
< href="https://www.cs.tau.ac.il/~nachum/calendar-book/third-edition/">Calendrical
< Calculations: Third Edition</a></cite>, Cambridge University Press (2008).
---
> An excellent resource in this area is Edward M. Reingold
> and Nachum Dershowitz, <cite><a
> href="https://www.cambridge.org/fr/academic/subjects/computer-science/computing-general-interest/calendrical-calculations-ultimate-edition-4th-edition">Calendrical
> Calculations: The Ultimate Edition</a></cite>, Cambridge University Press (2018).
1173,1174c1190,1191
< Jet Propulsion Laboratory (JPL) coordinators have kept Mars time on
< and off at least since 1997 for the
---
> Jet Propulsion Laboratory (JPL) coordinators kept Mars time on
> and off during the
1177c1194
< Some of their family members have also adapted to Mars time.
---
> Some of their family members also adapted to Mars time.
1265c1282
< (2004-01-14), pp A1, A20-A21.
---
> (2004-01-14), pp A1, A20–A21.
< whose clocks all agree about timestamps that occur after the of the <a
---
> whose clocks all agree about timestamps that occur after the <a
56c56
< Athough some information outside the scope of the database is
---
> Although some information outside the scope of the database is
71c71
< Group Base Specifications Issue 7</a>, IEEE Std 1003.1-2008, 2016
---
> Group Base Specifications Issue 7</a>, IEEE Std 1003.1-2017, 2018
82c82
< It doesn't even really make sense to talk about a region's
---
> It does not always make sense to talk about a region's
95,96c95,96
< interface that explains the names; for one example, see the 'tzselect'
< program in the <code><abbr>tz</abbr></code> code.
---
> interface that explains the names; for one example, see the
> <code>tzselect</code> program in the <code><abbr>tz</abbr></code> code.
139a140,142
> Some names are further qualified to help avoid confusion; for example,
> '<code>America/Indiana/Petersburg</code>' distinguishes Petersburg,
> Indiana from other Petersburgs in America.
162c165,166
< E.g., prefer '<code>Brunei</code>' to '<code>Bandar_Seri_Begawan</code>'.
---
> E.g., prefer <code>Asia/Brunei</code> to
> <code>Asia/Bandar_Seri_Begawan</code>.
180,181c184,185
< For example, '<code>America/New_York</code>' precludes
< '<code>America/New_York/Bronx</code>'.
---
> For example, <code>America/New_York</code> precludes
> <code>America/New_York/Bronx</code>.
196c200
< don't bother to include more than one location
---
> do not bother to include more than one location
203,204c207,209
< prefer '<code>Costa_Rica</code>' to '<code>San_Jose</code>' and
< '<code>Guyana</code>' to '<code>Georgetown</code>'.
---
> prefer <code>America/Costa_Rica</code> to
> <code>America/San_Jose</code> and <code>America/Guyana</code>
> to <code>America/Georgetown</code>.
211c216,217
< E.g., prefer '<code>Paris</code>' to '<code>France</code>', since
---
> E.g., prefer <code>Europe/Paris</code> to <code>Europe/France</code>,
> since
216,218c222,226
< Use mainstream English spelling, e.g., prefer '<code>Rome</code>'
< to '<code>Roma</code>', and prefer '<code>Athens</code>' to the
< Greek '<code>����������</code>' or the Romanized '<code>Ath��na</code>'.
---
> Use mainstream English spelling, e.g., prefer
> <code>Europe/Rome</code> to <code>Europe/Roma</code>, and
> prefer <code>Europe/Athens</code> to the Greek
> <code>Europe/����������</code> or the Romanized
> <code>Europe/Ath��na</code>.
223,224c231,232
< e.g., prefer '<code>Shanghai</code>' to
< '<code>Beijing</code>'.
---
> e.g., prefer <code>Asia/Shanghai</code> to
> <code>Asia/Beijing</code>.
226,227c234,235
< location, e.g., prefer '<code>Rome</code>' to
< '<code>Milan</code>'.
---
> location, e.g., prefer <code>Europe/Rome</code> to
> <code>Europe/Milan</code>.
230,231c238,239
< Use the singular form, e.g., prefer '<code>Canary</code>' to
< '<code>Canaries</code>'.
---
> Use the singular form, e.g., prefer <code>Atlantic/Canary</code> to
> <code>Atlantic/Canaries</code>.
236,239c244,249
< E.g., prefer '<code>Cayman</code>' to
< '<code>Cayman_Islands</code>' and '<code>Guatemala</code>' to
< '<code>Guatemala_City</code>', but prefer
< '<code>Mexico_City</code>' to '<code>Mexico</code>'
---
> E.g., prefer <code>America/Cayman</code> to
> <code>America/Cayman_Islands</code> and
> <code>America/Guatemala</code> to
> <code>America/Guatemala_City</code>, but prefer
> <code>America/Mexico_City</code> to
> <code>America/Mexico</code>
248c258,259
< E.g., prefer '<code>St_Helena</code>' to '<code>St._Helena</code>'.
---
> E.g., prefer <code>Atlantic/St_Helena</code> to
> <code>Atlantic/St._Helena</code>.
253,254c264,265
< For example, don't change the existing name '<code>Rome</code>' to
< '<code>Milan</code>' merely because Milan's population has grown
---
> For example, do not change the existing name <code>Europe/Rome</code> to
> <code>Europe/Milan</code> merely because Milan's population has grown
321,322c332,335
< '<code> </code>' and '<code>?</code>', but these characters have a
< special meaning to the shell and cause commands like
---
> space and '<code>?</code>', but these characters have a
> special meaning to the
> <a href="https://en.wikipedia.org/wiki/Unix_shell">UNIX shell</a>
> and cause commands like
691c704
< Civil time was not based on atomic time before 1972, and we don't
---
> Civil time was not based on atomic time before 1972, and we do not
723c736
< and it's not clear how to apply it here.
---
> and it is not clear how to apply it here.
767c780
< Also, POSIX <code>TZ</code> strings can't deal with daylight
---
> Also, POSIX <code>TZ</code> strings cannot deal with daylight
877c890
< In POSIX, there's no tamper-proof way for a process to learn the
---
> In POSIX, there is no tamper-proof way for a process to learn the
976,977c989,990
< if such code is moved to "old" systems that don't
< provide <code>tzsetwall</code>, you won't be able to generate an
---
> if such code is moved to "old" systems that do not
> provide <code>tzsetwall</code>, you will not be able to generate an
981c994
< indirectly – and there's no <code>TZ</code> environment
---
> indirectly – and there is no <code>TZ</code> environment
983c996,998
< behavior since it's not the way SVR2 systems behave.)
---
> behavior since it is not the way <a
> href="https://en.wikipedia.org/wiki/UNIX_System_V#SVR2"><abbr>SVR2</abbr></a>
> systems behave.)
1043c1058
< package; it's impossible to reliably map <code>timezone</code>'s
---
> package; it is impossible to reliably map <code>timezone</code>'s
1055c1070,1072
< The <abbr>4.2BSD</abbr> <code>gettimeofday</code> function is not
---
> The <a
> href="https://en.wikipedia.org/wiki/History_of_the_Berkeley_Software_Distribution#4.2BSD"><abbr>4.2BSD</abbr></a>
> <code>gettimeofday</code> function is not
1064c1081
< for places that don't use <abbr>UT</abbr>.
---
> for places that do not use <abbr>UT</abbr>.
1158,1161c1175,1178
< An excellent resource in this area is Nachum Dershowitz and Edward M.
< Reingold, <cite><a
< href="https://www.cs.tau.ac.il/~nachum/calendar-book/third-edition/">Calendrical
< Calculations: Third Edition</a></cite>, Cambridge University Press (2008).
---
> An excellent resource in this area is Edward M. Reingold
> and Nachum Dershowitz, <cite><a
> href="https://www.cambridge.org/fr/academic/subjects/computer-science/computing-general-interest/calendrical-calculations-ultimate-edition-4th-edition">Calendrical
> Calculations: The Ultimate Edition</a></cite>, Cambridge University Press (2018).
1173,1174c1190,1191
< Jet Propulsion Laboratory (JPL) coordinators have kept Mars time on
< and off at least since 1997 for the
---
> Jet Propulsion Laboratory (JPL) coordinators kept Mars time on
> and off during the
1177c1194
< Some of their family members have also adapted to Mars time.
---
> Some of their family members also adapted to Mars time.
1265c1282
< (2004-01-14), pp A1, A20-A21.
---
> (2004-01-14), pp A1, A20–A21.