<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[FrontAccounting forum — gettext not suitable, UTF-8 not functioning well enough]]></title>
		<link>https://frontaccounting.com/punbb/viewtopic.php?id=8215</link>
		<atom:link href="https://frontaccounting.com/punbb/extern.php?action=feed&amp;tid=8215&amp;type=rss" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in gettext not suitable, UTF-8 not functioning well enough.]]></description>
		<lastBuildDate>Wed, 12 Jun 2019 18:35:46 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[gettext not suitable, UTF-8 not functioning well enough]]></title>
			<link>https://frontaccounting.com/punbb/viewtopic.php?pid=35170#p35170</link>
			<description><![CDATA[<p>Please read the discussion at http://mantis.frontaccounting.com/view.php?id=4903 and answer here.</p><p>If UTF-8 is really a big problem for someone then why is there no option for choosing that other version and still having UTF-8 as the default setting?</p><p>Instead of &quot;gettext&quot;, we could build our own translation system that&#039;s context-based and where every translatable phrase has its unique identifier. I&#039;ve built such a system once, it&#039;s not rocket science. And it doesn&#039;t need additional software as &quot;gettext&quot; does.</p>]]></description>
			<author><![CDATA[null@example.com (peacecop kalmer:)]]></author>
			<pubDate>Wed, 12 Jun 2019 18:35:46 +0000</pubDate>
			<guid>https://frontaccounting.com/punbb/viewtopic.php?pid=35170#p35170</guid>
		</item>
	</channel>
</rss>
