Also, the comments in the two new uploaded files are somewhat misleading.
?
"u" is always ASCII 0x75, when encoded with the normal ANSI character set.
?
"?" is extended ASCII 0xB5, when encoded as a single byte with the ANSI character set.
?
LTspice transforms a leading "u" to a "?" when it is on a schematic and used as a units multiplier, unless you have changed that setting in LTspice's Settings / Control Panel.? So the default action in LTspice is to convert 0x75 to 0xB5 (that is, to convert 'u' to '?') when it is on a schematic and used that way.
?
LTspice can be changed to the exact opposite behavior, where it treats a "u" as a "u" and converts a "?" to a "u", when it is found on a schematic and used as a units multiplier.
?
Some programs misinterpret the extended ASCII character 0xB5, turning it into a different 1-byte or 2-byte character that it thinks should be similar.? When saved and later read back into LTspice, or saved and read by other text editing programs, in most cases it will appear to be a corrupt letter or pair of letters, of one form or another, and not as a "?" anymore.? I have now seen three different incorrect "substitute" characters for a "?", where none of them work when the schematic or SPICE Netlist file is read back into LTspice.
?
LTspice's handling of UTF* files is somewhat unconventional.? That is a grey area and best avoided, in my opinion.
?
Andy
?
