<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 26: Datafile function no longer reports illegal characters</title><link href="https://sourceforge.net/p/millscript/bugs/26/" rel="alternate"/><link href="https://sourceforge.net/p/millscript/bugs/26/feed.atom" rel="self"/><id>https://sourceforge.net/p/millscript/bugs/26/</id><updated>2006-05-25T07:51:36Z</updated><subtitle>Recent changes to 26: Datafile function no longer reports illegal characters</subtitle><entry><title>Datafile function no longer reports illegal characters</title><link href="https://sourceforge.net/p/millscript/bugs/26/" rel="alternate"/><published>2006-05-25T07:51:36Z</published><updated>2006-05-25T07:51:36Z</updated><author><name>Kevin Rogers</name><uri>https://sourceforge.net/u/moya/</uri></author><id>https://sourceforge.netafdb77e77f4eb86b037728590522fc933bd2a73c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The MISHAP generated when an encoding error occurs is &lt;br /&gt;
missing important information about the character &lt;br /&gt;
that cannot be encoded. &lt;/p&gt;
&lt;p&gt;MillScript 10.0.0 reported the unmappable characters &lt;br /&gt;
in a datafile, if they could not be written in the &lt;br /&gt;
current output encoding. MillScript 10.1.2 has &lt;br /&gt;
reverted to awful Java "Input length = 1" error &lt;br /&gt;
message. This needs to be corrected globally for all &lt;br /&gt;
renderers. &lt;/p&gt;&lt;/div&gt;</summary></entry></feed>