<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>The Behold User Forum Topic: ALL CAPS vs Capitalized</title>
<link>http://www.beholdgenealogy.com/forum/topic.php?id=48</link>
<description>The Behold User Forum Topic: ALL CAPS vs Capitalized</description>

		<image>
	<link>http://www.beholdgenealogy.com/forum/</link>
	<url>http://www.beholdgenealogy.com/blog/../beholddiscuss.gif</url>
	</image>
	<copyright>Posts by Louis Kessler are Copyright 2000-2013 Louis Kessler, All Rights Reserved.  Posts by others belong to the people who made them.</copyright>

<language>en</language>

<item>
<title>Report a Problem: ALL CAPS vs Capitalized</title>
<link>http://www.beholdgenealogy.com/forum/topic.php?id=48#post-170</link>
<pubDate>Fri, 12 May 2006 02:07:26 GMT</pubDate>
<dc:creator>lkessler</dc:creator>
<guid isPermaLink="false">170@http://www.beholdgenealogy.com/forum/</guid>
<description>This is excellent! You're doing some testing with multiple GEDCOMs that not too many other people have done. &#60;br&#62;&#60;br&#62;Up to now, I have purposely not changed the case of names. My thinking was that people would primarily be using Behold to find errors and inconsistencies in their own data, so that they could make corrections. They would want to see mistakes in their spelling and capitalization. &#60;br&#62;&#60;br&#62;But in your case, you are loading other sets of data from other people in order to combine them and see what is of interest to you. I can see how in that scenario you would want Behold to make the names as compatible as possible so that equivalent ones will be grouped in the index, etc.&#60;br&#62;&#60;br&#62;Converting case of names is not always easy: e.g. names like McKay have a capital in the middle of it. &#60;br&#62;&#60;br&#62;But I can see it might be useful to add a user option to allow specification of how you want to display the case of names as mixed or capitalized. Deciding exactly what options to add are not always obvious, so it takes a bit of thinking to get them right, e.g. do I allow a separate option for first names and for last names? How about an option for surnames to be shown as bold (see a thread on that in the Feature Suggestions section of this Forum)&#60;br&#62;&#60;br&#62;If this is something that would be considered to be a bug, then I'd fix it now, but I'm leaving options to Version 1.1, since I have to develop a whole set of them and a consistent user interface to enter them all.&#60;br&#62;&#60;br&#62;With regards to the trouble with multiple surnames and punctuations and brackets, I would be interested in seeing your examples. &#60;br&#62;&#60;br&#62;What I'd find easiest is if you could e-mail the files as attachments to me. My e-mail address is at the bottom of all of my Behold web pages.&#60;br&#62;&#60;br&#62;Louis</description>
<category>Report a Problem</category>
</item>
<item>
<title>Report a Problem: ALL CAPS vs Capitalized</title>
<link>http://www.beholdgenealogy.com/forum/topic.php?id=48#post-168</link>
<pubDate>Thu, 11 May 2006 23:03:55 GMT</pubDate>
<dc:creator>MaxHaiflichJr</dc:creator>
<guid isPermaLink="false">168@http://www.beholdgenealogy.com/forum/</guid>
<description>Louis&#60;br&#62;&#60;br&#62;When adding other GEDCOM files, if the same name is loaded once in all Caps and again Capitalized, they are processed as two different people.&#60;br&#62;&#60;br&#62;It also seems to have trouble handling multple Surnames and certain punctuations and brackets.&#60;br&#62;&#60;br&#62;Tell me how and i can upload some GEDCOMs and/or bho files that demonstrate these problems.&#60;br&#62;&#60;br&#62;Max</description>
<category>Report a Problem</category>
</item>

</channel>
</rss>


<!-- Dynamic Page Served (once) in 0.952 seconds -->
