git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
	"Christophe Simonis" <christophe@kn.gl>,
	"\"tbo >> Torsten Bögershausen\"" <tboegi@web.de>
Subject: Re: [PATCH v2 6/7] remote-bzr: add utf-8 support for fetching
Date: Mon, 08 Apr 2013 21:39:30 +0200	[thread overview]
Message-ID: <51631CF2.5090503@web.de> (raw)
In-Reply-To: <1365442036-25732-7-git-send-email-felipe.contreras@gmail.com>

On 08.04.13 19:27, Felipe Contreras wrote:
> From: Christophe Simonis <christophe@kn.gl>
> 
> Initial patch by Timotheus Pokorra.
> 
> [fc: added tests]
> 
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
>  contrib/remote-helpers/git-remote-bzr | 15 +++++++++------
>  contrib/remote-helpers/test-bzr.sh    | 32 ++++++++++++++++++++++++++++++++
>  2 files changed, 41 insertions(+), 6 deletions(-)
> 
> +
> +  export LC_ALL=en_US.UTF-8
> +
> +  (
> +  bzr init bzrrepo &&
> +  cd bzrrepo &&
> +
> +  echo test >> "áéíóú" &&
> +  bzr add "áéíóú" &&

Just a whish from my side:
bzr under MacOS is not able to handle some unicode characters correctly.
(Those we can decompose)
https://bugs.launchpad.net/bzr/+bug/172383

I just added a fix on the test-bzr script we have on git.git/next,
and the short version is to avoid all code points like áéíóú.
The greek stuff is probably OK, but the accents are not.
I choose a danish/norwegian "æ", which is not decomposable.
(And the non-portable echo -e could be avoided by using printf)
/Torsten
 

git diff git.git/next
diff --git a/contrib/remote-helpers/test-bzr.sh b/contrib/remote-helpers/test-bzr.sh
index f4c7768..2150e7c 100755
--- a/contrib/remote-helpers/test-bzr.sh
+++ b/contrib/remote-helpers/test-bzr.sh
@@ -175,8 +175,8 @@ test_expect_success 'fetch utf-8 filenames' '
   bzr init bzrrepo &&
   cd bzrrepo &&
 
-  echo test >> "áéíóú" &&
-  bzr add "áéíóú" &&
+  echo test >> "æ" &&
+  bzr add "æ" &&
   bzr commit -m utf-8
   ) &&
 
@@ -185,8 +185,7 @@ test_expect_success 'fetch utf-8 filenames' '
   cd gitrepo &&
   git ls-files > ../actual
   ) &&
-  echo "\"\\303\\241\\303\\251\\303\\255\\303\\263\\303\\272\"" > expected &&
+  echo "\"\\303\\246\"" > expected &&
   test_cmp expected actual
 '
 
@@ -209,15 +208,15 @@ test_expect_success 'push utf-8 filenames' '
   git clone "bzr::$PWD/bzrrepo" gitrepo &&
   cd gitrepo &&
 
-  echo test >> "áéíóú" &&
-  git add "áéíóú" &&
+  echo test >> "æ" &&
+  git add "æ" &&
   git commit -m utf-8 &&
 
   git push
   ) &&
 
   (cd bzrrepo && bzr ls > ../actual) &&
-  echo -e "content\náéíóú" > expected &&
+  printf "content\n\303\246\n" > expected &&
   test_cmp expected actual
 '
 

  reply	other threads:[~2013-04-08 19:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 17:27 [PATCH v2 0/7] remote-bzr: generic updates Felipe Contreras
2013-04-08 17:27 ` [PATCH v2 1/7] remote-bzr: fix directory renaming Felipe Contreras
2013-04-08 17:27 ` [PATCH v2 2/7] remote-bzr: remove files before modifications Felipe Contreras
2013-04-08 17:27 ` [PATCH v2 3/7] remote-bzr: set author if available Felipe Contreras
2013-04-08 17:27 ` [PATCH v2 4/7] remote-bzr: only update workingtree on local repos Felipe Contreras
2013-04-08 17:27 ` [PATCH v2 5/7] remote-bzr: improve tag handling Felipe Contreras
2013-04-08 17:27 ` [PATCH v2 6/7] remote-bzr: add utf-8 support for fetching Felipe Contreras
2013-04-08 19:39   ` Torsten Bögershausen [this message]
2013-04-08 17:27 ` [PATCH v2 7/7] remote-bzr: add utf-8 support for pushing Felipe Contreras
2013-04-08 18:26 ` [PATCH v2 0/7] remote-bzr: generic updates Junio C Hamano
2013-04-08 18:38   ` Felipe Contreras
2013-04-08 19:00     ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51631CF2.5090503@web.de \
    --to=tboegi@web.de \
    --cc=christophe@kn.gl \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).