From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: Making the malayalam rendering proper
Date: Tue, 27 May 2008 20:31:10 +0900 [thread overview]
Message-ID: <E1K0xOY-0003al-V7@etlken.m17n.org> (raw)
In-Reply-To: <57f75d610805270350p41018624v59022a20f6c84f40@mail.gmail.com> (aeshyamae@gmail.com)
In article <57f75d610805270350p41018624v59022a20f6c84f40@mail.gmail.com>, writes:
> In all unicode enabled gnu emacs that i tried, malayalam is rendered as a
> stream of unicode letters. Malayalam like other devanagari scripts, often
> requires to combine two characters(with two different glyphs) to display
> another glyph which represent the combination(complex script?)
> The picture attached,shows the difference in rendering of the same string in
> emacs and in gedit.The first one is made in emacs and the second bigger one
> in gedit.after developing some patches, Pango renders malayalam perfectly
> from version 1.20 onwards..
> How could this be made right.Where can i find more information about the
> rendering details of emacs?
> gpled fonts like the ones available from
> http://download.savannah.gnu.org/releases/smc/fonts/malayalam-fonts-04/
> are having sufficient glyphs to render malayalam perfectly..But this bug
> requires some work regarding rendering right?
Does your src/config.h contains these lines?
#define HAVE_LIBOTF 1
#define HAVE_M17N_FLT 1
If not, you must install libotf and libm17n-flt (see INSTALL
how to get them), and run configure again.
BTW, please send me the UTF-8 text you used in
emacs-rendering-difference.png.
---
Kenichi Handa
handa@ni.aist.go.jp
next parent reply other threads:[~2008-05-27 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57f75d610805270350p41018624v59022a20f6c84f40@mail.gmail.com>
2008-05-27 11:31 ` Kenichi Handa [this message]
2008-10-19 18:14 ` Rendering Fix progresses, Now Input-Method (Was:Re: Making the malayalam rendering proper) Shyam | ശ്യാം കാരനാട്ട് | Karanattu
2008-10-20 7:47 ` Kenichi Handa
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1K0xOY-0003al-V7@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).