TextExpander minor annoying bug and a workaround

I’ve used TextExpander since its very early days. I loved the app, especially the fill-in functionality, but as it moved to a subscription model and there have been minimal improvements to the Mac app in the last few years, it’s been difficult to justify continuing my subscription each year when it’s time to renew. I reported a bug in October 2023 that should be an easy fix (if you copy from Xcode into TextExpander to make a snippet, it turns ASCII spaces into Unicode non-breaking spaces so when you expand the snippet in Xcode, you get lots of compiler warnings - at least from the Swift compiler - about non-breaking spaces). After multiple requests to fix it, they did provide a workaround (which is the main reason for this post in case anyone else is having the same issue). When you want to make a snippet from some code in Xcode, copy the text from Xcode, paste into BBEdit, then copy the text from BBEdit, and paste that into TextExpander (which doesn’t create non-breaking spaces in the snippet when you expand it). I’ve sent another request to TextExpander support asking them again to fix this so the workaround isn’t needed.