Closed robrasti closed 3 years ago
For anyone that stumbled upon this, I was able to resolve the issue, but not in a way I think was very clear. I was using this as part of a Powershell script that did the following:
Turns out running this in Powershell was causing the character encoding issue somewhere in the process, because when I changed the Powershell scripts over to Bash scripts the problem went away.
I'm not against having my developers run Bash as most have it from installing Git, but it was a frustrating couple hours of my life I will never get back.
I have closed the issue request because I believe it is not an issue with this library, but rather the use of this library in Powershell vs Bash.
I'm not sure if I'm doing something incorrectly, but I have a spreadsheet that has a few columns as follows:
ContentKey EnglishText SpanishText
I am using it to generate a JSON object to force specific Spanish translations. The problem I'm having is I have in the spreadsheet something like:
Cómo utilizar este informe:
After running through the convert-excel-to-json using Node I end up with the following in my JSON object:
C├│mo utilizar este informe:
Some steps I've taken:
Neither has worked.
This appears to happen with all Spanish specific characters.
Any help would be appreciated if this isn't a bug, but rather user error.