From: Tuomas Ahola <taahol@utu.fi>
To: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Justin Tobler <jltobler@gmail.com>,
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>,
K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
Subject: Re: [GSoC Patch 0/2] add unicode support to git repo structure
Date: Sun, 23 Aug 2026 20:06:45 +0300 [thread overview]
Message-ID: <20260823170645.rBeci%taahol@utu.fi> (raw)
In-Reply-To: <aorzcZVdCK27pdjG@ugly.lan>
Oswald Buddenhagen <oswald.buddenhagen@gmx.de> wrote:
> i can instantly think of two popular applications i'm using every day
> which use box drawing chars: mutt (thread and attachment tree displays)
> and midnight commander (panel/dialog frames). if "often" above were
> accurate, these projects would be getting a lot of complaints about
> that, which they don't.
>
Hmm, mutt seems to use ACS (alternative character set) as a fallback option:
```
else if (Charset_is_utf8)
addstr("\342\224\224"); /* WACS_LLCORNER */
else
addch(ACS_LLCORNER);
```
How relevant that is to us, I don't know, but perhaps something to think about.
--
Tuomas
prev parent reply other threads:[~2026-08-23 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 13:53 [GSoC Patch 0/2] add unicode support to git repo structure K Jayatheerth
2026-08-21 13:53 ` [GSoC Patch 1/2] gettext: fall back to env-derived charset when unset K Jayatheerth
2026-08-21 13:53 ` [GSoC Patch 2/2] repo: add Unicode support for `repo structure` output K Jayatheerth
2026-08-21 16:59 ` [GSoC Patch 0/2] add unicode support to git repo structure Junio C Hamano
2026-08-23 13:19 ` Oswald Buddenhagen
2026-08-23 15:01 ` Junio C Hamano
2026-08-23 17:06 ` Tuomas Ahola [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260823170645.rBeci%taahol@utu.fi \
--to=taahol@utu.fi \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jayatheerthkulkarni2005@gmail.com \
--cc=jltobler@gmail.com \
--cc=lucasseikioshiro@gmail.com \
--cc=oswald.buddenhagen@gmx.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 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.