git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Abinsium <abinsium@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: `iconv` should have the encoding `ISO646-SE2`
Date: Thu, 26 Apr 2018 11:26:17 +0200 (DST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1804261125200.4978@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <6e8c0ae9-c699-6f39-014f-2008888722c8@gmail.com>

Hi Abinsium,

On Wed, 25 Apr 2018, Abinsium wrote:

> I installed from `Git-2.16.2-64-bit.exe` from git-scm.com. `iconv` is included
> in this package. I think `iconv` should have the encoding `ISO646-SE2`. Ubuntu
> 16.04 has this encoding. I use it to read old Swedish text files, which there
> are a lot of e.g.:
> `curl -s https://www.abc.se/programbanken/abc/abc80/asmkod/basicii.txt |
> dos2unix | iconv -f ISO646-SE2 -t UTF8 | less`
> `ISO646-SE2` is used by e.g. the retro-computers Luxor
> [ABC80](https://en.wikipedia.org/wiki/ABC_80) (1978) and
> [ABC800](https://en.wikipedia.org/wiki/ABC_800)-series (1981). At my
> university we only have Git Bash and not Ubuntu for WSL in Windows 10
> computers.
> 
> (Not clear where I should report this, but one should be able to report issues
> with the configuration of the other programs than `git` in the package
> somewhere. If there is a better place, please let me know.)
> Originally reported at https://github.com/git/git-scm.com/issues/1199

This has also been reported as
https://github.com/git-for-windows/git/issues/1655. I will comment there,
as this issue is really not relevant to Git.

Ciao,
Johannes

      reply	other threads:[~2018-04-26  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 12:32 `iconv` should have the encoding `ISO646-SE2` Abinsium
2018-04-26  9:26 ` Johannes Schindelin [this message]

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=nycvar.QRO.7.76.6.1804261125200.4978@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=abinsium@gmail.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.
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).