Good work, guys !

[Tomberry]

I wanted to thank you sincerely for your work!

For my work I'm using your xlsx.js for server-side conversion of xlsx - json. This is really something! It is easy to understand and very easy to use. Awesome!

Unfortunately it seems that the server side and a little more complicated. I would like to know whether or not you can help me settle the problems I encountered with xlsx?

• The biggest problem is the bad position of cells, it seems that empty boxes are ignored, so that the final table is in the topmost left position possible.
• When you provide digital-alpha information (45A for example) into a cell. After xlsx, we get a number (45 in this example), all letters after the first numbers are ignored even if there are other numbers.
• Special characters are not well transmitted ... I have the problem of "é" equivalent "Ã ©". Does there is something that you know of to help me?

Thank you!

[atinux]

+1

[stephen-hardy]

Hello Tomberry,

Thanks for letting us know about the challenges you're having, and for using our work! My apologies for the delay in response. I've needed to turn my attention to other work items, in addition to getting DOCX.js ready for release. So, thank you for your patience.

• I'm not sure what you mean by "empty boxes", but I do know that cell values of an empty string work fine as a spacer. For example, a worksheets value of [[['', ''], ['', 'hello']]] will produce a spreadsheet with "hello" in B2, nothing in A1, B2, or A2 - and no errors upon opening in Excel. Admittedly, this is not an efficient solution to the problem, but it should work well enough for most uses. Our initial goal was to get data out of applications and into an Excel sheet, leaving the formatting to the recipient of the sheet. We are now adding formatting capabilities to XLSX.js, such as positioning of the data, but empty string values should work until then.
• Yes, this was our mistake, sorry about that! It should be fixed now.
• Upon initial inspection, it looks like XLSX.js is correctly passing what is actually written in the worksheet xml file. When I create a spreadsheet with é as a cell value, Excel puts é in the sharedStrings entry. The A and copyright symbols shown appear to be correct for these entities, but I'm curious as to why Excel shows é instead of &#233. Seems like that would be the appropriate reference for the symbol in question. I'll continue to look into this, and when I understand why this is happening I'll try to implement something to mitigate it. However, until I know why Excel records é as é, I'm going to keep thing as they are in case there is a good reason for that behavior. In the meantime, you can easily accommodate for this by calling a replace function on values as they are read or written to and from XLSX.js.

Thanks! Stephen

[stephen-hardy]

The symbol issue was taken care of with v2.1.0

Thanks, Stephen