You’re correct, @ytfeldrawkcab, that this has been a longstanding bug. I’ve checked with the team and this is related to a special characters bug for Windows users as detailed here:
Our team does have a bug object filed in their backlog and has bumped it up the list. I know this has been around for a long time, but it has proven difficult to address, and it hasn’t received a priority since there are simple workarounds. We’ll be sure to update everyone when this is resolved, however.