How to reproduce:
vim-8.1.0342 in the xfce4 terminal on FreeBSD-11.2
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
This is due to the fact that in Vim, one character is one screen cell (or two cells for a "wide" East-Asian character). Now the basmala ligature U+FDFD is one "character" in the Vim sense of the word, but it corresponds to a lot of Arabic "letters", viz. (in some crude Latin letter-for-letter transliteration omitting harakat) bsm allh alrhmn alrhym. There's no way you can pack all this into the screen space meant for one letter and still make it understandable. Browsers, OTOH, use variable-length fonts, especially for highly cursive fonts like Arabic, and they will expand the basmala glyph to use any width it needs.
But don't worry, if you hit ga on that "unreadable" glyph in Vim and it tells you that (in UTF-8 'encoding') it has hex value FDFD, then it is indeed the basmala ligature, even though it is not recognizable in Vim.
Best regards,
Tony.
one character is one screen cell (or two cells for a "wide" East-Asian character)
Why doesn't vim expand this, and allow other characters to occupy two cells, or perhaps 3 cells too?
Mostly history of Vim, and the use of monospace fonts. Vim is not a WYSIWYG text processor, remember, but a plain text editor, which ultimately dates from the time when multi-language was in its infancy, Arabic script rendering was unknown, Chinese was possible but largely reserved to East-Asian editions of the OS. I saw the first steps of the Arabic-in-Unicode module of Vim a few years ago, and AFAIK it still doesn't support Indian-subcontinent scripts like the Devanagari script used for Hindi.
Best regards,
Tony.
A possible workaround is to manually insert ~10 spaces after Basmala character. Unless you're programming in Whitespace, you should be fine.
Basmala isn't the only extra-wide Unicode characters. There also
Maybe Vim can insert "virtual non-existent spaces" (something like :tabstop) after such characters?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()