unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Wolfgang Jenkner <wjenkner@inode.at>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Help with Tamil (Indic) font (Emacs from bzr)
Date: Wed, 16 Jan 2013 18:25:10 +0100	[thread overview]
Message-ID: <8538y19h1l.fsf@iznogoud.viz> (raw)
In-Reply-To: 87ip6x5ffp.fsf@gmail.com

On Wed, Jan 16 2013, Jambunathan K wrote:

> The attached screenshot shows the difference in behaviour between Emacs
> launched from Bzr (trunk) and Emacs23 that is distributed with Debian
> itself.  The character that is shown is the one you get by typing "ki"
> in tamil-itrans.
>
> You will note following differences:
>
> 1. Emacs23 uses Lohit font while EmacsBzr picks up gnu-unifont.
> 2. Emacs23 "composes" the glyphs correctly while EmacsBzr messes up the
>    display.


Please take a look at

src/config.h

and check that these lines

    /* Define to 1 if using libm17n-flt. */
    #define HAVE_M17N_FLT 1

    /* Define to 1 if using libotf. */
    #define HAVE_LIBOTF 1

are present.  If not see 

* Complex Text Layout support libraries

in the INSTALL file in the emacs top-level directory.  Given that this
works in your distro's emacs 23 you should already have the necessary
libraries, but perhaps they are too old or configure can't find them
(config.log should give a clue).

Wolfgang




  parent reply	other threads:[~2013-01-16 17:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 15:13 Help with Tamil (Indic) font (Emacs from bzr) Jambunathan K
2013-01-16 15:33 ` Andreas Schwab
2013-01-16 15:42   ` Jambunathan K
2013-01-16 17:59     ` Andreas Schwab
2013-01-16 17:25 ` Wolfgang Jenkner [this message]
2013-01-16 19:06   ` Jambunathan K
2013-01-16 19:20     ` Wolfgang Jenkner
2013-01-16 21:18       ` Jambunathan K
2013-01-17  1:39         ` Stephen J. Turnbull
2013-01-16 19:22     ` Eli Zaretskii

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=8538y19h1l.fsf@iznogoud.viz \
    --to=wjenkner@inode.at \
    --cc=emacs-devel@gnu.org \
    --cc=kjambunathan@gmail.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.
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).