|
From: | Roumen Petrov |
Subject: | Re: changing default handling of line graphics mode |
Date: | Sat, 20 Jan 2018 18:55:40 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30 |
Mike Frysinger wrote:
On 19 Jan 2018 04:33, Thomas Dickey wrote:----- Original Message ----- | From: "Mike Frysinger" <address@hidden> | To: address@hidden | Sent: Thursday, January 18, 2018 10:56:29 PM | Subject: changing default handling of line graphics mode | [SNIP] | + } else if (_nc_unicode_locale()) | + result = 1; | + } else if (_nc_unicode_locale()) | + result = 1; | returnCode(result); | }
Hmm,In method _nc_locale_breaks_acs logic to assume broken alternate character set if unicode is not correct.
Why modernization of terminal. Proposed modification look like to introduce defect into ncurses.why should I add a bug to ncurses, to compensate for others' defects?i don't see how trying to modernize terminals is a bug.
if you know the locale supports UTF-8 (and ncurses knows this), then why is it a bug for ncurses to stick with only UTF-8 vs switching in/out of legacy encodings ?
And what if terminal supports "percent" escape sequence?
seems to me it makes the system less complicated and more robust. it's certainly simpler to write a single UTF-8 codepoint than to juggle GL pointers via escape sequences. -mike
Roumen
[Prev in Thread] | Current Thread | [Next in Thread] |