User talk:Joe Kress/Archive 2006/10/15–2009/04/20

1064:

value of year which was most inaccurate in the history of mankind ( 6940 / 19 ). 6940 is a mere rounding off. We do not have records of actual year-length used by Babylonians (esp Chaldeans ) and Meton, and therefore one may accept the rounded value 6940/19. There are innumerable evidences which suggest that lunisolar year was used by Egyptians (near or before 3000 BCE,when they shifted to solar year),Babylonians,Greeks,Indians,etc. Vedanga Jyotisha of India is said to originate around 1400 BCE (H T Colebrooke),which is clearly based upon lunisolar year. Hence, the common origin of lunisolar year must be put in or before 4th millenium BCE, perhaps in North Africa. Users of lunisolar years needed accurate measurements of concurrences of Sun and Moon, and of intercalary months. Moreover, there are evidences suggesting a knowledge of precession of stars in Egypt(reorientation of structures according to reigning stars which shift over centuries). Vedanga Jyotish(of Lagadha) and Brihatsamhita (550 AD,Varah Mihira) suggest that Indians also knew that equinoxes move over time. Hence, it is not proper to assert that Hipparchus discovered precession. He may be the first recorded person to scientifically ascertain the value of precession though experimentation : that is his real contribution ; but he did not discover precession. But the value of his tropical year as given in Almagest is nearer to Metonic year than to tropical year. Hence I think Ptolemy is not wholly reliable in this respect. The ancients were perhaps more accurate than we imagine. I will not retouch your article,because you will not allow it, but please consider the points raised by me.I am an expert of Surya Siddhanta and other Indian systems, and related topics, esp of practical methods of computations which no commentator exactly knows : it has remained a trade secret of almanac makers of India. Published versions are crude, originally written for teaching students. -

2771:

dates are the calendar apps via micoformats and google earth via KML. Earth is the only one I know accepting dates at this time, and it doesn't allow dates before September 14, 1752. As for microformats the only apps doing dates are the calendar apps like yahoo/google calendar and they generally set a floor at 1970. There are other virtual earth applications that may in the future handle dates relevant for paleontology/ astronomic time, so we could start emitting those with very long leading zero values as soon as they start handling them. The beauty of WP is that all solutions may be upgraded as future contributors and technology determine more appropriate solutions. Anyway, as of today users will only see the ISO date generated for microformat emission when they copy paste. In the future, it might be made totally invisible if WP allowed the html (abbr) tag, as is usually done in microformat encodings. We are a bit of an oddball in using the span html tag with attribute display set to none. It's legal, but it mucks up the copy/paste a bit. For map applications, KML doesn't have this limitation because out output is via a url passed parameters to a toolserver php routine, or via a perl script that just reads the raw wikitext and lifts the values it need. So KML allows completely hidden values.

2606:

could explain what the Julian date is- but anyway- we are introducing some dissonance there). I can see the utility for translation due the transition period when both Julian and Gregorian were used, but if you were the master of the kml spec, would you stick with strict ISO8601 (Gregorian), or use it only for formatting instructions, and content should reflect the calendar of the period? Then what about Chinese calendar dates? You know these issues backwards and forwards, so I want to know what our first stab at this should be. Of course it can be changed later, but regarding kml, do you think we should stick with normalization of dates into gregorian?

109:

entitled "Development of the Latin ecclesiastical calendar" on pages 1-122 of the book. I took some liberty with Jones, because he did not mention Lent. Instead he concluded that Founder's Day could not be allowed within "Holy Week", presumably the last week of Lent, from Palm Sunday to Holy Saturday. Jones also notes that the Roman church may have reluctantly agreed that Easter could be as late as April 22 or 23 if they could not avoid pressure from Alexandria to accept its Easter because that would be a minimal intrusion into "Holy Week", which makes no sense because a two day intrusion would place Founder's Day on Good Friday! –

2303:(2) I'd appreciate your views on a language point: 'Precession of the equinoxes': It's likely to be a long time before astronomical folk stop referring to this, so calling it a 'former' term does not seem quite true. Granted, the officials are preferring 'precession of the equator', but it's not clear that this has taken over. The new term also has drawbacks (e.g. many things have equators but there is only one fiducial equinox not yet quite officially abolished) which mean that the old term might not ever disappear. I don't want to change the edit, but just to suggest reconsideration. Kind regards, 2681:. Both of these can be obtained via ftp. Although UTC technically began in 1961, for its first ten years broadcast seconds were lengthened slightly throughout the year but were still recorded for civil events as whole seconds, so I think that only whole leap seconds beginning in 1972 need be considered. At the beginning of 1972, TAI−UTC was defined to be 10 seconds, and the first leap second occurred at the end of June 1972. Thus JD(TAI) (plus leap seconds) may be used. Another possibility is to ignore all leap seconds, thus treating all date-times as UT1. 2694:}} in 2006, "trunc" and "floor" may not have been available. Because they are now available, the algorithm can be simplified. I note that {{JULIANDAY|2006|4|30|11|59|60}} is mentioned, which includes a positive leap second at noon, the end of a Julian day. However, such a date-time is impossible because because leap seconds only occur at the end of a UTC day at midnight, in the middle of a Julian day, so the algorithm is faulty regarding leap seconds. I suppose it could be correctted, but including any support for leap seconds would be a daunting task. 1769:

reorganization of its site, becoming a dead link unless you or some other knowledgable person is around to correct it. Similarly, if you include those holidays within the article and they change, the info becomes incorrect quickly unless you or someone else is around to update it. I'm not sure if you or anyone else can say that they will continue to monitor the article for years and years. The article is not of interest to most English language readers, so if you are not around, it may soon become hopelessly out-of-date. —

187:, I always click on "hist" to the right of the name of the talk page—I never click on the talk page itself. On the history I select the last post that I viewed in the left column of radio buttons. I then select "Compare selected versions". This allows me to view new discussions at the top, bottom, or middle of the talk page without having to scroll through any old discussion. This is especially appropriate for very active talk pages, when even fifty new edits scattered throughout the page in one day is not that unusual. 1753:. I've discarded the idea of colorizing the table as I did with Lunar Work holidays so as to add "holidays" that are not work holidays, as I think that would be confusing. Instead, I'm thinking of putting those in a second table for such as Children's Day, Teachers Day, the four armed forces days, etc. I also discarded the idea of adding columns for last, present and next year calendar dates in favor of a link to a yet-to-be decided government site (such as a Thai embassy) that lists them. What do you think? 2323:

long way to destroy its cyclic character. The error with respect to the solar calendar would have been something approaching ten days in a century, and the error with respect to the real motion of the moon would have been about as great, so that Anatolius' version of the 19-year cycle would have been probably a worse fit with the lunar motion than the 84-year lunar 'cycle' of the Roman computus that persisted for some centuries, giving trouble because of its inaccuracy.

1465:, even though the required changes have not been made. Please be careful not to remove any maintenance templates from articles before the issue is satisfactorily resolved. If you disagree with it or you are not sure if any more work needs to be done, discuss the issue on the relevant talk page and allow time for a consensus to be reached before you remove the notice. These notices and comments are needed to establish community consensus about the status of a page. -- 1387:, and the like. I'm sure this discussion occured many times in the early history of Knowledge (XXG), but I can't find it at the moment. This convention created the problem that the first decades BC and AD only have nine years each because there is no year 0. The alternative convention of identifying the aforementioned decades as 1921–1930 or 1991–2000 is rather awkward when speaking, even though it would have resulted in ten years in the first decades BC and AD. — 2720:. So if we accept Chris Bennett's reconstruction, Roman dates back to 263 BC can be converted into a fairly reliable proleptic Gregorian date. Chinese dates back to 841 BC are also relatively secure. However, Jewish dates given in the Old Testament are not well known. Any birth before the 20th century is usually not known, even approximately, so if Augustus' date of birth is known to a few days, that is the exception rather than the rule. — 2589:. Isn't #expr up to the task of these calculations? I haven't looked at his implementation either but theoretically, even if verdy made an error, the algorithm should be perfectible, since #expr has powerful enough functions for it? What if I folded that into the date templates so if date given is in the Julian range that the ISO date emitted for dates is calculated using it? But what to do about Roman Calendar? Eg: 2799:

Roman for dates from Roman history before AD 1. Any date from any other culture cannot be a Roman date, but is probably a Julian date. Dates from Maya pre-classic and classic periods are an exception which are usually given in the proleptic Gregorian calendar. Maya dates from the colonial period were Julian before 1585 (it took about three years for the papal bull to reach New Spain) and Gregorian thereafter.

1188:

is correct - as best I understand it, the fixed times of the molad interval correspond to the actual times one would observe or predict the lunar conjunction at a longitude 4 degrees east of Jerusalem. If I understand correctly, this is significant either because it suggests from where the calendrical calculations were developed (ie, Babylon?) and/or from whom (the Greek astronomers?). Is that close?

311:. In this case, they either do not recognize a "border-style" of "hidden" or do not let "hidden" supersede "solid". If the first, then an undesirable fix would be to repeat my single type in all neighboring cells. If the second, then more style rules would fix it. I did indeed conduct my testing in FireFox. After your alert, I checked it in IE7 and found the same problem that you found in IE6. — 575:

damage that this unblock will probably cause. There's no perfect solution, here, but I didn't feel that sitting by and watching so many users blocked for things they had no part in would be appropriate. You should be able to edit, at this moment, but please do be wary of such blocks in the future -- I can't make any absolute promises, except that I'll do my best.

