You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user wants to read a set from this sheet, in an xlsx file (also attached) created by Excel:
The amplxl driver is used like this:
set FAMILY;
table FAMILY "amplxl" "FAMILY.xlsx": [FAMILY] IN;
read table FAMILY;
display FAMILY;
But under Windows, the set displays like this in a command window,
and like this in the IDE:
The problem is that Excel uses UTF-8 encoding, while the command window and the IDE are displaying the set member names using different extended ASCII encodings. AMPL stores the correct UTF-8 bytes, so that results written out to a spreadsheet do show the correct accented characters.
It's not clear what to recommend to the user, other than to avoid accented (and other non-ASCII) characters in the spreadsheet, but I'm opening this issue in case anyone has an idea.
The text was updated successfully, but these errors were encountered:
Still looking at this. It works as expected in Linux. The xml library is supposed to handle the utf-8 conversion without intervention from the programmer. We probably need some specific configuration for MSVS.
A user wants to read a set from this sheet, in an xlsx file (also attached) created by Excel:
The amplxl driver is used like this:
But under Windows, the set displays like this in a command window,
and like this in the IDE:
The problem is that Excel uses UTF-8 encoding, while the command window and the IDE are displaying the set member names using different extended ASCII encodings. AMPL stores the correct UTF-8 bytes, so that results written out to a spreadsheet do show the correct accented characters.
It's not clear what to recommend to the user, other than to avoid accented (and other non-ASCII) characters in the spreadsheet, but I'm opening this issue in case anyone has an idea.
The text was updated successfully, but these errors were encountered: