Comment # 2
on bug 12500
from Guy Harris
CSV, the semi-standardized standard:
https://en.wikipedia.org/wiki/Comma-separated_values
That page says, among other things:
Microsoft Excel will open .csv files, but depending on the system's
regional settings, it may expect a semicolon as a separator instead of a comma,
since in some languages the comma is used as the decimal separator. It also
applies some magic, such as reformatting what looks like numbers, eliminating
leading + or 0, which breaks phone numbers, or a leading = makes the cell a
formula, where function names must be in the opener's local language. Also,
many regional versions of Excel will not be able to deal with Unicode in CSV.
One simple solution when encountering such difficulties is to change the
filename extension from .csv to .txt; then opening the file from an already
running Excel instance with the "Open" command, where the user can manually
specify the delimiters, encoding, format of columns, etc.
so we should probably *always* allow a choice of separator for "C"SV output,
Just In Case some program assumes, for example, semicolon-as-separator in all
locales where comma is the decimal separator.
You are receiving this mail because:
- You are watching all bug changes.
