I think that we've had issues with spreadsheets changing some of the existing GUIDs to Error:xxx (in various languages) several times, now, which is probably rather annoying for our contributors. (For the latest see #538.)
Unfortunately, the CSV standard is under-defined and the "proper" behaviour of cells starting with an equals sign isn't really defined. (Python's CSV module thinks that a cell starting with an equals sign is just a raw value; most spreadsheets try to interpret such a cell as a formula.)
Ideally (as a proper solution), we'd either:
Avoid having equals signs at the start of GUIDs. (This can't be solved in the general case, since such GUIDs are valid, and Anki will continue generating such GUIDs occasionally (so users importing existing decks from Anki to Brain Brew will still have such GUIDs); however, in AUG we generate the GUIDs ourselves (via BrainBrew) so we could avoid creating such.) (We'd also obviously still have the problem of such existing GUIDs in AUG.)
Find a reliable way of "escaping" the equal signs at the start of GUIDs, that works with most spreadsheet programs. (This might be easier than 1.)
I think that we've had issues with spreadsheets changing some of the existing GUIDs to
Error:xxx(in various languages) several times, now, which is probably rather annoying for our contributors. (For the latest see #538.)Unfortunately, the CSV standard is under-defined and the "proper" behaviour of cells starting with an equals sign isn't really defined. (Python's CSV module thinks that a cell starting with an equals sign is just a raw value; most spreadsheets try to interpret such a cell as a formula.)
Ideally (as a proper solution), we'd either: