<?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: Problem with Name order from GEDCOM file</title>
<link>http://www.beholdgenealogy.com/forum/topic.php?id=40</link>
<description>The Behold User Forum Topic: Problem with Name order from GEDCOM file</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: Problem with Name order from GEDCOM file</title>
<link>http://www.beholdgenealogy.com/forum/topic.php?id=40#post-142</link>
<pubDate>Sun, 08 Jan 2006 11:38:31 GMT</pubDate>
<dc:creator>kartiksubbarao</dc:creator>
<guid isPermaLink="false">142@http://www.beholdgenealogy.com/forum/</guid>
<description>Thanks for the quick response. Surname2 Given2 would be okay as a shortened form of the I2 person. A further abbreviated form for these people would be S2 M2 Given2, where S2 is the initial of the surname, and M2 is the initial of the middle name.&#60;br&#62;&#60;br&#62;Glad that I could provide a helpful suggestion :-) Good job on developing Behold. I like the concept and am looking forward to using it more.</description>
<category>Report a Problem</category>
</item>
<item>
<title>Report a Problem: Problem with Name order from GEDCOM file</title>
<link>http://www.beholdgenealogy.com/forum/topic.php?id=40#post-141</link>
<pubDate>Fri, 06 Jan 2006 22:22:18 GMT</pubDate>
<dc:creator>lkessler</dc:creator>
<guid isPermaLink="false">141@http://www.beholdgenealogy.com/forum/</guid>
<description>Thank you for posting this.&#60;br&#62;&#60;br&#62;I know there are other name variants, but I'm not familiar with them all and I haven't put specific coding into Behold to handle them yet. The GIVN and SURN tags are not used consistently among programs to properly define the name parts, but I should at some time put some code in to use them as best as I can to figure out the name parts. Maybe for Version 1.1.&#60;br&#62;&#60;br&#62;In the case of your I2 example, would it be proper to refer to the person in a shortened form as: Surname2 Given2 (without the Middle2 name)?&#60;br&#62;&#60;br&#62;But I really like your idea to get rid of the &#34;, see ...&#34; line and add it to the end of the previous line. Like you say, that will save space and avoid repetition. Sometimes the obvious things must be pointed out, because I completely missed that. I'll make that change for the next release.&#60;br&#62;&#60;br&#62;Louis</description>
<category>Report a Problem</category>
</item>
<item>
<title>Report a Problem: Problem with Name order from GEDCOM file</title>
<link>http://www.beholdgenealogy.com/forum/topic.php?id=40#post-140</link>
<pubDate>Fri, 06 Jan 2006 12:18:24 GMT</pubDate>
<dc:creator>kartiksubbarao</dc:creator>
<guid isPermaLink="false">140@http://www.beholdgenealogy.com/forum/</guid>
<description>I have a GEDCOM file with names that have different orderings -- some names use a traditional ordering (Surname Middlename Givenname), and others use a modern ordering (Givenname Middlename Surname). For example:&#60;br&#62;&#60;br&#62;0 @I1@ INDI&#60;br&#62;1 NAME Given1 Middle1 /Surname1/&#60;br&#62;2 GIVN Given1 Middle1&#60;br&#62;2 SURN Surname1&#60;br&#62;0 @I2@ INDI&#60;br&#62;1 NAME /Surname2/ Middle2 Given2&#60;br&#62;2 GIVN Given2 Middle2&#60;br&#62;2 SURN Surname2&#60;br&#62;&#60;br&#62;For people like I2, Behold will print &#34;For information about Surname2 Middle2, see ...&#34;. It looks like it is trying to parse everything up to the last word in NAME as a given name, instead of using the GIVN tag.&#60;br&#62;&#60;br&#62;A simple solution would be not to even print the given name in this type of reference -- it's redundant, since the full name has just been printed. i.e. just go with &#34;, see ...&#34;. That would also save an extra line which is critical for saving print space.&#60;br&#62;&#60;br&#62;This type of ordering is very common for traditional Indian names, so I expect it will come up in many cases.</description>
<category>Report a Problem</category>
</item>

</channel>
</rss>


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