<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: A Plethora of Extra GEDCOM Tags</title>
	<atom:link href="http://www.beholdgenealogy.com/blog/?feed=rss2&#038;p=876" rel="self" type="application/rss+xml" />
	<link>http://www.beholdgenealogy.com/blog/?p=876</link>
	<description>the Development of my Genealogy Program named Behold</description>
	
		<image>
	<link>http://www.beholdgenealogy.com/blog</link>
	<url>http://www.beholdgenealogy.com/blog/../beholdblog.gif</url>
	</image>
	<copyright>Comments by Louis Kessler are Copyright 2000-2013 Louis Kessler, All Rights Reserved.  Comments by others belong to the people who made them.</copyright>
		<item>
		<title>By: Louis Kessler</title>
		<link>http://www.beholdgenealogy.com/blog/?p=876#comment-392</link>

				<dc:creator>Louis Kessler</dc:creator>

		<pubDate>Sat, 26 Nov 2011 06:07:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=876#comment-392</guid>
		<description>mtibesar: That's an interesting question, and I don't have a good answer for you ... because I tend to only notice the bad ones during my testing, and not the good ones. I do know I have notes and comments in my program source for some problems that I've noted, and they include: Ancestral Quest, Brother's Keeper, Family Origins, FTM, Generations, Legacy and PAF. Then there's the mistake programs make with the CONC tag which is horrid! See "CONC Me On The Head": http://www.beholdgenealogy.com/blog/?p=739 

I do plan to in my Version 1.1 to store my database and export to (and ONLY export to) valid GEDCOM 5.5.1 which is the de facto standard. So Behold should be able to be the tool to bring all your GEDCOMs up to date in a manner that you can be confident can be read by any program that can properly read GEDCOM 5.5.1.  But don't ask me how many of them do that properly, because I don't know that.</description>
		<content:encoded><![CDATA[<p>mtibesar: That&#8217;s an interesting question, and I don&#8217;t have a good answer for you &#8230; because I tend to only notice the bad ones during my testing, and not the good ones. I do know I have notes and comments in my program source for some problems that I&#8217;ve noted, and they include: Ancestral Quest, Brother&#8217;s Keeper, Family Origins, FTM, Generations, Legacy and PAF. Then there&#8217;s the mistake programs make with the CONC tag which is horrid! See &#8220;CONC Me On The Head&#8221;: <a href="http://www.beholdgenealogy.com/blog/?p=739" rel="nofollow">http://www.beholdgenealogy.com/blog/?p=739</a> </p>
<p>I do plan to in my Version 1.1 to store my database and export to (and ONLY export to) valid GEDCOM 5.5.1 which is the de facto standard. So Behold should be able to be the tool to bring all your GEDCOMs up to date in a manner that you can be confident can be read by any program that can properly read GEDCOM 5.5.1.  But don&#8217;t ask me how many of them do that properly, because I don&#8217;t know that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mtibesar</title>
		<link>http://www.beholdgenealogy.com/blog/?p=876#comment-388</link>

				<dc:creator>mtibesar</dc:creator>

		<pubDate>Sat, 26 Nov 2011 05:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=876#comment-388</guid>
		<description>I would be interested to see your "Top Ten List of best GedCom Programs"  that rate genealogy programs from best to worst on how they follow the standard. Also, I will be very interested in your future program that makes "invalid" gedcoms valid. I don't trust any of the genealogy programs nowdays since they all have proprietary formats and file extensions. The one thing I want to depend on is exporting and saving my database into a gedcom. I have copies of my gedcoms 20 years back. Thank you for sharing your views on the Gedcom standard - it IS important and this standard is often slighted by the independent software vendors.</description>
		<content:encoded><![CDATA[<p>I would be interested to see your &#8220;Top Ten List of best GedCom Programs&#8221;  that rate genealogy programs from best to worst on how they follow the standard. Also, I will be very interested in your future program that makes &#8220;invalid&#8221; gedcoms valid. I don&#8217;t trust any of the genealogy programs nowdays since they all have proprietary formats and file extensions. The one thing I want to depend on is exporting and saving my database into a gedcom. I have copies of my gedcoms 20 years back. Thank you for sharing your views on the Gedcom standard - it IS important and this standard is often slighted by the independent software vendors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: genej</title>
		<link>http://www.beholdgenealogy.com/blog/?p=876#comment-382</link>

				<dc:creator>genej</dc:creator>

		<pubDate>Tue, 22 Nov 2011 21:18:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.beholdgenealogy.com/blog/?p=876#comment-382</guid>
		<description>"If Behold can’t read your GEDCOM, it’s likely no program can." --

That is so great, Louis.--GJ</description>
		<content:encoded><![CDATA[<p>&#8220;If Behold can’t read your GEDCOM, it’s likely no program can.&#8221; &#8211;</p>
<p>That is so great, Louis.&#8211;GJ</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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