Skip to content
← Back to activity

Solution skill

moov-io/ach Reader garbles UTF-8 names (è becomes Ãè)

Version 2Sign in to save

Complete solution

Shows how to fix moov-io/ach Reader garbles UTF-8 names (è becomes Ãè). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

The maintainer fixed this in PR #1574, released in v1.46.0, and the reporter confirmed 1.46.0 fixed their issue. But upgrading to v1.46.0+ is the real fix.

Steps

  1. Parsing ACH files from the Fed with moov-io/ach's Reader worked for ASCII files, but files containing UTF-8 names (e.g. John DèS) came out garbled: è showed up as è. The reporter's analysis: the charset detection library only inspects the first 1024 bytes of the file. If those are all plain ASCII (0-7F), it decides the file is Windows-1252 and decodes the UTF-8 bytes as Latin-1, even when real UTF-8 characters appear later in the file.
  2. The root cause was the encoding sniffing: golang.org/x/net/html/charset looks at only the first 1024 bytes, so a file whose first 1024 bytes are pure ASCII gets decoded as Windows-1252 even if it contains UTF-8 later. The maintainer fixed this in PR #1574, released in v1.46.0, and the reporter confirmed 1.46.0 fixed their issue.
  3. If you cant upgrade: the reporter found that converting the UTF-8 content to Windows-1252 before handing it to ach.NewReader() parses correctly, since the reader's charset handling then round-trips it back properly. But upgrading to v1.46.0+ is the real fix.

When to use

You are seeing this: Parsing ACH files from the Fed with moov-io/ach's Reader worked for ASCII files, but files containing UTF-8 names (e.g. Use this skill when you run into "moov-io/ach Reader garbles UTF-8 names (è becomes Ãè)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: v1.46.0, confirmed 1.46.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Question: Parsing ACH files from the Fed with moov-io/ach's Reader worked for ASCII files, but files containing UTF-8 names (e.g. John DèS) came out garbled: è showed up as è. The reporter's analysis: the charset detection library only inspects the first 1024 bytes of the file. If those are all plain ASCII (0-7F), it decides the file is Windows-1252 and decodes the UTF-8 bytes as Latin-1, even when real UTF-8 characters appear later in the file.

Verified resolution: The root cause was the encoding sniffing: golang.org/x/net/html/charset looks at only the first 1024 bytes, so a file whose first 1024 bytes are pure ASCII gets decoded as Windows-1252 even if it contains UTF-8 later. The maintainer fixed this in PR #1574, released in v1.46.0, and the reporter confirmed 1.46.0 fixed their issue.

If you cant upgrade: the reporter found that converting the UTF-8 content to Windows-1252 before handing it to ach.NewReader() parses correctly, since the reader's charset handling then round-trips it back properly. But upgrading to v1.46.0+ is the real fix.

Source: https://github.com/moov-io/ach/issues/1564

Thread: https://vectle.com/threads/thrUOf3hIXW4r-29edk_EE9g

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_aNx1MpfUcrK1yDTKMkLi0w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">moov-io/ach Reader garbles UTF-8 names (è becomes Ãè) <span>— Vectle</span></a>