git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Łukasz Stelmach" <stlman@poczta.fm>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, "Stefan Beller" <sbeller@google.com>,
	"Pat Thoyts" <patthoyts@users.sourceforge.net>,
	"Łukasz Stelmach" <l.stelmach@samsung.com>
Subject: Re: [PATCH] git-gui: Prevent double UTF-8 conversion
Date: Sat, 02 Dec 2017 11:33:43 +0100	[thread overview]
Message-ID: <87k1y5mnaw.fsf%stlman@poczta.fm> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1711281524390.6482@virtualbox>

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

On Tue, 28 Nov 2017 15:35:21 +0100, Johannes Schindelin wrote:
> On Tue, 28 Nov 2017, Łukasz Stelmach wrote:

> > With encoding on the file descriptor set to "binary" Tcl (8.6 in my
> > case) does double conversion which breaks e.g. author name in amended
> > commits.
>
> Is the problem in question occurring when a commit message contains
> non-ASCII characters encoded in UTF-8 and you click the "Amend Last
> Commit" radio button on the right side above the "Commit Message" text
> box?

No, only with the author data. That means there is a difference in how
Tcl handles input in with "read" (the message) and "gets" (headers
including the author header).

Indeed! A few lines below the message is converted from utf-8 and author
is not. So the right thing to do is to convert author too and not change
the file descriptor settings.

I am going back to the drawing board. Thanks. 

-- 
Było mi bardzo miło.                                  --- Rurku. --- ...
>Łukasz<                                --- To dobrze, że mnie słuchasz.

[-- Attachment #2: Type: application/pgp-signature, Size: 617 bytes --]

  reply	other threads:[~2017-12-02 10:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20171128102138eucas1p116ae54d723bb100202fae2c1aaf5a9d8@eucas1p1.samsung.com>
2017-11-28 10:21 ` [PATCH] git-gui: Prevent double UTF-8 conversion Łukasz Stelmach
2017-11-28 14:35   ` Johannes Schindelin
2017-12-02 10:33     ` Łukasz Stelmach [this message]
2017-12-02 12:20   ` [PATCH v2] " Łukasz Stelmach
2017-12-04 14:31     ` Johannes Schindelin
     [not found]     ` <CGME20171205142341eucas1p2b30072c799c8787f1b66db2fd4bac1a2@eucas1p2.samsung.com>
2017-12-05 14:23       ` [PATCH v3] " Łukasz Stelmach
2017-12-07  0:06         ` Johannes Schindelin
     [not found]         ` <CGME20171214093300eucas1p28ed9bf0261a43a12978b6a3bfe908321@eucas1p2.samsung.com>
2017-12-14  9:32           ` [PATCH v4] " Łukasz Stelmach
2017-12-14  9:42             ` Eric Sunshine
     [not found]               ` <CGME20171214104348eucas1p2921cdc8df00c90055927ec99eba3040a@eucas1p2.samsung.com>
2017-12-14 10:43                 ` Łukasz Stelmach
2017-12-14 18:18                   ` Eric Sunshine
     [not found] <CGME20170821115329eucas1p1c550891b502863669ca351de028f2b80@eucas1p1.samsung.com>
2017-08-21 11:53 ` [PATCH] " Łukasz Stelmach
2017-08-21 18:52   ` Stefan Beller

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=87k1y5mnaw.fsf%stlman@poczta.fm \
    --to=stlman@poczta.fm \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=l.stelmach@samsung.com \
    --cc=patthoyts@users.sourceforge.net \
    --cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).