From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: diagnostic character info (Re: [ANNOUNCEMENT] Updated: mintty 2.7.4)
Date: Tue, 07 Feb 2017 21:00:00 -0000 [thread overview]
Message-ID: <d80172a0-33d0-ef5e-f9db-35ccfeb47d2a@towo.net> (raw)
In-Reply-To: <bba687bb-b724-a7d2-2608-3bdc3af772ff@SystematicSw.ab.ca>
Am 07.02.2017 um 08:30 schrieb Brian Inglis:
> On 2017-02-06 12:46, Thomas Wolff wrote:
>> Am 05.02.2017 um 21:36 schrieb Brian Inglis:
>>> It may also be useful if mintty had some character hex value box
>>> display mode switch to display the actual codes at each visual
>>> position, or maybe a font used to display the character hex value in
>>> a box, often used in fonts as glyphs for non-printing control
>>> characters and those in the Private Use Area, in which case that could
>>> perhaps be added to the mintty package for use in testing.
>>> I have been searching for such a font with no success so far.
>> Hmm, ... it might be a nice feature.
> Displaying the character set codes passed to the console.
I'm preparing such an option. However, I plan to indicate the actual
Unicode characters effective on the cursor position (i.e. not the
multi-byte encoded characters).
> ...
> . Unicode BMP Fallback Font displays each character in the BMP as hex
> within a square box:
I don't see much purpose in using such a font because you won't easily
recognise your actual text anymore.
But if you want that for debugging, there's no specific mintty support
necessary for it.
Cheers
Thomas
> http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=UnicodeBMPFallbackFont
>
> . Unicode Last Resort font developed for Unicode on behalf of Apple
> displays the same representative glyph indicating its type within a
> thick rounded box for all characters of the same class or script; in
> large sizes the character type and range are visible within the box
> edges:
>
> http://unicode.org/policies/lastresortfont_eula.html
>
> . GNU Unifont provides low quality bitmapped style 8x16 or 16x16 fallback
> glyphs for all BMP characters and are working on increasing SMP support:
>
> https://savannah.gnu.org/projects/unifont
>
> Those interested can download, install, and check these out in Windows
> Charmap, using Group by Unicode Subrange, to see what they provide and
> how they could be used for diagnostic fallback.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-02-07 21:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 21:45 [ANNOUNCEMENT] Updated: mintty 2.7.4 Thomas Wolff
2017-02-04 16:13 ` Achim Gratz
2017-02-05 18:36 ` Thomas Wolff
2017-02-05 18:55 ` Achim Gratz
2017-02-06 19:16 ` Achim Gratz
2017-02-06 19:29 ` Thomas Wolff
2017-02-05 20:36 ` Brian Inglis
2017-02-06 19:46 ` Thomas Wolff
2017-02-07 1:03 ` Doug Henderson
2017-02-07 7:31 ` Brian Inglis
2017-02-07 20:52 ` Thomas Wolff
2017-02-08 2:17 ` Brian Inglis
2017-02-08 18:35 ` Achim Gratz
2017-02-08 22:52 ` Thomas Wolff
2017-02-09 19:37 ` Thomas Wolff
2017-02-09 19:42 ` Achim Gratz
2017-02-09 20:09 ` Thomas Wolff
2017-02-07 21:00 ` Thomas Wolff [this message]
2017-02-09 19:38 ` diagnostic character info (Re: [ANNOUNCEMENT] Updated: mintty 2.7.4) Thomas Wolff
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=d80172a0-33d0-ef5e-f9db-35ccfeb47d2a@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).