Igor characters messed up between computers

Share icon

Hi,

I am trying to type what in latex are \langle and \rangle.
I found them in Igor's special characters and I was able to use it on one computer.

Then, I moved the files to another computer, open them and they becomes something else:
\langle --> 〈I
\rangle --> 〉

I therefore tried to redo it on the 2nd computer, and everything looks fine.
Once I switched back to the 1st computer, the same things show up again; the \langle and \rangle again got replaced by the above characters.

The 1st computer is running Windows 7 x64, and the 2nd computer is running Windows 10 x64.
I don't know what is the difference between the two which caused this, is there a way to fix this?
It essentially prevented me from working between the two computers.

Any ideas are appreciated.
thomas_braun wrote:
Are you using Igor 6 or 7?

Thanks for the reminder,

On Win 7 computer, I am using both 6 and 7,
and on the Win 10 computer I am using Igor 7.

It seems to be independent of Igor Version, however, as they change as long as I go from one computer to another, regardless of the Igor Version.
Opening the files on the Win 7 computer, both versions will show the correct encoding, or the wrong one.

February 20, 2018 at 11:05 am - Permalink

I suspect that you are using Igor6 on one computer and Igor7 on another. This creates problems with text encodings.

For background information, in Igor7, execute this:
DisplayHelpTopic "Text Encodings"

Try sticking with Igor7 and using UTF-8 text encoding in all procedure files.

February 20, 2018 at 11:09 am - Permalink

hrodstein wrote:
I suspect that you are using Igor6 on one computer and Igor7 on another. This creates problems with text encodings.

For background information, in Igor7, execute this:
DisplayHelpTopic "Text Encodings"

Try sticking with Igor7 and using UTF-8 text encoding in all procedure files.


I would like to switch to Igor 7, but there are tons of IgorXOP which didn't seem to be compatible and I have to convert them all;
that prevented me from doing the switch, especially on the data taking computers. So Igor6 is still largely under use.

Also, I added that in my reply above, it didn't seem to be because of the Igor version, as it doesn't matter which version I use as long as I am on that computer;
The files saved on Win 10 cannot be decoded correctly on Win 7 computer, no matter I am using Igor 6 or 7.

February 20, 2018 at 12:26 pm - Permalink

Quote:
I would like to switch to Igor 7, but there are tons of IgorXOP which didn't seem to be compatible and I have to convert them all;
that prevented me from doing the switch, especially on the data taking computers. So Igor6 is still largely under use.


With rare exceptions, existing XOPs should work with Igor7 so long as you run the 32-bit version of Igor7 and properly activate the 32-bit XOPs.


Quote:
Also, I added that in my reply above, it didn't seem to be because of the Igor version, as it doesn't matter which version I use as long as I am on that computer; The files saved on Win 10 cannot be decoded correctly on Win 7 computer, no matter I am using Igor 6 or 7.


With Igor6, Windows 7 and Windows 10 use the same text encoding, code page 1252 if you are running a western system locale. If you are running different system locales on the two machines, that would explain the problem.

If you are running the same system locale, I have no explanation for the difference and recommend that you double-check your conclusion making sure that you are running Igor6 on both machines.

February 20, 2018 at 12:42 pm - Permalink

hrodstein wrote:
Quote:
I would like to switch to Igor 7, but there are tons of IgorXOP which didn't seem to be compatible and I have to convert them all;
that prevented me from doing the switch, especially on the data taking computers. So Igor6 is still largely under use.


With rare exceptions, existing XOPs should work with Igor7 so long as you run the 32-bit version of Igor7 and properly activate the 32-bit XOPs.


Quote:
Also, I added that in my reply above, it didn't seem to be because of the Igor version, as it doesn't matter which version I use as long as I am on that computer; The files saved on Win 10 cannot be decoded correctly on Win 7 computer, no matter I am using Igor 6 or 7.


With Igor6, Windows 7 and Windows 10 use the same text encoding, code page 1252 if you are running a western system locale. If you are running different system locales on the two machines, that would explain the problem.

If you are running the same system locale, I have no explanation for the difference and recommend that you double-check your conclusion making sure that you are running Igor6 on both machines.



Thanks for the idea,
I will try Igor 6 later on the Win10 machine, just to see if it makes a difference.

Update:
Actually, this doesn't happen to ALL files, but only to some.
I will pay more attention as to why this is limited to a certain files, and come back if I found anything new.

February 20, 2018 at 01:13 pm - Permalink