<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Family Tree Maker: Entering Foreign Names and Locations</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=family-tree-maker-entering-foreign-names-and-locations</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Wed, 19 Jun 2013 04:14:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/#comment-45410</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Wed, 14 Apr 2010 21:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3137#comment-45410</guid>
		<description>Julie,

There is another way to handle it.
Create a custom source- call it something like &quot;Research Annotations&quot; and then whatever you were going to enter that gets converted to Notes on the member trees enter that in the &quot;Actual Text&quot; part of your custom source.

Granted, people will have to click on that source link beside the person&#039;s name on the member tree overview page to actually read it - but it will at least be available.</description>
		<content:encoded><![CDATA[<p>Julie,</p>
<p>There is another way to handle it.<br />
Create a custom source- call it something like &#8220;Research Annotations&#8221; and then whatever you were going to enter that gets converted to Notes on the member trees enter that in the &#8220;Actual Text&#8221; part of your custom source.</p>
<p>Granted, people will have to click on that source link beside the person&#8217;s name on the member tree overview page to actually read it &#8211; but it will at least be available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julie</title>
		<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/#comment-45403</link>
		<dc:creator>Julie</dc:creator>
		<pubDate>Wed, 14 Apr 2010 12:40:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3137#comment-45403</guid>
		<description>@Brian Scheick- FTM10 does have issues but maybe not the ones you think.  Yes, it only shows 3 tabs for children but when you fill in the third spot it automatically creates a spot for the fourth, and so on. Theres a button to sort multiple children by birthdate. It won&#039;t be as difficult as you believe.  

The only &#039;real&#039; problem with FTM is that as you enter in your supporting documentation and upload to Ancestry, your documentation (which should go under &#039;Stories&#039; it seems to me) goes under &#039;Notes&#039; and therefore is only accessible to people you deem as &#039;Editors&#039;.  This means your documentation is not available to the masses. (Note: Ancestry&#039;s Help wrote back and acknowledged the bug and their solution was to type all my documentation into a word processing program, then attach it as files in the &#039;Media&#039; section. NOT a good working solution at all. Why use FTM then?) I&#039;m hoping Ancestry/FTM repairs this issue- and SOON.</description>
		<content:encoded><![CDATA[<p>@Brian Scheick- FTM10 does have issues but maybe not the ones you think.  Yes, it only shows 3 tabs for children but when you fill in the third spot it automatically creates a spot for the fourth, and so on. Theres a button to sort multiple children by birthdate. It won&#8217;t be as difficult as you believe.  </p>
<p>The only &#8216;real&#8217; problem with FTM is that as you enter in your supporting documentation and upload to Ancestry, your documentation (which should go under &#8216;Stories&#8217; it seems to me) goes under &#8216;Notes&#8217; and therefore is only accessible to people you deem as &#8216;Editors&#8217;.  This means your documentation is not available to the masses. (Note: Ancestry&#8217;s Help wrote back and acknowledged the bug and their solution was to type all my documentation into a word processing program, then attach it as files in the &#8216;Media&#8217; section. NOT a good working solution at all. Why use FTM then?) I&#8217;m hoping Ancestry/FTM repairs this issue- and SOON.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carel</title>
		<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/#comment-45395</link>
		<dc:creator>Carel</dc:creator>
		<pubDate>Tue, 13 Apr 2010 21:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3137#comment-45395</guid>
		<description>I realy enjoy using the Ancestry program, but I do have difficulty checking the european history, how can I contact and obtain that information?</description>
		<content:encoded><![CDATA[<p>I realy enjoy using the Ancestry program, but I do have difficulty checking the european history, how can I contact and obtain that information?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles</title>
		<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/#comment-45394</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Tue, 13 Apr 2010 17:13:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3137#comment-45394</guid>
		<description>i agree with dklart. if you use symbols they will not be recognized on ancestry.com or internet search engines. also, this cute feature is not available at ancestry.com, just the FTM product on your PC.</description>
		<content:encoded><![CDATA[<p>i agree with dklart. if you use symbols they will not be recognized on ancestry.com or internet search engines. also, this cute feature is not available at ancestry.com, just the FTM product on your PC.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Scheick</title>
		<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/#comment-45389</link>
		<dc:creator>Brian Scheick</dc:creator>
		<pubDate>Tue, 13 Apr 2010 13:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3137#comment-45389</guid>
		<description>Good to know. I&#039;ve been using the VERY old Ancestry Family Tree program (it was free to download back ~2005).  I bought FTM10 but hated the look, with big text and only 3 tabs (most of my ancestors seemed to have 10+ kids).  I&#039;m just now looking to upgrade to FTM-2010 and bet my old program only does GEDCOM 5.0, so I&#039;ll lose or have to correct my Swedish ancestors.
I use the windows keys (ALT+num keys) because I mostly use the same 2 and it&#039;s easier once I&#039;ve memorized those than all that clicking.</description>
		<content:encoded><![CDATA[<p>Good to know. I&#8217;ve been using the VERY old Ancestry Family Tree program (it was free to download back ~2005).  I bought FTM10 but hated the look, with big text and only 3 tabs (most of my ancestors seemed to have 10+ kids).  I&#8217;m just now looking to upgrade to FTM-2010 and bet my old program only does GEDCOM 5.0, so I&#8217;ll lose or have to correct my Swedish ancestors.<br />
I use the windows keys (ALT+num keys) because I mostly use the same 2 and it&#8217;s easier once I&#8217;ve memorized those than all that clicking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Donaldson</title>
		<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/#comment-45387</link>
		<dc:creator>John Donaldson</dc:creator>
		<pubDate>Tue, 13 Apr 2010 02:29:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3137#comment-45387</guid>
		<description>FTM 2010 supports GEDCOM 5.5.1

John D</description>
		<content:encoded><![CDATA[<p>FTM 2010 supports GEDCOM 5.5.1</p>
<p>John D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/#comment-45384</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Mon, 12 Apr 2010 23:01:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3137#comment-45384</guid>
		<description>Tanya,

The last GEDCOM standard released and approved for public use had no provision for using UFT-8.

There was a subsequent draft proposal (5.5.1 I think it was) but that draft was neither officially approved nor officially implemented.

GEDCOMs are, by definition, ascii text. Use of anything else will always cause problems of one type or another with the import routines of several other programs.</description>
		<content:encoded><![CDATA[<p>Tanya,</p>
<p>The last GEDCOM standard released and approved for public use had no provision for using UFT-8.</p>
<p>There was a subsequent draft proposal (5.5.1 I think it was) but that draft was neither officially approved nor officially implemented.</p>
<p>GEDCOMs are, by definition, ascii text. Use of anything else will always cause problems of one type or another with the import routines of several other programs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tana L. Pedersen</title>
		<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/#comment-45380</link>
		<dc:creator>Tana L. Pedersen</dc:creator>
		<pubDate>Mon, 12 Apr 2010 17:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3137#comment-45380</guid>
		<description>#1 Peter

I don&#039;t know that I have the perfect answer for recording multiple surnames. I record each individual under the name they were recorded with at birth (or the record I can find closest to that). Then I record each surname variation as a different Name fact for an individual. That way I can display the alternate names in reports and charts if I want. 

# 2 Renee

I&#039;m sorry you weren&#039;t able to download the PDF. If you&#039;d like to send me an email at tpedersen@ancestry.com, I&#039;d be happy to forward you a copy.

There is a source template you can use for phone calls, emails, interviews it&#039;s just a little difficult to find. Go to the source group Archives and Artifacts, then choose Private Holdings as the Category. In the Template drop-down list you&#039;ll see personal correspondence, person e-mail, and interview.

# 3

Thanks for the information on how characters are used in GEDCOMs. I&#039;ll have to do some experimenting with this.</description>
		<content:encoded><![CDATA[<p>#1 Peter</p>
<p>I don&#8217;t know that I have the perfect answer for recording multiple surnames. I record each individual under the name they were recorded with at birth (or the record I can find closest to that). Then I record each surname variation as a different Name fact for an individual. That way I can display the alternate names in reports and charts if I want. </p>
<p># 2 Renee</p>
<p>I&#8217;m sorry you weren&#8217;t able to download the PDF. If you&#8217;d like to send me an email at <a href="mailto:tpedersen@ancestry.com">tpedersen@ancestry.com</a>, I&#8217;d be happy to forward you a copy.</p>
<p>There is a source template you can use for phone calls, emails, interviews it&#8217;s just a little difficult to find. Go to the source group Archives and Artifacts, then choose Private Holdings as the Category. In the Template drop-down list you&#8217;ll see personal correspondence, person e-mail, and interview.</p>
<p># 3</p>
<p>Thanks for the information on how characters are used in GEDCOMs. I&#8217;ll have to do some experimenting with this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tenant Verification Miami</title>
		<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/#comment-45374</link>
		<dc:creator>Tenant Verification Miami</dc:creator>
		<pubDate>Mon, 12 Apr 2010 03:17:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3137#comment-45374</guid>
		<description>This is so useful for scandinavian names!</description>
		<content:encoded><![CDATA[<p>This is so useful for scandinavian names!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kerry</title>
		<link>http://blogs.ancestry.com/ancestry/2010/04/05/family-tree-maker-entering-foreign-names-and-locations/#comment-45322</link>
		<dc:creator>Kerry</dc:creator>
		<pubDate>Thu, 08 Apr 2010 12:12:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=3137#comment-45322</guid>
		<description>dklart&#039;s comment is more a reflection on the inability of some software to handle UTF-8 encoding in the GEDCOM. One reason why I haven&#039;t used many of the &quot;big name&quot; packages that can&#039;t handle my GEDCOM of mixed Chinese and English characters.</description>
		<content:encoded><![CDATA[<p>dklart&#8217;s comment is more a reflection on the inability of some software to handle UTF-8 encoding in the GEDCOM. One reason why I haven&#8217;t used many of the &#8220;big name&#8221; packages that can&#8217;t handle my GEDCOM of mixed Chinese and English characters.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
