<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Hi Robert<br><div><div>On 12 Mar 2009, at 02:53, Robert J Burns wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">Since you keep repeating the following example (by copy and paste?) I will mention that you have the year wrong in one place or the other (1731 and 1732). Dates only diverge by years between Julian and Gregorian many millions of years in the future or past or in BC if using eras that insert a zero year into the calendar. Since we're not even proposing the ability to change eras, we should assume the same era for both calendars (in any event that only applies to BCE/BC dates). </span></blockquote><br></div><div>I used that example since it's the Julian date example used in the TEI docs for the <date> element. Happy to give other examples but that one seems to nicely demonstrate historical dates. Just one correction. 1 January was not adopted as the start of a new year until 1752. Hence Jan, Feb, Mar 1731 in the Julian Calendar are Jan, Feb, Mar 1732 in the calendar we use now (Gregorian).</div><div><br></div><div>On the issue of the calendar attribute, I suggested that as it's already present in TEI-encoded documents. TEI is in wide use by archives and libraries to digitise historical text and the calendar attribute is familiar to TEI authors. Obviously, the semantic info captured by TEI is lost when documents are transformed to HTML in order for publication online. I thought it would be useful to retain this semantic information in HTML but, as I also said, it isn't essential,</div><div><br></div><div>Regards</div><div>Jim</div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div>Jim O'Donnell</div><div><a href="mailto:jim@eatyourgreens.org.uk">jim@eatyourgreens.org.uk</a></div><div><a href="http://eatyourgreens.org.uk">http://eatyourgreens.org.uk</a></div><div><a href="http://flickr.com/photos/eatyourgreens">http://flickr.com/photos/eatyourgreens</a></div><div><a href="http://twitter.com/pekingspring">http://twitter.com/pekingspring</a></div><div><br class="khtml-block-placeholder"></div><br class="Apple-interchange-newline"></span></span><br class="Apple-interchange-newline"> </div><br></body></html>