CSV has special conventions for escaping characters. To escape newlines and commas or you need to contain them within double quotes ("). To escape a double quote you simply repeat twice within a quoted section. So..wrote:CSV specifically seems kinda messy to use for this, as the translations will certainly be using special characters like quotes, commas, semicolons and newlines a lot. Not just that, but it becomes a mess to look at in text form. I'd prefer something that looks clean so it more easily serves the people translating it.
"foo,""bar"""
...is literally interpreted as...
foo,"bar"
Parsing CSV correctly is a pita.
Then you delve into multibyte characters and things get complicated real quick.
How does the interpreter know when the Japanese text ends and the English text begins? Or is there no instance of double line-breaks in the script?wrote:It's readable in any text editor by anyone wanting to translate, and it seems easy enough to parse, right? It's even Markdown compatible. And untranslated lines could just have a little dash inserted or something.