Formatting .op Data Labels in LTspice for Mac

[seamusdemora]

Typing it in - that's why I think it is a TextEdit bug, it's not respecting the encoding of the input file (unless it's just blithely ignoring the \0's it contains)

I would have guessed that TextEdit.app would respect the character encoding, but perhaps not. What was the Plain Text Encoding drop-down menu setting (bottom of the TextEdit.app window)?

[nfmax]

Odd, I don't have any such drop-down menu, the text edit area goes right to the bottom of the window. In preferences, input & output encodings are set to Automatic. TextEdit identifies itself as Version 1.15 (355)

[nfmax]

I just sent the following bug report to LTspice@analog.com...

And AD responded (or at least some email script did)

Thank you for contacting the European Customer Interaction Center at Analog Devices. A case has been generated  for your request.

[Zero999]

Is there a Linux version of LTspice?

No, but the Windows version is specifically designed to work under WINE, which is does quite well.

 

Yes, but again, from various reports, WINE does not work well with Catalina - which is where I need it to be.

Have you tried it youself? I assumed you had, which is why I suggested a Linux VM running LTSpice under WINE. It's clunky but at least you don't need Windows.

[seamusdemora]

Typing it in - that's why I think it is a TextEdit bug, it's not respecting the encoding of the input file (unless it's just blithely ignoring the \0's it contains)

The TextEdit app has a dialog that provides options for text encoding - options that are available for "open" and for "save as..." are a bit different, but are present in both cases - see the attached figures for clarification. You may have to click the "Options" button to see this dialog/drop-down. I wonder if this could be part of the problem?

[seamusdemora]

I submitted a "bug report" of sorts to AD on this issue last week. Yesterday, I received a reply from. He said, in summary:

• He confirmed the problem, and notified the "design team", and
• It might take a while to resolve the issue

He was speaking of the inability for users to create a "round" directive in LTspice-Mac. He did not mention the issue w/ the odd character-encoding scheme used in LTspice-Mac?!

That's all I know. If I hear anything else, I'll post it here.

~S

[nfmax]

An AD application engineer has also acknowledged my bug report, on the text encoding problem:

Thank you for contacting us.

I will forward your feedback to our design team. The team will review this and make the necessary changes to the structure of the tool.
Thank you.

[seamusdemora]

Cool... let's revisit this one year from today - hopefully it will be corrected.

[nbenm]

Cool... let's revisit this one year from today - hopefully it will be corrected.

Sadly two years and half after, it's still not.