Numbers export CSV with semicolons, I need commas

I can do "trial and error" myself. I've done it since my first computer, in the 80s.

I was asking for a solution. The one offered "Choose a Language/Region that uses . as the decimal separator" doesn't work.

If I were to answer leaning towards a controversial tone I could say that "I find that adding a "delimiter selection" to the option panel is quicker and easier and way more straightforward.

But the point is just that I'll make do with exporting the way Numbers has decided I have to and then Search-and-Replace in Textedit until either Apple - I'm a loyal customer, don't get me wrong - fixes this (yes: it clearly needs fixing) or someone comes out with a full, clear workaround that actually works.

Thanks for you time, though. I know this is a customer-based forum and I appreciate your effort.

Indeed, I have tried.

My usual setting, as I work in an EU region, is set with te decimal separator to be the Comma:

So I have moved to the UK setting, instead:

I have exported (please note the file name) and yet the file still shows the semicolons:

Any hit? Is UTF-8 - the standard choice when exporting to CSV - right?

You'd be surprised, but I'all about "keeping the user interface simple", as long as it works always.

This US-centric approach ("it works on my system") is clearly... a US-centric system. But I'd go with it... if it worked.

I have set the Language/Region to United States:

And yet it doesn't export it right:

So I say: since the "C" in the file format name stays nowadays for "Character" and not just only for "comma" (in fact, it exports it with semicolon, on mine) just make it possible to easily control what is the result.

But since "comma" is the most common character used - and still the original chosen one - make sure that that is the standard choice and the system takes care of adjusting its parameter in order to obtain the result.

Thanks, yes, I'll provide Apple with feedback (again) and, since I'm also a (long-time) beta user I'll also use that channel.

Enjoy the rest of the day.

So, you are telling me that the indication "Choose a Language/Region that uses . as the decimal separator" is not a complete valid solution?

Considering that an option when exporting, side by side with the encoding option would immediately sort out this issue, this is quite disappointing.