git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Michal Suchánek'" <msuchanek@suse.de>
Cc: <git@vger.kernel.org>
Subject: RE: Need multibyte advice - Shift-JIS
Date: Wed, 27 Feb 2019 13:50:18 -0500	[thread overview]
Message-ID: <003301d4cecd$4bced250$e36c76f0$@nexbridge.com> (raw)
In-Reply-To: <20190227191814.054c2f3c@kitsune.suse.cz>

On February 27, 2019 13:18, Michal Suchánek wrote:
> On Wed, 27 Feb 2019 12:59:15 -0500
> "Randall S. Becker" <rsbecker@nexbridge.com> wrote:
> 
> > On February 27, 2019 12:51, Michal Suchánek wrote:
> > > To: Randall S. Becker <rsbecker@nexbridge.com>
> > > Cc: git@vger.kernel.org
> > > Subject: Re: Need multibyte advice - Shift-JIS
> > >
> 
> > I'm sorry if I was not clear about all this. NonStop is not a Linux platform. It
> is POSIX. Not all utilities are available and not all utilities have all capabilities.
> lv is not available for the platform. less considers the data binary and displays
> what usually is displayed when you try to use it for binary multibyte. You get
> @^@- and such. It does not present the data in the correct character set for
> the user.
> >
> > This was only one part of my original question. I am searching elsewhere
> for support on pagers, because this really is not an appropriate discussion for
> the git group to focus on, do let's drop this, please, as not worth continuing.
> My original request was more about how to set up the file attributes,
> difference engine, and the rest of the git infrastructure. The partner I am
> working with is doing this with git hooks, which I am not really happy about.
> Let's prune this discussion as not worthy.
> >
> 
> Yes, this is totally unclear. Setting git hooks is possible but setting
> LESSCHARDEF is not?
It can enter the environment simply through .profile, where we can change GIT_PAGER. We have established that separately.

> Is patching git acceptable or is that out of question too?
I have done a bunch of git patching, where specifically.

> What are your requirements, exactly?
Source code and comments contain SJIS content. The requirement is to be able to move seamlessly in and out of git, and have git show/diff/log display SJIS as well as ASCII content. How that happens is open. The UTF-16 is a red-herring, only as an attempt at getting at SJIS content differently than the limitation imposed by less.



  reply	other threads:[~2019-02-27 18:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 13:04 Need multibyte advice - Shift-JIS Randall S. Becker
2019-02-27 14:08 ` Michal Suchánek
2019-02-27 15:54   ` Randall S. Becker
2019-02-27 16:11     ` Michal Suchánek
2019-02-27 16:19       ` Randall S. Becker
2019-02-27 16:28         ` Michal Suchánek
2019-02-27 16:33           ` Randall S. Becker
2019-02-27 16:51             ` Michal Suchánek
2019-02-27 17:03               ` Randall S. Becker
2019-02-27 17:14                 ` Michal Suchánek
2019-02-27 17:38                   ` Randall S. Becker
2019-02-27 17:50                     ` Michal Suchánek
2019-02-27 17:59                       ` Randall S. Becker
2019-02-27 18:18                         ` Michal Suchánek
2019-02-27 18:50                           ` Randall S. Becker [this message]
2019-02-27 18:59                             ` Michal Suchánek
2019-02-27 19:36                             ` Johannes Sixt
2019-02-27 19:53                               ` Randall S. Becker

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='003301d4cecd$4bced250$e36c76f0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=msuchanek@suse.de \
    /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).