1787:, I put the wrong date for Thai Armed Forces Day, which had already been changed due do recalculation of the year of the fight it commemorated. Luckily, a Thai Knowledge (XXG) article straightened me out, once I found and decoded it. "Trooping the colors" is also bound to change, as it precedes the current monarch's birthday, but will be a minor detail when 2712:, so I don't know how 2 August 216 BC was obtained, nor whether it is a Roman Republican date or a proleptic Julian date. It is extremely unlikely that it is proleptic Gregorian date. It is most likely a Roman Republican date with the name "August" replacing the original month name of "Sextilis" (it was changed in 8 BC). The table associated with 2805:

article to determine what that local time is. UTC with leap seconds did not exist before 1972, and all except experts assume that even UTC without leap seconds did not exist before 1972. No one would realize that any time given by any source could include a leap second, even after 1971, so in my opinion leap seconds can be safely ignored.

554: 517:. My IP address is within the range 67.150.*.* but is dynamic (it is now 67.150.59.105). That range was previously blocked by other administrators earlier in the year for only a few hours at a time, so it never affected me before. It is possible that my ISP, ArcZip, has been assigned that range (its headquarters are in Utah). Consult 2751:

the definitive conversion should be performed by a maintenance bot with a full featured language that goes through and makes use of the ISO8601 parameter to override the template calculation. The ISO8601 parameter could also be used by editors if they took exception to the algorithms used by the either the bot or the template code.

2700:

zeros. For example -0043 for Julius Caesar's assassination (= 44 BC). But if five digit years were allowed, this implies that four digits years like the current year 2009 should be padded to 02009, which may be unacceptable if they are revealed to the general reader. Thus I recommend that only four digit years be used.

2663:

