Saturday, November 3, 2018

Re: Indic fonts

On Sat, Nov 3, 2018 at 2:06 PM Rudra Banerjee <bnrj.rudra@gmail.com> wrote:
>
> Thanks for your reply. I would have love to make my hand dirty, except I have minimal idea of how the fonts are displayed. Like, I thought, it should not be a problem with encode=utf-8, but clearly ots not. As you said, probably due to fixed cell grid of vim.
> Being said that, I have started looking at how gedit has solved the problem. But most probably, they don't use fixed cell grid as vim/gvim.
> Anywhere to start? Can you give me any suggestions?
>
Knowing as little as I do about Indic writing, I would have a look at
some encyclopædic sources describing what they are and how they are
displayed, but maybe you can skip that, I don't know. I would also
have a look at which Unicode codepoints are available for Indic
scripts (see the third column of http://www.unicode.org/charts/ ) and
I might perhaps also have a look at src/arabic.c to see how Nadim
Shaikli solved the problem of rendering one single codepoint by one of
several glyphs depending on context — the latter might or might not
give inspiration to someone having (or wishing) to tackle the problem
of Indic scripts. Further than that, you're probably better placed
than I am to determine how to go about, considering that Mechelynck is
a Belgian family name (i.e. from a country where everything used to be
written in Latin script, though Greek, Cyrillic and Maghreb Arabic
scripts have made an apparition in the latest decades) while
Ban(n)erjee is an Indian one. ;-)

Best regards,
Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment