It's odd, as the construction of the table is already using semicolons, perhaps not at the right time. IIRC StringBuilder can be given a culture, so in
the batch save function it might work to add InvariantCulture to it. I'm surprised that Google Docs is not able to auto-identify whether the CSV uses commas or semicolons as separators, though.