last minute beginning at second 00), while a positive leap second increases it to 60 and a negative leap second (which has never occurred but is possible) decreases it to 58. However, the Julian Date calculated from UTC time cannot itself be UTC—it can be either UT1 (mean solar time at Greenwich), TAI (

2552:

Wow. That's great. I think I just pass the ISO-8601 parameter verbatim. The authority on the format for that value is ISO8601 specs. BTW- this date information would be not just for microformats but all metadata emission from wikipedia, and by far the dominant metadata is mapping information that

2460:

at the southern tip of Sweden, 12º42' east of Greenwich or 50.8 minutes earlier. The article on Kepler's tables probably should mention that they were used by Protestant Germany, Denmark (including Norway) and Sweden (including Finland) to calculate Easter. In addition I have done some research since

2038:

The other values in the infobox may have excessive precision, but most sources don't give the maximum precision available, and I have not researched them yet. Although many of the parameters do indeed vary, they do so over thousands or millions of years, so their current value should be valid for the

2017:

Okay I see what you're getting at. There should perhaps be an explanatory note added to that field to avoid further confusion. However, surely the orbital period (as measured in days) changes as the length of the day varies (since it is given in solar days). Also I believe that eccentricity undergoes

1839:

translation of the Thai, but you are right that "Kho So (Thai: ค.ศ.)" should be "A.D." As for Chinese, an American, who lived there for a year studying Mandarin, told me they just use plain numerals without an era designation, so "Common Era" without a linkage works for me. Some other editor may come

891:

Please take a moment to examine (but do not edit) my biography. I see you have taken considerable time to revise my additions throughout wikipedia. I wish you knew more about me, my research, and my present health condition. Yes, I am new to the wikipedia environment, but would appreciate a kinder

2620:

So they are explicit. We can't do non gregorian and be kml conformant. Interestingly, in the google earth dialog box for time, the dialog does not allow you to enter a year earlier than 1752- further evidence that they are anticipating people entering historical dates, and have taken the trouble to

2322:

Computus & Anatolius: I saw your amendment of my edit about Anatolius, and agree that it adds relevant detail. You might also be interested to notice that Anatolius' omission of some two or three leap years (relative to the Julian calendar) clearly changed the length of the 'cycle', and went a

1609:

Dear Mr. Kress: The guidelines to which you referred me state that "...there is no need to correct typing errors, grammar, etc...." This is far from an absolute prohibition, which seems to be your interpretation. As an English teacher, I consider it a favor to my fellow wikipedians to help them with

1187:

Thanks for your helpful comments at the talk page. I have reinstated a part of the long paragraph, with attribution, and I am continuing work on it. I don't have such a great grasp of the astronomy, however, so I hope what I have in there regarding the "reference meridian" for the "molad interval"

536:

I've now determined that my IP address will change to some other value within the range 67.150.*.* simply by disconnecting and reconnecting the dialup connection to my ISP, ArcZip. My computer does not need to be restarted or powered off. Your IP address can also be determined by Start | Run | cmd |

2750:

These technical conversion approaches suggest a tidy solution. I may take a stab at the non leap second Julian conversion but due to the size of Bennett's tables, a template converter for roman would be problematic, both in terms of coding arcanery needed, and server load. I remain convinced that

2605:

whether the Gregorian translation issue is irrelevant for kml data. Is it such a good idea to have google earth telling a schoolkid what the gregorian equivalent of Battle of Hastings is? (Actually, an accurate scenario might not be that bleak. I think there is a description text field where we

2397:

Well, I borrowed a copy of the volume containing the van der Waerden paper when I went in for some other things. There's a whole lot in there and he gives a bunch of evidence for developmental stages of zodiacal constellations, the earliest items mentioned seem to be from 7th-c BC and 5th-c BC. I

1981:

The rotation period of Earth is stable at the millisecond level. It has not deviated from the eight significant digit value given (which includes +1 ms) by more than about 2 ms since 1650, thus it meets the Manual of Style criteria. Other values within the infobox have even more significant digits,

1795:

to leave local observances, but to put them in the the provincial article or on a page of their own, linked to Category:Festivals in Thailand. I then broke my own rule by adding Yee Ping Festival in Chiang Mai, because it has more notoriety among English readers than, say, Ubol's Candle Festival or

397:

says that the previous usage was only by drug enforcement agents—by Christmas the Phoenix airport will begin using the machine for those passengers who fail the initial screening, who even then can opt out and choose a pat down. Several more airports will begin using the machines in early 2007. The

2358:

About your research in the history of the zodiac that you mentioned on the talk page of 'Zodiac': (a) I'd suggest that O Neugebauer, 'History of Ancient Mathematical Astronomy' (1975) may also be worth a look. (b) Also, I might be able soon to get to a library that has your wished-for reference

2104:

I agree that extra gallactic radio sources can be and are used for measuring the Earths rotation, but the Solar day can only ultimately be measured by observing the sun. By way of explanation, if the radio sources ever moved out of syncronisation with the rotation of the earth around the sun, ( an

2798:

Thanks for the citation, which only shows that the date was in the Roman calendar, but does not state what ancient source gave it. Nevertheless, that only concerns historians, not a user of microformat dates. We can presume implied Julian for all dates before 1582, but we can only presume implied

2760:

As for syntax implications, this gives us the technical option of allowing very simple syntax with the calendar implied Julian or implied Roman if they fall within particular spans of time. It is true that we have not evaded the need of users to be able to explicitly declare calendar in cases of

2662:

ISO 8601 requires the use of the UTC time scale, which may include a positive or negative leap second at the end of a month. A proposal exists to save up all leap seconds until one leap hour is needed several hundred years in the future. The last second of a month is usually numbered 59 (with the

2643:

Admittedly, this is a little speculative as no one is yet making use of this data. But I think it is a no brainer to predict that all the map applications will filter kml layers by date- the maps are already very cluttered if you turn many of these layers on. It would be excellent to see all WP

2505:

You have made the statement I think on the julian day article talk page that the Julian templates are accurate enough for calculating gregorian equivalent dates. I note the template don't appear to be used by any significant number of articles though. I'd like to know if you think the templates

1237:

Yes, the terms can be grouped either way, but there's one way that's more efficient and also demonstrates that only years that are multiples of 4 are potentially leap years. And leaving the parens out will, in most programming languages, group them the other way (and being higher precedence than

705:

The additions have some nuggets of truth intertwined with personal optinion. As one editor said, his additions are bizarre. Some of his latest additions appear to be direct copies of other articles. I'm not sure whether to revert it or include some of his changes. Obviously he has de-wikified the

2770:

Re 4/5 digit years. It's only relevant for microformat recipient applications because values for KML recipient applications are never seen. At this time, 4 digit years is fine for both even though users would seldom see the iso date in the microformat case. The only consumers I know for these

2699:

ISO 8601:2004 3.6 states that if a time element has a defined length, then leading zeros shall be used as required. ISO 8601:2004 4.1.2.1 requires that years have four digits "unless specified otherwise". Thus two digit years in the two centuries centered on year 0000 must be padded with leading

1127:

vandalism, so I didn't reverse it. I figured that if it was wrong, someone with greater knowledge of the subject would come along and correct it. That's the most harmful kind of vandalism on WP, though, the kind where it sounds just plausible enough that people are reluctant to reverse it. --

1063:

The final version about Hipparchus and Meton as written by you is perfectly true. But you should consider one point. Meton took the 19 year cycle from Babylon, where astronomical calculations of high precision were being made. Hence it is inconceivable that the users of this 19 year cycle used a

604:

Your assumption that Babylonians had always used the 19-year cycle is false. The cycle was introduced probably in the V century BC. So do you imply that before that time there was no Babylonian calendar? Of course, there was, and Babylonians had to rely solely on the vernal equinox as a point of

574:

intense abuse originating from this IP range, recently -- you had nothing to do with that, but unfortunately the IP addresses in here are very dynamic, so the only options are "block nothing" and "block everything." I've worked out a trial soft-blocking, provided that I'll be taking care of the

108:

Sorry, my cryptic citation has mislead you. That is not a quote but my version of a conclusion by Jones from a remark by Prosper in 444 who complained about "circuses and bedlam" during Founder's Day. It has nothing whatsoever to do with Bede. It occurs within Jones' long preface to Bede's work

2804:

Times may be needed for historical maps, which can include military formations that change as a day progresses. ISO 8601 assumes local time if a time zone designation is not given. This implies that if the time is to be converted into UTC, which is Greenwich time, then some human must read the

1480:

I've just noticed that you did it again, and that your edit summary included "internal link to clarification". I'm not sure what you thought you were doing, as the section you've added a link to bears no relation to what the clarify request is about, i.e. what cards are being talked about. --

684:

to the a/n article, made by an anon who has some form for introducing rather idiosyncratic original research into calendrics-related articles. I suspect these additions include more of the same, spliced together perhaps with some less-comprehensible restatements of what was already documented.

2164:

on 24 June 2007, who had included the last haexadecimal digit of the Unicode table entry as its heading. It was changed 31 January 2009 by an anonymous editor (98.244.52.159) who thought "it was copied from a hexadecimal conversion table". I believe the last hexadecimal digit is essential to

1768:

I agree that holidays when work ceases should be distinguished from calendar days for which some group commemorates some cause or idea. Keeping the article up-to-date regarding holidays is a daunting task. If you rely on a government or any other internet site, it may soon be changed due to

1539:, scroll down to the bottom to see it; there's also apparently a book associated with it). I have raised my concerns there re the accuracy of how these 'sources' portray the workings and interpretations of the aztec calendrical systems. I would respect any input you may have. Cheers, -- 1146:. Saying that "areas" are aligned to it is not wrong, just awkward and not strictly related to the article. Because of my continuing study, I now know that the paragraph itself is somewhat erroneous, even though I wrote much of it myself. The problem I now have is how to reword it. — 2575:

ISO8601 parameter, if you put in time figure for some neolithic or geologic time event, it should just emit it as is, even if it is malformed. If that is not the case, I will correct it. The intent was for bots with a full featured language to come in and figure things out more

135:

If this reason is not accepted, then we have no explanation for Rome's vociferous rejection of Easter after April 21, at the same time that they willingly changed the vernal equinox from March 25 to March 21 (c. AD 340). Nevertheless, you are correct that it properly belongs in

2300:(1) I found your formatting improvements instructive when I noticed them on a couple of edits that I'd done: so _thanks_ for your example -- because I'm still a bit inexperienced on this. I'm trying to figure out the style instructions, but I do still find them a maze. 2506:

JULIANDAY.Year/Month/Day are accurate enough for generating Gregorian equivalent dates if the date falls between certian dates. If so, what would those dates be? The idea would be to incorporate these into the microformat date templates if they are up to the task. -

1579:

No worries, quite understand. If you do come across anything in your readings, that clarifies or even contradicts the line taken in that discussion, would be glad to hear of it; it's not my specialty subject area so I cld very well be overlooking something. Regards,

2593:

gives 2 August 216 BC. Are gregorian equivalents of these Roman calendar dates known with any accuracy? Are there any tables available so that a bot could figure these out? Gerry Ashton was telling me that the birth of Augustus is only known within a few days of

2039:

life of Knowledge (XXG). Regarding the orbital period, most astronomical sources do not give its value in mean solar days, but in International Astronomical Union days, each of which have exactly 86400 SI seconds, the same day (d) used in Earth's rotation period. —

2002:

is the integration of the given length-of-day (LOD) over many years (millions of seconds) so it includes several leap seconds, and is now 65 seconds greater than its average value between 1750 and 1892, called Terrestrial Time (TT). Do not confuse time with LOD. —

818:

Hello. I put a note and references about the month name of February in the Gregorian calendar article. I had bad luck: the most relevant link reference, that what relates "February", "fever" and "influenza", was broken hours after I put it on the article.

1986:(the graph at the end shows deviations slightly greater than the tabulated figures). The two trailing zeros within the h:m:s value are significant. Indeed, if the value is given in "seconds of mean solar time" rather than SI seconds, the IERS gives this 1652:

Sorry, but I do not have any knowledge of or interest in Thai festivals. My main interest is the calendar's history and technical aspects. Nor can I read Thai even though I did spend a year in the country during the Vietnam conflict (at Udon Thani). —

2618:"Time values encoded within elements that extend kml:AbstractTimePrimitiveGroup shall be in the context of the temporal reference system specified by ISO 8601, which uses the Gregorian Calendar and 24 hour local or Coordinated Universal Time (UTC)." 2105:

extremely unlikely but not impossible event) then we would have to rely on our observations of the Sun to give us our Solar day. The point I am trying to make is that apparant Solar time can be measured by nothing more complicated than a sundial.

2243:

regarding an issue with the article. When he calls for the views of 'Joe' it seems he is hoping you will respond. If you are not following this any more, please leave a note to that effect on Talk so that the 3O request can be closed. Thanks,

169:

I presume your complaint was triggered by my placement of the archival notice at the top of the page. Nevertheless, you are fighting a losing battle. The vast majority of Knowledge (XXG) editors add new discussion to the bottom of the page as

767:

concerning the early medieval zeros at Wiki items and and to react to these contributions. But I would ask you and JPD and other ones to react to the discussion concerning Wiki item , specially to my proposals to improve this Wiki item, at

2761:

ambiguity. Perhaps an optional "calendar" parameter would suffice- but if the community prefers, we could postpend a suffix like -j, -g, -r so that dates could be made explicit in a second calendar. Do you have a recommendation on that?

2567:. They are using ISO8601 too, though spot checks of google earth shows it is a little sloppy- you will see Z on the start date, but not on the end date if you set a pushpin timespan (see view tab), then save it as kml. Anyway, for the 716:

OK, thanks Joe. It seems another editor has since decided to wholesale revert those additions, which on balance I think is appropriate. If there was anything worth saving, it would at the very least need a concerted rewrite to be

822:

I reviewed the broken link; apparently, it is due to the fact that the web site host is being rearranged. As soon as the supporting article becomes available on line, I wish to restore the full original note with the new link.

1892:

Don't alter articles when you clearly don't know the subject. You alterations have had to be reversed becuase they are either weak, irrelevant or incorrect. Article writers should be expert before they consider alterations.

322:

The problem is that IE5,6,7 do not recognize "hidden", so I had to substitute "none". Although "hidden" supersedes "solid", "solid" supersedes "none", which requires the borders of virtually all cells to be specified. —

2529:

is much more complicated than necessary, although that may be due to all of the parameter formats allowed. By the way, I had to do some research to even find out what a "microformat date" is. I get the impression from

2146:

Sorry, your edit wasn't vandalism, just wrong. The headings in that table are the number coded by those unicode roman numerals; if it were just the index into the table, the heading line shouldn't be there at all. —

1808:

are also bound to change, but I embedded hidden table headings for all dates to make it easier for future editors to find the write place. Oh, and thanks for your clarification, below; I copied it to TSC's Talk page.

2671:= TAI+32.184s). The International Astronomical Union (IAU) recommends TT, but it is concerned with the proper calculation of the positions of astronomical bodies, not human events. If JD(UT1) were used, knowledge of 2259:

It would help if you reworded the section in question for clarity (ie, is year zero actually a year long, or only a place holder), and more so if you gave a source demonstrating this usage in modern astronomy.

999:

I agree. My only concern is that the table is very long and could be replaced by a more compact representation of the same information. I added something towards this in the Calendar Wikia version of the page

2378:

pp.287+. Unfortunately, my local university library where I now live only has a limited collection so I do not have immediate access to Neugebauer even though I have consulted HAMA many times in the past. —

748:

regarding the relationship between TAI and TT. Why? What was wrong with my text? The former (and current) article text is wrong. TT is by definition perfectly uniform, and TAI is a realisation of it.

2359:"Archiv fuer Orientforschung", and if there is anything you can tell me about what you would like within the van der Waerden paper, I'd be happy to try and see what I can get transmitted over to you. 178:, and you also answered at the bottom, just like I did. Editors can and do put their comments anywhere on the talk page, including the middle, which neither a top nor bottom posting request will stop. 2716:

by Chris Bennett proposes that the equivalent date in the proleptic Julian calendar was 29 July 216 BC, which is -02150725 in the proleptic Gregorian calendar using the ISO 8601 format according to

293:

Just thought you should know -- the limits table looks great under FireFox, but have a look at it under IE 6.0. Microsoft seems to really screw it up. I don't know what the solution is for this.

1049:

I tried creating this page, but somehow it got removed, even when I had provided proper citations for the same. Kindly respond at my talk page. Can you share with me your resources about Mayan?

364:

was not formed on that date. I can't say for sure that I haven't reverted him since then, although if I have, I didn't feel it necessary to send him a warning about it. I did, however, revert

2521:

I am quite familiar with the Julian date concept and have even programmed date conversion a long time age, so I can discuss the concept in general. But I have never studied the Knowledge (XXG)

159:) any new discussion topics added to the bottom of a page? That means that the old cruft stays on top and we always have to page through it to get to the current issues. A Bad Idea IMNSHO. 1253:

I was trying to stop the ongoing edit war by noting that either grouping is correct. One editor even said that one of the two groupings was wrong. Efficiency and the order of preference is

2483:

improved! (Even better than "fixing" the tables article, as I'd asked for.) Though it makes the usually stiffly well-organized and punctual Swedes look even worse than it did before... -

1217:

Probably, because I was an IBM employee until 1994. However, that is so long ago that I don't remember specifically appending to IBMPC FORUM. My greatest activity was in CALENDAR FORUM. —

2822:, which was usually used before 1972. Zone time was not used by the United States before 1983 and not used before 1847 by England, the first country to use any kind of zone time. Thus 2210:

He's had several blocks and an arbitration decision against him for OR. I've just given him 2 warnings, and I am at the end of my tether with him. 3 1/2 years and he hasn't learned.

1561:

I have never studied the Aztec calendar, so I could not comment at the time you asked for my opinion. I have done some research since then, but I'm still not ready to comment. —

98:

Good detective work, but is that a quote from Bede or from Jones? I assume it's from Bede, the cite for it should also indicate the point in the original Opera de Temporibus. --

1804:

in Phuket, then spread to just about everywhere with a large Thai Chinese community, to the point of displacing Thetsagan Sart Thai and Sart Chin on the calendars I've seen.

871:

coming to the harem of the Emperor and I thought it would be cool to say "The Year of the Dog" instead of a Western year, so thank-you for finding that for me. God Bless! --

2435:

The looks of this talk page convinces me that you do know what you are talking about. :) But then, for the sake of lay people like me, could you please do some work on

895:

Incidentally, may I kindly suggest that you eliminate the tautological definition of calendar reform in your opening line: "Calendar reform is any reform of a calendar".

1964:

over time. I challenge you to demonstrate that a reader will care about higher precision than six decimals. Are you going to keep updating the value over time? Thanks.—

2644:

articles for a given time period in a given geographic area. Anyway, we need to be thinking about how we want to emit this information, and express it in templates. -

981:

Yes, I saw that article. Although I have not read it completely, I doubt that it violates NPOV judging by the title. My initial thought is that it should merge with

2678:. If JD(TAI) were used, a list of leap seconds and when they occurred would be needed to recover a UTC date-time, which is available in machine readable format via 2456:

Although Sweden specified the Rudolphine Tables, any tables could have been used, even modern calculations, as long as all dates are calculated at the meridian of

852:, which is more relevant to the case. Did you know that the winter flu kills about 36,000 people a year only in the US? Think about flu and ancient Romans then... 1831:

Right now it reads, in part, "... (Thai: คริสต์ศักราช, kritsakarat) , abbreviated Kho So (Thai: ค.ศ.). They also show Chinese numerals for the Common Era...."

2585:

One editor in the MOSNUM imbroglio over plain text dates made a good suggestion to take a look at the Julian templates, and I stumbled on the contribution of

227:. I'm not sure what happened there; I guess something got mangled because he was vandalizing the page so frequently. You're right...time to archive. -- 913: 608: 119:

Hmm. That makes it sound like an inference and a not particularly certain one at that. I have Jones' book on order through ILL, thanks for the cite.

786:

Hi Joe. Have you seen my comment at the top of the TAI discussion page? I'm not prone to make the change myself, and I'm wondering if you are game.

1238:

or). So I don't really see the point of your edit, but since I don't want to prolong an edit war, I leave it to you to do something about (or not).

763:

Joe Kress, I would ask you (after your contribution of 17-1-2007) to take cognizance of the new contributions of JPD and of me to the discussion at

1862:(this level of detail has been edited out), since 1949 mainland China has often identified Western Gregorian years (January–December) via the term 2338:

McCarthy observed that Anatolius must have thought the Second Coming was soon, otherwise he would not have proposed such an irregular 'cycle'. —

420:

affect me. I'm flying on Tuesday, and it looks like I'm going to have to check my bag; my smallest contact lens solution bottles are 120 ml. --

941:

Hi, just a short note to say thanks for your tireless work on the calendar articles. I have translated some of them or used them as a model on

361: 2675:(=TT−UT1) at the end of June or December (when leap seconds normally occur) would be needed, which is available in machine readable format at 393:

dated June 2005 indicated that the machines were being used at 16 or more airports. The TSA was requesting funds to install them nationwide.

960: 945:, from 2004 on, and have them on my watch list -- and I see that you're constantly improving them. Thanks and keep up the good work! -- 2236: 1082: 967:

or just not being notable enough to justify its existence as a separate article. It has been created by the same author who added the

620: 1517: 2561:

emits in the KML format. This is a consumer of time information as well. For example, map applications are adding history features

1956:

would usually not be, because both values are unstable at that level of precision, and readers are unlikely to care in the context.)

925: 465: 426: 378: 233: 82: 61: 1944:

Avoid over-precise values where they are unlikely to be stable or accurate, or where the precision is unnecessary in the context. (

2165:

determine the Unicode hexadecimal code of the entry. The numerical headings do not match the third line of the table as shown in

2018:

variation on the order of 0.0004 per thousand years, so it may have too many digits. I haven't finished checking the others yet.—

1866:(gōngyuán 公元), to distinguish them from the same numbered years in the traditional lunisolar calendar (agricultural calendar or 651:

Jupiter is not where we see it now. If the Earth didn't move, Jupiter would be at yet a DIFFERENT spot than where we see it now.

2374:

I would be interested in his conclusions relative to those of Rogers. He gives a very cryptic summary of his paper in his book

2085:. Note that messages on the bot talk page may not be seen. Such messages are best left on my talk page. Anyway, thanks again. 1360: 1413:(system 0-9). The same problem exists in the Russian Knowledge (XXG) (categories which have interwikis vs. articles). In the 1036: 537:

ipconfig, but only if you are currently connected to your ISP. If you are not connected, no IP address will be displayed. —

492:

I've contacted the blocking administrator for comment; in the meantime, please bear with us, and thanks for your patience.

368:

tonight, but this was after his note to me caused me to review his recent edits. BTW, has the TSA actually deployed those

2835: 2789: 2729: 2653: 2630: 2547: 2515: 2492: 2470: 2450: 2407: 2388: 2368: 2347: 2332: 2312: 2287: 2269: 2253: 2219: 2200: 2178: 2154: 2133: 2114: 2094: 2071: 2048: 2029: 2012: 1975: 1921: 1902: 1879: 1849: 1818: 1778: 1762: 1732: 1714: 1688: 1662: 1646: 1622: 1596: 1570: 1555: 1490: 1474: 1438: 1396: 1353: 1333: 1292: 1274: 1247: 1226: 1211: 1192: 1177: 1150: 1132: 1113: 1099: 1095:

I have added some text based on your input and that of Dojarca about this topic. Take a look and adjust as you see fit --

1053: 1007: 993: 975: 949: 929: 875: 856: 834: 808: 790: 776: 753: 731: 710: 699: 668: 640: 624: 590: 541: 525: 496: 480: 470: 431: 410: 383: 327: 315: 297: 282: 258: 238: 212: 163: 144: 129: 113: 102: 87: 66: 2398:

could transmit something in scanned form if there's an available route, feel free to email me (link on my user-page). --

2064: 853: 831: 208:

without making any changes to it. This reverts the vandalism without missing even minor changes that the vandal made. —

2809:

are only used in an article about leap seconds. Conversion from AM/PM to a 24-hour system at Greenwich might be needed.

476:

I was aware of that discussion but felt no need to participate because you and others handled the situtation nicely. —

1746: 1502: 403: 1162: 348:. That one wasn't even a close call; he was trying to insert a diatribe about 9/11 and subsequent events into the 2461:

my revert, so I can expand the Easter section of the Swedish calendar article, including applicable references. —

888:

What inspires your interest in calendar reform? I would be interested to learn about your research in this area.

2664: 1406: 1174: 1001: 308: 122:

In any case I wonder if this remark shouldn't really be n the article on Easter rather than the Julian calendar?

1142:

at the Royal Observatory, so I am aware that astronomical instruments are aligned to the local plumb line via a

2713: 1909: 633: 2565: 2189: 196:. To revert such vandalsim, do not correct each change individually. Instead, select the last good version on 2526: 1898: 1434: 1349: 1078: 685:

Unfortunately I don't have the background on egyptian calendrics to confirm one way or the other. Cheers, --

1070: 1024: 605:

reference to fix the beginning of the new year in their calendar. This can be seen from the VI BC tablets.

2151: 2082: 2060: 1618: 1410: 1207: 827: 769: 616: 394: 304: 52: 44: 1698: 772:(the only right place for this discussion after all), at which I would like to continue this discussion. 2785: 2649: 2626: 2511: 1750: 1591: 1550: 1414: 921: 750: 724: 692: 463: 424: 376: 345: 334: 231: 80: 59: 1894: 1074: 986: 2562: 2705: 2525:, so I can provide no recommendation regarding its acceptable date range. The algorithm described at 2249: 2215: 2090: 1050: 872: 2717: 2831: 2819: 2725: 2570: 2543: 2531: 2488: 2466: 2446: 2403: 2384: 2364: 2343: 2328: 2308: 2174: 2129: 2044: 2008: 1917: 1875: 1797: 1774: 1710: 1658: 1634: 1566: 1528: 1425:

refers to period 1990-1999, only in Russian Knowledge (XXG) it refers to the period 1991-2000 (see

1392: 1270: 1222: 1139: 787: 453: 183:

I never page through the talk page to get to current issues. Whenever I see a page that I watch on

17: 2739: 2823: 2691: 2522: 1845: 1814: 1758: 1728: 1684: 1642: 1455: 1430: 1345: 1189: 1096: 1032: 805: 279: 255: 126: 99: 2741:(see footnote), and so with Bennet's table we could generate a proleptic gregorian for that too. 1325: 303:

Thanks for the alert. I have read that Internet Explorer does not implement all of the rules of

1284: 1239: 2437: 2428: 2148: 1702: 1614: 1203: 674: 612: 506: 369: 1983: 1254: 964: 2781: 2709: 2668: 2645: 2622: 2590: 2507: 2416: 2196: 2121: 2023: 1969: 1867: 1581: 1540: 1364: 1004: 972: 917: 907: 718: 686: 587: 514: 493: 460: 421: 390: 373: 228: 77: 73: 56: 1937: 1372: 1262: 2278:

I see you just responded while I was typing this. I'll read your resp and then respond.

2245: 2211: 2110: 2086: 1421:– the table with lines from x0 to x9. In all wikipedias (except Russian) the article like 1368: 826:

To see the private discussion about "February", "fever" and "influenza", please visit the

160: 2738:

From what I looked up yesterday when composing my note, the Cannae date is roman calendar

2240: 1165:... Let's discuss further there if needed, but I believe your revert was unwarranted. ++ 2827: 2815: 2721: 2556: 2539: 2484: 2462: 2442: 2399: 2380: 2360: 2339: 2324: 2304: 2283: 2265: 2232: 2170: 2161: 2140: 2125: 2040: 2004: 1913: 1871: 1770: 1719:

I found the 'a' in '-pal' means it is an adjective; '-le' is le noun. But I settled on

1706: 1654: 1562: 1532: 1514: 1486: 1470: 1462: 1388: 1288: 1266: 1243: 1218: 1147: 990: 982: 801: 707: 637: 538: 522: 477: 407: 399: 324: 312: 254:. I'm going to NPOV it a bit, but hopefully, not change the substance. Thanks again! 209: 141: 110: 2067:. I should have done a better job to checking the results. Thanks again for the fix. 1991: 1405:

So, I observe that different users can apply the system they like more - for example:

1960:

0.997267 gives a value accurate to the tenth of a second, and the number is going to

1841: 1810: 1754: 1724: 1680: 1638: 1170: 1028: 1018: 665: 662: 657: 652: 294: 251: 244: 2059:

Thanks for fixing my mistake in failing to do a complete job reverting the edits by

2687: 2586: 2081:

Thanks for referring me to the incorrect unlinking by Lighbot of the letter 'M' in

1418: 1143: 840:

The link was repaired and I restored the note and the reference again. I also cite

353: 1429:). It’s a pity but there is no real consensus (only the first user’s will :-) ).-- 513:

at 22:34 on 24 December 2006 for one week (I hope Essjay is not on vacation). See

192:

When applied to articles, this allows me to catch vandalism like that recently on

276: 2806: 2192: 2019: 1965: 1202:

Are you the same Joe Kress who used to contribute to the IBMPC FORUM on VNET? --

1065: 764: 510: 175: 156: 32: 2614: 1932:

We appear to have an issue with the precision of the Sidereal day field on the

1840:

along and change it, so I'll put this on TSC's Talk page for future reference.

402:. The complete TSA list of allowed and prohibited items, including liquids, is 2106: 2068: 1936:

article, so I would like to discuss this before we get into a revert war. Per

1859: 1129: 1110: 849: 841: 773: 344:, with a clear explanation in the edit summary and another explanation on his 171: 2679: 2676: 985:, which I presume is monitored by the current World Calendar representative, 48: 2457: 2279: 2261: 2225: 1510: 1482: 1466: 1258: 845: 442: 273: 2166: 1426: 2535: 1376: 1321: 1166: 946: 193: 2613:

Under 15.1.2 of the KML spec (OGC 07-147r2- see OGC KML pdf download at

1123:

That vandalism was just subtle enough that I wasn't completely sure it

1017:

Thanks for correcting my sloppy spelling and grammer. Much appreciated

892:

interaction (I am accustomed to publishing in peer-reviewed journals).

745: 738: 372:

units? I've only flown a few times this year; I haven't seen them. --

340:

Hi, Joe! The silly thing is, as far as I can tell I only reverted him

2160:

I was returning the table to its stable state since it was created by

1527:

Hi there Joe. If you have the time, would appreciate you looking over

553: 2423: 1536: 1309: 868: 449:

nasty comments that would have probably caused someone to send me an

137: 1982:

so these eight significant digits are not excessive in context. See

31:

Hi Joe, small difference of opinion about the precise definition of

1667:

Thanks for your help with the headings. I'm confused as to whether

1417:

one can see the table with lines from x1 to x0, but in the article

989:. He can remove any incorrect, redundant, or excessive material. — 2672: 1933: 1422: 1384: 1380: 2818:

has existed technically since 1928, it was only another name for

1950:

The distance from the Earth to the Sun is 149,014,769 kilometres

1535:

talkpg, concerning an ext link to an animated "aztec" calendar (

357: 349: 1946:

The speed of light in a vacuum is 299,792,458 metres per second

680:

Hi there Joe. When you get a chance would you kindly look over

518: 45:

User_talk:Gerry_Ashton#Your_edits_to_Anno_Domini_and_Common_Era

278:). If you agree, I'll be glad to make the change in the text. 1984:

IERS Excess of the duration of the day to 86400s … since 1623

1359:

All Knowledge (XXG) conventions I've checked are consistent:

2479:

Thanks for answering and for fixing the calendar article --

445:, check it out. I had to restrain myself from posting some 1697:

It should be "principal" meaning the "most important". See

1313: 867:

Thanks for the year thing. I'm writing a short story about

1501:

Hi. I'd be interested to read your opinion on my recent

942: 548: 360:

page is for things that happened on that date -- and the

1379:

apparently are derived from calling modern decades the

1306: 681: 365: 341: 224: 40: 36: 2564:, and the KML format allows passing of time parameters 1265:

discussion, which is prohibited on Knowledge (XXG). —

830:(the other member that drops my original note). Yours. 647:

Of course the motion of the Earth affects travel time

2611:

edit- ignore previous paragraph, it's not an option.

1109:

My rv caused it to appear again; sorry for trouble.

955:

Comparison of World Calendar with Gregorian Calendar

961:

Comparison of World Calendar and Gregorian Calendar

74:

Talk:Anno_Domini#Epoch_is_nativity_or_conception.3F

2667:kept by atomic clocks, now about UT1+65s), or TT ( 1721:Work holidays and festivals regulated by the moon 509:, an entire range of IP addresses was blocked by 1283:Fair enough. Thanks for your thoughtful edits. 1261:section even though it can be construed to be a 1328:(because it is possible for somebody to create 416:I just realized that those liquid restrictions 1605:"It is not necessary..." ≠ "Thou shalt not..." 2441:to make clear the connection? Thank you. - 1257:. I have restrained myself from deleting the 800:Hi, I replied to an old comment of yours, on 744:You reverted some corrections that I made to 8: 2376:Science awakening II: The birth of astronomy 1998:(it excludes the +1 ms). On the other hand, 1910:Talk:Babylonian calendar#Article alterations 1677:Holidays and festivals regulated by the moon 1585: 1544: 352:article. No matter how you look at it, the 2826:maps, for example, used local mean time. — 1610:their grammar, spelling, and punctuation. 1163:Talk:Treaty_of_Tordesillas#Map_Image_issues 2621:respond to some of the issues with code. - 55:believes the definition is in dispute. -- 1336:for years 1-10 and so on). If this was a 959:I draw your attention to the new article 35:. Can you take a look at these edits in 1990:to fourteen significant digits in their 1954:The population of Cape Town is 2,968,790 1013:Thank you "Royal Observatory, Greenwich" 963:, which could be construed as violating 2603:Stepping back from this, I ask myself 2354:#3 Source materials for zodiac history 1451:Your recent edit removed the template 578:Thank you for your time and patience. 1796:Yasothon's Rocket Festival. Phuket's 1045:Do you have details about Pravan Veda 72:Ok, the discussion has been moved to 7: 2538:format for the year is but not . — 1800:also made the list, because it just 1334:Category:First decade of 1st century 1255:outside the scope of Knowledge (XXG) 250:Thanks, Joe, for the corrections to 2706:Livy's History of Rome: Book 22.46 1361:Knowledge (XXG):Timeline standards 1340:, can you indicate the Wikipedian 24: 1938:Knowledge (XXG):MoS#Large_numbers 1791:changes. I left an embedded note 1138:I just happen to be studying the 881:Your interest in calendar reform. 552: 521:to determine your IP address. — 307:in the manner prescribed by the 27:Need an opinion on these changes 1835:"Christian Era" is the correct 2049:20:31, 27 September 2008 (UTC) 2030:18:35, 27 September 2008 (UTC) 2013:22:43, 25 September 2008 (UTC) 1976:16:36, 24 September 2008 (UTC) 1675:, so side-stepped to Diller's 1419:20th century#Decades and years 1178:16:48, 28 September 2007 (UTC) 1151:21:39, 11 September 2007 (UTC) 1133:20:56, 11 September 2007 (UTC) 802:Talk:Longitude#Mile conversion 515:User talk:Essjay#67.150.0.0/16 391:EPIC Spotlight on Surveillance 51:agrees with my understanding; 1: 2313:13:53, 27 February 2009 (UTC) 2296:Thanks , and a language point 2288:20:20, 23 February 2009 (UTC) 2270:20:18, 23 February 2009 (UTC) 2254:03:24, 22 February 2009 (UTC) 2095:07:56, 30 December 2008 (UTC) 1948:is probably appropriate, but 1633:Would you take a new look at 1320:years?! I suppose that it is 1227:06:59, 10 February 2008 (UTC) 844:as a source and redirect the 791:17:22, 22 February 2007 (UTC) 777:12:56, 22 February 2007 (UTC) 591:10:00, 28 December 2006 (UTC) 567:for the following reason(s): 542:04:33, 28 December 2006 (UTC) 526:03:03, 28 December 2006 (UTC) 497:23:44, 26 December 2006 (UTC) 283:19:36, 20 November 2006 (UTC) 259:01:06, 20 November 2006 (UTC) 239:23:39, 11 November 2006 (UTC) 223:Took me a minute to see what 2233:Talk:Year zero#Third opinion 2220:20:33, 7 February 2009 (UTC) 2201:01:33, 7 February 2009 (UTC) 2179:03:37, 3 February 2009 (UTC) 2155:02:44, 3 February 2009 (UTC) 2134:20:44, 21 January 2009 (UTC) 2115:02:16, 21 January 2009 (UTC) 2065:Geographic coordinate system 2055:Geographic coordinate system 1928:Date precision on Earth page 1212:19:22, 9 February 2008 (UTC) 1193:13:27, 1 November 2007 (UTC) 814:February name and references 754:14:54, 7 February 2007 (UTC) 732:04:44, 6 February 2007 (UTC) 711:07:55, 5 February 2007 (UTC) 700:01:22, 5 February 2007 (UTC) 669:09:35, 2 February 2007 (UTC) 641:00:22, 21 January 2007 (UTC) 625:12:33, 20 January 2007 (UTC) 561:Your request to be unblocked 481:07:43, 2 December 2006 (UTC) 471:04:38, 2 December 2006 (UTC) 432:17:03, 2 December 2006 (UTC) 411:07:43, 2 December 2006 (UTC) 384:04:32, 2 December 2006 (UTC) 328:12:13, 2 December 2006 (UTC) 316:03:11, 2 December 2006 (UTC) 298:22:23, 1 December 2006 (UTC) 213:23:38, 31 October 2006 (UTC) 164:10:08, 30 October 2006 (UTC) 145:23:38, 31 October 2006 (UTC) 130:20:43, 21 October 2006 (UTC) 114:02:45, 21 October 2006 (UTC) 103:15:55, 20 October 2006 (UTC) 88:00:48, 15 October 2006 (UTC) 67:00:31, 15 October 2006 (UTC) 2814:Although (non-coordinated) 2318:#2 Computus & Anatolius 2072:03:54, 1 October 2008 (UTC) 1922:00:41, 21 August 2008 (UTC) 1783:You're right! When I added 1747:Public holidays in Thailand 1745:Right now I'm playing with 1741:Public holidays in Thailand 1305:Hello! You’ve written here 1114:05:59, 18 August 2007 (UTC) 2852: 2836:05:30, 20 April 2009 (UTC) 2790:23:59, 13 April 2009 (UTC) 2730:20:44, 13 April 2009 (UTC) 2654:18:43, 12 April 2009 (UTC) 2631:22:41, 12 April 2009 (UTC) 2548:08:09, 12 April 2009 (UTC) 2516:07:40, 11 April 2009 (UTC) 2389:19:48, 31 March 2009 (UTC) 2369:11:06, 31 March 2009 (UTC) 2348:19:48, 31 March 2009 (UTC) 2333:11:06, 31 March 2009 (UTC) 1785:Other national observances 1518:09:03, 23 April 2008 (UTC) 1491:21:02, 19 March 2008 (UTC) 1475:18:43, 15 March 2008 (UTC) 1439:18:21, 19 March 2008 (UTC) 1397:07:31, 19 March 2008 (UTC) 1140:deflection of the vertical 1100:21:59, 4 August 2007 (UTC) 876:21:02, 29 April 2007 (UTC) 857:09:21, 24 April 2007 (UTC) 835:08:37, 23 April 2007 (UTC) 809:00:46, 17 March 2007 (UTC) 632:Copied to and answered on 551: 268:of the Sept. 1493 Bull is 2665:International Atomic Time 2493:14:13, 9 April 2009 (UTC) 2471:02:11, 9 April 2009 (UTC) 2451:14:00, 8 April 2009 (UTC) 2408:22:00, 2 April 2009 (UTC) 1903:17:37, 31 July 2008 (UTC) 1880:05:49, 29 July 2008 (UTC) 1858:As formerly mentioned in 1850:11:56, 28 July 2008 (UTC) 1819:12:18, 29 July 2008 (UTC) 1779:05:49, 29 July 2008 (UTC) 1715:04:23, 30 June 2008 (UTC) 1689:15:05, 25 June 2008 (UTC) 1669:Principal lunar festivals 1663:18:53, 23 June 2008 (UTC) 1647:16:38, 22 June 2008 (UTC) 1623:22:16, 16 June 2008 (UTC) 1407:List of battles 1901-2000 1354:14:29, 7 March 2008 (UTC) 1293:07:17, 4 March 2008 (UTC) 1275:04:54, 4 March 2008 (UTC) 1248:09:33, 2 March 2008 (UTC) 1054:11:38, 10 July 2007 (UTC) 1008:14:59, 21 June 2007 (UTC) 994:01:39, 21 June 2007 (UTC) 976:09:34, 19 June 2007 (UTC) 910:06:45, 16 May 2007 (UTC) 782:International Atomic Time 309:World Wide Web Consortium 2190:Western Semitic Calendar 2185:Western Semitic Calender 1763:10:39, 4 July 2008 (UTC) 1733:10:39, 4 July 2008 (UTC) 1597:12:57, 31 May 2008 (UTC) 1571:07:40, 21 May 2008 (UTC) 1496: 950:11:43, 28 May 2007 (UTC) 930:06:22, 16 May 2007 (UTC) 828:Gerry Ashton's talk page 634:Talk:Babylonian calendar 443:Talk:1 BC#Requested move 2780:How does that sound? - 2527:Template talk:JULIANDAY 1556:07:42, 9 May 2008 (UTC) 1377:MOS:DATE#Longer periods 1344:of that idea? Thanks.-- 854:Ricardo Cancho Niemietz 832:Ricardo Cancho Niemietz 2708:gives no date for the 2083:NATO phonetic alphabet 2077:NATO phonetic alphabet 1411:List of wars 1900-1944 1091:End of consular dating 971:template you deleted. 770:Talk:Dionysius_Exiguus 682:these recent additions 305:Cascading Style Sheets 155:Joe, Why do you want ( 1703:Principle / Principal 1699:Principal / Principle 1415:Category:20th century 1373:WP:MOS#Longer periods 1157:Treaty_of_Tordesillas 1085:) 07:19, 12 July 2007 916:comment was added by 611:comment was added by 335:User talk:Darthvader1 49:Catholic Encyclopedia 2534:that the acceptable 2501:Your recommendation? 2167:Unicode number forms 2061:User:203.202.188.211 1505:about the NATO/ICAO 1308:. Are you sure that 1059:Hipparchus and Meton 1039:) 08:10, 2 July 2007 759:early medieval zeros 570:There has been some 264:It appears that the 43:and the followup on 2820:Greenwich Mean Time 2532:Template:Start-date 1888:Babylonian calendar 1827:Thai solar calendar 1798:Vegetarian Festival 1635:Thai lunar calendar 1629:Thai lunar calendar 1259:Leap Year#Algorithm 600:Babylonian calendar 585:Request handled by: 507:Special:ipblocklist 398:TSA description is 219:Good catch, thanks! 18:User talk:Joe Kress 2824:American Civil War 2523:Template:JULIANDAY 2239:, has requested a 1994:, which they call 1671:should perhaps be 94:Parilia and Easter 2438:Rudolphine Tables 2429:Rudolphine Tables 2422:"...according to 1595: 1554: 1409:(system 1-0) vs. 1316:) may consist of 1087: 1073:comment added by 1041: 1027:comment added by 933: 885:Hello Mr. Kress: 729: 717:comprehensible.-- 697: 675:Egyptian calendar 628: 597: 596: 519:WhatIsMyIPAddress 370:backscatter X-ray 2843: 2710:Battle of Cannae 2669:Terrestrial Time 2591:Battle of Cannae 2574: 2560: 2417:Swedish calendar 2122:Talk:Leap second 1992:Useful constants 1868:Chinese calendar 1589: 1588: 1587: 1548: 1547: 1546: 1511:NigelG (or Ndsg) 1497:NATO 'fower' (4) 1460: 1454: 1365:Category:Decades 1086: 1067: 1040: 1021: 911: 796:Gore & Globe 725: 723: 693: 691: 660: 655: 606: 556: 549: 458: 452: 2851: 2850: 2846: 2845: 2844: 2842: 2841: 2840: 2568: 2554: 2503: 2420: 2356: 2320: 2298: 2229: 2208: 2187: 2144: 2102: 2079: 2057: 1930: 1890: 1829: 1743: 1631: 1607: 1584: 1543: 1529:this discussion 1525: 1499: 1458: 1452: 1449: 1369:List of decades 1303: 1235: 1200: 1185: 1183:Hebrew calendar 1159: 1121: 1107: 1093: 1068: 1061: 1051:BalanceRestored 1047: 1022: 1015: 969:Calendar Reform 957: 939: 912:—The preceding 883: 873:Working for Him 865: 816: 798: 784: 761: 742: 721: 689: 678: 658: 653: 649: 607:—The preceding 602: 489: 468: 456: 450: 439: 429: 381: 338: 291: 289:Hebrew Calendar 248: 236: 221: 153: 96: 85: 64: 29: 22: 21: 20: 12: 11: 5: 2849: 2847: 2839: 2838: 2816:Universal Time 2811: 2810: 2801: 2800: 2795: 2794: 2793: 2792: 2775: 2774: 2773: 2772: 2765: 2764: 2763: 2762: 2755: 2754: 2753: 2752: 2745: 2744: 2743: 2742: 2733: 2732: 2702: 2701: 2696: 2695: 2683: 2682: 2659: 2658: 2657: 2656: 2638: 2637: 2636: 2635: 2634: 2633: 2598: 2597: 2596: 2595: 2580: 2579: 2578: 2577: 2502: 2499: 2498: 2497: 2496: 2495: 2474: 2473: 2419: 2414: 2413: 2412: 2411: 2410: 2392: 2391: 2355: 2352: 2351: 2350: 2319: 2316: 2297: 2294: 2293: 2292: 2291: 2290: 2273: 2272: 2235:an IP editor, 2228: 2223: 2207: 2204: 2186: 2183: 2182: 2181: 2143: 2141:Roman numerals 2138: 2137: 2136: 2101: 2098: 2078: 2075: 2056: 2053: 2052: 2051: 2035: 2034: 2033: 2032: 1958: 1957: 1929: 1926: 1925: 1924: 1889: 1886: 1885: 1884: 1883: 1882: 1853: 1852: 1828: 1825: 1824: 1823: 1822: 1821: 1742: 1739: 1738: 1737: 1736: 1735: 1694: 1693: 1692: 1691: 1630: 1627: 1613:All the best, 1606: 1603: 1602: 1601: 1600: 1599: 1574: 1573: 1533:Aztec calendar 1524: 1523:Aztec calendar 1521: 1498: 1495: 1494: 1493: 1463:Roman numerals 1461:from the page 1448: 1445: 1444: 1443: 1442: 1441: 1400: 1399: 1302: 1299: 1298: 1297: 1296: 1295: 1278: 1277: 1234: 1231: 1230: 1229: 1199: 1196: 1184: 1181: 1158: 1155: 1154: 1153: 1120: 1119:Prime Meridian 1117: 1106: 1103: 1092: 1089: 1060: 1057: 1046: 1043: 1014: 1011: 997: 996: 983:World Calendar 956: 953: 938: 935: 882: 879: 864: 861: 860: 859: 815: 812: 797: 794: 788:Steven L Allen 783: 780: 760: 757: 741: 737:TAI and TT in 735: 714: 713: 677: 672: 648: 645: 644: 643: 601: 598: 595: 594: 581:Best regards. 569: 568: 557: 547: 546: 545: 544: 531: 530: 529: 528: 500: 499: 488: 485: 484: 483: 466: 441:If you missed 438: 435: 427: 414: 413: 379: 337: 332: 331: 330: 319: 318: 290: 287: 286: 285: 272:(see, e. g., 270:Dudum siquidem 247: 242: 234: 220: 217: 216: 215: 202:Edit this page 200:, then select 189: 188: 180: 179: 152: 149: 148: 147: 117: 116: 95: 92: 91: 90: 83: 62: 28: 25: 23: 15: 14: 13: 10: 9: 6: 4: 3: 2: 2848: 2837: 2833: 2829: 2825: 2821: 2817: 2813: 2812: 2808: 2803: 2802: 2797: 2796: 2791: 2787: 2783: 2779: 2778: 2777: 2776: 2769: 2768: 2767: 2766: 2759: 2758: 2757: 2756: 2749: 2748: 2747: 2746: 2740: 2737: 2736: 2735: 2734: 2731: 2727: 2723: 2719: 2715: 2711: 2707: 2704: 2703: 2698: 2697: 2693: 2689: 2685: 2684: 2680: 2677: 2674: 2670: 2666: 2661: 2660: 2655: 2651: 2647: 2642: 2641: 2640: 2639: 2632: 2628: 2624: 2619: 2615: 2612: 2609: 2608: 2607: 2602: 2601: 2600: 2599: 2592: 2588: 2584: 2583: 2582: 2581: 2572: 2566: 2563: 2558: 2551: 2550: 2549: 2545: 2541: 2537: 2533: 2528: 2524: 2520: 2519: 2518: 2517: 2513: 2509: 2500: 2494: 2490: 2486: 2482: 2478: 2477: 2476: 2475: 2472: 2468: 2464: 2459: 2455: 2454: 2453: 2452: 2448: 2444: 2440: 2439: 2433: 2432: 2430: 2425: 2418: 2415: 2409: 2405: 2401: 2396: 2395: 2394: 2393: 2390: 2386: 2382: 2377: 2373: 2372: 2371: 2370: 2366: 2362: 2353: 2349: 2345: 2341: 2337: 2336: 2335: 2334: 2330: 2326: 2317: 2315: 2314: 2310: 2306: 2301: 2295: 2289: 2285: 2281: 2277: 2276: 2275: 2274: 2271: 2267: 2263: 2258: 2257: 2256: 2255: 2251: 2247: 2242: 2238: 2234: 2227: 2224: 2222: 2221: 2217: 2213: 2205: 2203: 2202: 2198: 2194: 2191: 2184: 2180: 2176: 2172: 2168: 2163: 2159: 2158: 2157: 2156: 2153: 2150: 2142: 2139: 2135: 2131: 2127: 2123: 2119: 2118: 2117: 2116: 2112: 2108: 2099: 2097: 2096: 2092: 2088: 2084: 2076: 2074: 2073: 2070: 2066: 2062: 2054: 2050: 2046: 2042: 2037: 2036: 2031: 2027: 2026: 2021: 2016: 2015: 2014: 2010: 2006: 2001: 1997: 1993: 1989: 1985: 1980: 1979: 1978: 1977: 1973: 1972: 1967: 1963: 1955: 1951: 1947: 1943: 1942: 1941: 1939: 1935: 1927: 1923: 1919: 1915: 1911: 1907: 1906: 1905: 1904: 1900: 1896: 1887: 1881: 1877: 1873: 1869: 1865: 1861: 1857: 1856: 1855: 1854: 1851: 1847: 1843: 1838: 1834: 1833: 1832: 1826: 1820: 1816: 1812: 1807: 1803: 1799: 1794: 1790: 1786: 1782: 1781: 1780: 1776: 1772: 1767: 1766: 1765: 1764: 1760: 1756: 1752: 1748: 1740: 1734: 1730: 1726: 1722: 1718: 1717: 1716: 1712: 1708: 1704: 1700: 1696: 1695: 1690: 1686: 1682: 1678: 1674: 1670: 1666: 1665: 1664: 1660: 1656: 1651: 1650: 1649: 1648: 1644: 1640: 1636: 1628: 1626: 1625:Writtenright 1624: 1620: 1616: 1611: 1604: 1598: 1594: 1593: 1583: 1578: 1577: 1576: 1575: 1572: 1568: 1564: 1560: 1559: 1558: 1557: 1553: 1552: 1542: 1538: 1534: 1530: 1522: 1520: 1519: 1516: 1512: 1508: 1504: 1492: 1488: 1484: 1479: 1478: 1477: 1476: 1472: 1468: 1464: 1457: 1447:Your deletion 1446: 1440: 1436: 1432: 1431:ChroniclerSPb 1428: 1424: 1420: 1416: 1412: 1408: 1404: 1403: 1402: 1401: 1398: 1394: 1390: 1386: 1382: 1378: 1374: 1370: 1366: 1362: 1358: 1357: 1356: 1355: 1351: 1347: 1346:ChroniclerSPb 1343: 1339: 1335: 1331: 1327: 1323: 1319: 1315: 1311: 1307: 1300: 1294: 1290: 1286: 1282: 1281: 1280: 1279: 1276: 1272: 1268: 1264: 1260: 1256: 1252: 1251: 1250: 1249: 1245: 1241: 1232: 1228: 1224: 1220: 1216: 1215: 1214: 1213: 1209: 1205: 1197: 1195: 1194: 1191: 1190:Kaisershatner 1182: 1180: 1179: 1176: 1172: 1168: 1164: 1156: 1152: 1149: 1145: 1141: 1137: 1136: 1135: 1134: 1131: 1126: 1118: 1116: 1115: 1112: 1104: 1102: 1101: 1098: 1097:Chris Bennett 1090: 1088: 1084: 1080: 1076: 1072: 1066: 1058: 1056: 1055: 1052: 1044: 1042: 1038: 1034: 1030: 1026: 1020: 1012: 1010: 1009: 1006: 1002: 995: 992: 988: 984: 980: 979: 978: 977: 974: 970: 966: 962: 954: 952: 951: 948: 944: 936: 934: 931: 927: 923: 919: 915: 909: 905: 902: 899: 896: 893: 889: 886: 880: 878: 877: 874: 870: 862: 858: 855: 851: 847: 843: 839: 838: 837: 836: 833: 829: 824: 820: 813: 811: 810: 807: 803: 795: 793: 792: 789: 781: 779: 778: 775: 771: 766: 758: 756: 755: 752: 751:195.224.75.71 747: 740: 736: 734: 733: 730: 728: 720: 712: 709: 704: 703: 702: 701: 698: 696: 688: 683: 676: 673: 671: 670: 667: 664: 661: 656: 646: 642: 639: 635: 631: 630: 629: 626: 622: 618: 614: 610: 599: 593: 592: 589: 586: 582: 579: 576: 573: 566: 562: 558: 555: 550: 543: 540: 535: 534: 533: 532: 527: 524: 520: 516: 512: 508: 505:According to 504: 503: 502: 501: 498: 495: 491: 490: 486: 482: 479: 475: 474: 473: 472: 469: 464: 462: 455: 448: 444: 437:By the way... 436: 434: 433: 430: 425: 423: 419: 412: 409: 405: 401: 396: 392: 388: 387: 386: 385: 382: 377: 375: 371: 367: 363: 359: 356:entry on the 355: 351: 347: 343: 336: 333: 329: 326: 321: 320: 317: 314: 310: 306: 302: 301: 300: 299: 296: 288: 284: 281: 280:NorCalHistory 277: 274: 271: 267: 263: 262: 261: 260: 257: 256:NorCalHistory 253: 252:Inter caetera 246: 245:Inter caetera 243: 241: 240: 237: 232: 230: 226: 218: 214: 211: 207: 203: 199: 195: 191: 190: 186: 182: 181: 177: 173: 168: 167: 166: 165: 162: 158: 151:bottomfeeder? 150: 146: 143: 139: 134: 133: 132: 131: 128: 127:Chris Bennett 123: 120: 115: 112: 107: 106: 105: 104: 101: 100:Chris Bennett 93: 89: 86: 81: 79: 75: 71: 70: 69: 68: 65: 60: 58: 54: 50: 46: 42: 38: 34: 26: 19: 2807:Leap seconds 2617: 2610: 2604: 2587:User:Verdy p 2504: 2480: 2436: 2434: 2427: 2421: 2375: 2357: 2321: 2302: 2299: 2237:24.242.42.17 2230: 2209: 2188: 2149:Arthur Rubin 2145: 2120:Response at 2103: 2080: 2058: 2024: 1999: 1995: 1987: 1970: 1961: 1959: 1953: 1949: 1945: 1931: 1908:Answered at 1895:Cal Enda Gar 1891: 1863: 1836: 1830: 1806:Work holiday 1805: 1801: 1792: 1788: 1784: 1744: 1720: 1676: 1672: 1668: 1632: 1615:Writtenright 1612: 1608: 1590: 1549: 1526: 1506: 1500: 1450: 1341: 1337: 1332:categories: 1329: 1317: 1304: 1236: 1204:Gerry Ashton 1201: 1186: 1160: 1144:spirit level 1124: 1122: 1108: 1094: 1075:59.94.47.127 1062: 1048: 1016: 998: 987:TWCAdirector 968: 958: 943:bg.wikipedia 940: 906: 903: 901:-Dr. Markel 900: 897: 894: 890: 887: 884: 866: 863:Thanxies!!!! 825: 821: 817: 806:Andy Mabbett 799: 785: 762: 743: 726: 715: 694: 679: 650: 613:Bravehearted 603: 584: 583: 580: 577: 571: 564: 560: 559: 459:warning. -- 446: 440: 417: 415: 395:Today's news 354:September 11 339: 292: 269: 265: 249: 222: 205: 201: 198:Page history 197: 185:My watchlist 184: 154: 124: 121: 118: 97: 53:Gerry Ashton 30: 2782:J JMesserly 2714:Roman Dates 2690:designed {{ 2646:J JMesserly 2623:J JMesserly 2576:accurately. 2508:J JMesserly 2100:Leap Second 2063:in article 1988:stellar day 1069:—Preceding 1023:—Preceding 918:Paul Markel 908:Paul Markel 904:Semper Fi 898:Thank you. 765:Talk:Number 706:article. — 588:Luna Santin 494:Luna Santin 461:Jim Douglas 422:Jim Douglas 374:Jim Douglas 229:Jim Douglas 225:you changed 176:Talk:Easter 157:Talk:Easter 78:Jim Douglas 57:Jim Douglas 37:Anno Domini 33:Anno Domini 2718:Calendrica 2571:start-date 2246:EdJohnston 2212:dougweller 2087:Lightmouse 1864:Common Era 1860:Common Era 1751:my sandbox 1537:found here 1338:convention 850:flu season 842:Censorinus 467:(contribs) 428:(contribs) 380:(contribs) 235:(contribs) 161:Tom Peters 84:(contribs) 63:(contribs) 41:Common Era 2828:Joe Kress 2722:Joe Kress 2692:JULIANDAY 2594:accuracy. 2540:Joe Kress 2485:Hordaland 2463:Joe Kress 2458:Uraniborg 2443:Hordaland 2400:Terry0051 2381:Joe Kress 2361:Terry0051 2340:Joe Kress 2325:Terry0051 2305:Terry0051 2226:Year zero 2171:Joe Kress 2162:Random832 2126:Joe Kress 2041:Joe Kress 2005:Joe Kress 1914:Joe Kress 1872:Joe Kress 1771:Joe Kress 1723:for now. 1707:Joe Kress 1673:Principle 1655:Joe Kress 1563:Joe Kress 1456:clarifyme 1427:ru:1990-е 1389:Joe Kress 1267:Joe Kress 1233:Leap Year 1219:Joe Kress 1148:Joe Kress 991:Joe Kress 937:Calendars 846:influenza 708:Joe Kress 638:Joe Kress 563:has been 539:Joe Kress 523:Joe Kress 478:Joe Kress 408:Joe Kress 346:talk page 325:Joe Kress 313:Joe Kress 210:Joe Kress 206:Save page 142:Joe Kress 111:Joe Kress 2536:ISO 8601 2231:Over at 1842:Pawyilee 1811:Pawyilee 1755:Pawyilee 1725:Pawyilee 1681:Pawyilee 1639:Pawyilee 1330:parallel 1326:WP:CFORK 1322:nonsense 1083:contribs 1071:unsigned 1037:contribs 1029:Horology 1025:unsigned 1019:Horology 926:contribs 914:unsigned 848:link to 621:contribs 609:unsigned 295:Karlhahn 194:computus 2688:Verdy p 1837:English 1802:started 1531:at the 1301:Decades 965:WP:NPOV 746:Delta T 739:Delta T 565:granted 487:Unblock 266:incipit 204:, then 174:did on 47:? The 2424:Kepler 2206:Rktect 2193:Rktect 2152:(talk) 1383:, the 1375:, and 1342:source 1310:decade 1263:how-to 869:Wu Mei 511:Essjay 447:really 138:Easter 2686:When 2557:coord 2241:WP:3O 2107:Canol 2069:Dbiel 1996:exact 1934:Earth 1870:). — 1582:cjllw 1541:cjllw 1509:. -- 1507:fower 1503:query 1423:1990s 1385:1990s 1381:1920s 1198:IBMPC 1130:Zsero 774:Jan Z 719:cjllw 687:cjllw 666:arris 172:Myzou 76:. -- 16:< 2832:talk 2786:talk 2726:talk 2650:talk 2627:talk 2544:talk 2512:talk 2489:talk 2481:much 2467:talk 2447:talk 2404:talk 2385:talk 2365:talk 2344:talk 2329:talk 2309:talk 2284:talk 2280:NJGW 2266:talk 2262:NJGW 2250:talk 2216:talk 2197:talk 2175:talk 2169:. — 2130:talk 2124:. — 2111:talk 2091:talk 2045:talk 2025:talk 2009:talk 2000:time 1971:talk 1962:vary 1952:and 1918:talk 1912:. — 1899:talk 1876:talk 1846:talk 1815:talk 1789:that 1775:talk 1759:talk 1729:talk 1711:talk 1705:. — 1685:talk 1659:talk 1643:talk 1619:talk 1592:TALK 1567:talk 1551:TALK 1515:Talk 1487:talk 1483:Smjg 1471:talk 1467:Smjg 1435:talk 1393:talk 1350:talk 1324:and 1318:nine 1289:talk 1285:Ysth 1271:talk 1244:talk 1240:Ysth 1223:talk 1208:talk 1161:See 1111:Tony 1079:talk 1033:talk 1005:Karl 973:Karl 922:talk 727:TALK 695:TALK 636:. — 617:talk 572:very 454:agf1 418:will 406:. — 404:here 400:here 366:this 358:2001 350:2001 342:once 275:and 140:. — 39:and 2426:'s 2020:RJH 1966:RJH 1793:not 1749:in 1701:or 1167:Lar 1125:was 1105:Sry 947:5ko 389:An 362:TSA 2834:) 2788:) 2728:) 2673:ΔT 2652:) 2629:) 2616:) 2573:}} 2569:{{ 2559:}} 2555:{{ 2546:) 2514:) 2491:) 2469:) 2449:) 2431:." 2406:) 2387:) 2367:) 2346:) 2331:) 2311:) 2286:) 2268:) 2252:) 2218:) 2199:) 2177:) 2132:) 2113:) 2093:) 2047:) 2028:) 2011:) 1974:) 1940:: 1920:) 1901:) 1893:-- 1878:) 1848:) 1817:) 1777:) 1761:) 1731:) 1713:) 1687:) 1679:. 1661:) 1645:) 1637:? 1621:) 1580:-- 1569:) 1513:| 1489:) 1473:) 1459:}} 1453:{{ 1437:) 1395:) 1371:, 1367:, 1363:, 1352:) 1314:0s 1291:) 1273:) 1246:) 1225:) 1210:) 1169:: 1081:• 1035:• 1003:. 928:) 924:• 804:. 722:| 690:| 623:) 619:• 457:}} 451:{{ 125:-- 2830:( 2784:( 2724:( 2648:( 2625:( 2542:( 2510:( 2487:( 2465:( 2445:( 2402:( 2383:( 2363:( 2342:( 2327:( 2307:( 2282:( 2264:( 2248:( 2214:( 2195:( 2173:( 2128:( 2109:( 2089:( 2043:( 2022:( 2007:( 1968:( 1916:( 1897:( 1874:( 1844:( 1813:( 1773:( 1757:( 1727:( 1709:( 1683:( 1657:( 1641:( 1617:( 1586:ʘ 1565:( 1545:ʘ 1485:( 1469:( 1433:( 1391:( 1348:( 1312:( 1287:( 1269:( 1242:( 1221:( 1206:( 1175:c 1173:/ 1171:t 1077:( 1031:( 932:. 920:( 663:H 659:B 654:S 627:. 615:(

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Index