{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifssykinqxqof7ghrcomet7jprsporgtq7jfwgfof6fmnofdkoxua",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mikecgud5sd2"
  },
  "path": "/viewtopic.php?t=33205&p=271751#p271751",
  "publishedAt": "2026-04-02T22:43:01.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> This patch solved the problem of stopping the build, but the \"powershell.exe not find\" message still appears.\n\nSo we at least got past the immediate str/bytes issues, that's good. It was kind of a rushed patch because I was trying to get ready for company arriving at noon and didn't have much time... glad it was really just what it looked like.\n\nWell, I definitely didn't add that powershell check, so that's going to be hard to track down... but if it's not breaking anything, then perhaps we can leave it alone.\n\n> There is also a problem with the display in the console. There used to be Russian letters here.\n>\n> codepage.png\n\nThat's definitely worth investigating, sounds like a Unicode/locale issue... which obviously wouldn't come up in my environment because I'm a native English speaker and thus everything was either UTF-8 or CP-1252 during the entire testing run. But yeah, these are the kind of edge cases I was a little paranoid about already, so nothing here is particularly shocking... the issues seem to be coming up mostly on things like Windows 7, 32-bit builds, and non-English locales.\n\n* * *",
  "title": "Platform Development • Re: I created a Python 3 port of UXP out of boredom...",
  "updatedAt": "2026-04-02T22:43:01.000Z"
}