darcs

Issue 2262 display of meta-data should be in local encoding

Title display of meta-data should be in local encoding
Priority Status resolved
Milestone Resolved in
Superseder Nosy List bfrk
Assigned To
Topics

Created on 2012-10-24.19:14:14 by bfrk, last changed 2018-06-17.16:59:01 by ganesh.

Messages
msg16263 (view) Author: bfrk Date: 2012-10-24.19:14:12
1. Summarise the issue (what were doing, what went wrong?)

ben@sarun[1]: ~/tmp > cd bla 
ben@sarun[1]: .../tmp/bla > darcs initialize   
ben@sarun[1]: .../tmp/bla > darcs tag öü
ben@sarun[1]: .../tmp/bla > echo $LC_CTYPE 
de_DE.UTF-8
ben@sarun[1]: .../tmp/bla > darcs changes -a
Wed Oct 24 20:55:35 CEST 2012  Ben Franksen <ben.franksen@online.de>
  tagged <U+00C3><U+00B6><U+00C3><U+00BC>

2. What behaviour were you expecting instead?

I expected that darcs displays

ben@sarun[1]: .../tmp/bla > darcs changes -a
Wed Oct 24 20:55:35 CEST 2012  Ben Franksen <ben.franksen@online.de>
  tagged öü

that is, takes $LC_CTYPE into account when displaying patch meta-data.

I *dearly hope* that darcs internally stores the meta-data in locale
independent format and uses the current locale to interpret the user's
input when recording a patch, but I have not verified that. (If not,
this would be another issue and a much graver one).

3. What darcs version are you using? (Try: darcs --exact-version)

2.9.5 (+ 157 patches)
msg20151 (view) Author: ganesh Date: 2018-06-10.19:13:58
This is fixed in darcs 2.14, on Linux, right?

On the other hand it's still broken on Windows so I'm inclined to re-
open it to track that problem, or I could open a new one.
msg20152 (view) Author: bfrk Date: 2018-06-11.21:41:06
Yes, it is fixed on Linux. You opened another ticket for the Windows
issues you observed after that. I made some comments there IIRC.
msg20155 (view) Author: bfrk Date: 2018-06-13.18:23:13
I meant the comments I made here: http://bugs.darcs.net/patch1628
msg20165 (view) Author: ganesh Date: 2018-06-17.16:58:59
OK, I'm marking it as resolved, as it is on Linux.

I've raised issue2590 and issue2591 to cover the two aspects of the 
problems on Windows (the issue described in this ticket isn't fixed, 
and other tests have regressed), and will disable the relevant tests 
for now with pointers to those issues.
History
Date User Action Args
2012-10-24 19:14:14bfrkcreate
2017-07-31 00:49:42ghsetstatus: unknown -> given-up
2018-06-10 19:14:00ganeshsetmessages: + msg20151
2018-06-11 21:41:07bfrksetmessages: + msg20152
2018-06-13 18:23:15bfrksetmessages: + msg20155
2018-06-17 16:59:01ganeshsetstatus: given-up -> resolved
messages: + msg20165