In testing PB 2025 Beta2, I've noticed that the object source files that are created during the migration to a PB Solution, as well as the new .pbsln and .pbproj files use UTF-8 encoding, and this greatly surprises me... since PB uses Unicode 16LE encoding internally, I would've thought that the source files would be created with the same encoding schema. Thankfully, the files are all created with a Byte Order Marker (BOM), so the UTF-8 encoding can be easily identified.
Why was UTF-8 encoding chosen?
One disadvantage of this is that it makes the process of retrofitting new or modified code and objects into prior versions considerably more difficult, particularly since it is not currently possible to export (or copy, since all objects are in source format) and import them into earlier versions. And yes, I know that migrating to a PB Solution is a one-way street - but when I have to continue to maintain a production version of an app in an earlier version, there are going to be times when I'll need to retrofit code from the newer Solution-based version back into the Workspace-based version. Removal of the export header and comments lines from every object when the app is migrated to a Solution makes it very difficult to do this.