http://www.beholdgenealogy.com/forum/topic.php?id=132 The Behold User Forum Topic: Date validation - case sensitive http://www.beholdgenealogy.com/forum/ http://www.beholdgenealogy.com/blog/../beholddiscuss.gif Posts by Louis Kessler are Copyright 2000-2013 Louis Kessler, All Rights Reserved. Posts by others belong to the people who made them. en http://www.beholdgenealogy.com/forum/topic.php?id=132#post-402 Sat, 14 Apr 2012 16:15:10 GMT lkessler 402@http://www.beholdgenealogy.com/forum/ <p>Yes. All parts of the date. And that actually simplifies the work that Behold is doing.</p> <p>Personally, I think it is a great idea that the GEDCOM designers had. I should have discovered it earlier, but now that I have, I'll make use of it.</p> <p>Louis </p> Report a Problem http://www.beholdgenealogy.com/forum/topic.php?id=132#post-401 Sat, 14 Apr 2012 05:49:42 GMT brett 401@http://www.beholdgenealogy.com/forum/ <p>I assume this applies to BET, ABt etc in that they can be Bet, bet etc but compared upper or lower cased.</p> <p>Brett </p> Report a Problem http://www.beholdgenealogy.com/forum/topic.php?id=132#post-400 Sat, 14 Apr 2012 05:05:13 GMT lkessler 400@http://www.beholdgenealogy.com/forum/ <p>I think it simply means comparing for the purpose of interpreting its value. </p> <p>For a DATE value, I don't just compare the month-part to JAN, FEB, MAR,..., but I compare the uppercased value of the month-part to JAN, FEB, MAR,...</p> <p>For a TYPE value, I don't just compare the value to STILLBORN, but I compare the uppercased value of the value to STILLBORN.</p> <p>Louis </p> Report a Problem http://www.beholdgenealogy.com/forum/topic.php?id=132#post-399 Sat, 14 Apr 2012 04:45:30 GMT brett 399@http://www.beholdgenealogy.com/forum/ <p>So what does:</p> <p>values should be converted to all uppercase or all lowercase prior to comparing.</p> <p>actually mean?</p> <p>Is this when:</p> <p>1. comparing two dates within a program, such as to work out age or</p> <p>2. two supposedly identical GEDCOMs are compared for differences?</p> <p>If 1 above, how does a user know it is being done correctly by the user?</p> <p>If 2 above, how do we change a GEDCOM to same case in both files, without a large (and possibly manual) conversion.</p> <p>Brett </p> Report a Problem http://www.beholdgenealogy.com/forum/topic.php?id=132#post-398 Sat, 14 Apr 2012 04:07:49 GMT lkessler 398@http://www.beholdgenealogy.com/forum/ <p>Brett,</p> <p>See my blog post: <a href="http://www.beholdgenealogy.com/blog/?p=1087">How To Get A Developer To Fix A Bug</a>.</p> <p>No, Tamura's correct. The statement: "values should be converted to all uppercase or all lowercase prior to comparing" means that aPR and aPr should be both changed to APR (if uppercase is used for comparison) or to apr (if lowercase is used for comparison). Either way, aPR and aPr are equivalent to apr, APR and Apr. </p> <p>Louis </p> Report a Problem http://www.beholdgenealogy.com/forum/topic.php?id=132#post-397 Fri, 13 Apr 2012 23:02:39 GMT brett 397@http://www.beholdgenealogy.com/forum/ <p>Louis<br /> What do you make of Tamura Jone's comment (http://www.tamurajones.net/SiblingTortureTest.xhtml):</p> <p>None of these produced any errors or warnings, except Behold 1.04.<br /> Behold warned that the date 13 Apr 2012 is non-standard, and should be 13 APR 2012; the warning is that the abbrevation should be in ALL-CAPITALS.<br /> That is what the specification seems to say, but it does not;<br /> Chapter 2 of the GEDCOM 5.5.1 specification clearly states that All controlled line_value choices should be considered as case insensitive.,<br /> and that values should be converted to all uppercase or all lowercase prior to comparing.<br /> That means that Apr is fine, and that means that you may even write aPR or aPr</p> <p>It seems to me that all lower or all upper is correct but not mixed, as Tamura suggests.</p> <p>Brett </p> Report a Problem