<p>Actually I tested SciTE, which is kind enough to open the file without problem, and simply showing plain bytes for the invalid ones, making line 1738 (last one) look like this:<br>
<a href="https://cloud.githubusercontent.com/assets/793526/18629100/cbc62c9a-7e63-11e6-867e-cc052e495886.png" target="_blank"><img src="https://cloud.githubusercontent.com/assets/793526/18629100/cbc62c9a-7e63-11e6-867e-cc052e495886.png" alt="l1738" style="max-width:100%;"></a></p>

<p>It's pretty messy but fair enough.  However, we probably won't do that, because being able to have a fixed encoding in the data we load means that we have to handle encoding conversion in a single place, instead of everywhere something touches the data -- and there are a lot of code that does that, it's and editor after all.<br>
Also, as UTF-8 can represent virtually any textual data (anything inside Unicode), it would only help with invalid input (like here) or binary data (which probably would better be handled with a hex filter).  So I'm afraid it won't happen.<br>
If someone has a nice solution though, I'd love to be proven wrong.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/1238#issuecomment-247959290">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJxyn_D6HnSccEW2ujyI4eGt1tWZIks5qrmQwgaJpZM4KAGgV">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ_WTEzmV7zkeIz_FvJ80jmb6K25Mks5qrmQwgaJpZM4KAGgV.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/issues/1238#issuecomment-247959290"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@b4n in #1238: Actually I tested SciTE, which is kind enough to open the file without problem, and simply showing plain bytes for the invalid ones, making line 1738 (last one) look like this:\r\n\r\n\r\nIt's pretty messy but fair enough.  However, we probably won't do that, because being able to have a fixed encoding in the data we load means that we have to handle encoding conversion in a single place, instead of everywhere something touches the data -- and there are a lot of code that does that, it's and editor after all.\r\nAlso, as UTF-8 can represent virtually any textual data (anything inside Unicode), it would only help with invalid input (like here) or binary data (which probably would better be handled with a hex filter).  So I'm afraid it won't happen.\r\nIf someone has a nice solution though, I'd love to be proven wrong."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1238#issuecomment-247959290"}}}</script>