public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: mintty overstrokes some fonts unexpectedly
Date: Sun, 25 Apr 2021 22:33:57 +0200	[thread overview]
Message-ID: <4660c89e-6cdd-1fda-f754-a9289f281ba3@towo.net> (raw)
In-Reply-To: <20210425224102.FF0E.50F79699@gmail.com>


Am 25.04.2021 um 15:41 schrieb Lemures Lemniscati via Cygwin:
> Hi!
>
> mintty overstrokes some fonts unexpectedly.
> https://gitlab.com/test.cases/mintty-test/-/tree/54ae800e695ecd1741851cab57320a9d0e95a6fd
>
>
> How to reproduce
>
> Setting mintty to use msgothic.ttc in 20pt, run a
> following command.
>
> ====
> perl -e '
> binmode STDOUT, ":utf8";
> print <<END;
> 01234567
> \x{3042}\x{3044}\x{3046}\x{3048}
> AaBbCcDe
> \x{25cb}\x{25cb}\x{25cb}\x{25cb}
> \x{3007}\x{3007}\x{3007}\x{3007}
> \x{300c}\x{300e}\x{3010}\x{3012}
> \x{300d}\x{300f}\x{3011}\x{3013}
> \x{ff62}\x{ff63}\x{ff62}\x{ff63}\x{ff62}\x{ff63}\x{ff62}\x{ff63}
> \x{ff71}\x{ff72}\x{ff73}\x{ff74}\x{ff75}\x{ff76}\x{ff77}\x{ff78}
> END
> '
> ====
>
>
> I got a result mintty-sample-msgothic.png.
> https://gitlab.com/test.cases/mintty-test/-/blob/54ae800e695ecd1741851cab57320a9d0e95a6fd/mintty-sample-msgothic.png
>
> In the 4th line of the output, fonts (of u+25cb) were overstruck
> unexpectedly.
> And there are other characters also, which are similarly overstruck.
This is a Windows bug. Mintty clearly instruct Windows to apply 
equidistant spacing to achieve fixed-width character cell behaviour. But 
for certain character ranges, Windows ignores that. Another example for 
such misbehaviour is the Tibetan block (U+0F00-U+0FFF). Mintty could 
work around that by rendering characters separately, at a significant 
penalty for output speed however. Or it could do that only for affected 
ranges, but criteria to identify them are obscure.
Thomas

  reply	other threads:[~2021-04-25 20:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 13:41 Lemures Lemniscati
2021-04-25 20:33 ` Thomas Wolff [this message]
2021-04-25 23:14   ` Lemures Lemniscati
2021-04-26 18:31     ` Thomas Wolff
2021-04-26 22:55       ` Lemures Lemniscati

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=4660c89e-6cdd-1fda-f754-a9289f281ba3@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).