Hi all, Below is a list of the latest obituary collections added online. The complete list can be found at http://www.genealogybuff.com/obituary_collections.htm To search any of these collections, be sure to use the search box that has the watermark inside the search field and the name of the county or state on the search button. ALABAMA - Morgan County Obituary Collection http://www.genealogybuff.com/al/morgan/webbbs_config.pl ALABAMA - Tuscaloosa County Obituary Collection http://www.genealogybuff.com/al/tuscaloosa/webbbs_config.pl ARIZONA - Statewide Obituary Collection http://www.genealogybuff.com/az/state/webbbs_config.pl ARKANSAS - Statewide Obituary Collection http://www.genealogybuff.com/ar/state/webbbs_config.pl ARKANSAS - Yell County Obituary Collection http://www.genealogybuff.com/ar/yell/webbbs_config.pl CALIFORNIA - Alameda County Obituary Collection http://www.genealogybuff.com/ca/alameda/webbbs_config.pl CALIFORNIA - San Diego County Obituary Collection http://www.genealogybuff.com/ca/sandiego/webbbs_config.pl GEORGIA - Statewide Obituary Collection http://www.genealogybuff.com/ga/state/webbbs_config.pl OKLAHOMA - Statewide Obituary Collection http://www.genealogybuff.com/ok/state/webbbs_config.pl SOUTH CAROLINA - Statewide Obituary Collection http://www.genealogybuff.com/sc/state/webbbs_config.pl VIRGINIA - Statewide Obituary Collection http://www.genealogybuff.com/va/state/webbbs_config.pl Hope this helps. Bill

Shorthand Points of Reference: Countries/Areas Worldwide In the continuing process of upgrades, the following are noted as important: (1) OneSource Comprehensive Directory Index http://www.academic-genealogy.com/onesource.htm has instructions for use of country - nation area index A to Z at: Ancestor Roots Information. http://www.academic-genealogy.com/ancestorrootsinformationdatabases.htm This reference has been updated completely. http://goo.gl/Wn8Am Evaluation format for sample country is duplicated for every other world country. Every national site in the world, with information related to their civil records, culture, genealogy, libraries, museums, printed - country family history outlines, country studies groups, individual identity information, indigenous peoples, etc., is now online here.* The horizontal use of internal links combines all major area data sources together without the necessity to vertically return back to the top of the pages for connective research. . . . FIFTH LINK goes to Map from World Atlas; Etc., with famous natives, fast facts, flags, land statistics, landforms, latitude - longitude, links, maps, symbols, time, timeline, travel information and weather; as presented. EXAMPLE: [SAME FORMAT FOR ANY COUNTRY] EIGHTH LINK SUB SET goes to Culture of [Italy Country Insight]; Italy taken from: globalEDGE| Country Insights by globalEDGE Business Knowledge; (or else, the [Country / Geographical Location] is taken from a carefully selected country / geographical location resource.) This is then followed by the Topic Outline of Area from Wikipedia®, in combination with listing of higher education studies sites, libraries, depositories, or other related country culture links, as shown: . . . (2) Reference and Homework Help http://www.academic-genealogy.com/referencehomeworkhelp.htm Provides under Reference Help http://goo.gl/kYA49 * Credo Reference: Credo Reference Smart research starts here. Easy access to trusted content from over 70 of the world's leading academic publishers. - Citable Information At Your Fingertips - Start Research With Topic Pages: Examples - Credo Reference: Blog Free access to Credo available through any subscribing library. (3) Regional Genealogy and Local History Research http://www.academic-genealogy.com/regionalgenealogy.htm Presents direct access to country links at IndexY (Yahoo!); or, where available, country GlobalTower Resource Directory, giving full access to Britannica Online Encyclopedia references. (4) Schools - Colleges - Universities http://www.academic-genealogy.com/schoolscollegesuniversities.htm Immediately lists Universities, with links to websites of Ministries of Education and other national agencies or institutions responsible for education in each individual country, where available via UNESCO. Countries by population can be individually compared with Zip (BYU), http://lib.byu.edu/sites/familyhistory/education/ or Genealogy Links: Education in Selected Country - Directory: Information & Search. http://goo.gl/zosub Respectfully yours, V. Chris & Tom Tinney, Sr. http://academic-genealogy.com/

Hi friends are you interested in dating come and find sexy girls for ur secret sex visit all 5 companies we give ur partner within hour http://123maza.com/65/boat345/ FREE REGISTRATION

