From 9da3db2e172e0b3d82e1d2c7c9e3d0725877fbce Mon Sep 17 00:00:00 2001 From: milde Date: Fri, 17 Jun 2022 11:31:17 +0000 Subject: Command line encoding is now handled by Python. Replacing the auto-decoding by Python 3 with a home-baked approach is not worth the effort, so I retract this TODO suggestion. git-svn-id: https://svn.code.sf.net/p/docutils/code/trunk@9076 929543f6-e4f2-0310-98a6-ba3bd3dd1d04 --- docutils/docs/dev/todo.txt | 21 --------------------- 1 file changed, 21 deletions(-) (limited to 'docutils/docs/dev') diff --git a/docutils/docs/dev/todo.txt b/docutils/docs/dev/todo.txt index 32db35673..5db8a331a 100644 --- a/docutils/docs/dev/todo.txt +++ b/docutils/docs/dev/todo.txt @@ -133,27 +133,6 @@ Code cleanup and modernization: .. _flake8: https://pypi.org/project/flake8/ .. _backwards compatibility: policies.html#backwards-compatibility-policy -* Encoding of command line arguments can only be guessed: - - * try UTF-8/strict first, then try the locale's encoding with - strict error handling, then ASCII/replace? - - UTF-8 is almost 100% safe to try first; false positives are rare, - The locale's encoding with strict error handling may be a - reasonable compromise, but any error would indicate that the - locale's encoding is inappropriate. The only safe fallback is - ASCII/replace. - - * Do not decode argv before option parsing but individual string - values? - - +1 Allows for separate command-line vs. filesystem encodings, - respectively to keep file names encoded. - +1 Allows to configure command-line encoding in a config file, - -1 More complicated. - - Cf. . - * Improve handling on Windows: - Get graphical installer. -- cgit v1.2.1