From 73dacc8e690e69eefbc74cf86a229f0c09200b3e Mon Sep 17 00:00:00 2001 From: wiemann Date: Thu, 8 Mar 2007 08:34:12 +0000 Subject: removed "Workaround for Localized Dates" section; no longer needed git-svn-id: http://svn.code.sf.net/p/docutils/code/trunk/docutils@5007 929543f6-e4f2-0310-98a6-ba3bd3dd1d04 --- docs/dev/repository.txt | 28 ---------------------------- 1 file changed, 28 deletions(-) diff --git a/docs/dev/repository.txt b/docs/dev/repository.txt index c7367098c..0ec415a70 100644 --- a/docs/dev/repository.txt +++ b/docs/dev/repository.txt @@ -109,34 +109,6 @@ If you changed your mind and want to use a different repository root, svn switch --relocate OLDROOT NEWROOT -Workaround for Localized Dates -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -If you have a non-english locale, you should perform all check-out and -update operations with ``LC_TIME=C`` in the environment. Either set -it in your shell init file (e.g. ``~/.bashrc``), or (if you like -localized dates in other programs) always do :: - - env LC_TIME=C svn checkout ... - env LC_TIME=C svn update ... - -This applies both to anonymous and developer access. - -The reason is that subversion localizes its expansion of the ``Date`` -keyword, which may result in non-ASCII characters in other locales. -Non-ASCII characters upset Python, even if they only appear in -comments. Strangely, Subversion always uses UTF-8 to format the date, -ignoring locale settings. So adding a UTF-8 encoding declaration to -all Python sources would help. However, we are not sure if we want to -do this. - -(Arguably, the Right Thing would be for subversion to understand file -encodings: convert file contents, localize keywords and expand an -Encoding keyword to reflect the encoding used. But for now, -``LC_TIME=C`` fixes this by disabling the translation of the date [the -current time zone is still respected].) - - Information for Developers -------------------------- -- cgit v1.2.1