Tom Morris

@EliasStihl I wrote up #6403, which is a piece of this epic, as a possible candidate for your group to consider, unless @wetneb has a better suggestion. It will affect...

@Edvinnordling @karindev I'm not trying to ignore you. When I looked at the Exporters side of things again, I was no longer convinced that the benefit was worth the API...

@karindev, @EliasStihl, @Ishaqezaz, @Edvinnordling - I've written up the exporter refactoring task (see link above). If you're up for a bit of an experimental challenge, please feel free to tackle...

@ostephens Thanks for the feedback. On reflection, I think the 1.0 behavior is a symptom of https://github.com/OpenRefine/OpenRefine/issues/5469#issuecomment-1334611706

@Kurocifer It's actually assigned to me, as you can see in the upper right of the page, but since you've created a PR, I'll review it.

I like the idea of always using a decimal separator for floats. It's simple and more intuitive than (kind of) emulating Excel's "General" style.

> I like the idea of always using a decimal separator for floats. Unfortunately, it's technically a little challenging because Javascript doesn't have floats and ints, just numbers, and it...

Custom JSON serialization similar to what is discussed [here](https://stackoverflow.com/questions/53256165/serialise-bigdecimal-bignumber-bigint-etc-to-and-from-json) might be a possibility.

The recommended way to do this is use Javascript style comments and run things through JSmin before doing the JSON decoding. The one reservation that I have to doing this...

If this is useful functionality, which it would appear to be, it should be in the core product, not an extension (plus the VIB extension appears to be gone. My...