I’ve tried using chcp 65001, set LANG=“C.UTF-8”, both to no avail. I don’t know if it makes a difference, but i’ve tried in native cmd, powershell, as well as cmder instances of both.
Since the issue seems to happen in the command line, it affects all beets commands.
The configuration of the Windows console is pretty hard to get right, I’ve heard! One way around it is to use our terminal_encoding setting to override the currently-configured locale and ask beets to force UTF-8 output.
Definitely seems to be the case. I checked my config and apparently I had already set terminal_encoding: utf8, which makes this even stranger. As expected, commenting it out didn’t help either.
I’m getting around importing by creating ascii folders around unicode subfolders, but for beet queries I’m stuck.
Huh! That’s strange. I don’t have a good explanation for why that config option wouldn’t do what it’s supposed to. Can you paste the output of beet config?