From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: Need multibyte advice - Shift-JIS
Date: Wed, 27 Feb 2019 08:04:08 -0500 [thread overview]
Message-ID: <001e01d4ce9c$eff07400$cfd15c00$@nexbridge.com> (raw)
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.
I normally do all of my UTF-16 work from a workstation via ECLIPSE, with
UTF-8 comments, so never really have encountered this as an issue. Although
our UTF-16 HTML files look pretty ugly in a diff.
The platform (NonStop) does not have a lot of UTF-16 tooling by default
(less does not support it), so I may have to write stuff, which is no issue.
We are on 2.21.0 officially as of yesterday.
Kind Regards,
Randall
-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next reply other threads:[~2019-02-27 13:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 13:04 Randall S. Becker [this message]
2019-02-27 14:08 ` Need multibyte advice - Shift-JIS 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
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='001e01d4ce9c$eff07400$cfd15c00$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.