On Tue, May 6, 2025 at 10:21 PM, wai wai wrote:
The solution, to force LTspice to save schematic to be UTF8 or UFT16, just add some local "char" (double bytes) to the schematic, and then LTSpice will be saved files as UTF16 by default.
That lacks backwards compatibility to anyone using an older version of LTspice.? (Yes, there are still some out there with old XP computers who do not wish to - or can't - upgrade to a newer LTspice.)? Also, I am unsure whether the native Mac version yet supports "Unicode" schematics.? (I
think it does.)? If not, they would be unable to open said schematics.
?
Furthermore, LTspice's "Unicode" has proven to be a much bigger headache than anyone imagined.? Most problems with it have finally died down now, but I am sure they will still arise.? With an alphabet of some 150,000 characters, it is a thousand problems just waiting to happen.
?
The easier solution, is this one:
- Go to LTspice's Control Panel (or Settings)
- Netlist Options
- Check the checkbox next to "Convert '?' to 'u'".
- Click OK
?
This problem with '?' rarely ever happens anymore, now that the group migrated from Yahoo to Groups.io.? Since people should never email LTspice schematics by cut-and-pasting raw text, that isn't a problem either, or it should not be.? For person-to-person emails, attaching an LTspice schematic (as an attached file) works great, as does attaching a .ZIP file.? For schematics sent to this group, uploading the LTspice schematic works great, and that is what everyone should do.? So there should be no issue anymore, unless you do things wrong.
?
By the way, LTspice is not spelled "LTSpice".? Also, files should only be uploaded to the "Temp" folder.? Always navigate to that folder first, before clicking the "+New/Upload" button.? Just like it says in the group's guidelines.
?
Andy
?
?
?
