<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 72: Use Unicode internally.</title><link>https://sourceforge.net/p/mpgravity/feature-requests/72/</link><description>Recent changes to 72: Use Unicode internally.</description><atom:link href="https://sourceforge.net/p/mpgravity/feature-requests/72/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 20 Oct 2009 16:30:34 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/mpgravity/feature-requests/72/feed.rss" rel="self" type="application/rss+xml"/><item><title>Use Unicode internally.</title><link>https://sourceforge.net/p/mpgravity/feature-requests/72/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Maybe time to patch Gravity to use utf-16 instead obsolete CP-125X. All Windowses are NT based now and uses unicode internally. This change would allow the abandonment of for example a type conversion utf-8-&amp;gt; utf-16-&amp;gt; cp-125x before displaying in riched control. This would also allow the correct handling of the post encoded in utf-8 in which certain characters now must be converted to '?' char.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 20 Oct 2009 16:30:34 -0000</pubDate><guid>https://sourceforge.net86b3133af7b952f1350f4b865a7487948df7a926</guid></item></channel></rss>