Neil Bell wrote: > Still no word about version 8 - just silence. I used to wonder - > "will it be available this month?" Then is was "will it be available > this year?" Now I am wondering "Will it be available this decade?" > > So will TMG still be making software at all ? I don't use TMG and I'm not even sure I like it, but Bob has never taken the editorial approach (you know the one: I don't want it good, I want it NOW). Most users prefer that over the necessity of d/l and installing and tweaking frequent bug-fixes, updates, and so on. And, down at the bottom line, your mother didn't get rid of you just because you were a couple years old, I doubt you buy a new car every year ... and so on. Cheryl

Still no word about version 8 - just silence. I used to wonder - "will it be available this month?" Then is was "will it be available this year?" Now I am wondering "Will it be available this decade?" So will TMG still be making software at all ? Neil Bell

Musings on Research Objectives: Family History, Genealogy, Internet & Library Collections http://goo.gl/lAg4U Archives and Knowledge Management: Scholarly online resource evidence and records for use by genealogists and family historians, now includes the UK Web Archive, with its Links to Other Web Archives Worldwide; also data concerning Web Archiving and a List of Web Archiving Initiatives currently online or in progress throughout the world. http://www.academic-genealogy.com/archives.htm

Musings on Research Objectives: Family History - Genealogy - Internet - Library Collections http://goo.gl/lAg4U

On 03-29-2011 18:07, Dr. Brian Leverich wrote: > Moreover, maybe I have a twisted sense of humor, but I think > it's funny as heck having the coat-of-arms-crap advertisement > on the largest index to genealogical resources on the Web. It's not funny to me because I am aware of how many people are still falling for it. -- Wes Groleau He looked upShe smiled http://Ideas.Lang-Learn.us/BlindDog?itemid=3915

From: "Brian M. Scott" <[email protected]> Merely rather pointless. That you can save a few keystrokes on a pocket calculator may be mildly interesting from the standpoint of algorithm design, but it has virtually no practical significance. One who rarely needs such calculations will find any halfway decent algorithm adequate, not to mention any of the multitude of online calculators; anyone who has frequent need of them obviously ought to program a calculator or use an existing app to reduce the keystrokes to mere data entry. (On the rare occasions when I need to make such calculations, I prefer to use Conway's algorithm and do it in my head.) Well...both the content as well as my intent were beneath you, eh? My posts here made reference to those, as someone here did make an effort to follow, of mine on other groups. They include routines in 68000 assembler or superBASIC as a take-off on Hans' method for calculators on sci.math. My 68000 routine was for a series of calculators by TI, who deceptively claim to have invented the shirt-pocket calculator, whereas the BASIC routine was for computers made by its true inventor. Even if you didn't have the decency to follow the links, it should also be obvious to such a numerate mind, that the Julian version of Hans' method allows for more flexible & efficient routines ideal for low-end devices; but lacking enough sense to know what's senseless, you didn't see any of the satire, e.g. my reference to real genealogists, which plays on another meaning of real, as in real tennis, to sarcastically refer to Laurence Gardner. He has AD 33's spring equinox being 14 Nisan & 20 March, which cannot be until the Jewish calendar's creation 300 years later. Were he scrupulous, he'd have confirmed his date with those without his particular bias, esp. the Samaritans. Instead of the Jewish, they keep the Hebrew calendar, as did the Chief Priests under the Herodians--Malthace, Antipas' & Archelaus' mother, was a Samaritan wife of Herod the Great. But it would certainly contradict Gardner's date, and in turn the resulting date for the Crucifixion, if not the wrong day used by The Church that makes Sadducee Priests look at best like hypocrites. So he instead confirms his date with charlatans like Barbara Thiering who misrepresents the significance of the Essenes' forerunner to the Jewish calendar in the Dead Sea Scrolls: http://www.peshertechnique.infinitesoulutions.com/Finding_the_pesher/Chronology.html#Julian_dates But at least he refrains from defending the indefensible on genealogy news groups, and has a reason for ignoring the correct calendar when conducting genealogical research: his own crusade that the Crucifixion occurred on an impossible date. Nonetheless, you & others here are in good company--Apple Computers who have no scruples about being unscrupulous when calling the Jewish calendar "Hebrew" in MacOS>System Preferences>International>Formats. One might as well call the Gregorian calendar "Julian." So...the purported advantage of saving key-clicks is April Fools' bait. The obvious advantage is flexibility: it can be combined with Conway's and Deal's methods such that they enhance each other, e.g. for an Old-Style Doomsday sliding calendar; alternatively, the modification for Old-Style dates can also be extended in a consistent manner to cover dates on the Anglican calendar or even the Byzantine as mentioned in my previous post here in this thread. In comparison, existing applications are barely "halfway decent" for errors or omissions in coverage as blatant as using the Jewish calendar for the Hebrew. Otherwise I was taking the mickey out of Hans for his minimalism that lobotomises his basic method (by using the least of all calculators, applying it just to this century & last and thereby only to the Gregorian calendar), and out of others for their dogmatism in adhering to their m. o. by barring any nonconformity that might help those encountering calendrical divergence, from astronomers to astrologers. The Old-Style Doomsday sliding calendar was therefore improvised out of said methods that paint themselves into a corner.

[Note: This revision using 0=Sun combines a new parameter YLDM with a flag of 94 for months placed after December as in Old Style and Byzantine calendars. Please post comments, if any, via Usenet. Thanks.] HOW TO CALCULATE THE DAY OF THE WEEK FOR JULIAN DATES AS OF 1.iii.IV - via Hans' E-Z Wondrous 2-Fold 3-Step 4-Function Calculator Method - This is a less involved method to calculate the day of the week for dates on Julian calendars from 1.iii.IV and as far into the future as workable using standard four-function calculators and certain mobile phones via a generalised formula requiring fewer key-clicks than any previous method not relying on tables. Given: Day.Month.Year as a Date on a Julian Calendar (starting with 01.march.0004 as the earliest Date to be converted); & YLLD as the 'Year in which the Last Leap Day occurred' before the given Date for calendar years beginning on or before January 1st (starting at Year IV, so that YLLD is a positive multiple of 4); or Y2MB as the 'Year 2 Months Before' a given (historical Julian) Date, whereby YLLD/4 = Integer(Y2MB/4); one can convert the given Date into a day of the week after completing the 3 steps below using a standard four-function calculator with less than 3 dozen key-clicks (or at most 3 dozen using RPN & algebraic ones). STEP 1. Calculate the given Date's MonthIndex: Month * 2.56 + 93 and then drop the fraction, and the hundreds digit, if any, e.g. 123.72 becomes 23, to get an integer less than 100. STEP 2. Apply the generalised formula for converting the Date: (YLLD/4 + Year + MonthIndex + Day) / 7 2.a. Calculate YLLD/4: Divide Y2MB by 4 If the result has a fraction, re-enter just the integer portion. (This in effect is identical to applying Hans' older formula of 1990's vintage. If one knows YLLD, one can divide that instead.) 2.b. Continue with the remainder of the formula. STEP 3. Apply Hans' keypad mapping: Take the first digit after the decimal point (if none, use 0) and map that to a day using the following patterns: +-----+-----+-----+ +-----+-----+-----+ | Fri | Sat | | | 1 | 2 | 3 | | 7 | 8 | 9 | | Mon | Tue | | +-----+-----+-----+ +-----+-----+-----+ | Wed | Thu | | | 4 | 5 | 6 | | 4 | 5 | 6 | | Wed | Thu | | +-----+-----+-----+ +-----+-----+-----+ | Mon | Tue | | | 7 | 8 | 9 | | 1 | 2 | 3 | | Fri | Sat | | +-----+-----+-----+ +-----+-----+-----+ | Sun | | 0 | | 0 | | Sun | +-----+ +-----+ (This is equivalent to assigning days to remainders of divisions by 7 as for: Sun=0 Mon=1 Tue=2 Wed=3 Thu=4 Fri=5 Sat=6.) The use of a value of 4 for YLLD in Hans' Method remains valid, even if IV A.D. was not a leap year as claimed by some historians, if it is used just for dates after February IV A.D. whereby the value of 4 for YLLD is a boundary condition for valid conversions on later (historical Julian) dates. If IV A.D. is a leap year, Hans' Method is historically correct for Julian dates as far back as 1.iii.N by allowing, as do astronomers, a value of 0 for YLLD, as well as Julian year 'N'--the improvised Roman numeral for 0. EXAMPLE N. January 30th, 1649 Y2MB = 1648 2.56 + 93 = 95.56 (MonthIndex = 95) 1648 / 4 = 412 (no need to re-enter) + 1649 + 95 + 30 Divide by 7 = 312.285714... first decimal = 2 Day of Week = Tue EXAMPLE I. February 8th, 1587 Y2MB = 1586 2 * 2.56 + 93 = 98.12 (MonthIndex = 98) 1586 / 4 = 396.5 396 + 1587 + 98 + 8 Divide by 7 = 298.428571... first decimal = 4 Day of Week = Wed EXAMPLE II. June 15th, 1215 Y2MB = 1215 6 * 2.56 + 93 = 108.36 (MonthIndex = 8) 1215 / 4 = 303.75 303 + 1215 + 8 + 15 Divide by 7 = 220.142857... first decimal = 1 Day of Week = Mon EXAMPLE III. October 13th, 1307 Y2MB = 1307 10 * 2.56 + 93 = 118.6 (MonthIndex = 18) 1307 / 4 = 326.75 326 + 1307 + 18 + 13 Divide by 7 = 237.714285... first decimal = 7 Day of Week = Fri EXAMPLE IV. December 12th, 287 Y2MB = 287 12 * 2.56 + 93 = 123.72 (MonthIndex = 23) 287 / 4 = 71.75 71 + 287 + 23 + 12 Divide by 7 = 56.142857... first decimal = 1 Day of Week = Mon Q. What significant events occurred on the dates above? (With just 2 modifications, Hans' method is adaptable to Old Style years too, such that it still is easy to do with standard calculators, if not mentally, for the recent English usage of 'Old Style' as below. For the usage of 'Old Style' applicable to Anglo-Saxon times: dates before January 1st in such a calendar year must use a flag of 92 in Step 1; and only YLLD is to be used in Step 2; both modifications likewise apply to the Anglican calendar year. Examples are left to the Reader as an exercise. The month-numbers remain defined in terms of the historical calendar in each case.) MODIFICATIONS FOR THE LATE OLD STYLE YEAR 1. Because of its initial overlap with the historical year, a flag of 93 is to apply till December 31st. From January 1st, a flag of 94 applies till the end of the Old Style year on March 24th (which similarly applies for a Byzantine year till its end on August 31st.) 2. YLLD & Y2MB are replaced by YLDM, 'Year on the Last Day of the Month'. EXAMPLE V. January 30th, 1648 YLDM = 1648 2.56 + 94 = 96.56 (MonthIndex = 96) 1648 / 4 = 412 (no need to re-enter) + 1648 + 96 + 30 Divide by 7 = 312.285714... first decimal = 2 Day of Week = Tue EXAMPLE VI. February 8th, 1586 YLDM = 1586 2 * 2.56 + 94 = 99.12 (MonthIndex = 99) 1586 / 4 = 396.5 396 + 1586 + 99 + 8 Divide by 7 = 298.428571... first decimal = 4 Day of Week = Wed EXAMPLE VII. March 15th, 1751 YLDM = 1752 3 * 2.56 + 94 = 101.68 (MonthIndex = 1) 1752 / 4 = 438 (no need to re-enter) + 1751 + 1 + 15 Divide by 7 = 315. first decimal = 0 Day of Week = Sun EXAMPLE IIX. March 25th, 1752 YLDM = 1752 3 * 2.56 + 93 = 100.68 (MonthIndex = 0) 1752 / 4 = 438 (no need to re-enter) + 1752 (+ 0) + 25 Divide by 7 = 316.428571... first decimal = 7 Day of Week = Wed And just when you thought that all's well, there lurks... AN OLD STYLE DOOMSDAY SLIDING CALENDAR a..mJ.o..aJ.sD.jF.mN.a..mJ.o..aJ.sD.jF u..aA.c..pU.eE.uE.aO.u..aA.c..pU.eE.uE g..yN.t..rL.pC.nB.rV.g..yN.t..rL.pC.nB su.mo.tu.we.th.fr.sa ......................1..2..3..4..5..6 .1..2..3..4..5..6..7..8..9.10.11.12.13 .8..9.10.11.12.13.14.15.16.17.18.19.20 15.16.17.18.19.20.21.22.23.24.25.26.27 22.23.24.25.26.27.28.29.30.31 29.30.31 This chart will give calendars that are the same as for mar-DEC of the historical Year, but the following JAN & FEB as in the Old Style year. Each month appears vertically in lower case above a column of dates, except when in pairs, in which case the later month is ALL CAPS. The column of dates underneath are those of all corresponding "Doomsdates" --defined as all dates for which MonthIndex + Day is divisible by 7. Thus, the Old Style February 13th is a Doomsdate. "Doomsday" is defined as the weekday on which Doomsdates occur in said span of months. Because MonthIndex + Day is divisible by 7, one may simplify Step 2 by omitting both terms from that calculation, and so find the Doomsday, as in Step A below. This Doomsday is used in Steps B & C to display calendars just by sliding the row of weekdays--by adding or deleting spaces to the left of 'su'. Copy & paste the chart into a text-editor with a monospaced font, e.g. Courier, and do as follows: A. Calculate Doomsday: For the given Year in the Old Style calendar, calculate the weekday of its Doomsdates using (YLLD/4 + Year) / 7, and then applying Step 3's keypad mapping. B. Display the calendar for March & November: Slide the row of weekdays so that the weekday of Doomsday rests over 28 to show the calendar for the March that begins the Year with Lady Day. One has as well the calendar for the following November. C. Display calendars for the other 10 months: for any month other than March or the following November: slide the row of weekdays to put Doomsday under the month to be displayed. D. Display calendars for months in Century 21: if you're patient and can wait until 1.iii.MMC, the foregoing will also work for the remainder of that Century in the Gregorian calendar. (Why?) Q. How would you modify Step A for any earlier Gregorian Century? (There's more than one right answer.) -- REFERENCES: http://oz.ccnet.us/dayofweek/ http://www.merlyn.demon.co.uk/zel-like.htm#Keith http://www.angelfire.com/my/zelime/calendarslide.html http://en.wikipedia.org/wiki/Doomsday.rule#Overview.of.all.Doomsdays

