I'm trying to convert a spreadsheet to csv semi-colon delimited

I can -convert-to it to csv, but I need semicolon delimited since the data may have commas already. I know unoconv can be used, but my version of libre office 4 does not seem to come with that and I want to use, I may only use, something that comes native to the package. I know the following command for regular conversion:

–convert-to output_file_extension[:output_filter_name] [–outdir output_dir] files

being that it was forked from openoffice and it is opensource, I assumed that the -convert-to command must use some version of unoconv, so I wonder if I can somehow use that program’s option for choosing a delimiter:

-e FilterOptions=59,34,0,1,1/5/2/1/3/1/4/1

with LO’s convert-to command?

Are you trying to do an automated conversion?

When you use Save As… you do have the option to choose the delimiter. If you are converting from CSV to CSV, an intermediate save to LO ods format will then offer the delimiter selection again.

Yes I am trying to write a script that automates the process. The xls file keeps a listing of credentials. I have recently been doing it by hand by doing as you mentioned. I am writing a login script that will check said xls file and compare the modified date with the current CSV file. If the xls file is newer than the csv file it will move said csv file to an archive folder, then convert and move the new csv file into the former’s directory. Thing is, that the data may have commas as the

credentials require symbols as a requirement, and since I never know when a comma may get used, I’d rather account for that possibility ahead of time. Oh and semi-colon is not an allowed symbol for the credentials, so I’m safe in using that as the delimiter.

And lastly, I’d rather use something that is included with the package than have to go through approval requests for a new installation. If I can use LO as it is, that’d be great. Like I said, since the LO is forked from OpenOffice and from my understanding it used to come with unoconv, I assume it must have been included in the package as part of LO and not included as a separate program. I don’t think they’d create a completely new conversion tool when one is already available.

I played around withe CLI command and ended up answering this question by answering another person’s question…