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 10:54:23 -0500 [thread overview]
Message-ID: <000001d4ceb4$b930df50$2b929df0$@nexbridge.com> (raw)
In-Reply-To: <20190227150836.495f1692@kitsune.suse.cz>
On February 27, 2019 9:09, Michal Suchánek wrote:
> On Wed, 27 Feb 2019 08:04:08 -0500
> "Randall S. Becker" <rsbecker@nexbridge.com> wrote:
>
> > Hi Git Team,
> >
> > I have to admit being perplexed by this one. I have been asked to
> > support the Shift-JIS character set in file contents, comments, and
> > logs, for a partner of mine. I know there are a few ways to do this,
> > but I'm looking for the official non-hacky way to do this. This is CLI
> > only, and our pager, less, does not support multi-byte, so I'm looking
for
> options there also.
>
> SJIS is about as much multibyte as UTF-8.
>
> Why do you think less does not support it?
>
> Last time I looked there was SJIS locale for libc so it is only matter of
> generating the correct locales and using them. Of course, if you are
running
> in UTF-8 SJIS will look like garbage.
Sadly, I did not personally build less on this platform, and the libc used
did not include UTF-16, on the platform vendor supplied less. cat works
fine, but the usual LESSCHARSET=utf-16 is unsupported, so I am looking for
an alternative. THAT is why I think less does not support it. Sorry, I
should have made that more clear.
cat works fine, so if I set GIT_PAGER=cat, I can at least see the diffs
cleanly in SJIS, but this partner wants a pager that is usable.
next prev parent reply other threads:[~2019-02-27 15:54 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 [this message]
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
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='000001d4ceb4$b930df50$2b929df0$@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).