Yes, the encoding was UTF-8. No worries: I'm a developer too; I know these things happen. Given some of the regressions I've been dealing with recently, it was

Yes, the encoding was UTF-8. No worries: I'm a developer too; I know these things happen. Given some of the regressions I've been dealing with recently, it was entirely believable that but was in my software -- otherwise I would have cross-checked with something else much earlier!