On 2014-06-30 11:40, vanadovv@hetnet.nl wrote:
In reply to: [tz] [PATCH] More spelling and accent fixes. Paul Eggert eggert at CS.UCLA.EDU Fri Jun 27 23:06:47 UTC 2014 A small problem regarding the transition to UTF-8. Let me refer to a copy of some text from the diff, sent through the mailing list: @@ -383,7 +383,7 @@ Zone Asia/Chongqing 7:06:20 - LMT 1928 # or Chungking # Wusu, Qiemo, Xinyan, Wulanwusu, Jinghe, Yumin, Tacheng, Tuoli, Emin, # Shihezi, Changji, Yanqi, Heshuo, Tuokexun, Tulufan, Shanshan, Hami, # Fukang, Kuitun, Kumukuli, Miquan, Qitai, and Turfan. -Zone Asia/Urumqi 5:50:20 - LMT 1928 # Ãœrümqi or Urumchi +Zone Asia/Urumqi 5:50:20 - LMT 1928 # Ãœrümqi or Ãœrümchi The correct spelling of the Asian city at hand is Ürümchi, with two u-diaeresis. The github asia file has the correct spelling and the correct encoding. The diff file however gets mangled by some publishing process. Hence, the diff published through the mailing list is rather useless. I have a lot of text encoding conversion filters, but noone is able to decode the mangled "Ãœrümqi". It looks to me like a doubly UTF-8 encoded piece of text. Perhaps something to look into? Oscar van Vlijmen
I think the lack of MIME headers in Paul's email is the reason why. When I tried emailing the same patch to myself using git send-email, I got prompted to specify an 8-bit encoding as follows: The following files are 8bit, but do not declare a Content-Transfer-Encoding. /tmp/8jzhF_MOTQ/0001-More-spelling-and-accent-fixes.patch Which 8bit encoding should I declare [UTF-8]? It can also be specified on the command line of git send-email using the '--8bit-encoding=<encoding>' option, or specified in the git configuration in the 'sendmail.assume8bitEncoding' option. -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-