sftse
sftse
While revisiting this to add a unit test, I noticed that the formula that is triggering this high byte string panic is also the one from row 43 col 9...
Actually, let's hold off on merge until we can investigate this further.
Haven't forgotten about this, thanks for your review. Rebased, will revisit.
1. On all platforms it holds that `path.file_name().is_some() == path.file_stem().is_some()` so at least one of the introduced fallbacks is useless. 2. This may or may not have to do with...
Unfortunately not, client data. Comparing to other dimension arrays from files that do not have issues, the numbers seem to line up and have sensible values, just the two extra...
If we strip the last two 0s from the arrays, we get 14 bytes that match spec-conformant `Dimensions`. The first three examples parsed that way are then ```rust Dimensions {...
This hits the same error, but if Excel cannot read it will further investigate, maybe the root cause is something else.
> Is Excel able to read your 16 byte DIMENSIONS file? Have not checked but that was what I was going to look into.
Excel is able to read the file that triggered this issue without warnings. If I open the test file gh577.xls in the online version of excel it opens with a...
It's not a particularly clean fix, just moving enough out of `tauri-build` and duplicating some code into `tauri-cli`.