How should CSV exports handle formula-like cells?

Neutralize formula-like text

A cell whose text begins with an equals sign, a plus, a minus, an at sign or a tab can be executed as a formula by some spreadsheet software when the file is opened. The studio's writer prefixes those cells so the spreadsheet treats them as text. Documentation runs into this often, because a definition or a value meaning can easily begin with one of those characters.

Preserve RFC-style quoting

Any cell containing a comma, a double quote or a line break is wrapped in quotes with its internal quotes doubled, which is what the CSV convention asks for. This matters more in a documentation export than in most data files, because definitions and value meanings are prose, and prose contains all three routinely. The same writer produces the sample survey file, which the studio's own importer parses back on every build.

Review downstream expectations

Neutralising a cell changes how it displays: the prefix is visible to anyone who looks for it, and a formula somebody wanted will not run. Import settings, locale and separator conventions still vary between spreadsheet programs, so open the exported file in the software your reader uses before you send it. A safely written file says nothing about whether its contents are correct.

Worked example from the sample project

Export the dictionary CSV from the sample and every cell has been through the same defensive writer: cells beginning with a formula trigger character are prefixed so a spreadsheet treats them as text, and any cell containing a comma, a quote or a line break is quoted with its internal quotes doubled. A definition that happens to start with a minus sign, or a value label containing a comma, both survive intact.

This matters more in a documentation export than in most CSVs, because definitions are prose. Prose contains commas, quotation marks and line breaks routinely, and a naive writer turns any of those into a broken column that the recipient discovers days later while trying to read the file.

What this does not do

• Neutralising a cell changes how a spreadsheet displays it; check downstream expectations.
• It does not protect against every spreadsheet's import settings or locale handling.
• A safe CSV says nothing about whether its contents are correct.

Do this in the studio

Open the exported CSV in the software your recipient uses before you send it.

1. Open the Handoff packet station and export the dictionary CSV.
2. Open it in a spreadsheet and check the columns line up.
3. Send the reader page alongside it for anyone who does not want a spreadsheet.

Open the studio at the Handoff packet station

Related reading

• The handoff packet
• End to end worked example
• Security and local-data model