It looks like when a cell has an inlineStr with multiple t nodes ParseXLSX only uses the first, discarding any text in subsequent nodes. The sharedStrings parser, on the other hand, properly steps through all nodes and joins their values. Unfortunately, I can't share the original spreadsheet, Excel insists on moving values into sharedStrings when I try to create a minimal example, and I don't know the format well enough to craft an example by hand, so I can't give you a proper test file. The raw XML for the cell looks roughly like this, though:
It looks like when a cell has an inlineStr with multiple t nodes ParseXLSX only uses the first, discarding any text in subsequent nodes. The sharedStrings parser, on the other hand, properly steps through all nodes and joins their values. Unfortunately, I can't share the original spreadsheet, Excel insists on moving values into sharedStrings when I try to create a minimal example, and I don't know the format well enough to craft an example by hand, so I can't give you a proper test file. The raw XML for the cell looks roughly like this, though:
The following patch appears to fix the issue: