NickyMcLean 21 hours ago

On receiving a daily .xlsx file from a data logger (eg Inverter Operation Report(20261028)_2115501862195265538.xlsx) Libre Office 24.2 complains that the file is corrupt and offers a repair option, which so far has worked. As the objective is to save a .csv text file for input to a normal prog. to read this has become tiresome. An existing prog, xls2csv rejects such a file because of the compression - it would be convenient if there was one command that deals with both sorts. So, xlsx2csv. And I don't have to poke a dialogue box as with Libre Office. Yay. However, every run, even if just "xlsx2csv -v" or "xlsx2csv ---version" throws forth complaints. For the data run, "/usr/bin/xlsx2csv:809: SyntaxWarning: invalid escape sequence '\d'" then " elif re.match("^\d+(\.\d+)?$", self.data) and re.match(".*[hsmdyY]", format_str) and not re.match(" sprays forth with another seven similar rants. The extracted .csv file is however good.