Busingen revisited
With the new year, a revised attempt to handle the German exclave of Busingen (which followed Zurich rather than Berlin in 1980). These changes are relative to the latest github.com/eggert/tz versions; they are both below (with tabs mangled) and attached. --ado *** old/europe 2013-01-07 08:05:19.093905100 -0500 --- europe 2013-01-07 08:13:01.260316900 -0500 *************** *** 1239,1244 **** --- 1239,1265 ---- 1:00 Germany CE%sT 1980 1:00 EU CE%sT + # From Tobias Conradi (2011-09-12): + # The German enclave of Büsingen + # <a href=http://www.buesingen.de> + # (http://www.buesingen.de) + # </a> + # surrounded by the Swiss canton Schaffhausen, + # did not start observing DST in 1980 as the rest of DE + # (West Germany at that time) and DD (East Germany at that time) did. + # DD merged into DE, the area is currently covered by code DE in ISO 3166-1, + # which in turn is covered by the zone Europe/Berlin. + # + # Source for the time in Büsingen 1980: + # <a href=" http://www.videoportal.sf.tv/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3"> + # http://www.videoportal.sf.tv/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3 + # </a> + + # From Arthur David Olson (2012-03-03): + # Büsingen and Zurich have shared clocks since 1970. + + Link Europe/Zurich Europe/Busingen + # Georgia # Please see the "asia" file for Asia/Tbilisi. # Herodotus (Histories, IV.45) says Georgia north of the Phasis (now Rioni) *** old/zone.tab 2013-01-07 08:05:21.511909300 -0500 --- zone.tab 2013-01-07 08:18:15.587807500 -0500 *************** *** 159,165 **** CX -1025+10543 Indian/Christmas CY +3510+03322 Asia/Nicosia CZ +5005+01426 Europe/Prague ! DE +5230+01322 Europe/Berlin DJ +1136+04309 Africa/Djibouti DK +5540+01235 Europe/Copenhagen DM +1518-06124 America/Dominica --- 159,166 ---- CX -1025+10543 Indian/Christmas CY +3510+03322 Asia/Nicosia CZ +5005+01426 Europe/Prague ! DE +5230+01322 Europe/Berlin Germany except Busingen ! DE +4742+00841 Europe/Busingen Busingen Germany DJ +1136+04309 Africa/Djibouti DK +5540+01235 Europe/Copenhagen DM +1518-06124 America/Dominica
On Mon, 07 Jan 2013 14:28:30 +0100, Arthur David Olson <arthurdavidolson@gmail.com> wrote:
With the new year, a revised attempt to handle the German exclave of Busingen (which followed Zurich rather than Berlin in 1980). These changes are relative to the latest github.com/eggert/tz versions; they are both below (with tabs mangled) and attached.
--ado
*** old/europe 2013-01-07 08:05:19.093905100 -0500 --- europe 2013-01-07 08:13:01.260316900 -0500 *************** *** 1239,1244 **** --- 1239,1265 ---- 1:00 Germany CE%sT 1980 1:00 EU CE%sT + # From Tobias Conradi (2011-09-12): + # The German enclave of Büsingen
It should be "exclave" there (it's an exclave of Germany and an enclave of Switzerland). I'm not sure, are the files supposed to be UTF-8? If so, that ü should be 'ü'. Alternately, you could also write "Buesingen" (ü becoming ue).
+ # <a href=http://www.buesingen.de> + # (http://www.buesingen.de) + # </a> + # surrounded by the Swiss canton Schaffhausen, + # did not start observing DST in 1980 as the rest of DE + # (West Germany at that time) and DD (East Germany at that time) did. + # DD merged into DE, the area is currently covered by code DE in ISO 3166-1, + # which in turn is covered by the zone Europe/Berlin. + # + # Source for the time in Büsingen 1980:
See ü comment above.
+ # <a href="http://www.videoportal.sf.tv/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3"> + # http://www.videoportal.sf.tv/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3 + # </a> ++ # From Arthur David Olson (2012-03-03): + # Büsingen and Zurich have shared clocks since 1970.
And here.
++ Link Europe/Zurich Europe/Busingen + # Georgia # Please see the "asia" file for Asia/Tbilisi. # Herodotus (Histories, IV.45) says Georgia north of the Phasis (now Rioni) *** old/zone.tab 2013-01-07 08:05:21.511909300 -0500 --- zone.tab 2013-01-07 08:18:15.587807500 -0500 *************** *** 159,165 **** CX -1025+10543 Indian/Christmas CY +3510+03322 Asia/Nicosia CZ +5005+01426 Europe/Prague ! DE +5230+01322 Europe/Berlin DJ +1136+04309 Africa/Djibouti DK +5540+01235 Europe/Copenhagen DM +1518-06124 America/Dominica --- 159,166 ---- CX -1025+10543 Indian/Christmas CY +3510+03322 Asia/Nicosia CZ +5005+01426 Europe/Prague ! DE +5230+01322 Europe/Berlin Germany except Busingen ! DE +4742+00841 Europe/Busingen Busingen Germany
Could be Buesingen here too. Sascha
On Wed, 9 Jan 2013, Sascha Wildner wrote:
On Mon, 07 Jan 2013 14:28:30 +0100, Arthur David Olson <arthurdavidolson@gmail.com> wrote:
+ # <a href=http://www.buesingen.de> + # (http://www.buesingen.de) + # </a> + # surrounded by the Swiss canton Schaffhausen, + # did not start observing DST in 1980 as the rest of DE + # (West Germany at that time) and DD (East Germany at that time) did. + # DD merged into DE, the area is currently covered by code DE in ISO 3166-1, + # which in turn is covered by the zone Europe/Berlin. + # + # Source for the time in Büsingen 1980:
See ü comment above.
+ # <a href="http://www.videoportal.sf.tv/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3"> + # http://www.videoportal.sf.tv/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3 + # </a> + # From Arthur David Olson (2012-03-03): + # Büsingen and Zurich have shared clocks since 1970.
And here.
++ Link Europe/Zurich Europe/Busingen
And the one here above I would say? The "correct" transliteration with be Europe/Buesingen. cheers, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug Posted with an email client that doesn't mangle email: alpine
On 2013-01-09 14:47, Derick Rethans wrote:
On Wed, 9 Jan 2013, Sascha Wildner wrote:
On Mon, 07 Jan 2013 14:28:30 +0100, Arthur David Olson <arthurdavidolson@gmail.com> wrote:
+ # <a href=http://www.buesingen.de> + # (http://www.buesingen.de) + # </a> + # surrounded by the Swiss canton Schaffhausen, + # did not start observing DST in 1980 as the rest of DE + # (West Germany at that time) and DD (East Germany at that time) did. + # DD merged into DE, the area is currently covered by code DE in ISO 3166-1, + # which in turn is covered by the zone Europe/Berlin. + # + # Source for the time in Büsingen 1980:
See ü comment above.
+ # <a href="http://www.videoportal.sf.tv/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3"> + # http://www.videoportal.sf.tv/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3 + # </a> + # From Arthur David Olson (2012-03-03): + # Büsingen and Zurich have shared clocks since 1970.
And here.
++ Link Europe/Zurich Europe/Busingen
And the one here above I would say? The "correct" transliteration with be Europe/Buesingen.
By the same rule, the "correct" transliteration of Europe/Zurich would be Europe/Zuerich, wouldn't it? But we're using English zone names rather than transliterated zone names and I think either "Buesingen" or "Busingen" would do for the English name. I've seen both used in a quick Google search, and the English Wikipedia redirects both spellings to "Büsingen". -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
Ian Abbott <abbotti@mev.co.uk> wrote: |On 2013-01-09 14:47, Derick Rethans wrote: |> On Wed, 9 Jan 2013, Sascha Wildner wrote: |> |>> On Mon, 07 Jan 2013 14:28:30 +0100, Arthur David Olson \ |.. <arthurdavidolson@gmail.com> wrote: |>> |>>> + # <a href=http://www.buesingen.de> |>>> + # (http://www.buesingen.de) |>>> + # </a> |>>> + # surrounded by the Swiss canton Schaffhausen, |>>> + # did not start observing DST in 1980 as the rest of DE |>>> + # (West Germany at that time) and DD (East Germany at that time) did. |>>> + # DD merged into DE, the area is currently covered by code DE in ISO \ |... 3166-1, |>>> + # which in turn is covered by the zone Europe/Berlin. |>>> + # |>>> + # Source for the time in Büsingen 1980: |>> |>> See ü comment above. |>> |>>> |>>> + # <a href="http://www.videoportal.sf.tv/video?id=c012c029-03b7-4c2b-91\ |... 64-aa5902cd58d3"> |>>> + # http://www.videoportal.sf.tv/video?id=c012c029-03b7-4c2b-9164-aa5902\ |... cd58d3 |>>> + # </a> |>>> + # From Arthur David Olson (2012-03-03): |>>> + # Büsingen and Zurich have shared clocks since 1970. |>> |>> And here. |>> |>>> |>>> ++ Link Europe/Zurich Europe/Busingen |> |> And the one here above I would say? The "correct" transliteration with |> be Europe/Buesingen. | |By the same rule, the "correct" transliteration of Europe/Zurich would |be Europe/Zuerich, wouldn't it? But we're using English zone names That is true in theory, but the swiss people are more relaxed in respect to their friendliness to the english speaking, and afaik. E.g., the Zürich Insurance renamed *themselve* to Zurich; i have a CD from »The Zurich String Quintet« (though they seem not to know exactly how to call themselves). |rather than transliterated zone names and I think either "Buesingen" or |"Busingen" would do for the English name. I've seen both used in a |quick Google search, and the English Wikipedia redirects both spellings |to "Büsingen". Not that i really care, since these names are not ment for end users, as has been clarified multiple times in the last months… Maybe you are just ahead of our time. I'm against any mutilation of the German language, on principle. |-- |-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- |-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=- --steffen
On 09/01/2013 18:22, Steffen Daode Nurpmeso wrote:
Ian Abbott <abbotti@mev.co.uk> wrote: |On 2013-01-09 14:47, Derick Rethans wrote: |> On Wed, 9 Jan 2013, Sascha Wildner wrote: |> |>> On Mon, 07 Jan 2013 14:28:30 +0100, Arthur David Olson \ |.. <arthurdavidolson@gmail.com> wrote: |>>> ++ Link Europe/Zurich Europe/Busingen |> |> And the one here above I would say? The "correct" transliteration with |> be Europe/Buesingen. | |By the same rule, the "correct" transliteration of Europe/Zurich would |be Europe/Zuerich, wouldn't it? But we're using English zone names
That is true in theory, but the swiss people are more relaxed in respect to their friendliness to the english speaking, and afaik. E.g., the Zürich Insurance renamed *themselve* to Zurich; i have a CD from »The Zurich String Quintet« (though they seem not to know exactly how to call themselves).
Zürich is well known enough in the English language to be given an anglified spelling ("Zurich"). I just mentioned it as an example because the spelling "Zuerich" would look *really* odd in English ...
|rather than transliterated zone names and I think either "Buesingen" or |"Busingen" would do for the English name. I've seen both used in a |quick Google search, and the English Wikipedia redirects both spellings |to "Büsingen".
... whereas Büsingen isn't really well known enough in English-speaking countries for an anglified version of the name to appear in English dictionaries (well, maybe the full-size OED is large enough to include it, but not the smaller dictionaries).
Not that i really care, since these names are not ment for end users, as has been clarified multiple times in the last months… Maybe you are just ahead of our time. I'm against any mutilation of the German language, on principle.
You should see how the English spell Köln! Fortunately, it's not in the tz database. ;)
Ian Abbott <abbotti@mev.co.uk> wrote: |On 09/01/2013 18:22, Steffen Daode Nurpmeso wrote: |> Ian Abbott <abbotti@mev.co.uk> wrote: |>|On 2013-01-09 14:47, Derick Rethans wrote: |>|> On Wed, 9 Jan 2013, Sascha Wildner wrote: |>|> |>|>> On Mon, 07 Jan 2013 14:28:30 +0100, Arthur David Olson \ |>|.. <arthurdavidolson@gmail.com> wrote: |>|>>> ++ Link Europe/Zurich Europe/Busingen |>|> |>|> And the one here above I would say? The "correct" transliteration with |>|> be Europe/Buesingen. |>| |>|By the same rule, the "correct" transliteration of Europe/Zurich would |>|be Europe/Zuerich, wouldn't it? But we're using English zone names [.] |> Not that i really care, since these names are not ment for end |> users, as has been clarified multiple times in the last months… |> Maybe you are just ahead of our time. |> I'm against any mutilation of the German language, on principle. | |You should see how the English spell Köln! Fortunately, it's not in the |tz database. ;) They use the old roman name?. Ach, i'm sick that only words like »Kindergarten« and »Blitzkrieg« go the other direction ; Not at last because all germans born in between 1940 and 1980 have been socialized with the best film of all times [1], called »Die Brucke« in English (not even freedom of art..). But this is all blabla. Except that maybe tz should be converted to UTF-8 so that at least the comments won't mutilate names of reporters etc. in the future, and could thus mention the real name »Büsingen« just as is, with the zone name being whatever fits best in ASCII filename. Using HTML entities does not seem to be a good solution to me. --steffen [1] <http://www.youtube.com/watch?v=uTyga7HviTU&list=UUYO3p7nVCI2xCw0RyKQbTPg&ind...> (Start at 80 seconds)
On 2013-01-10 11:33, Steffen Daode Nurpmeso wrote:
Ian Abbott <abbotti@mev.co.uk> wrote: |On 09/01/2013 18:22, Steffen Daode Nurpmeso wrote: |> Not that i really care, since these names are not ment for end |> users, as has been clarified multiple times in the last months… |> Maybe you are just ahead of our time. |> I'm against any mutilation of the German language, on principle. | |You should see how the English spell Köln! Fortunately, it's not in the |tz database. ;)
They use the old roman name?. Ach, i'm sick that only words like »Kindergarten« and »Blitzkrieg« go the other direction ;
The English use the French name, as in "eau de Cologne", but derived from the first part of the Roman name, "Colonia Claudia Ara Agrippinensium".
But this is all blabla.
Yes, the thread topic has drifted a bit. I changed the subject.
Except that maybe tz should be converted to UTF-8 so that at least the comments won't mutilate names of reporters etc. in the future, and could thus mention the real name »Büsingen« just as is, with the zone name being whatever fits best in ASCII filename. Using HTML entities does not seem to be a good solution to me.
I'd prefer the comments to be in UTF-8 without the HTML entities and HTML tags, but the non-comment parts of the files to be restricted to plain-old ASCII. The current HTML mark-up tags seem to have been added around December 1997 or earlier, although there have been URLs in the files since 1996 or earlier. The TZ files pre-date HTML by several years and pre-date UTF-8 by several more years. I'm not sure how widespread the adoption of UTF-8 text files is in the big, wide world, but I don't suppose we should care as long as the zic compilers don't break and the systems that zic is run on support 8-bit text files. -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
On 01/10/13 05:04, Ian Abbott wrote:
I'd prefer the comments to be in UTF-8 without the HTML entities and HTML tags, but the non-comment parts of the files to be restricted to plain-old ASCII. The current HTML mark-up tags seem to have been added around December 1997 or earlier, although there have been URLs in the files since 1996 or earlier. The TZ files pre-date HTML by several years and pre-date UTF-8 by several more years.
The HTML markup has bothered me, too; I have found it more distracting than useful. URLs themselves should be fine, but the <a href='...'> business gets in the way.
I'm not sure how widespread the adoption of UTF-8 text files is in the big, wide world, but I don't suppose we should care as long as the zic compilers don't break and the systems that zic is run on support 8-bit text files.
There still is the problem that people who are editing the files with their own text editors may be hampered. In my normal way of editing text across the network (ssh and LC_ALL=C and emacs -nw), non-ASCII characters are rendered as ugly hexadecimalish strings that are hard to read. I can work around the problem but it is an annoyance.
On 2013/01/10 05:58 PM, Paul Eggert wrote:
On 01/10/13 05:04, Ian Abbott wrote:
I'd prefer the comments to be in UTF-8 without the HTML entities and HTML tags, but the non-comment parts of the files to be restricted to plain-old ASCII. The current HTML mark-up tags seem to have been added around December 1997 or earlier, although there have been URLs in the files since 1996 or earlier. The TZ files pre-date HTML by several years and pre-date UTF-8 by several more years.
The HTML markup has bothered me, too; I have found it more distracting than useful. URLs themselves should be fine, but the <a href='...'> business gets in the way.
The HTML entities are also rather unreadable. If the HTML markup is removed, and the HTML entities can't be replaced with UTF-8 sequences, perhaps the non-ASCII characters could be replaced with TeX markup sequences e.g. 'B\"usingen' rather than 'Büingen'.
I'm not sure how widespread the adoption of UTF-8 text files is in the big, wide world, but I don't suppose we should care as long as the zic compilers don't break and the systems that zic is run on support 8-bit text files.
There still is the problem that people who are editing the files with their own text editors may be hampered. In my normal way of editing text across the network (ssh and LC_ALL=C and emacs -nw), non-ASCII characters are rendered as ugly hexadecimalish strings that are hard to read. I can work around the problem but it is an annoyance.
Even worse for non 8-bit-clean editors such as the original 'vi', I suppose. Thanks, I hadn't considered that! -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
On 2013/01/11 10:05 AM, Ian Abbott wrote:
The HTML entities are also rather unreadable. If the HTML markup is removed, and the HTML entities can't be replaced with UTF-8 sequences, perhaps the non-ASCII characters could be replaced with TeX markup sequences e.g. 'B\"usingen' rather than 'Büingen'.
Typo: 'Büsingen'. -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
Is it really necessary to avoid UTF-8 or 8 bit text in general in 2013? Can anyone name a system in use today that is not capable of dealing with it? Deborah On Jan 11, 2013, at 2:28 AM, Ian Abbott <abbotti@mev.co.uk> wrote:
On 2013/01/11 10:05 AM, Ian Abbott wrote:
The HTML entities are also rather unreadable. If the HTML markup is removed, and the HTML entities can't be replaced with UTF-8 sequences, perhaps the non-ASCII characters could be replaced with TeX markup sequences e.g. 'B\"usingen' rather than 'Büingen'.
Typo: 'Büsingen'.
-- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
I also add one vote for UTF-8 On 2013-01-11 9:51, Deborah Goldsmith wrote:
Is it really necessary to avoid UTF-8 or 8 bit text in general in 2013? Can anyone name a system in use today that is not capable of dealing with it?
Deborah
On Jan 11, 2013, at 2:28 AM, Ian Abbott <abbotti@mev.co.uk> wrote:
On 2013/01/11 10:05 AM, Ian Abbott wrote:
The HTML entities are also rather unreadable. If the HTML markup is removed, and the HTML entities can't be replaced with UTF-8 sequences, perhaps the non-ASCII characters could be replaced with TeX markup sequences e.g. 'B\"usingen' rather than 'Büingen'. Typo: 'Büsingen'.
-- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
--
On Fri 2013-01-11T06:51:43 -0800, Deborah Goldsmith hath writ:
Can anyone name a system in use today that is not capable of dealing with it?
In addition to those already mentioned, my preferred text editor is not capable. I suspect that consensus on 8 bits requires a few more of us to die first. -- Steve Allen <sla@ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m
I would like to argue against the use of markup or html entities or anything similar. The comments in the files aren't going to be rendered for display by some other application - the direct viewing of the plain text is all that there is, and it can and should display correctly. On Fri, Jan 11, 2013 at 7:38 AM, Steve Allen <sla@ucolick.org> wrote:
On Fri 2013-01-11T06:51:43 -0800, Deborah Goldsmith hath writ:
Can anyone name a system in use today that is not capable of dealing with it?
In addition to those already mentioned, my preferred text editor is not capable. I suspect that consensus on 8 bits requires a few more of us to die first.
-- Steve Allen <sla@ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m
On 1/11/2013 10:38 AM, Steve Allen wrote:
In addition to those already mentioned, my preferred text editor is not capable. What _does_ your preferred text editor do when handed such a file? (What editor, by the way?) Same question to everyone else whose text editors "don't support" UTF-8 or 8-bit generally.
Re what do editors do when they see a character with the high order bit set, I've seen a few. Some crash hard, some stop reading, acting as though it were eof. Some just display unexpected gibberish. Some seem to work, but don't write a modified version out exactly correctly. I recall occasions when the only text editor on a system that could robustly edit the kernel as /dev/mem was gnu emacs. Or adb, of course, but that didn't give bragging rights.
This discussion does not matter, sooner or later it will be utf-8 as it has been for the rest of the world. What can you do. Like even if I'm still confused about this horseless carriage thing, I have one too. -- Foreca Ltd Jaakko.Hyvatti@foreca.com Keilaranta 1, FI-02150 Espoo, Finland http://www.foreca.com
On 01/12/2013 10:00 PM, Jaakko Hyvätti wrote:
sooner or later it will be utf-8 as it has been for the rest of the world.
In the long term UTF-8 is no doubt the way to go, but we might not be quite there yet. Your email's header used ISO-8859-15, an 8-bit scheme that is distinct from and incompatible with UTF-8.
Paul Eggert wrote on 2013-01-13 07:23 UTC:
On 01/12/2013 10:00 PM, Jaakko Hyvätti wrote:
sooner or later it will be utf-8 as it has been for the rest of the world.
In the long term UTF-8 is no doubt the way to go, but we might not be quite there yet.
UTF-8 has been very well supported by all major Unix/Linux distibutions for nearly a decade now, and has been the default locale in most new installations since about 2005. I strongly recommend that you use unset LC_ALL LANG=en_US.UTF-8 # or en_GB.UTF-8, ... outside the US LC_COLLATE=POSIX # to avoid surprises with sorting order and globbing With that, I hope that you will quickly find UTF-8 perfectly acceptable now in source code. UTF-8 has long become common practice in comments of many open-source projects. Markus http://www.cl.cam.ac.uk/~mgk25/unicode.html#collate -- Markus Kuhn, Computer Laboratory, University of Cambridge http://www.cl.cam.ac.uk/~mgk25/ || CB3 0FD, Great Britain
Am 14.02.2013 15:10, schrieb Markus Kuhn:
Paul Eggert wrote on 2013-01-13 07:23 UTC:
On 01/12/2013 10:00 PM, Jaakko Hyvätti wrote:
sooner or later it will be utf-8 as it has been for the rest of the world.
In the long term UTF-8 is no doubt the way to go, but we might not be quite there yet.
UTF-8 has been very well supported by all major Unix/Linux distibutions for nearly a decade now, and has been the default locale in most new installations since about 2005.
I strongly recommend that you use
unset LC_ALL LANG=en_US.UTF-8 # or en_GB.UTF-8, ... outside the US LC_COLLATE=POSIX # to avoid surprises with sorting order and globbing
With that, I hope that you will quickly find UTF-8 perfectly acceptable now in source code.
UTF-8 has long become common practice in comments of many open-source projects.
Markus
i prefer plain ascii because i get trouble from time to time with mixed code documentation. (last week some wired 16bit thing). being conservative seems the most practical way. just my 2 cents, wh
On 01/11/2013 06:51 AM, Deborah Goldsmith wrote:
Can anyone name a system in use today that is not capable of dealing with it?
It depends on what one means by "capable". When I type the command "emacs southamerica" here's some text that I see on my remote-shell terminal window: # A partir de entonces, San Luis establecer\u00E1 el huso horario propio de That is, Emacs correctly infers that the file uses Latin-1, but because I prefer the LC_ALL='C' locale it displays all non-ASCII characters by using hexadecimal escape sequences. It would do the same if the file used UTF-8. I could work around the problem by using, say, the the LC_ALL='en_US.utf8' locale, but that has some undesirable side effects (it mishandles character ranges, and it's noticeably slower for some other things I do), and I'd rather not. The main systems I use these days are Ubuntu 12.10, Fedora 17, and RHEL 6.3; these are all the latest stable versions, and they all work this way. I wouldn't be surprised if the latest OS X release worked this way too. For this particular case, the fix is simple: translate the text into English (it's an English-language database, after all). Names can be a bit trickier, but again, things are simpler (at least for this maintainer) if the commentary is in ASCII.
On 11/01/13 15:46, Paul Eggert wrote:
On 01/11/2013 06:51 AM, Deborah Goldsmith wrote:
Can anyone name a system in use today that is not capable of dealing with it?
It depends on what one means by "capable". When I type the command "emacs southamerica" here's some text that I see on my remote-shell terminal window:
# A partir de entonces, San Luis establecer\u00E1 el huso horario propio de
That is, Emacs correctly infers that the file uses Latin-1, but because I prefer the LC_ALL='C' locale it displays all non-ASCII characters by using hexadecimal escape sequences. It would do the same if the file used UTF-8. I could work around the problem by using, say, the the LC_ALL='en_US.utf8' locale, but that has some undesirable side effects (it mishandles character ranges, and it's noticeably slower for some other things I do), and I'd rather not.
The main systems I use these days are Ubuntu 12.10, Fedora 17, and RHEL 6.3; these are all the latest stable versions, and they all work this way. I wouldn't be surprised if the latest OS X release worked this way too.
At least for Ubuntu 12.10 you could try LC_ALL=C.utf8 for the others maybe LC_ALL= LANG=C LC_TYPE=en_US.UTF-8.
For this particular case, the fix is simple: translate the text into English (it's an English-language database, after all). Names can be a bit trickier, but again, things are simpler (at least for this maintainer) if the commentary is in ASCII.
Fair enough, but transliterating personal names into plain ASCII is problematic! -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
On 12/01/13 08:59, Ian Abbott wrote:
At least for Ubuntu 12.10 you could try LC_ALL=C.utf8 for the others maybe LC_ALL= LANG=C LC_TYPE=en_US.UTF-8.
Another typo: LC_CTYPE, not LC_TYPE. -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
Paul Eggert <eggert@cs.ucla.edu> wrote: |The HTML markup has bothered me, too; I have found it more |distracting than useful. URLs themselves should be fine, |but the <a href='...'> business gets in the way. How about turning over to a simple generic approach, as in L<http://www.url1.com> and/or L<Some descriptive text><http://www.url2.com> and having "I" for informational links that follow the same style but do not provide hyperlinks and "D" for dead links? I'll append a small script i have written the last few hours (i've driven car a dozen hours in the last 36 thereof, so please be patient and take it as a first draft only; it seems to work fine, however). That thing may be used in two different ways: htwork.pl html [<] DATA_FILE | lynx -stdin htwork.pl check [<] DATA_FILE > NEW_DATA_FILE The first mode will produce a valid HTML file, expanding all L<> links along the way (ditto the others, but differently, text-only). The second will check the L<> URLs, and replace them with D<> URLs if curl(1) cannot access the file (i think using curl(1) should be fine as git(1) seems to be the new direction of the tz database). That could be used pre-release to update the data-content automatically, or to adjust the links manually. (Say.) Both modes can also work with STDIN. I've also converted "southamerica" to this new syntax, and append it here. Note that there would be many D<> links, if they would be checked. I don't know emacs(1) (i need some memory for other tasks :) nor Lisp, but i could surely write a perl(1) script that converts UTF-8 mail text into HTML (numeric) entities. Like that we could end up with a good solution that would satisfy all parties; plain ASCII text, even in the comment part, that would be more readable and more unique than today. And, if transformed via 'htwork.pl html', valid, browsable UTF-8 HTML data with unmodified names of people and earth locations. If that would be an acceptable approach then i would volunteer to convert the other links in the database files to this new syntax. (I need two more weeks to release the next version of my mailer, which i'm looking forward to a lot, but afterwards i would go for it.) Thanks and ciao, --steffen diff --git a/htwork.pl b/htwork.pl new file mode 100755 index 0000000..64f0cb3 --- /dev/null +++ b/htwork.pl @@ -0,0 +1,182 @@ +#!/usr/bin/env perl +require 5.008_001; +#@ htwork.pl - HTML reference checks / output dumper for tz data files. +#@ Public domain, 2013, Steffen Nurpmeso. +#@ Synopsis: htwork.pl html < DATA_FILE | lynx -stdin +#@ Synopsis: htwork.pl check < DATA_FILE > NEW_DATA_FILE +#@ The latter mode requires an installed curl(1) (<http://curl.haxx.se>). +#@ Understood links: L<URL>, L<Text><URL>. Dead links: D<URL>, D<Text><URL>. +#@ Links that should not be converted (informational): I<URL>, I<Text><URL>. +#@ XXX Assumes links fit on one line. + +my $CURL = 'curl -q --silent --fail --head --location'; + +## -- >8 -- 8< -- ## + +use diagnostics -verbose; +use strict; +use warnings; + +# We do support L<URL> and L<text><URL>; D instead of L is for dead links. +my $URL_CONTENT = qr{ + (.*?) + (l|d|i) + <([^>]+)> + (?:<([^>]+)>)? + (.*) +}xi; + +my $EX_USAGE = 64; +my $EX_NOINPUT = 66; +my $INPUT; + +sub main_fun { + usage($EX_USAGE) unless @ARGV >= 1; + usage() if $ARGV[0] eq '-h' || $ARGV[0] eq '--help'; + if (@ARGV == 1) { + $INPUT = *STDIN; + if (! -f $INPUT) { + print STDERR "No file argument, and STDIN is not a file.\n\n"; + usage($EX_NOINPUT); + } + } elsif (! -f $ARGV[1]) { + print STDERR "File \"${ARGV[1]}\" does not exist.\n\n"; + usage($EX_NOINPUT); + } elsif (! open $INPUT, '<', $ARGV[1]) { + print STDERR "File \"${ARGV[1]}\" cannot be opened for reading.\n\n"; + usage($EX_NOINPUT); + } + mode_html() if $ARGV[0] eq 'html'; + mode_check() if $ARGV[0] eq 'check'; + usage($EX_USAGE); +} + +sub usage { + print STDERR <<__EOT__; +Synopsis: + htwork.pl html < DATA_FILE | lynx -stdin + htwork.pl check < DATA_FILE > NEW_DATA_FILE + +The first mode expands the links of a tz data file and generates +a simple HTML page that can easily be reviewed and browsed and re- +veals the native languages of entry authors, cities and regions. + +The second mode is used in the release phase of the tz zoneinfo +database and checks all L<> and L<><> links for resolvability, +converting all those to D<> and D<><> (dead link) entries that +cannot be resolved. I<> and I<><> links are left alone. +This mode requires an installed curl(1) (<http://curl.haxx.se>). +__EOT__ + + exit(@_ ? $_[0] : 0) +} + +sub mode_html { + print <<__EOT__; +<html> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> +<body> +<pre> +__EOT__ + + while (<$INPUT>) { + my $ld = parse_line($_); + if (! $ld->[0] || ! ($ld->[1] =~ $URL_CONTENT)) { + die unless print $ld->[1], "\n"; + next; + } + + my ($ln, $rest); + do { + $ln .= $1 ? $1 : ''; + $rest = $5; + my $comm = lc $2; + my $url = $4 ? $4 : $3; + my $text = $4 ? $3 : ''; + if ($comm eq 'l') { + $text = $url unless $text; + $ln .= '<a href="' . $url . '">' . $text . '</a>'; + } else { + $comm = ($comm eq 'd') ? '[dead] ' : ''; + if ($text) { + $ln .= '(' . $comm . $text . ' -- <' . $url . '>)'; + } else { + $ln .= '(' . $comm . '<' . $url . '>)'; + } + } + } while $rest =~ $URL_CONTENT; + $ln .= $rest if $rest; + die unless print $ln, "\n"; + } + die unless close $INPUT; + + print <<__EOT__; +</pre> +</body> +</html> +<!-- vim:set fenc=utf-8 syntax=html ts=8 sts=8 sw=8 noet tw=79: --> +__EOT__ + + exit +} + +sub mode_check { + while (<$INPUT>) { + my $ld = parse_line($_); + if (! $ld->[0] || ! ($ld->[1] =~ $URL_CONTENT)) { + die unless print $ld->[1], "\n"; + next; + } + + my ($ln, $rest); + do { + $ln .= $1 ? $1 : ''; + $rest = $5; + my $comm = lc $2; + my $url = $4 ? $4 : $3; + my $text = $4 ? $3 : ''; + if ($comm ne 'l') { + $comm = uc $comm; + if ($text) { + $ln .= $comm . '<' . $text . '><' . $url . '>'; + } else { + $ln .= $comm . '<' . $url . '>'; + } + next; + } + + print STDERR " Checking URL <$url> "; + system($CURL . ' "' . $url . '" >/dev/null 2>/dev/null'); + die 'Cannot exec curl(1)' if $? < 0; + die 'curl(1) died with signal' if $? & 127; + if ($? >> 8) { + $comm = 'D'; + print STDERR "ERROR!\r!\n"; + } else { + $comm = uc $comm; + print STDERR "ok\r.\n"; + } + if ($text) { + $ln .= $comm . '<' . $text . '><' . $url . '>'; + } else { + $ln .= $comm . '<' . $url . '>'; + } + } while $rest =~ $URL_CONTENT; + $ln .= $rest if $rest; + die unless print $ln, "\n"; + } + die unless close $INPUT; + exit +} + +sub parse_line { + my ($line, $is_comm) = ($_[0]); + chomp $line; + $is_comm = ($line =~ /\s*#/) ? 1 : 0; + [ $is_comm, $line ] +} + +{package main; main_fun()} + +# vim:set fenc=utf-8 syntax=perl ts=8 sts=3 sw=3 et tw=79: diff --git a/southamerica b/southamerica index e4c8720..2e1c973 100644 --- a/southamerica +++ b/southamerica @@ -1,4 +1,3 @@ -# <pre> # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. @@ -126,21 +125,21 @@ Rule Arg 2000 only - Mar 3 0:00 0 - # one of the major newspapers here in Argentina said that the 1999 # Timezone Law (which never was effectively applied) will (would?) be # in effect.... The article is at -# http://ar.clarin.com/diario/2001-06-06/e-01701.htm +# L<http://ar.clarin.com/diario/2001-06-06/e-01701.htm> # ... The Law itself is "Ley No 25155", sanctioned on 1999-08-25, enacted # 1999-09-17, and published 1999-09-21. The official publication is at: -# http://www.boletin.jus.gov.ar/BON/Primera/1999/09-Septiembre/21/PDF/BO21-09-... +# L<http://www.boletin.jus.gov.ar/BON/Primera/1999/09-Septiembre/21/PDF/BO21-09-...> # Regretfully, you have to subscribe (and pay) for the on-line version.... # # (2001-06-12): # the timezone for Argentina will not change next Sunday. # Apparently it will do so on Sunday 24th.... -# http://ar.clarin.com/diario/2001-06-12/s-03501.htm +# L<http://ar.clarin.com/diario/2001-06-12/s-03501.htm> # # (2001-06-25): # Last Friday (yes, the last working day before the date of the change), the # Senate annulled the 1999 law that introduced the changes later postponed. -# http://www.clarin.com.ar/diario/2001-06-22/s-03601.htm +# L<http://www.clarin.com.ar/diario/2001-06-22/s-03601.htm> # It remains the vote of the Deputies..., but it will be the same.... # This kind of things had always been done this way in Argentina. # We are still -03:00 all year round in all of the country. @@ -148,7 +147,7 @@ Rule Arg 2000 only - Mar 3 0:00 0 - # From Steffen Thorsen (2007-12-21): # A user (Leonardo Chaim) reported that Argentina will adopt DST.... # all of the country (all Zone-entries) are affected. News reports like -# http://www.lanacion.com.ar/opinion/nota.asp?nota_id=973037 indicate +# L<http://www.lanacion.com.ar/opinion/nota.asp?nota_id=973037> indicate # that Argentina will use DST next year as well, from October to # March, although exact rules are not given. # @@ -158,9 +157,7 @@ Rule Arg 2000 only - Mar 3 0:00 0 - # By the way thanks to Mariano Absatz and Daniel Mario Vega for the link to # the original scanned proposal, where the dates and the zero hours are # clear and unambiguous...This is the article about final approval: -# <a href="http://www.lanacion.com.ar/politica/nota.asp?nota_id=973996"> -# http://www.lanacion.com.ar/politica/nota.asp?nota_id=973996 -# </a> +# L<http://www.lanacion.com.ar/politica/nota.asp?nota_id=973996> # # From Paul Eggert (2007-12-22): # For dates after mid-2008, the following rules are my guesses and @@ -170,13 +167,9 @@ Rule Arg 2000 only - Mar 3 0:00 0 - # As per message from Carlos Alberto Fonseca Arauz (Nicaragua), # Argentina will start DST on Sunday October 19, 2008. # -# <a href="http://www.worldtimezone.com/dst_news/dst_news_argentina03.html"> -# http://www.worldtimezone.com/dst_news/dst_news_argentina03.html -# </a> +# L<http://www.worldtimezone.com/dst_news/dst_news_argentina03.html> # OR -# <a href="http://www.impulsobaires.com.ar/nota.php?id=57832 (in spanish)"> -# http://www.impulsobaires.com.ar/nota.php?id=57832 (in spanish) -# </a> +# L<(in spanish)><http://www.impulsobaires.com.ar/nota.php?id=57832> # From Rodrigo Severo (2008-10-06): # Here is some info available at a Gentoo bug related to TZ on Argentina's DST: @@ -185,40 +178,28 @@ Rule Arg 2000 only - Mar 3 0:00 0 - # Hi, there is a problem with timezone-data-2008e and maybe with # timezone-data-2008f # Argentinian law [Number] 25.155 is no longer valid. -# <a href="http://www.infoleg.gov.ar/infolegInternet/anexos/60000-64999/60036/norma.htm"> -# http://www.infoleg.gov.ar/infolegInternet/anexos/60000-64999/60036/norma.htm -# </a> +# L<http://www.infoleg.gov.ar/infolegInternet/anexos/60000-64999/60036/norma.htm> # The new one is law [Number] 26.350 -# <a href="http://www.infoleg.gov.ar/infolegInternet/anexos/135000-139999/136191/norma.htm"> -# http://www.infoleg.gov.ar/infolegInternet/anexos/135000-139999/136191/norma.... -# </a> +# L<http://www.infoleg.gov.ar/infolegInternet/anexos/135000-139999/136191/norma....> # So there is no summer time in Argentina for now. # From Mariano Absatz (2008-10-20): # Decree 1693/2008 applies Law 26.350 for the summer 2008/2009 establishing DST in Argentina # From 2008-10-19 until 2009-03-15 -# <a href="http://www.boletinoficial.gov.ar/Bora.Portal/CustomControls/PdfContent.aspx?fp=16102008&pi=3&pf=4&s=0&sec=01"> -# http://www.boletinoficial.gov.ar/Bora.Portal/CustomControls/PdfContent.aspx?... -# </a> +# L<http://www.boletinoficial.gov.ar/Bora.Portal/CustomControls/PdfContent.aspx?...> # # Decree 1705/2008 excepting 12 Provinces from applying DST in the summer 2008/2009: # Catamarca, La Rioja, Mendoza, Salta, San Juan, San Luis, La Pampa, Neuquen, Rio Negro, Chubut, Santa Cruz # and Tierra del Fuego -# <a href="http://www.boletinoficial.gov.ar/Bora.Portal/CustomControls/PdfContent.aspx?fp=17102008&pi=1&pf=1&s=0&sec=01"> -# http://www.boletinoficial.gov.ar/Bora.Portal/CustomControls/PdfContent.aspx?... -# </a> +# L<http://www.boletinoficial.gov.ar/Bora.Portal/CustomControls/PdfContent.aspx?...> # # Press release 235 dated Saturday October 18th, from the Government of the Province of Jujuy saying # it will not apply DST either (even when it was not included in Decree 1705/2008) -# <a href="http://www.jujuy.gov.ar/index2/partes_prensa/18_10_08/235-181008.doc"> -# http://www.jujuy.gov.ar/index2/partes_prensa/18_10_08/235-181008.doc -# </a> +# L<http://www.jujuy.gov.ar/index2/partes_prensa/18_10_08/235-181008.doc> # From fullinet (2009-10-18): # As announced in -# <a hef="http://www.argentina.gob.ar/argentina/portal/paginas.dhtml?pagina=356"> -# http://www.argentina.gob.ar/argentina/portal/paginas.dhtml?pagina=356 -# </a> +# L<http://www.argentina.gob.ar/argentina/portal/paginas.dhtml?pagina=356> # (an official .gob.ar) under title: "Sin Cambio de Hora" (english: "No hour change") # # "Por el momento, el Gobierno Nacional resolvio no modificar la hora @@ -235,22 +216,21 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # From Mariano Absatz (2004-05-21): # Today it was officially published that the Province of Mendoza is changing # its timezone this winter... starting tomorrow night.... -# http://www.gobernac.mendoza.gov.ar/boletin/pdf/20040521-27158-normas.pdf +# L<http://www.gobernac.mendoza.gov.ar/boletin/pdf/20040521-27158-normas.pdf> # From Paul Eggert (2004-05-24): # It's Law No. 7,210. This change is due to a public power emergency, so for # now we'll assume it's for this year only. # # From Paul Eggert (2006-03-22): -# <a href="http://www.spicasc.net/horvera.html"> -# Hora de verano para la Republica Argentina (2003-06-08) -# </a> says that standard time in Argentina from 1894-10-31 +# L<Hora de verano para la Republica Argentina (2003-06-08)><http://www.spicasc.net/horvera.html> +# says that standard time in Argentina from 1894-10-31 # to 1920-05-01 was -4:16:48.25. Go with this more-precise value # over Shanks & Pottenger. # # From Mariano Absatz (2004-06-05): # These media articles from a major newspaper mostly cover the current state: -# http://www.lanacion.com.ar/04/05/27/de_604825.asp -# http://www.lanacion.com.ar/04/05/28/de_605203.asp +# L<http://www.lanacion.com.ar/04/05/27/de_604825.asp> +# L<http://www.lanacion.com.ar/04/05/28/de_605203.asp> # # The following eight (8) provinces pulled clocks back to UTC-04:00 at # midnight Monday May 31st. (that is, the night between 05/31 and 06/01). @@ -266,7 +246,7 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # annoyance with the change is much higher than the power savings obtained.... # # From Gwillim Law (2004-06-14): -# http://www.lanacion.com.ar/04/06/10/de_609078.asp ... +# L<http://www.lanacion.com.ar/04/06/10/de_609078.asp> ... # "The time change in Tierra del Fuego was a conflicted decision from # the start. The government had decreed that the measure would take # effect on June 1, but a normative error forced the new time to begin @@ -282,15 +262,15 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # The previous law 7210 which changed the province of Mendoza's time zone # back in May have been modified slightly in a new law 7277, which set the # new end date to 2004-09-26 (original date was 2004-10-17). -# http://www.gobernac.mendoza.gov.ar/boletin/pdf/20040924-27244-normas.pdf +# L<http://www.gobernac.mendoza.gov.ar/boletin/pdf/20040924-27244-normas.pdf> # # From Mariano Absatz (2004-10-05): # San Juan changed from UTC-03:00 to UTC-04:00 at midnight between # Sunday, May 30th and Monday, May 31st. It changed back to UTC-03:00 # at midnight between Saturday, July 24th and Sunday, July 25th.... -# http://www.sanjuan.gov.ar/prensa/archivo/000329.html -# http://www.sanjuan.gov.ar/prensa/archivo/000426.html -# http://www.sanjuan.gov.ar/prensa/archivo/000441.html +# L<http://www.sanjuan.gov.ar/prensa/archivo/000329.html> +# L<http://www.sanjuan.gov.ar/prensa/archivo/000426.html> +# L<http://www.sanjuan.gov.ar/prensa/archivo/000441.html> # From Alex Krivenyshev (2008-01-17): # Here are articles that Argentina Province San Luis is planning to end DST @@ -299,25 +279,17 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # Provincia argentina retrasa reloj y marca diferencia con resto del pais # (Argentine Province delayed clock and mark difference with the rest of the # country) -# <a href="http://cl.invertia.com/noticias/noticia.aspx?idNoticia=200801171849_EFE_ET4373&idtel"> -# http://cl.invertia.com/noticias/noticia.aspx?idNoticia=200801171849_EFE_ET43... -# </a> +# L<http://cl.invertia.com/noticias/noticia.aspx?idNoticia=200801171849_EFE_ET43...> # # Es inminente que en San Luis atrasen una hora los relojes # (It is imminent in San Luis clocks one hour delay) -# <a href="http://www.lagaceta.com.ar/vernotae.asp?id_nota=253414"> -# http://www.lagaceta.com.ar/vernotae.asp?id_nota=253414 -# </a> +# L<http://www.lagaceta.com.ar/vernotae.asp?id_nota=253414> # -# <a href="http://www.worldtimezone.net/dst_news/dst_news_argentina02.html"> -# http://www.worldtimezone.net/dst_news/dst_news_argentina02.html -# </a> +# L<http://www.worldtimezone.net/dst_news/dst_news_argentina02.html> # From Jesper Norgaard Welen (2008-01-18): # The page of the San Luis provincial government -# <a href="http://www.sanluis.gov.ar/notas.asp?idCanal=0&id=22812"> -# http://www.sanluis.gov.ar/notas.asp?idCanal=0&id=22812 -# </a> +# L<http://www.sanluis.gov.ar/notas.asp?idCanal=0&id=22812> # confirms what Alex Krivenyshev has earlier sent to the tz # emailing list about that San Luis plans to return to standard # time much earlier than the rest of the country. It also @@ -336,9 +308,7 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # important pages of 2008." # # You can use -# <a href="http://www.sanluis.gov.ar/notas.asp?idCanal=8141&id=22834"> -# http://www.sanluis.gov.ar/notas.asp?idCanal=8141&id=22834 -# </a> +# L<http://www.sanluis.gov.ar/notas.asp?idCanal=8141&id=22834> # instead it seems. Or use "Buscador" from the main page of the San Luis # government, and fill in "huso" and click OK, and you will get 3 pages # from which the first one is identical to the above. @@ -372,17 +342,12 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # to utc-04:00 until the second Saturday in October... # # The press release is at -# <a href="http://www.sanluis.gov.ar/SL/Paginas/NoticiaDetalle.asp?TemaId=1&InfoPrensaId=3102"> -# http://www.sanluis.gov.ar/SL/Paginas/NoticiaDetalle.asp?TemaId=1&InfoPrensaI... -# </a> -# (I couldn't find the decree, but -# <a href="http://www.sanluis.gov.ar"> -# www.sanluis.gov.ar -# <a/> +# L<http://www.sanluis.gov.ar/SL/Paginas/NoticiaDetalle.asp?TemaId=1&InfoPrensaI...> +# (I couldn't find the decree, but L<http://www.sanluis.gov.ar> # is the official page for the Province Government). # # There's also a note in only one of the major national papers ... -# http://www.lanacion.com.ar/nota.asp?nota_id=1107912 +# L<http://www.lanacion.com.ar/nota.asp?nota_id=1107912> # # The press release says [quick and dirty translation]: # ... announced that next Sunday, at 00:00, Puntanos (the San Luis @@ -396,9 +361,7 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # ...the Province of San Luis is a case in itself. # # The Law at -# <a href="http://www.diputadossanluis.gov.ar/diputadosasp/paginas/verNorma.asp?NormaID...>" -# http://www.diputadossanluis.gov.ar/diputadosasp/paginas/verNorma.asp?NormaID... -# </a> +# L<http://www.diputadossanluis.gov.ar/diputadosasp/paginas/verNorma.asp?NormaID...> # is ambiguous because establishes a calendar from the 2nd Sunday in # October at 0:00 thru the 2nd Saturday in March at 24:00 and the # complement of that starting on the 2nd Sunday of March at 0:00 and @@ -433,13 +396,9 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # Argentina (UTC-3) (no DST). # # Confirmaron la prórroga del huso horario de verano (Spanish) -# <a href="http://www.eldiariodelarepublica.com/index.php?option=com_content&task=view&id=29383&Itemid=9"> -# http://www.eldiariodelarepublica.com/index.php?option=com_content&task=view&... -# </a> +# L<http://www.eldiariodelarepublica.com/index.php?option=com_content&task=view&...> # or (some English translation): -# <a href="http://www.worldtimezone.com/dst_news/dst_news_argentina08.html"> -# http://www.worldtimezone.com/dst_news/dst_news_argentina08.html -# </a> +# L<http://www.worldtimezone.com/dst_news/dst_news_argentina08.html> # From Mariano Absatz (2010-04-12): # yes...I can confirm this...and given that San Luis keeps calling @@ -672,14 +631,12 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # Norte (RN), and the eastern part of Para (PA) are all in BR1 without DST. # From Marcos Tadeu (1998-09-27): -# <a href="http://pcdsh01.on.br/verao1.html"> -# Brazilian official page -# </a> +# L<Brazilian official page><http://pcdsh01.on.br/verao1.html> # From Jesper Norgaard (2000-11-03): # [For an official list of which regions in Brazil use which time zones, see:] -# http://pcdsh01.on.br/Fusbr.htm -# http://pcdsh01.on.br/Fusbrhv.htm +# L<http://pcdsh01.on.br/Fusbr.htm> +# L<http://pcdsh01.on.br/Fusbrhv.htm> # From Celso Doria via David Madeo (2002-10-09): # The reason for the delay this year has to do with elections in Brazil. @@ -705,7 +662,7 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # From Steffen Thorsen (2007-09-20): # Brazil will start DST on 2007-10-14 00:00 and end on 2008-02-17 00:00: -# http://www.mme.gov.br/site/news/detail.do;jsessionid=BBA06811AFCAAC28F028521... +# L<http://www.mme.gov.br/site/news/detail.do;jsessionid=BBA06811AFCAAC28F028521...> # From Paul Schulze (2008-06-24): # ...by law number 11.662 of April 24, 2008 (published in the "Diario @@ -728,9 +685,7 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # From Rodrigo Severo (2008-06-24): # Just correcting the URL: -# <a href="https://www.in.gov.br/imprensa/visualiza/index.jsp?jornal=do&secao=1&pagina=1&data=25/04/2008"> -# https://www.in.gov.br/imprensa/visualiza/index.jsp?jornal=do&secao=1&pagina=... -# </a> +# L<https://www.in.gov.br/imprensa/visualiza/index.jsp?jornal=do&secao=1&pagina=...> # # As a result of the above Decree I believe the America/Rio_Branco # timezone shall be modified from UTC-5 to UTC-4 and a new timezone shall @@ -743,9 +698,7 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # From Alex Krivenyshev (2008-06-24): # This is a quick reference page for New and Old Brazil Time Zones map. -# <a href="http://www.worldtimezone.com/brazil-time-new-old.php"> -# http://www.worldtimezone.com/brazil-time-new-old.php -# </a> +# L<http://www.worldtimezone.com/brazil-time-new-old.php> # # - 4 time zones replaced by 3 time zones-eliminating time zone UTC- 05 # (state Acre and the part of the Amazonas will be UTC/GMT- 04) - western @@ -753,9 +706,7 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # From Paul Eggert (2002-10-10): # The official decrees referenced below are mostly taken from -# <a href="http://pcdsh01.on.br/DecHV.html"> -# Decretos sobre o Horario de Verao no Brasil -# </a>. +# L<Decretos sobre o Horario de Verao no Brasil><http://pcdsh01.on.br/DecHV.html>. # From Steffen Thorsen (2008-08-29): # As announced by the government and many newspapers in Brazil late @@ -764,28 +715,18 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # past years experience with the elections, there was a good chance that # the start was postponed to November, but it did not happen this year. # -# It has not yet been posted to http://pcdsh01.on.br/DecHV.html +# It has not yet been posted to L<http://pcdsh01.on.br/DecHV.html> # # An official page about it: -# <a href="http://www.mme.gov.br/site/news/detail.do?newsId=16722"> -# http://www.mme.gov.br/site/news/detail.do?newsId=16722 -# </a> +# <http://www.mme.gov.br/site/news/detail.do?newsId=16722> # Note that this link does not always work directly, but must be accessed -# by going to -# <a href="http://www.mme.gov.br/first"> -# http://www.mme.gov.br/first -# </a> +# by going to L<http://www.mme.gov.br/first> # # One example link that works directly: -# <a href="http://jornale.com.br/index.php?option=com_content&task=view&id=13530&Itemid=54"> -# http://jornale.com.br/index.php?option=com_content&task=view&id=13530&Itemid... -# (Portuguese) -# </a> +# L<http://jornale.com.br/index.php?option=com_content&task=view&id=13530&Itemid...> (Portuguese) # # We have a written a short article about it as well: -# <a href="http://www.timeanddate.com/news/time/brazil-dst-2008-2009.html"> -# http://www.timeanddate.com/news/time/brazil-dst-2008-2009.html -# </a> +# L<http://www.timeanddate.com/news/time/brazil-dst-2008-2009.html> # # From Alexander Krivenyshev (2011-10-04): # State Bahia will return to Daylight savings time this year after 8 years off. @@ -793,19 +734,15 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # television station in Salvador. # In Portuguese: -# <a href="http://g1.globo.com/bahia/noticia/2011/10/governador-jaques-wagner-confirma-horario-de-verao-na-bahia.html"> -# http://g1.globo.com/bahia/noticia/2011/10/governador-jaques-wagner-confirma-... -# </a> and -# <a href="http://noticias.terra.com.br/brasil/noticias/0,,OI5390887-EI8139,00-Bahia+volta+a+ter+horario+de+verao+apos+oito+anos.html"> -# http://noticias.terra.com.br/brasil/noticias/0,,OI5390887-EI8139,00-Bahia+vo... -# </a> +# L<http://g1.globo.com/bahia/noticia/2011/10/governador-jaques-wagner-confirma-...> +# and +# L<http://noticias.terra.com.br/brasil/noticias/0,,OI5390887-EI8139,00-Bahia+vo...> # From Guilherme Bernardes Rodrigues (2011-10-07): # There is news in the media, however there is still no decree about it. # I just send a e-mail to Zulmira Brandao at -# <a href="http://pcdsh01.on.br/">http://pcdsh01.on.br/</a> the -# official agency about time in Brazil, and she confirmed that the old rule is -# still in force. +# L<http://pcdsh01.on.br/>, the official agency about time in Brazil, and she +# confirmed that the old rule is still in force. # From Guilherme Bernardes Rodrigues (2011-10-14) # It's official, the President signed a decree that includes Bahia in summer @@ -815,57 +752,55 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # # DECRETO No- 7.584, DE 13 DE OUTUBRO DE 2011 # Link : -# <a href="http://www.in.gov.br/visualiza/index.jsp?data=13/10/2011&jornal=1000&pagina=6&totalArquivos=6"> -# http://www.in.gov.br/visualiza/index.jsp?data=13/10/2011&jornal=1000&pagina=... -# </a> +# L<http://www.in.gov.br/visualiza/index.jsp?data=13/10/2011&jornal=1000&pagina=...> # From Kelley Cook (2012-10-16): # The governor of state of Bahia in Brazil announced on Thursday that # due to public pressure, he is reversing the DST policy they implemented # last year and will not be going to Summer Time on October 21st.... -# http://www.correio24horas.com.br/r/artigo/apos-pressoes-wagner-suspende-hora... +# L<http://www.correio24horas.com.br/r/artigo/apos-pressoes-wagner-suspende-hora...> # From Rodrigo Severo (2012-10-16): # Tocantins state will have DST. -# http://noticias.terra.com.br/brasil/noticias/0,,OI6232536-EI306.html +# L<http://noticias.terra.com.br/brasil/noticias/0,,OI6232536-EI306.html> # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -# Decree <a href="http://pcdsh01.on.br/HV20466.htm">20,466</a> (1931-10-01) -# Decree <a href="http://pcdsh01.on.br/HV21896.htm">21,896</a> (1932-01-10) +# Decree L<20,466><http://pcdsh01.on.br/HV20466.htm> (1931-10-01) +# Decree L<21,896><http://pcdsh01.on.br/HV21896.htm> (1932-01-10) Rule Brazil 1931 only - Oct 3 11:00 1:00 S Rule Brazil 1932 1933 - Apr 1 0:00 0 - Rule Brazil 1932 only - Oct 3 0:00 1:00 S -# Decree <a href="http://pcdsh01.on.br/HV23195.htm">23,195</a> (1933-10-10) +# Decree L<23,195><http://pcdsh01.on.br/HV23195.htm> (1933-10-10) # revoked DST. -# Decree <a href="http://pcdsh01.on.br/HV27496.htm">27,496</a> (1949-11-24) -# Decree <a href="http://pcdsh01.on.br/HV27998.htm">27,998</a> (1950-04-13) +# Decree L<27,496><http://pcdsh01.on.br/HV27496.htm> (1949-11-24) +# Decree L<27,998><http://pcdsh01.on.br/HV27998.htm> (1950-04-13) Rule Brazil 1949 1952 - Dec 1 0:00 1:00 S Rule Brazil 1950 only - Apr 16 1:00 0 - Rule Brazil 1951 1952 - Apr 1 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/HV32308.htm">32,308</a> (1953-02-24) +# Decree L<32,308><http://pcdsh01.on.br/HV32308.htm> (1953-02-24) Rule Brazil 1953 only - Mar 1 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/HV34724.htm">34,724</a> (1953-11-30) +# Decree L<34,724><http://pcdsh01.on.br/HV34724.htm> (1953-11-30) # revoked DST. -# Decree <a href="http://pcdsh01.on.br/HV52700.htm">52,700</a> (1963-10-18) +# Decree L<52,700><http://pcdsh01.on.br/HV52700.htm> (1963-10-18) # established DST from 1963-10-23 00:00 to 1964-02-29 00:00 # in SP, RJ, GB, MG, ES, due to the prolongation of the drought. -# Decree <a href="http://pcdsh01.on.br/HV53071.htm">53,071</a> (1963-12-03) +# Decree L<53,071><http://pcdsh01.on.br/HV53071.htm> (1963-12-03) # extended the above decree to all of the national territory on 12-09. Rule Brazil 1963 only - Dec 9 0:00 1:00 S -# Decree <a href="http://pcdsh01.on.br/HV53604.htm">53,604</a> (1964-02-25) +# Decree L<53,604><http://pcdsh01.on.br/HV53604.htm> (1964-02-25) # extended summer time by one day to 1964-03-01 00:00 (start of school). Rule Brazil 1964 only - Mar 1 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/HV55639.htm">55,639</a> (1965-01-27) +# Decree L<55,639><http://pcdsh01.on.br/HV55639.htm> (1965-01-27) Rule Brazil 1965 only - Jan 31 0:00 1:00 S Rule Brazil 1965 only - Mar 31 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/HV57303.htm">57,303</a> (1965-11-22) +# Decree L<57,303><http://pcdsh01.on.br/HV57303.htm> (1965-11-22) Rule Brazil 1965 only - Dec 1 0:00 1:00 S -# Decree <a href="http://pcdsh01.on.br/HV57843.htm">57,843</a> (1966-02-18) +# Decree L<57,843><http://pcdsh01.on.br/HV57843.htm> (1966-02-18) Rule Brazil 1966 1968 - Mar 1 0:00 0 - Rule Brazil 1966 1967 - Nov 1 0:00 1:00 S -# Decree <a href="http://pcdsh01.on.br/HV63429.htm">63,429</a> (1968-10-15) +# Decree L<63,429><http://pcdsh01.on.br/HV63429.htm> (1968-10-15) # revoked DST. -# Decree <a href="http://pcdsh01.on.br/HV91698.htm">91,698</a> (1985-09-27) +# Decree L<91,698><http://pcdsh01.on.br/HV91698.htm> (1985-09-27) Rule Brazil 1985 only - Nov 2 0:00 1:00 S # Decree 92,310 (1986-01-21) # Decree 92,463 (1986-03-13) @@ -873,42 +808,42 @@ Rule Brazil 1986 only - Mar 15 0:00 0 - # Decree 93,316 (1986-10-01) Rule Brazil 1986 only - Oct 25 0:00 1:00 S Rule Brazil 1987 only - Feb 14 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/HV94922.htm">94,922</a> (1987-09-22) +# Decree L<94,922><http://pcdsh01.on.br/HV94922.htm> (1987-09-22) Rule Brazil 1987 only - Oct 25 0:00 1:00 S Rule Brazil 1988 only - Feb 7 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/HV96676.htm">96,676</a> (1988-09-12) +# Decree L<96,676><http://pcdsh01.on.br/HV96676.htm> (1988-09-12) # except for the states of AC, AM, PA, RR, RO, and AP (then a territory) Rule Brazil 1988 only - Oct 16 0:00 1:00 S Rule Brazil 1989 only - Jan 29 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/HV98077.htm">98,077</a> (1989-08-21) +# Decree L<98,077><http://pcdsh01.on.br/HV98077.htm> (1989-08-21) # with the same exceptions Rule Brazil 1989 only - Oct 15 0:00 1:00 S Rule Brazil 1990 only - Feb 11 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/HV99530.htm">99,530</a> (1990-09-17) +# Decree L<99,530><http://pcdsh01.on.br/HV99530.htm> (1990-09-17) # adopted by RS, SC, PR, SP, RJ, ES, MG, GO, MS, DF. # Decree 99,629 (1990-10-19) adds BA, MT. Rule Brazil 1990 only - Oct 21 0:00 1:00 S Rule Brazil 1991 only - Feb 17 0:00 0 - -# <a href="http://pcdsh01.on.br/HV1991.htm">Unnumbered decree</a> (1991-09-25) +# L<Unnumbered decree><http://pcdsh01.on.br/HV1991.htm> (1991-09-25) # adopted by RS, SC, PR, SP, RJ, ES, MG, BA, GO, MT, MS, DF. Rule Brazil 1991 only - Oct 20 0:00 1:00 S Rule Brazil 1992 only - Feb 9 0:00 0 - -# <a href="http://pcdsh01.on.br/HV1992.htm">Unnumbered decree</a> (1992-10-16) +# L<Unnumbered decree><http://pcdsh01.on.br/HV1992.htm> (1992-10-16) # adopted by same states. Rule Brazil 1992 only - Oct 25 0:00 1:00 S Rule Brazil 1993 only - Jan 31 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/HV942.htm">942</a> (1993-09-28) +# Decree L<942><http://pcdsh01.on.br/HV942.htm> (1993-09-28) # adopted by same states, plus AM. -# Decree <a href="http://pcdsh01.on.br/HV1252.htm">1,252</a> (1994-09-22; +# Decree L<1,252><http://pcdsh01.on.br/HV1252.htm> (1994-09-22; # web page corrected 2004-01-07) adopted by same states, minus AM. -# Decree <a href="http://pcdsh01.on.br/HV1636.htm">1,636</a> (1995-09-14) +# Decree L<1,636><http://pcdsh01.on.br/HV1636.htm> (1995-09-14) # adopted by same states, plus MT and TO. -# Decree <a href="http://pcdsh01.on.br/HV1674.htm">1,674</a> (1995-10-13) +# Decree L<1,674><http://pcdsh01.on.br/HV1674.htm> (1995-10-13) # adds AL, SE. Rule Brazil 1993 1995 - Oct Sun>=11 0:00 1:00 S Rule Brazil 1994 1995 - Feb Sun>=15 0:00 0 - Rule Brazil 1996 only - Feb 11 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/HV2000.htm">2,000</a> (1996-09-04) +# Decree L<2,000><http://pcdsh01.on.br/HV2000.htm> (1996-09-04) # adopted by same states, minus AL, SE. Rule Brazil 1996 only - Oct 6 0:00 1:00 S Rule Brazil 1997 only - Feb 16 0:00 0 - @@ -921,53 +856,51 @@ Rule Brazil 1997 only - Feb 16 0:00 0 - # # Decree 2,317 (1997-09-04), adopted by same states. Rule Brazil 1997 only - Oct 6 0:00 1:00 S -# Decree <a href="http://pcdsh01.on.br/figuras/HV2495.JPG">2,495</a> +# Decree L<2,495><http://pcdsh01.on.br/figuras/HV2495.JPG> # (1998-02-10) Rule Brazil 1998 only - Mar 1 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/figuras/Hv98.jpg">2,780</a> (1998-09-11) +# Decree L<2,780><http://pcdsh01.on.br/figuras/Hv98.jpg> (1998-09-11) # adopted by the same states as before. Rule Brazil 1998 only - Oct 11 0:00 1:00 S Rule Brazil 1999 only - Feb 21 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/figuras/HV3150.gif">3,150</a> -# (1999-08-23) adopted by same states. -# Decree <a href="http://pcdsh01.on.br/DecHV99.gif">3,188</a> (1999-09-30) +# Decree L<3,150><http://pcdsh01.on.br/figuras/HV3150.gif> (1999-08-23) +# adopted by same states. +# Decree L<3,188><http://pcdsh01.on.br/DecHV99.gif> (1999-09-30) # adds SE, AL, PB, PE, RN, CE, PI, MA and RR. Rule Brazil 1999 only - Oct 3 0:00 1:00 S Rule Brazil 2000 only - Feb 27 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/DEC3592.htm">3,592</a> (2000-09-06) +# Decree L<3,592><http://pcdsh01.on.br/DEC3592.htm> (2000-09-06) # adopted by the same states as before. -# Decree <a href="http://pcdsh01.on.br/Dec3630.jpg">3,630</a> (2000-10-13) +# Decree L<3,630><http://pcdsh01.on.br/Dec3630.jpg> (2000-10-13) # repeals DST in PE and RR, effective 2000-10-15 00:00. -# Decree <a href="http://pcdsh01.on.br/Dec3632.jpg">3,632</a> (2000-10-17) +# Decree L<3,632><http://pcdsh01.on.br/Dec3632.jpg> (2000-10-17) # repeals DST in SE, AL, PB, RN, CE, PI and MA, effective 2000-10-22 00:00. -# Decree <a href="http://pcdsh01.on.br/figuras/HV3916.gif">3,916</a> +# Decree L<3,916><http://pcdsh01.on.br/figuras/HV3916.gif> # (2001-09-13) reestablishes DST in AL, CE, MA, PB, PE, PI, RN, SE. Rule Brazil 2000 2001 - Oct Sun>=8 0:00 1:00 S Rule Brazil 2001 2006 - Feb Sun>=15 0:00 0 - # Decree 4,399 (2002-10-01) repeals DST in AL, CE, MA, PB, PE, PI, RN, SE. -# <a href="http://www.presidencia.gov.br/CCIVIL/decreto/2002/D4399.htm">4,399</a> +# L<4,399><http://www.presidencia.gov.br/CCIVIL/decreto/2002/D4399.htm> Rule Brazil 2002 only - Nov 3 0:00 1:00 S # Decree 4,844 (2003-09-24; corrected 2003-09-26) repeals DST in BA, MT, TO. -# <a href="http://www.presidencia.gov.br/CCIVIL/decreto/2003/D4844.htm">4,844</a> +# L<4,844><http://www.presidencia.gov.br/CCIVIL/decreto/2003/D4844.htm> Rule Brazil 2003 only - Oct 19 0:00 1:00 S # Decree 5,223 (2004-10-01) reestablishes DST in MT. -# <a href="http://www.planalto.gov.br/ccivil_03/_Ato2004-2006/2004/Decreto/D5223.htm">5,223</a> +# L<5,223><http://www.planalto.gov.br/ccivil_03/_Ato2004-2006/2004/Decreto/D5223.htm> Rule Brazil 2004 only - Nov 2 0:00 1:00 S -# Decree <a href="http://pcdsh01.on.br/DecHV5539.gif">5,539</a> (2005-09-19), +# Decree L<5,539><http://pcdsh01.on.br/DecHV5539.gif> (2005-09-19), # adopted by the same states as before. Rule Brazil 2005 only - Oct 16 0:00 1:00 S -# Decree <a href="http://pcdsh01.on.br/DecHV5920.gif">5,920</a> (2006-10-03), +# Decree L<5,920><http://pcdsh01.on.br/DecHV5920.gif> (2006-10-03), # adopted by the same states as before. Rule Brazil 2006 only - Nov 5 0:00 1:00 S Rule Brazil 2007 only - Feb 25 0:00 0 - -# Decree <a href="http://pcdsh01.on.br/DecHV6212.gif">6,212</a> (2007-09-26), +# Decree L<6,212><http://pcdsh01.on.br/DecHV6212.gif> (2007-09-26), # adopted by the same states as before. Rule Brazil 2007 only - Oct Sun>=8 0:00 1:00 S # From Frederico A. C. Neves (2008-09-10): # Acording to this decree -# <a href="http://www.planalto.gov.br/ccivil_03/_Ato2007-2010/2008/Decreto/D6558.htm"> -# http://www.planalto.gov.br/ccivil_03/_Ato2007-2010/2008/Decreto/D6558.htm -# </a> +# L<http://www.planalto.gov.br/ccivil_03/_Ato2007-2010/2008/Decreto/D6558.htm> # [t]he DST period in Brazil now on will be from the 3rd Oct Sunday to the # 3rd Feb Sunday. There is an exception on the return date when this is # the Carnival Sunday then the return date will be the next Sunday... @@ -1139,7 +1072,7 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # on April 3, (one-time change). # From Oscar van Vlijmen (2006-10-08): -# http://www.horaoficial.cl/cambio.htm +# L<http://www.horaoficial.cl/cambio.htm> # From Jesper Norgaard Welen (2006-10-08): # I think that there are some obvious mistakes in the suggested link @@ -1150,7 +1083,7 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # From Paul Eggert (2006-12-27): # The following data for Chile and America/Santiago are from -# <http://www.horaoficial.cl/horaof.htm> (2006-09-20), transcribed by +# L<http://www.horaoficial.cl/horaof.htm> (2006-09-20), transcribed by # Jesper Norgaard Welen. The data for Pacific/Easter are from Shanks # & Pottenger, except with DST transitions after 1932 cloned from # America/Santiago. The pre-1980 Pacific/Easter data are dubious, @@ -1161,26 +1094,18 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # is one-time change (Saturday 3/29 at 24:00 for America/Santiago # and Saturday 3/29 at 22:00 for Pacific/Easter) # The Supreme Decree is located at -# <a href="http://www.shoa.cl/servicios/supremo316.pdf"> -# http://www.shoa.cl/servicios/supremo316.pdf -# </a> +# L<http://www.shoa.cl/servicios/supremo316.pdf> # and the instructions for 2008 are located in: -# <a href="http://www.horaoficial.cl/cambio.htm"> -# http://www.horaoficial.cl/cambio.htm -# </a>. +# L<http://www.horaoficial.cl/cambio.htm>. # From Jose Miguel Garrido (2008-03-05): # ... # You could see the announces of the change on -# <a href="http://www.shoa.cl/noticias/2008/04hora/hora.htm"> -# http://www.shoa.cl/noticias/2008/04hora/hora.htm -# </a>. +# L<http://www.shoa.cl/noticias/2008/04hora/hora.htm>. # From Angel Chiang (2010-03-04): # Subject: DST in Chile exceptionally extended to 3 April due to earthquake -# <a href="http://www.gobiernodechile.cl/viewNoticia.aspx?idArticulo=30098"> -# http://www.gobiernodechile.cl/viewNoticia.aspx?idArticulo=30098 -# </a> +# L<http://www.gobiernodechile.cl/viewNoticia.aspx?idArticulo=30098> # (in Spanish, last paragraph). # # This is breaking news. There should be more information available later. @@ -1192,15 +1117,11 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # It appears that the Chilean government has decided to postpone the # change from summer time to winter time again, by three weeks to April # 2nd: -# <a href="http://www.emol.com/noticias/nacional/detalle/detallenoticias.asp?idnoticia=467651"> -# http://www.emol.com/noticias/nacional/detalle/detallenoticias.asp?idnoticia=... -# </a> +# L<http://www.emol.com/noticias/nacional/detalle/detallenoticias.asp?idnoticia=...> # # This is not yet reflected in the offical "cambio de hora" site, but # probably will be soon: -# <a href="http://www.horaoficial.cl/cambio.htm"> -# http://www.horaoficial.cl/cambio.htm -# </a> +# L<http://www.horaoficial.cl/cambio.htm> # From Arthur David Olson (2011-03-02): # The emol.com article mentions a water shortage as the cause of the @@ -1208,9 +1129,7 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # From Glenn Eychaner (2011-03-28): # The article: -# <a href="http://diario.elmercurio.com/2011/03/28/_portada/_portada/noticias/7565897A-CA86-49E6-9E03-660B21A4883E.htm?id=3D{7565897A-CA86-49E6-9E03-660B21A4883E}"> -# http://diario.elmercurio.com/2011/03/28/_portada/_portada/noticias/7565897A-CA86-49E6-9E03-660B21A4883E.htm?id=3D{7565897A-CA86-49E6-9E03-660B21A4883E} -# </a> +# L<http://diario.elmercurio.com/2011/03/28/_portada/_portada/noticias/7565897A-CA86-49E6-9E03-660B21A4883E.htm?id=3D{7565897A-CA86-49E6-9E03-660B21A4883E}> # # In English: # Chile's clocks will go back an hour this year on the 7th of May instead @@ -1220,7 +1139,7 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # From Mauricio Parada (2012-02-22), translated by Glenn Eychaner (2012-02-23): # As stated in the website of the Chilean Energy Ministry -# http://www.minenergia.cl/ministerio/noticias/generales/gobierno-anuncia-fech... +# L<http://www.minenergia.cl/ministerio/noticias/generales/gobierno-anuncia-fech...> # The Chilean Government has decided to postpone the entrance into winter time # (to leave DST) from March 11 2012 to April 28th 2012. The decision has not # been yet formalized but it will within the next days. @@ -1346,8 +1265,8 @@ Link America/Curacao America/Kralendijk # Bonaire, Sint Estatius and Saba # # From Paul Eggert (2007-03-04): # Apparently Ecuador had a failed experiment with DST in 1992. -# <http://midena.gov.ec/content/view/1261/208/> (2007-02-27) and -# <http://www.hoy.com.ec/NoticiaNue.asp?row_id=249856> (2006-11-06) both +# L<http://midena.gov.ec/content/view/1261/208/> (2007-02-27) and +# L<http://www.hoy.com.ec/NoticiaNue.asp?row_id=249856> (2006-11-06) both # talk about "hora Sixto". Leave this alone for now, as we have no data. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -1414,9 +1333,7 @@ Zone Pacific/Galapagos -5:58:24 - LMT 1931 # Puerto Baquerizo Moreno # daylight saving time. # # One source: -# <a href="http://www.falklandnews.com/public/story.cfm?get=5914&source=3"> -# http://www.falklandnews.com/public/story.cfm?get=5914&source=3 -# </a> +# L<http://www.falklandnews.com/public/story.cfm?get=5914&source=3> # # We have gotten this confirmed by a clerk of the legislative assembly: # Normally the clocks revert to Local Mean Time (UTC/GMT -4 hours) on the @@ -1502,9 +1419,7 @@ Rule Para 1996 only - Mar 1 0:00 0 - # (10-01). # # Translated by Gwillim Law (2001-02-27) from -# <a href="http://www.diarionoticias.com.py/011000/nacional/naciona1.htm"> -# Noticias, a daily paper in Asuncion, Paraguay (2000-10-01) -# </a>: +# L<Noticias, a daily paper in Asuncion, Paraguay><http://www.diarionoticias.com.py/011000/nacional/naciona1.htm>: # Starting at 0:00 today, the clock will be set forward 60 minutes, in # fulfillment of Decree No. 7,273 of the Executive Power.... The time change # system has been operating for several years. Formerly there was a separate @@ -1531,14 +1446,12 @@ Rule Para 2002 2003 - Sep Sun>=1 0:00 1:00 S # From Steffen Thorsen (2005-01-05): # Decree 1,867 (2004-03-05) # From Carlos Raul Perasso via Jesper Norgaard Welen (2006-10-13) -# <http://www.presidencia.gov.py/decretos/D1867.pdf> +# L<http://www.presidencia.gov.py/decretos/D1867.pdf> Rule Para 2004 2009 - Oct Sun>=15 0:00 1:00 S Rule Para 2005 2009 - Mar Sun>=8 0:00 0 - # From Carlos Raul Perasso (2010-02-18): # By decree number 3958 issued yesterday ( -# <a href="http://www.presidencia.gov.py/v1/wp-content/uploads/2010/02/decreto3958.pdf"> -# http://www.presidencia.gov.py/v1/wp-content/uploads/2010/02/decreto3958.pdf -# </a> +# L<http://www.presidencia.gov.py/v1/wp-content/uploads/2010/02/decreto3958.pdf> # ) # Paraguay changes its DST schedule, postponing the March rule to April and # modifying the October date. The decree reads: @@ -1560,7 +1473,7 @@ Zone America/Asuncion -3:50:40 - LMT 1890 # Peru # -# <a href="news:xrGmb.39935$gA1.13896113@news4.srv.hcvlny.cv.net"> +# news:xrGmb.39935$gA1.13896113@news4.srv.hcvlny.cv.net # From Evelyn C. Leeper via Mark Brader (2003-10-26):</a> # When we were in Peru in 1985-1986, they apparently switched over # sometime between December 29 and January 3 while we were on the Amazon. @@ -1660,21 +1573,21 @@ Rule Uruguay 1992 only - Oct 18 0:00 1:00 S Rule Uruguay 1993 only - Feb 28 0:00 0 - # From Eduardo Cota (2004-09-20): # The uruguayan government has decreed a change in the local time.... -# http://www.presidencia.gub.uy/decretos/2004091502.htm +# L<http://www.presidencia.gub.uy/decretos/2004091502.htm> Rule Uruguay 2004 only - Sep 19 0:00 1:00 S # From Steffen Thorsen (2005-03-11): # Uruguay's DST was scheduled to end on Sunday, 2005-03-13, but in order to # save energy ... it was postponed two weeks.... -# http://www.presidencia.gub.uy/_Web/noticias/2005/03/2005031005.htm +# L<http://www.presidencia.gub.uy/_Web/noticias/2005/03/2005031005.htm> Rule Uruguay 2005 only - Mar 27 2:00 0 - # From Eduardo Cota (2005-09-27): -# http://www.presidencia.gub.uy/_Web/decretos/2005/09/CM%20119_09%2009%202005_... +# L<http://www.presidencia.gub.uy/_Web/decretos/2005/09/CM%20119_09%2009%202005_...> # This means that from 2005-10-09 at 02:00 local time, until 2006-03-12 at # 02:00 local time, official time in Uruguay will be at GMT -2. Rule Uruguay 2005 only - Oct 9 2:00 1:00 S Rule Uruguay 2006 only - Mar 12 2:00 0 - # From Jesper Norgaard Welen (2006-09-06): -# http://www.presidencia.gub.uy/_web/decretos/2006/09/CM%20210_08%2006%202006_... +# L<http://www.presidencia.gub.uy/_web/decretos/2006/09/CM%20210_08%2006%202006_...> Rule Uruguay 2006 max - Oct Sun>=1 2:00 1:00 S Rule Uruguay 2007 max - Mar Sun>=8 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -1691,7 +1604,7 @@ Zone America/Montevideo -3:44:44 - LMT 1898 Jun 28 # published today in the "Gaceta Oficial de la Republica Bolivariana # de Venezuela, numero 38.819" (official document for all laws or # resolution publication) -# http://www.globovision.com/news.php?nid=72208 +# L<http://www.globovision.com/news.php?nid=72208> # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Caracas -4:27:44 - LMT 1890
Steffen "Daode" Nurpmeso <sdaoden@gmail.com> writes:
How about turning over to a simple generic approach, as in
L<http://www.url1.com> and/or L<Some descriptive text><http://www.url2.com>
and having "I" for informational links that follow the same style but do not provide hyperlinks and "D" for dead links?
Note that this is very, very close to POD syntax, and if you move the rest of the way to POD syntax, you could then just extract the comments and use any of the existing POD formatters and, from that, get any output format you want from text through HTML to PDF. The only changes that you'd need to make would be to change your second example to: L<Some descriptive text|http://www.url2.com> and then decide how you'd like to handle the I and D links. One option for the latter would be to just prefilter the output to remove the link and return just the descriptive text before processing the rest of the document with a POD formatter, which would be quite easy to do using either a simple script or existing POD parsing modules. If you do decide to use POD, you may want to pick a different letter than I, since I<> is already a POD formatting code (for italics). D<> is safe to use; there's no existing formatting code. POD would also give you headings, verbatim paragraphs, and a (very verbose, admittedly) syntax for lists if you wanted to use them, but you of course wouldn't have to. This doesn't solve the character set problem, sadly; POD of course has its own method of representing characters outside the input character set, but it's as ugly (or uglier) than all the encoding methods already proposed. But neither would it get in the way; POD is happy with any input character set you want to use, and just wants a single =encoding command somewhere to tell it what to expect if you're not using US-ASCII or UTF-8. I'm happy to help with any POD issues, including showing how to subclass Pod::Text to add new formatting codes, if you want to go that route. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
Russ Allbery <rra@stanford.edu> wrote: |Steffen "Daode" Nurpmeso <sdaoden@gmail.com> writes: |> How about turning over to a simple generic approach, as in | |> L<http://www.url1.com> |> and/or |> L<Some descriptive text><http://www.url2.com> | |> and having "I" for informational links that follow the same style |> but do not provide hyperlinks and "D" for dead links? | |Note that this is very, very close to POD syntax, and if you move the rest |of the way to POD syntax, you could then just extract the comments and use |any of the existing POD formatters and, from that, get any output format |you want from text through HTML to PDF. This would indeed not be a step that big for the parser, given that it sticks as a filter in the middle, nor for the editor when unrotting/converting the database files. |The only changes that you'd need to make would be to change your second |example to: | | L<Some descriptive text|http://www.url2.com> See below.. |and then decide how you'd like to handle the I and D links. One option |for the latter would be to just prefilter the output to remove the link |and return just the descriptive text before processing the rest of the |document with a POD formatter, which would be quite easy to do using |either a simple script or existing POD parsing modules. | |If you do decide to use POD, you may want to pick a different letter than |I, since I<> is already a POD formatting code (for italics). D<> is safe |to use; there's no existing formatting code. Well, that was just what came to my mind on saturday. Maybe U<> (for URL)? It seems unused. |POD would also give you headings, verbatim paragraphs, and a (very |verbose, admittedly) syntax for lists if you wanted to use them, but you |of course wouldn't have to. I would think of headings and (verbatim) paragraphs, trying to make the output match the input, which will be somewhat hard and require adjustments from what i see at a glance, because text-filling obviously has not been thought of when adding entries to the tz database files. I also can hardly imagine that spreading formatting tags will be accepted by the actual tz maintainer(s), since otherwise they might have done it 15 years ago. |This doesn't solve the character set problem, sadly; POD of course has its |own method of representing characters outside the input character set, but |it's as ugly (or uglier) than all the encoding methods already proposed. |But neither would it get in the way; POD is happy with any input character |set you want to use, and just wants a single =encoding command somewhere |to tell it what to expect if you're not using US-ASCII or UTF-8. I think the script can easily get extended by another mode which simply takes an encoding name and reads text from STDIN/file, converting to tz database-style comment output along the way; i.e., HTML entities. It would have to decode HTML entities to E<>, which should work, then? Shouldn't be that hard either. |I'm happy to help with any POD issues, including showing how to subclass |Pod::Text to add new formatting codes, if you want to go that route. ..Well i think for L<> to work the way you show it above the POD parser must be adjusted; or we need to use special tags and make POD treat them as links. I haven't yet used POD any more sophisticated than this: use Pod::Text; my $parser = Pod::Text->new(loose => 1, indent => 0, width => 72); $parser->parse_from_file($0, '-'); and of course normal module documentation, so some hints how to do the required task would be appreciated. It of course all stands and falls with wether these adjustments will be acceptable for the tz database as such. I'm not planning to fork the project. |-- |Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/> --steffen
|Russ Allbery <rra@stanford.edu> wrote: ||Steffen "Daode" Nurpmeso <sdaoden@gmail.com> writes: ||> How about turning over to a simple generic approach, as in || ||> L<http://www.url1.com> ||> and/or ||> L<Some descriptive text><http://www.url2.com> [.] ||If you do decide to use POD, you may want to pick a different letter than ||I, since I<> is already a POD formatting code (for italics). D<> is safe ||to use; there's no existing formatting code. | |Well, that was just what came to my mind on saturday. |Maybe U<> (for URL)? It seems unused. I'll append an updated version that uses U<> not I<>. It also makes use of that in one case, and fixes the one messed up link i've introduced via the new N<> that can be used for URLs that should produce an <a> tag but are not checkable by curl(1) (news:). --steffen diff --git a/htwork.pl b/htwork.pl index 64f0cb3..ee85291 100755 --- a/htwork.pl +++ b/htwork.pl @@ -6,7 +6,8 @@ require 5.008_001; #@ Synopsis: htwork.pl check < DATA_FILE > NEW_DATA_FILE #@ The latter mode requires an installed curl(1) (<http://curl.haxx.se>). #@ Understood links: L<URL>, L<Text><URL>. Dead links: D<URL>, D<Text><URL>. -#@ Links that should not be converted (informational): I<URL>, I<Text><URL>. +#@ Links that should be converted to <a>, but not checked: N<URL>, N<Text><URL>. +#@ Links that should neither be converted nor checked: U<URL>, U<Text><URL>. #@ XXX Assumes links fit on one line. my $CURL = 'curl -q --silent --fail --head --location'; @@ -17,10 +18,9 @@ use diagnostics -verbose; use strict; use warnings; -# We do support L<URL> and L<text><URL>; D instead of L is for dead links. my $URL_CONTENT = qr{ (.*?) - (l|d|i) + (l|d|u|n) <([^>]+)> (?:<([^>]+)>)? (.*) @@ -64,7 +64,7 @@ veals the native languages of entry authors, cities and regions. The second mode is used in the release phase of the tz zoneinfo database and checks all L<> and L<><> links for resolvability, converting all those to D<> and D<><> (dead link) entries that -cannot be resolved. I<> and I<><> links are left alone. +cannot be resolved. This mode requires an installed curl(1) (<http://curl.haxx.se>). __EOT__ @@ -94,7 +94,7 @@ __EOT__ my $comm = lc $2; my $url = $4 ? $4 : $3; my $text = $4 ? $3 : ''; - if ($comm eq 'l') { + if ($comm eq 'l' || $comm eq 'n') { $text = $url unless $text; $ln .= '<a href="' . $url . '">' . $text . '</a>'; } else { @@ -115,7 +115,6 @@ __EOT__ </pre> </body> </html> -<!-- vim:set fenc=utf-8 syntax=html ts=8 sts=8 sw=8 noet tw=79: --> __EOT__ exit diff --git a/southamerica b/southamerica index 2e1c973..49a2adb 100644 --- a/southamerica +++ b/southamerica @@ -718,7 +718,7 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # It has not yet been posted to L<http://pcdsh01.on.br/DecHV.html> # # An official page about it: -# <http://www.mme.gov.br/site/news/detail.do?newsId=16722> +# U<http://www.mme.gov.br/site/news/detail.do?newsId=16722> # Note that this link does not always work directly, but must be accessed # by going to L<http://www.mme.gov.br/first> # @@ -1473,8 +1473,7 @@ Zone America/Asuncion -3:50:40 - LMT 1890 # Peru # -# news:xrGmb.39935$gA1.13896113@news4.srv.hcvlny.cv.net -# From Evelyn C. Leeper via Mark Brader (2003-10-26):</a> +# N<From Evelyn C. Leeper via Mark Brader (2003-10-26)><news:xrGmb.39935$gA1.13896113@news4.srv.hcvlny.cv.net>: # When we were in Peru in 1985-1986, they apparently switched over # sometime between December 29 and January 3 while we were on the Amazon. #
On 2013-01-12 21:04, Steffen Daode Nurpmeso wrote:
Paul Eggert <eggert@cs.ucla.edu> wrote:
|The HTML markup has bothered me, too; I have found it more |distracting than useful. URLs themselves should be fine, |but the <a href='...'> business gets in the way.
How about turning over to a simple generic approach, as in
L<http://www.url1.com> and/or L<Some descriptive text><http://www.url2.com>
and having "I" for informational links that follow the same style but do not provide hyperlinks and "D" for dead links?
Do we really have a use for post-processing the comments into another document format? I think it's fine just to keep the comments in the files readable by humans (which is where the HTML stuff currently gets in the way). Some consistency would be nice though. Some URLs are just written as-is, some are enclosed in angle brackets, and most currently get the HTML href treatment. I think we only really need to distinguish between named links and unnamed links, and if the comments are only intended to be processed by humans, there is no need to mark-up the "name" part of the link specially. For human-only rendering of links, perhaps stick with plain links enclosed in angle brackets, and for named links just enclose the reference in angle brackets and parentheses after the link name. For example, replace: # Since 1998 Joseph S. Myers has been updating # and extending this list, which can be found in # http://student.cusu.cam.ac.uk/~jsm28/british-time/ # <a href="http://www.polyomino.org.uk/british-time/"> # History of legal time in Britain # </a> # Rob Crowther (2012-01-04) reports that that URL no longer # exists, and the article can now be found at: # <a href="http://www.polyomino.org.uk/british-time/"> # http://www.polyomino.org.uk/british-time/ # </a> with: # Since 1998 Joseph S. Myers has been updating # and extending this list, which can be found in # History of legal time in Britain # (<http://student.cusu.cam.ac.uk/~jsm28/british-time/>). # Rob Crowther (2012-01-04) reports that that URL no longer # exists, and the article can now be found at: # <http://www.polyomino.org.uk/british-time/>. or something like that. -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
Ian Abbott <abbotti@mev.co.uk> wrote: |On 2013-01-12 21:04, Steffen Daode Nurpmeso wrote: |> Paul Eggert <eggert@cs.ucla.edu> wrote: |> |>|The HTML markup has bothered me, too; I have found it more |>|distracting than useful. URLs themselves should be fine, |>|but the <a href='...'> business gets in the way. |> |> How about turning over to a simple generic approach, as in |> |> L<http://www.url1.com> |> and/or |> L<Some descriptive text><http://www.url2.com> | |Do we really have a use for post-processing the comments into another |document format? I think it's fine just to keep the comments in the |files readable by humans (which is where the HTML stuff currently gets |in the way). Well it seems that the possibility to use HTML for easier previewing with hyperlink support is desired, but one must uncomment one line to get at this feature, and from my memory point of view it seems that not few people use it. My thought was just to make this an automatic, documented and regular feature. And just as Russ Allbery pointed out, that could very easily be extended - almost strictly on the script side - to support a lot of output formats, of which PDF is possibly the most interesting. I.e., with an index and TOC (=headX lines needed) and working hyperlinks etc. I didn't really think of that on saturday, but it's surely of interest .. once available, i'm pretty sure. |Some consistency would be nice though. Some URLs are just written |as-is, some are enclosed in angle brackets, and most currently get the |HTML href treatment. I think we only really need to distinguish between |named links and unnamed links, and if the comments are only intended to |be processed by humans, there is no need to mark-up the "name" part of |the link specially. | |For human-only rendering of links, perhaps stick with plain links |enclosed in angle brackets, and for named links just enclose the |reference in angle brackets and parentheses after the link name. Yes i know there are editors out there which get this kind of URL right (well, how do [i/]they get [t]here?), but mine doesn't. Also using a - savage but - command syntax allows automatic classification of URL content, etc. and of course. Btw. i usually have max. 3 minutes CPU time wasted after an entire week of work (unless foldmarks were used to excessively), and i could almost bike-shed the energy required for that. At least in the summertime. Not tz-related, however. --steffen
Ian Abbott <abbotti@mev.co.uk> wrote on Mon, 14 Jan 2013 at 18:16:55 +0000 in <50F44B97.4000808@mev.co.uk>:
with:
# Since 1998 Joseph S. Myers has been updating # and extending this list, which can be found in # History of legal time in Britain # (<http://student.cusu.cam.ac.uk/~jsm28/british-time/>).
I find this whole bracketting annoying and tough to deal with when copy-pasting URLs. What's wrong with no special markup at all: # History of legal time in Britain # http://student.cusu.cam.ac.uk/~jsm28/british-time/. --jhawk@mit.edu John Hawkinson
+1. Comments are for humans And +1 on UTF-8 Cheers, Carlos El 14/01/2013 17:53, "Andy Heninger" <aheninger@google.com> escribió:
John Hawkinson <jhawk@mit.edu> wrote
I find this whole bracketting annoying and tough to deal with when copy-pasting URLs. What's wrong with no special markup at all
+1
On 14/01/13 19:32, John Hawkinson wrote:
Ian Abbott <abbotti@mev.co.uk> wrote on Mon, 14 Jan 2013 at 18:16:55 +0000 in <50F44B97.4000808@mev.co.uk>:
with:
# Since 1998 Joseph S. Myers has been updating # and extending this list, which can be found in # History of legal time in Britain # (<http://student.cusu.cam.ac.uk/~jsm28/british-time/>).
I find this whole bracketting annoying and tough to deal with when copy-pasting URLs. What's wrong with no special markup at all:
# History of legal time in Britain # http://student.cusu.cam.ac.uk/~jsm28/british-time/.
Well is that punctuation at the end of your URL part of the URL or not? It's fairly obviously not in that case, but not always so. The brackets help to delimit the URL. -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
On 01/14/2013 11:45 PM, Ian Abbott wrote:
On 14/01/13 19:32, John Hawkinson wrote:
Ian Abbott <abbotti@mev.co.uk> wrote on Mon, 14 Jan 2013 at 18:16:55 +0000 in <50F44B97.4000808@mev.co.uk>:
with:
# Since 1998 Joseph S. Myers has been updating # and extending this list, which can be found in # History of legal time in Britain # (<http://student.cusu.cam.ac.uk/~jsm28/british-time/>).
I find this whole bracketting annoying and tough to deal with when copy-pasting URLs. What's wrong with no special markup at all: +1, also for UTF-8 (no BOM) in comments only without the HTML entities / tags etc etc and non-comment parts of the files to be restricted to plain-old ASCII until there is a compelling need.
# History of legal time in Britain # http://student.cusu.cam.ac.uk/~jsm28/british-time/.
Well is that punctuation at the end of your URL part of the URL or not? It's fairly obviously not in that case, but not always so. The brackets help to delimit the URL.
Thunderbird seams to think it's not part :) It is for humans in any case, maybe simply "require" to have an URL always need to be surrounded with 2 spaces (U+0020) ? just my 2 cents, Gunther
On 14 January 2013 18:50, gunther Vermeir <gunther.vermeir@gmail.com> wrote:
# History of legal time in Britain # http://student.cusu.cam.ac.uk/~jsm28/british-time/.
Well is that punctuation at the end of your URL part of the URL or not? It's fairly obviously not in that case, but not always so. The brackets help to delimit the URL.
Thunderbird seams to think it's not part :) It is for humans in any case, maybe simply "require" to have an URL always need to be surrounded with 2 spaces (U+0020) ?
+1 on "comments are for humans"; unless and until we push the comments out into standalone documents (which I don't see as likely), we don't particularly need to use any markup in the official database for URLs. Honestly, all but the shortest URLs are long enough to be given their own line anyway, so why not just do that for all of them? It's about as unambiguous as one can reasonably get while keeping things simple for readability's sake, and you can name links (for those that need names) by just putting the title followed by a colon (:) on the previous line(s). Maybe indent the URL with a couple spaces for stylistic/parsing reasons, but nothing fancier than that. On 14 January 2013 18:50, gunther Vermeir <gunther.vermeir@gmail.com> wrote:
+1, also for UTF-8 (no BOM) in comments only without the HTML entities / tags etc etc and non-comment parts of the files to be restricted to plain-old ASCII until there is a compelling need.
+1 on UTF-8 for comments, ASCII elsewhere; if it's feasibly implementable. I'm not certain how one would actually go about actually supporting that, but such an approach would allow each user to choose how to handle and/or view the non-ASCII characters in comments while not affecting how the data/code itself is interpreted... again, unless and until there's need to support UTF-8 there, too. -- Tim Parenti
On 2013-01-14 23:50, gunther Vermeir wrote:
On 01/14/2013 11:45 PM, Ian Abbott wrote:
On 14/01/13 19:32, John Hawkinson wrote:
Ian Abbott <abbotti@mev.co.uk> wrote on Mon, 14 Jan 2013 at 18:16:55 +0000 in <50F44B97.4000808@mev.co.uk>:
with:
# Since 1998 Joseph S. Myers has been updating # and extending this list, which can be found in # History of legal time in Britain # (<http://student.cusu.cam.ac.uk/~jsm28/british-time/>).
I find this whole bracketting annoying and tough to deal with when copy-pasting URLs. What's wrong with no special markup at all: +1, also for UTF-8 (no BOM) in comments only without the HTML entities / tags etc etc and non-comment parts of the files to be restricted to plain-old ASCII until there is a compelling need.
# History of legal time in Britain # http://student.cusu.cam.ac.uk/~jsm28/british-time/.
Well is that punctuation at the end of your URL part of the URL or not? It's fairly obviously not in that case, but not always so. The brackets help to delimit the URL.
Thunderbird seams to think it's not part :)
Thunderbird seems clever enough to copy URLs that have been line-wrapped, as long as they are bracketed by angle brackets. :) But this is a plain text file and not subject to line wrapping, so the point is moot.
It is for humans in any case, maybe simply "require" to have an URL always need to be surrounded with 2 spaces (U+0020) ?
That works too, and I've done it myself before, but the space before the punctuation looks a little odd. I just happen to prefer angle brackets. Call me weird if you like. ;) -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
On 2013-01-09 13:49, Sascha Wildner wrote:
On Mon, 07 Jan 2013 14:28:30 +0100, Arthur David Olson <arthurdavidolson@gmail.com> wrote:
With the new year, a revised attempt to handle the German exclave of Busingen (which followed Zurich rather than Berlin in 1980). These changes are relative to the latest github.com/eggert/tz <http://github.com/eggert/tz> versions; they are both below (with tabs mangled) and attached.
--ado
*** old/europe 2013-01-07 08:05:19.093905100 -0500 --- europe 2013-01-07 08:13:01.260316900 -0500 *************** *** 1239,1244 **** --- 1239,1265 ---- 1:00 Germany CE%sT 1980 1:00 EU CE%sT
+ # From Tobias Conradi (2011-09-12): + # The German enclave of Büsingen
It should be "exclave" there (it's an exclave of Germany and an enclave of Switzerland).
I'm not sure, are the files supposed to be UTF-8? If so, that ü should be 'ü'. Alternately, you could also write "Buesingen" (ü becoming ue).
The 'ü' is a HTML entity for 'ü'. There are several HTML entities in the tz file comments, along with other random bits of HTML, but that's a discussion for another thread. (ISTR there was such a thread a while ago but I can't find it.) -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
Getting back to the main topic, I pushed Arthur's change to the experimental tz repository on github, with minor changes for consistency with the rest of the data, and an updated URL (the old one got redirected). This change uses the name "Busingen" in comments as well as in the database. I've seen it "Buesingen" in English-language texts, but "Busingen" is also common and there is some advantage to spelling it the same way in the comments as it is in the data.
From 3daaa8e3469aa53179d1155323f0f7bf152c10a3 Mon Sep 17 00:00:00 2001 From: Paul Eggert <eggert@cs.ucla.edu> Date: Fri, 11 Jan 2013 11:58:07 -0800 Subject: [PATCH 1/2] New alias Europe/Busingen for Europe/Zurich.
* europe, zone.tab (Europe/Busingen): New Link. See Arthur David Olson in <http://mm.icann.org/pipermail/tz/2013-January/018511.html>. Original heads-up from Tobias Conradi in <http://mm.icann.org/pipermail/tz/2011-September/008784.html>. --- europe | 15 +++++++++++++++ zone.tab | 3 ++- 2 files changed, 17 insertions(+), 1 deletion(-) diff --git a/europe b/europe index d00582d..dbd9a71 100644 --- a/europe +++ b/europe @@ -1239,6 +1239,21 @@ Zone Europe/Berlin 0:53:28 - LMT 1893 Apr 1:00 Germany CE%sT 1980 1:00 EU CE%sT +# From Tobias Conradi (2011-09-12): +# Busingen <http://www.buesingen.de>, surrounded by the Swiss canton +# Schaffhausen, did not start observing DST in 1980 as the rest of DE +# (West Germany at that time) and DD (East Germany at that time) did. +# DD merged into DE, the area is currently covered by code DE in ISO 3166-1, +# which in turn is covered by the zone Europe/Berlin. +# +# Source for the time in Busingen 1980: +# http://www.srf.ch/player/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3 + +# From Arthur David Olson (2012-03-03): +# Busingen and Zurich have shared clocks since 1970. + +Link Europe/Zurich Europe/Busingen + # Georgia # Please see the "asia" file for Asia/Tbilisi. # Herodotus (Histories, IV.45) says Georgia north of the Phasis (now Rioni) diff --git a/zone.tab b/zone.tab index 4ba2087..c1cd95e 100644 --- a/zone.tab +++ b/zone.tab @@ -159,7 +159,8 @@ CW +1211-06900 America/Curacao CX -1025+10543 Indian/Christmas CY +3510+03322 Asia/Nicosia CZ +5005+01426 Europe/Prague -DE +5230+01322 Europe/Berlin +DE +5230+01322 Europe/Berlin most locations +DE +4742+00841 Europe/Busingen Busingen DJ +1136+04309 Africa/Djibouti DK +5540+01235 Europe/Copenhagen DM +1518-06124 America/Dominica -- 1.7.10.4
participants (20)
-
Andy Heninger -
Arthur David Olson -
Bennett Todd -
Carlos Raúl Perasso -
David Patte ₯ -
Deborah Goldsmith -
Derick Rethans -
gunther Vermeir -
Ian Abbott -
Jaakko Hyvätti -
John Hawkinson -
Markus Kuhn -
Paul Eggert -
Random832 -
Russ Allbery -
Sascha Wildner -
Steffen Daode Nurpmeso -
Steve Allen -
Tim Parenti -
walter harms