[Note: This revision using 0=Sun combines a new parameter YLDM with a flag of 94 for months placed after December as in Old Style, Byzantine & Anglican calendars. Please post comments, if any, via Usenet. Thanks.] HOW TO CALCULATE THE DAY OF THE WEEK FOR JULIAN DATES AS OF 1.iii.IV - via Hans' E-Z Wondrous 2-Fold 3-Step 4-Function Calculator Method - This is a less involved method to calculate the day of the week for dates on Julian calendars from 1.iii.IV and as far into the future as workable using standard four-function calculators and certain mobile phones via a generalised formula requiring fewer key-clicks than any previous method not relying on tables. Given: Day.Month.Year as a Date on a Julian Calendar (starting with 01.march.0004 as the earliest Date to be converted); & YLLD as the 'Year in which the Last Leap Day occurred' before the given Date for calendar years beginning on or before January 1st (starting at Year IV, so that YLLD is a positive multiple of 4); or Y2MB as the 'Year 2 Months Before' a given (historical Julian) Date, whereby YLLD/4 = Integer(Y2MB/4); one can convert the given Date into a day of the week after completing the 3 steps below using a standard four-function calculator with less than 3 dozen key-clicks (or at most 3 dozen using RPN & algebraic ones). STEP 1. Calculate the given Date's MonthIndex: Month * 2.56 + 93 and then drop the fraction, and the hundreds digit, if any, e.g. 123.72 becomes 23, to get an integer less than 100. STEP 2. Apply the generalised formula for converting the Date: (YLLD/4 + Year + MonthIndex + Day) / 7 2.a. Calculate YLLD/4: Divide Y2MB by 4 If the result has a fraction, re-enter just the integer portion. (This in effect is identical to applying Hans' older formula of 1990's vintage. If one knows YLLD, one can divide that instead.) 2.b. Continue with the remainder of the formula. STEP 3. Apply Hans' keypad mapping: Take the first digit after the decimal point (if none, use 0) and map that to a day using the following patterns: +-----+-----+-----+ +-----+-----+-----+ | Fri | Sat | | | 1 | 2 | 3 | | 7 | 8 | 9 | | Mon | Tue | | +-----+-----+-----+ +-----+-----+-----+ | Wed | Thu | | | 4 | 5 | 6 | | 4 | 5 | 6 | | Wed | Thu | | +-----+-----+-----+ +-----+-----+-----+ | Mon | Tue | | | 7 | 8 | 9 | | 1 | 2 | 3 | | Fri | Sat | | +-----+-----+-----+ +-----+-----+-----+ | Sun | | 0 | | 0 | | Sun | +-----+ +-----+ (This is equivalent to assigning days to remainders of divisions by 7 as for: Sun=0 Mon=1 Tue=2 Wed=3 Thu=4 Fri=5 Sat=6.) The use of a value of 4 for YLLD in Hans' Method remains valid, even if IV A.D. was not a leap year as claimed by some historians, if it is used just for dates after February IV A.D. whereby the value of 4 for YLLD is a boundary condition for valid conversions on later (historical Julian) dates. If IV A.D. is a leap year, Hans' Method is historically correct for Julian dates as far back as 1.iii.N by allowing, as do astronomers, a value of 0 for YLLD, as well as Julian year 'N'--the improvised Roman numeral for 0. EXAMPLE N. January 30th, 1649 Y2MB = 1648 2.56 + 93 = 95.56 (MonthIndex = 95) 1648 / 4 = 412 (no need to re-enter) + 1649 + 95 + 30 Divide by 7 = 312.285714... first decimal = 2 Day of Week = Tue EXAMPLE I. February 8th, 1587 Y2MB = 1586 2 * 2.56 + 93 = 98.12 (MonthIndex = 98) 1586 / 4 = 396.5 396 + 1587 + 98 + 8 Divide by 7 = 298.428571... first decimal = 4 Day of Week = Wed EXAMPLE II. June 15th, 1215 Y2MB = 1215 6 * 2.56 + 93 = 108.36 (MonthIndex = 8) 1215 / 4 = 303.75 303 + 1215 + 8 + 15 Divide by 7 = 220.142857... first decimal = 1 Day of Week = Mon EXAMPLE III. October 13th, 1307 Y2MB = 1307 10 * 2.56 + 93 = 118.6 (MonthIndex = 18) 1307 / 4 = 326.75 326 + 1307 + 18 + 13 Divide by 7 = 237.714285... first decimal = 7 Day of Week = Fri EXAMPLE IV. December 12th, 287 Y2MB = 287 12 * 2.56 + 93 = 123.72 (MonthIndex = 23) 287 / 4 = 71.75 71 + 287 + 23 + 12 Divide by 7 = 56.142857... first decimal = 1 Day of Week = Mon Q. What significant events occurred on the dates above? (With just 2 modifications, Hans' method is adaptable to Old Style years too, such that it still is easy to do with standard calculators, if not mentally, for the recent English usage of 'Old Style' as below. For the usage of 'Old Style' applicable to Anglo-Saxon times: dates before January 1st in such a calendar year must use a flag of 92 in Step 1; and only YLLD is to be used in Step 2; both modifications likewise apply to the Anglican calendar year. Examples are left to the Reader as an exercise. The month-numbers remain defined in terms of the historical calendar in each case.) MODIFICATIONS FOR THE LATE OLD STYLE YEAR 1. Because of its initial overlap with the historical year, a flag of 93 is to apply till December 31st. From January 1st, a flag of 94 applies till the end of the Old Style year on March 24th (which similarly applies for a Byzantine year till its end on August 31st.) 2. YLLD & Y2MB are replaced by YLDM, 'Year on the Last Day of the Month'. EXAMPLE V. January 30th, 1648 YLDM = 1648 2.56 + 94 = 96.56 (MonthIndex = 96) 1648 / 4 = 412 (no need to re-enter) + 1648 + 96 + 30 Divide by 7 = 312.285714... first decimal = 2 Day of Week = Tue EXAMPLE VI. February 8th, 1586 YLDM = 1586 2 * 2.56 + 94 = 99.12 (MonthIndex = 99) 1586 / 4 = 396.5 396 + 1586 + 99 + 8 Divide by 7 = 298.428571... first decimal = 4 Day of Week = Wed EXAMPLE VII. March 15th, 1751 YLDM = 1752 3 * 2.56 + 94 = 101.68 (MonthIndex = 1) 1752 / 4 = 438 (no need to re-enter) + 1751 + 1 + 15 Divide by 7 = 315. first decimal = 0 Day of Week = Sun EXAMPLE IIX. March 25th, 1752 YLDM = 1752 3 * 2.56 + 93 = 100.68 (MonthIndex = 0) 1752 / 4 = 438 (no need to re-enter) + 1752 (+ 0) + 25 Divide by 7 = 316.428571... first decimal = 7 Day of Week = Wed And just when you thought that all's well, there lurks... AN OLD STYLE DOOMSDAY SLIDING CALENDAR a..mJ.o..aJ.sD.jF.mN.a..mJ.o..aJ.sD.jF u..aA.c..pU.eE.uE.aO.u..aA.c..pU.eE.uE g..yN.t..rL.pC.nB.rV.g..yN.t..rL.pC.nB su.mo.tu.we.th.fr.sa ......................1..2..3..4..5..6 .1..2..3..4..5..6..7..8..9.10.11.12.13 .8..9.10.11.12.13.14.15.16.17.18.19.20 15.16.17.18.19.20.21.22.23.24.25.26.27 22.23.24.25.26.27.28.29.30.31 29.30.31 This chart will give calendars that are the same as for mar-DEC of the historical Year, but the following JAN & FEB as in the Old Style year. Each month appears vertically in lower case above a column of dates, except when in pairs, in which case the later month is ALL CAPS. The column of dates underneath are those of all corresponding "Doomsdates" --defined as all dates for which MonthIndex + Day is divisible by 7. Thus, the Old Style February 13th is a Doomsdate. "Doomsday" is defined as the weekday on which Doomsdates occur in said span of months. Because MonthIndex + Day is divisible by 7, one may simplify Step 2 by omitting both terms from that calculation, and so find the Doomsday, as in Step A below. This Doomsday is used in Steps B & C to display calendars just by sliding the row of weekdays--by adding or deleting spaces to the left of 'su'. Copy & paste the chart into a text-editor with a monospaced font, e.g. Courier, and do as follows: A. Calculate Doomsday: For the given Year in the Old Style calendar, calculate the weekday of its Doomsdates using (YLLD/4 + Year) / 7, and then applying Step 3's keypad mapping. B. Display the calendar for March & November: Slide the row of weekdays so that the weekday of Doomsday rests over 28 to show the calendar for the March that begins the Year with Lady Day. One has as well the calendar for the following November. C. Display calendars for the other 10 months: for any month other than March or the following November: slide the row of weekdays to put Doomsday under the month to be displayed. D. Display calendars for months in Century 21: if you're patient and can wait until 1.iii.MMC, the foregoing will also work for the remainder of that Century in the Gregorian calendar. (Why?) Q. How would you modify Step A for any earlier Gregorian Century? (There's more than one right answer.) -- REFERENCES: http://oz.ccnet.us/dayofweek/ http://www.merlyn.demon.co.uk/zel-like.htm#Keith http://www.angelfire.com/my/zelime/calendarslide.html http://en.wikipedia.org/wiki/Doomsday.rule#Overview.of.all.Doomsdays

