<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 8: Separate input and output encoding</title><link>https://sourceforge.net/p/geoclassphp/bugs/8/</link><description>Recent changes to 8: Separate input and output encoding</description><atom:link href="https://sourceforge.net/p/geoclassphp/bugs/8/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 05 Oct 2005 11:50:42 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/geoclassphp/bugs/8/feed.rss" rel="self" type="application/rss+xml"/><item><title>Separate input and output encoding</title><link>https://sourceforge.net/p/geoclassphp/bugs/8/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Just a wish: There is not too much sense in assuming &lt;br /&gt;
latin-1 output encoding, when the data can be in &lt;br /&gt;
UTF-8 or other encodings, as latin-1 or else is just &lt;br /&gt;
a subset of UTF-8. The data will always be resetted &lt;br /&gt;
to subset of characters of the original encoding, so &lt;br /&gt;
we cannot restore the characters to there original &lt;br /&gt;
values, I think. &lt;/p&gt;
&lt;p&gt;So it would be good to have an input_encoding AND an &lt;br /&gt;
output_encoding selectable, to be able to use UFT-8 &lt;br /&gt;
data on output. &lt;/p&gt;
&lt;p&gt;It would be an alternative, to encode all data in &lt;br /&gt;
UTF-8 on output. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Mack</dc:creator><pubDate>Wed, 05 Oct 2005 11:50:42 -0000</pubDate><guid>https://sourceforge.net3de5f7a8993b30c0b618880570ad967be26f7e7f</guid></item></channel></rss>