Support for non-latin or language independent markup

[karbassi]

From @damascene on December 22, 2015 14:10

Most markups in todo.txt files (priority (A)(B) and Date t:, due:) depends on Latin characters so a user of other alphabets like Arabic, Russian, Chinese would have to switch keyboard to write the markup. It would be much easier for a user to write todo.txt tasks in his language letters without having to use Latin characters.

My thought is that many symbols that are available on every keyboard could be used like # & ^ +__()*&&{} [] and numbers could be used for priorities.

example for due: you can use:

Visit London {2015-12-22}

For completed tasks:

× Visit London

For priorities:

(1) Save my life
(2) Visit my mother

Copied from original issue: todotxt/todo.txt-cli#171

[karbassi]

From @mabkenar on June 14, 2016 10:17

Very good idea. Is the '×' in '× Visit London' available in other keyboard layouts? It is not available in American (en-US) layout, but it is available in Persian (fa-IR) layout, on GNU/Linux.

[karbassi]

From @damascene on June 30, 2016 17:22

well, I think there should be a discussion on those markups. if it's not in common keyboard layouts then something else should be chosen IMO.

[pablito1755]

I certainly agree with the goal, but a different approach may be preferable. Tokens should be configurable. The spec could thus define a standard config file in which the needed tokens can be assigned. If not present, a particular token defaults to the existing specification value. Above all, this lets the user select something meaningful to them.

[karbassi]

@pablito1755 I like the direction of where you're going with this. Default to x but allow overrides in a configuration file.

[kdehairy]

For priority, numbers are not language agnostic. 1 is One in English ١ is One in Arabic They are not the same Unicode endpoints