From: Jiri Slaby <jirislaby@kernel.org>
To: Nicolas Pitre <nico@fluxnic.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Nicolas Pitre <npitre@baylibre.com>, Dave Mielke <Dave@mielke.cc>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 03/11] vt: properly support zero-width Unicode code points
Date: Mon, 14 Apr 2025 08:51:15 +0200 [thread overview]
Message-ID: <7fce92da-62d3-421d-9cd1-f9167c05d2b0@kernel.org> (raw)
In-Reply-To: <20250410011839.64418-4-nico@fluxnic.net>
On 10. 04. 25, 3:13, Nicolas Pitre wrote:
> From: Nicolas Pitre <npitre@baylibre.com>
>
> Zero-width Unicode code points are causing misalignment in vertically
> aligned content, disrupting the visual layout. Let's handle zero-width
> code points more intelligently.
...
> --- a/drivers/tty/vt/vt.c
> +++ b/drivers/tty/vt/vt.c
> @@ -443,6 +443,15 @@ static void vc_uniscr_scroll(struct vc_data *vc, unsigned int top,
> }
> }
>
> +static u32 vc_uniscr_getc(struct vc_data *vc, int relative_pos)
> +{
> + int pos = vc->state.x + vc->vc_need_wrap + relative_pos;
> +
> + if (vc->vc_uni_lines && pos >= 0 && pos < vc->vc_cols)
So that is:
in_range(pos, 0, vc->vc_cols)
right?
> + return vc->vc_uni_lines[vc->state.y][pos];
> + return 0;
> +}
> +
> static void vc_uniscr_copy_area(u32 **dst_lines,
> unsigned int dst_cols,
> unsigned int dst_rows,
> @@ -2905,18 +2914,49 @@ static bool vc_is_control(struct vc_data *vc, int tc, int c)
> return false;
> }
>
> +static void vc_con_rewind(struct vc_data *vc)
> +{
> + if (vc->state.x && !vc->vc_need_wrap) {
> + vc->vc_pos -= 2;
> + vc->state.x--;
> + }
> + vc->vc_need_wrap = 0;
> +}
> +
> static int vc_con_write_normal(struct vc_data *vc, int tc, int c,
> struct vc_draw_region *draw)
> {
> - int next_c;
> + int next_c, prev_c;
> unsigned char vc_attr = vc->vc_attr;
> u16 himask = vc->vc_hi_font_mask, charmask = himask ? 0x1ff : 0xff;
> u8 width = 1;
> bool inverse = false;
>
> if (vc->vc_utf && !vc->vc_disp_ctrl) {
> - if (ucs_is_double_width(c))
> + if (ucs_is_double_width(c)) {
> width = 2;
> + } else if (ucs_is_zero_width(c)) {
> + prev_c = vc_uniscr_getc(vc, -1);
> + if (prev_c == ' ' &&
> + ucs_is_double_width(vc_uniscr_getc(vc, -2))) {
> + /*
> + * Let's merge this zero-width code point with
> + * the preceding double-width code point by
> + * replacing the existing whitespace padding.
> + */
> + vc_con_rewind(vc);
> + } else if (c == 0xfe0f && prev_c != 0) {
> + /*
> + * VS16 (U+FE0F) is special. Let it have a
> + * width of 1 when preceded by a single-width
> + * code point effectively making the later
> + * double-width.
> + */
> + } else {
> + /* Otherwise zero-width code points are ignored */
> + goto out;
> + }
> + }
Please, extract this width evaluation to a separate function.
...
> --- a/include/linux/consolemap.h
> +++ b/include/linux/consolemap.h
...
> @@ -63,6 +68,11 @@ static inline bool ucs_is_double_width(uint32_t cp)
> {
> return false;
> }
> +
> +static inline bool ucs_is_zero_width(uint32_t cp)
> +{
> + return false;
> +}
Again, is this necessary?
thanks,
--
js
suse labs
next prev parent reply other threads:[~2025-04-14 6:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 1:13 [PATCH 00/11] vt: implement proper Unicode handling Nicolas Pitre
2025-04-10 1:13 ` [PATCH 01/11] vt: minor cleanup to vc_translate_unicode() Nicolas Pitre
2025-04-10 1:13 ` [PATCH 02/11] vt: move unicode processing to a separate file Nicolas Pitre
2025-04-14 6:47 ` Jiri Slaby
2025-04-15 19:03 ` Nicolas Pitre
2025-04-10 1:13 ` [PATCH 03/11] vt: properly support zero-width Unicode code points Nicolas Pitre
2025-04-14 6:51 ` Jiri Slaby [this message]
2025-04-15 19:06 ` Nicolas Pitre
2025-04-10 1:13 ` [PATCH 04/11] vt: introduce gen_ucs_width.py to create ucs_width.c Nicolas Pitre
2025-04-14 7:04 ` Jiri Slaby
2025-04-15 19:13 ` Nicolas Pitre
2025-04-10 1:13 ` [PATCH 05/11] vt: update ucs_width.c using gen_ucs_width.py Nicolas Pitre
2025-04-11 3:47 ` kernel test robot
2025-04-10 1:13 ` [PATCH 06/11] vt: introduce gen_ucs_recompose.py to create ucs_recompose.c Nicolas Pitre
2025-04-14 7:08 ` Jiri Slaby
2025-04-10 1:13 ` [PATCH 07/11] vt: create ucs_recompose.c using gen_ucs_recompose.py Nicolas Pitre
2025-04-11 6:00 ` kernel test robot
2025-04-10 1:14 ` [PATCH 08/11] vt: support Unicode recomposition Nicolas Pitre
2025-04-10 1:14 ` [PATCH 09/11] vt: update gen_ucs_width.py to produce more space efficient tables Nicolas Pitre
2025-04-14 7:14 ` Jiri Slaby
2025-04-15 19:16 ` Nicolas Pitre
2025-04-10 1:14 ` [PATCH 10/11] vt: update ucs_width.c following latest gen_ucs_width.py Nicolas Pitre
2025-04-14 7:17 ` Jiri Slaby
2025-04-10 1:14 ` [PATCH 11/11] vt: pad double-width code points with a zero-white-space Nicolas Pitre
2025-04-14 7:18 ` Jiri Slaby
2025-04-10 19:38 ` [PATCH 12/11] vt: remove zero-white-space handling from conv_uni_to_pc() Nicolas Pitre
2025-04-11 14:49 ` [PATCH 00/11] vt: implement proper Unicode handling Greg Kroah-Hartman
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=7fce92da-62d3-421d-9cd1-f9167c05d2b0@kernel.org \
--to=jirislaby@kernel.org \
--cc=Dave@mielke.cc \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=npitre@baylibre.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