<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Dying For Diacriticals &#8230;    Beyond ASCII  &#8212;  #HowTo, #Genealogy, #Polish</title>
	<atom:link href="http://mikeeliasz.wordpress.com/2012/02/28/dying-for-diacriticals-beyond-ascii-howto-genealogy-polish/feed/" rel="self" type="application/rss+xml" />
	<link>http://mikeeliasz.wordpress.com/2012/02/28/dying-for-diacriticals-beyond-ascii-howto-genealogy-polish/</link>
	<description>A Muse-ing</description>
	<lastBuildDate>Thu, 23 May 2013 13:14:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Genealogy Indexer &#8211; Logan Kleinwak &#8212; #Genealogy, #Historical, #Directories, #Military, #Yizkor &#124; Stanczyk &#8211; Internet Muse</title>
		<link>http://mikeeliasz.wordpress.com/2012/02/28/dying-for-diacriticals-beyond-ascii-howto-genealogy-polish/#comment-991</link>
		<dc:creator><![CDATA[Genealogy Indexer &#8211; Logan Kleinwak &#8212; #Genealogy, #Historical, #Directories, #Military, #Yizkor &#124; Stanczyk &#8211; Internet Muse]]></dc:creator>
		<pubDate>Thu, 03 May 2012 14:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://mikeeliasz.wordpress.com/?p=2195#comment-991</guid>
		<description><![CDATA[[...] for articles or data entry into genealogy software. You may remember, I wrote about that in &#8220;Dying for Diacriticals&#8221; or any of the other dozen articles (some of which cover [...]]]></description>
		<content:encoded><![CDATA[<p>[...] for articles or data entry into genealogy software. You may remember, I wrote about that in &#8220;Dying for Diacriticals&#8221; or any of the other dozen articles (some of which cover [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diacritical Redux &#8211; Ancestry GEDCOM &#8212; #Genealogy, #Technology &#124; Stanczyk &#8211; Internet Muse</title>
		<link>http://mikeeliasz.wordpress.com/2012/02/28/dying-for-diacriticals-beyond-ascii-howto-genealogy-polish/#comment-807</link>
		<dc:creator><![CDATA[Diacritical Redux &#8211; Ancestry GEDCOM &#8212; #Genealogy, #Technology &#124; Stanczyk &#8211; Internet Muse]]></dc:creator>
		<pubDate>Fri, 02 Mar 2012 15:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://mikeeliasz.wordpress.com/?p=2195#comment-807</guid>
		<description><![CDATA[[...] (that I assumed you have been working so hard to add since my aritcle on Tuesday,  &#8221;Dying For Diacriticals&#8220;)? I&#8217;ll give you a HINT, it is the #1 Genealogy Website  &#8211; Yes,  it is [...]]]></description>
		<content:encoded><![CDATA[<p>[...] (that I assumed you have been working so hard to add since my aritcle on Tuesday,  &#8221;Dying For Diacriticals&#8220;)? I&#8217;ll give you a HINT, it is the #1 Genealogy Website  &#8211; Yes,  it is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David A Knight</title>
		<link>http://mikeeliasz.wordpress.com/2012/02/28/dying-for-diacriticals-beyond-ascii-howto-genealogy-polish/#comment-799</link>
		<dc:creator><![CDATA[David A Knight]]></dc:creator>
		<pubDate>Wed, 29 Feb 2012 07:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://mikeeliasz.wordpress.com/?p=2195#comment-799</guid>
		<description><![CDATA[Small correction.  

ASCII is 7 bit, not 8.   UTF-8 will fail if it encounters a character &gt; 127 in HEAD as that value indicates that the character is more than 1 octet in UTF-8.   This could very easily happen with NAME, CORP, ADDR etc. in HEAD prior to the CHAR tag informing you of the actual character set in use.

The 8 bit character sets you will normally see are ANSI with one of the various codepages.

[Editor -
          David,
                 Yes, you are correct. Thanks for helping me out -- ASCII is indeed 7 bit (0-127 decimal) ANSI standard. When I wrote 8bit Ascii,  I was meaning the ISO_8859_ 1/2 code pages (or Windows-1250) which provided the diacriticals by using the 8th bit to map Ascii codes for the characters 128-255 decimal.

--Stanczyk ]]]></description>
		<content:encoded><![CDATA[<p>Small correction.  </p>
<p>ASCII is 7 bit, not 8.   UTF-8 will fail if it encounters a character &gt; 127 in HEAD as that value indicates that the character is more than 1 octet in UTF-8.   This could very easily happen with NAME, CORP, ADDR etc. in HEAD prior to the CHAR tag informing you of the actual character set in use.</p>
<p>The 8 bit character sets you will normally see are ANSI with one of the various codepages.</p>
<p>[Editor -<br />
          David,<br />
                 Yes, you are correct. Thanks for helping me out -- ASCII is indeed 7 bit (0-127 decimal) ANSI standard. When I wrote 8bit Ascii,  I was meaning the ISO_8859_ 1/2 code pages (or Windows-1250) which provided the diacriticals by using the 8th bit to map Ascii codes for the characters 128-255 decimal.</p>
<p>--Stanczyk ]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis Kessler (@louiskessler)</title>
		<link>http://mikeeliasz.wordpress.com/2012/02/28/dying-for-diacriticals-beyond-ascii-howto-genealogy-polish/#comment-798</link>
		<dc:creator><![CDATA[Louis Kessler (@louiskessler)]]></dc:creator>
		<pubDate>Wed, 29 Feb 2012 00:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://mikeeliasz.wordpress.com/?p=2195#comment-798</guid>
		<description><![CDATA[&quot;UTF-8 can have that byte-order-mark (BOM) at the front of our gedcom or not and it is still UTF-8 &quot; - I didn&#039;t know that. Thanks.]]></description>
		<content:encoded><![CDATA[<p>&#8220;UTF-8 can have that byte-order-mark (BOM) at the front of our gedcom or not and it is still UTF-8 &#8221; &#8211; I didn&#8217;t know that. Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
