heX16

Есть еще пятый вариант: подписывать статью своим ключем. Но этот вариант "традиционно" имеет огромное кол-во технических проблем которые отталкивают даже гиков.

"Make a version comment on the first line of a todo.txt file optional" +1 and make as tag: "todotxt_version:2.0"

My vote is "UTF-8 with **BOM**". Because "UTF-8" some times have problem with encoding detection (and incorrect definitions like ANSI (and damage to characters)).

> CR+LF? Backslash as "directory" separator? I smell windows indoctrination. CR+LF - for better windows support (no difference CR+LF/CR/LF, but the majority uses Windows). Backslash as "directory" - because in...

> Most changes seems like a fork of current spec, not a v3. Or perhaps you should just move to JSON? Yes, this is an improvement of the current specification....

https://github.com/todotxt/todo.txt/issues/13

@tomByrer JSON is not the most successful format, which was born by chance. For machine is better msgpack.org and BSON. For people YAML and Markdown.

> JSON wasn't by 'chance'; it IS JavaScript. Frontend programmers started passing JS objects through the network and called it JSON. It became popular because it was supported in all...

New entity "comment" is not needed. Just add at first line "Todo.txt file. Version:2.0 Encoding:UTF-8".

Why this PR?