>>>>>>>> D. Stussy wrote: >>>>>>>>> "Ian Goddard" <[email protected]> wrote: >>>>>>>>>> I'm working on a program to help capture data from websites such >>>>>>>>>> as the new Familysearch %>< > > None - because it's not on that site. > > D. Stussy :( -- Ian The Hotmail address is my spam-bin. Real mail address is iang at austonley org uk Ian Goddard <[email protected]>

Does anyone use Microsoft One Note for genealogical research? How useful do you find it? Any tips? -- Steve Hayes from Tshwane, South Africa Web: http://hayesfam.bravehost.com/stevesig.htm Blog: http://methodius.blogspot.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk

> >>>>>> D. Stussy wrote: > >>>>>>> "Ian Goddard" <[email protected]> wrote: > >>>>>>>> I'm working on a program to help capture data from websites such > >>>>>>>> as the new Familysearch into a format which can be imported into > >>>>>>>> existing genealogy software. This was prompted by ... > >>>>>> I think, looking back at my OP "from there" was ambiguous. I meant > >>>>>> from the new site which generates text such as: > >>>>>> > >>>>>> "Ian Goddard" <[email protected]> > >>>>> OK, if you have only a specific website in mind and not a general > >>>>> parser (as implied by your OP), that's different. However, you did > >>>>> say "websites" (plural) and only suggested one possible expected > >>>>> format. > >>>>> > >>>>> D. Stussy > >>>> It would work with any site which provides name/value pairs with a > >>>> colon as the separator - and that could easily be made configurable. > >>>> In fact Ancestry also fits that bill. > >>>> > >>>> "Ian Goddard" <[email protected]> > >>> Including those which have source footnotes in the value field? > >> Example? > >> > >> "Ian Goddard" <[email protected]> > > > > Previously given in message with MID > > <[email protected]> > > > > D. Stussy > > You posted a few bits of HTML. What search terms do I have to put > into > https://www.familysearch.org/ > to find it? > > "Ian Goddard" <[email protected]> None - because it's not on that site.

On 2011-03-22, Wes Groleau <[email protected]> wrote: > On 03-21-2011 23:55, Denis Beauregard wrote: > > > As for the "new" engine, I think linkpendium has achieve better > > results if you look for US data. mocavo looks like a new player > > I am personally not impresed with Linkpendium. Most surnames offer > high on the page a pointer to the sort of crap that Halberd's used to > provide. Thanks, Denis. And c'mon, Wes, develop a sense of humor and cut LP a little slack. Something has to pay for the show. Turns out there are actually people (this includes me) who are perfectly aware of the whole coat-of-arms-crap thing who nonetheless think having a coffee cup with my surname and a pretty picture on it is pretty cool. It's about the only cup I can leave in the drying rack in the coffee room without worrying about somebody else walking off with it. ;-) Moreover, maybe I have a twisted sense of humor, but I think it's funny as heck having the coat-of-arms-crap advertisement on the largest index to genealogical resources on the Web. Cheers, B. -- Dr. Brian Leverich Co-moderator, soc.genealogy.methods/GENMTD-L Co-Founder, RootsWeb and Linkpendium http://www.linkpendium.com/ P.O. Box 6831, Frazier Park, CA 93222-6831 [email protected]

>>>>>> D. Stussy wrote: >>>>>>> "Ian Goddard" <[email protected]> wrote: >>>>>>>> I'm working on a program to help capture data from websites such >>>>>>>> as the new Familysearch into a format which can be imported into >>>>>>>> existing genealogy software. This was prompted by ... >>>>>> I think, looking back at my OP "from there" was ambiguous. I meant >>>>>> from the new site which generates text such as: >>>>>> >>>>>> "Ian Goddard" <[email protected]> >>>>> OK, if you have only a specific website in mind and not a general >>>>> parser (as implied by your OP), that's different. However, you did >>>>> say "websites" (plural) and only suggested one possible expected >>>>> format. >>>>> >>>>> D. Stussy >>>> It would work with any site which provides name/value pairs with a >>>> colon as the separator - and that could easily be made configurable. >>>> In fact Ancestry also fits that bill. >>>> >>>> "Ian Goddard" <[email protected]> >>> Including those which have source footnotes in the value field? >> Example? >> >> "Ian Goddard" <[email protected]> > > > Previously given in message with MID > <[email protected]> > > D. Stussy You posted a few bits of HTML. What search terms do I have to put into https://www.familysearch.org/ to find it? -- Ian The Hotmail address is my spam-bin. Real mail address is iang at austonley org uk Ian Goddard <[email protected]>

On 29-Mar-2011 9:51 am, Ian Goddard wrote: > Jennifer Mathews Land wrote: >> No open-ended questions allowed for this project per my committee, > > I think you have a problem with your committee ;) > Maybe we could just allow the lady to work in her own way with the rules she has? Armchair criticism is hardly helpful. Paul

On 03-28-2011 20:56, Joe Makowiec wrote: > On 28 Mar 2011 in soc.genealogy.computing, Wes Groleau wrote: > >> No guarantee. I frequently get e-mails with a blurb at the bottom >> saying that if you want to reply you should go to the Rootsweb >> message board because the original poster may not be subscribed to >> the mailing list. > > That's boilerplate on Rootsweb message boards which are linked to mailing > lists on the same topic. The point is that it indicates e-mail/group gateways are not guaranteed bi-directional. -- Wes Groleau ¡Qué quiero realmente hacer es comer un perrito caliente! 私が実際にしたいと思う何をホットドッグを食べることである! http://Ideas.Lang-Learn.us/WWW?itemid=463

On 28 Mar 2011 in soc.genealogy.computing, Wes Groleau wrote: > No guarantee. I frequently get e-mails with a blurb at the bottom > saying that if you want to reply you should go to the Rootsweb > message board because the original poster may not be subscribed to > the mailing list. That's boilerplate on Rootsweb message boards which are linked to mailing lists on the same topic. -- Joe Makowiec http://makowiec.org/ Email: http://makowiec.org/contact/?Joe Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/

Jennifer Mathews Land wrote: > No open-ended questions allowed for this project per my committee, I think you have a problem with your committee ;) -- Ian The Hotmail address is my spam-bin. Real mail address is iang at austonley org uk