Mon, 07 Jun 2010 16:29:06 +0200 merge with stable
Sune Foldager <cryo@cyanite.org> [Mon, 07 Jun 2010 16:29:06 +0200] rev 11300
merge with stable
Mon, 07 Jun 2010 16:28:23 +0200 push/pull: fix bug in "--branch ." handling stable
Sune Foldager <cryo@cyanite.org> [Mon, 07 Jun 2010 16:28:23 +0200] rev 11299
push/pull: fix bug in "--branch ." handling The branch wasn't expanded, so only the tip was operated on.
Sun, 06 Jun 2010 22:39:32 +0530 shrink-repo: wrong variable name
Pradeepkumar Gayam <in3xes@gmail.com> [Sun, 06 Jun 2010 22:39:32 +0530] rev 11298
shrink-repo: wrong variable name
Sun, 06 Jun 2010 17:20:10 +0900 replace Python standard textwrap by MBCS sensitive one for i18n text
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Sun, 06 Jun 2010 17:20:10 +0900] rev 11297
replace Python standard textwrap by MBCS sensitive one for i18n text Mercurial has problem around text wrapping/filling in MBCS encoding environment, because standard 'textwrap' module of Python can not treat it correctly. It splits byte sequence for one character into two lines. According to unicode specification, "east asian width" classifies characters into: W(ide), N(arrow), F(ull-width), H(alf-width), A(mbiguous) W/N/F/H can be always recognized as 2/1/2/1 bytes in byte sequence, but 'A' can not. Size of 'A' depends on language in which it is used. Unicode specification says: If the context(= language) cannot be established reliably they should be treated as narrow characters by default but many of class 'A' characters are full-width, at least, in Japanese environment. So, this patch treats class 'A' characters as full-width always for safety wrapping. This patch focuses only on MBCS safe-ness, not on writing/printing rule strict wrapping for each languages MBCS sensitive textwrap class is originally implemented by ITO Nobuaki <daydream.trippers@gmail.com>.
(0) -10000 -3000 -1000 -300 -100 -30 -10 -4 +4 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip