<?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: Universal UTF-8</title>
	<atom:link href="http://www.texdev.net/2009/01/06/universal-utf-8/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.texdev.net/2009/01/06/universal-utf-8/</link>
	<description>Coding in the TeX world</description>
	<lastBuildDate>Mon, 08 Mar 2010 14:08:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joseph Wright</title>
		<link>http://www.texdev.net/2009/01/06/universal-utf-8/comment-page-1/#comment-72</link>
		<dc:creator>Joseph Wright</dc:creator>
		<pubDate>Wed, 28 Jan 2009 19:37:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=85#comment-72</guid>
		<description>As I said, I&#039;ve never had a BOM issue.  However, some people do, so it is worth thinking about.</description>
		<content:encoded><![CDATA[<p>As I said, I&#8217;ve never had a BOM issue.  However, some people do, so it is worth thinking about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Eli Kalderon</title>
		<link>http://www.texdev.net/2009/01/06/universal-utf-8/comment-page-1/#comment-71</link>
		<dc:creator>Mark Eli Kalderon</dc:creator>
		<pubDate>Wed, 28 Jan 2009 19:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=85#comment-71</guid>
		<description>BOM is not required for UTF-8 encoding. Indeed, UTF-8 encoded documents can easily be identified to nearly 100% without a BOM (for more information see http://blog.macromates.com/2005/handling-encodings-utf-8/). If BOM is making things choke, don&#039;t blame UTF-8, blame your editor for unnecessarily inserting a BOM.</description>
		<content:encoded><![CDATA[<p>BOM is not required for UTF-8 encoding. Indeed, UTF-8 encoded documents can easily be identified to nearly 100% without a BOM (for more information see <a href="http://blog.macromates.com/2005/handling-encodings-utf-8/)" rel="nofollow">http://blog.macromates.com/2005/handling-encodings-utf-8/)</a>. If BOM is making things choke, don&#8217;t blame UTF-8, blame your editor for unnecessarily inserting a BOM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carbon Emacs, SimpleTeX4ht, philosophy und brain_damage, LuaTeX, Blogs &#171; TeX &#38; Friends</title>
		<link>http://www.texdev.net/2009/01/06/universal-utf-8/comment-page-1/#comment-21</link>
		<dc:creator>Carbon Emacs, SimpleTeX4ht, philosophy und brain_damage, LuaTeX, Blogs &#171; TeX &#38; Friends</dc:creator>
		<pubDate>Sat, 10 Jan 2009 02:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=85#comment-21</guid>
		<description>[...] Schluß diesmal eine kleine Blogschau: Joseph Wright gibt Tips, die man beachten sollte, wenn man vorhat, seine LaTeX-Dokumente in UTF-8 zu schreiben. [...]</description>
		<content:encoded><![CDATA[<p>[...] Schluß diesmal eine kleine Blogschau: Joseph Wright gibt Tips, die man beachten sollte, wenn man vorhat, seine LaTeX-Dokumente in UTF-8 zu schreiben. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Wright</title>
		<link>http://www.texdev.net/2009/01/06/universal-utf-8/comment-page-1/#comment-19</link>
		<dc:creator>Joseph Wright</dc:creator>
		<pubDate>Wed, 07 Jan 2009 07:12:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=85#comment-19</guid>
		<description>Thanks for the detailed comments, Marcin.  You are quite right about the BOM issue, but I&#039;ve never had a problem with that one myself, hence it slipped my mind. I&#039;ve not really tried amsrefs either, as I have lots of references in a BibTeX database (used for general tracking of references). With care, you can use some UTF-8, provided it is kept away from BibTeX; so no accents in keys, for example. 
MiKTeX doesn&#039;t so much have a problem with LuaTeX, more it&#039;s simply not been integrated yet. There are other things that MiKTeX handles much more cleanly on Windows, so for the moment I shall be patient!</description>
		<content:encoded><![CDATA[<p>Thanks for the detailed comments, Marcin.  You are quite right about the BOM issue, but I&#8217;ve never had a problem with that one myself, hence it slipped my mind. I&#8217;ve not really tried amsrefs either, as I have lots of references in a BibTeX database (used for general tracking of references). With care, you can use some UTF-8, provided it is kept away from BibTeX; so no accents in keys, for example.<br />
MiKTeX doesn&#8217;t so much have a problem with LuaTeX, more it&#8217;s simply not been integrated yet. There are other things that MiKTeX handles much more cleanly on Windows, so for the moment I shall be patient!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcin</title>
		<link>http://www.texdev.net/2009/01/06/universal-utf-8/comment-page-1/#comment-18</link>
		<dc:creator>Marcin</dc:creator>
		<pubDate>Tue, 06 Jan 2009 22:21:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=85#comment-18</guid>
		<description>Hi,

first of all I&#039;d like to say `thank you&#039; for your blog!

As for the UTF-8 problem, I&#039;d add a few thoughts, especially that my mother tongue is incompatible with ASCII.

1. Not using e-TeX really sucks, as of 2008...

2. Probably XeTeX *is* an `obvious choice&#039;; I, however, still use (for LaTeX) a more `traditional&#039; TeX engine (pdf-e-TeX) with [utf8]{inputenc}.  Being aware of inputenc&#039;s problems (it messes with catcodes, and log/terminal output with UTF-8 is rather garbled), I&#039;m ok with it.  I&#039;ll consider switching to XeTeX, too.  When using ConTeXt, I use luaTeX.  (encTeX is another option, btw.)

3. Does luaTeX really have problems with MikTeX?  If yes, maybe that&#039;s another reason to switch to texlive?

4. BibTeX sucks.  Really.  *Do* use amsrefs instead.  (Or maybe some kind of a replacement for BibTeX, there are a few; having amsrefs, I&#039;ve never needed them.)

5. You didn&#039;t mention another problem with UTF-8: the infamous BOMs.  (I use Linux almost exclusively, and convert to CP-1250 when going Windows at work, so it&#039;s not a problem for me;).)

6. As for data interchange, CP-1250 is probably a reasonable choice when working with Polish-speaking Windows people; Emacs (and vim, too) have no problems with it.  Emacs even parses the LaTeX file to find an inputenc-loading line, checks the encoding and acts accordingly.

Greets</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>first of all I&#8217;d like to say `thank you&#8217; for your blog!</p>
<p>As for the UTF-8 problem, I&#8217;d add a few thoughts, especially that my mother tongue is incompatible with ASCII.</p>
<p>1. Not using e-TeX really sucks, as of 2008&#8230;</p>
<p>2. Probably XeTeX *is* an `obvious choice&#8217;; I, however, still use (for LaTeX) a more `traditional&#8217; TeX engine (pdf-e-TeX) with [utf8]{inputenc}.  Being aware of inputenc&#8217;s problems (it messes with catcodes, and log/terminal output with UTF-8 is rather garbled), I&#8217;m ok with it.  I&#8217;ll consider switching to XeTeX, too.  When using ConTeXt, I use luaTeX.  (encTeX is another option, btw.)</p>
<p>3. Does luaTeX really have problems with MikTeX?  If yes, maybe that&#8217;s another reason to switch to texlive?</p>
<p>4. BibTeX sucks.  Really.  *Do* use amsrefs instead.  (Or maybe some kind of a replacement for BibTeX, there are a few; having amsrefs, I&#8217;ve never needed them.)</p>
<p>5. You didn&#8217;t mention another problem with UTF-8: the infamous BOMs.  (I use Linux almost exclusively, and convert to CP-1250 when going Windows at work, so it&#8217;s not a problem for me;).)</p>
<p>6. As for data interchange, CP-1250 is probably a reasonable choice when working with Polish-speaking Windows people; Emacs (and vim, too) have no problems with it.  Emacs even parses the LaTeX file to find an inputenc-loading line, checks the encoding and acts accordingly.</p>
<p>Greets</p>
]]></content:encoded>
	</item>
</channel>
</rss>
