From: mehran khajavi <sinoohe.mkh@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Kenichi Handa <handa@m17n.org>
Subject: Re: Persian RTL problem
Date: Sun, 25 Sep 2011 21:07:56 +0330 [thread overview]
Message-ID: <CAF=P4s1C8ai8Rq2OHU9bS1MQKhc7dTZM2Lum-DvAhaMCb4M6Qg@mail.gmail.com> (raw)
In-Reply-To: <E1R7gmF-0002xN-Gy@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
wow great
it solved
but only with gtk+ screen, not from emacs -nw option!
any solution to get it work in terminal?!
On Sun, Sep 25, 2011 at 8:27 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Kenichi Handa <handa@m17n.org>
> > Cc: sinoohe.mkh@gmail.com, emacs-devel@gnu.org
> > Date: Sun, 25 Sep 2011 12:58:01 +0900
> >
> > For Arabic shaping, you need all of them; i.e. m17n-db,
> > m17n-lib, and libotf.
>
> Thanks.
>
> But I was mistaken in my previous mail: these libraries, if present,
> are mentioned in different Makefile variables than the one I asked
> about. Here's what I have in my src/Makefile:
>
> FREETYPE_CFLAGS = -I/usr/include/freetype2
> FREETYPE_LIBS = -lfreetype
> LIBOTF_CFLAGS = -I/usr/include/freetype2
> LIBOTF_LIBS = -lz -lotf -lfreetype
> M17N_FLT_CFLAGS =
> M17N_FLT_LIBS = -lm17n-flt -lm17n-core
>
> Please make sure you have this in your src/Makefile. If one or more
> of these variables are empty or mention only some of the libraries,
> config.log should tell you why the configure script didn't think they
> were available.
>
> You can see if GCC is able to find these libraries like this:
>
> gcc --print-file-name=libotf.a
>
> If GCC displays an absolute name in response to this command, it means
> it can find it during compilation. If it just repeats the name
> without leading directories, it cannot.
>
--
-----
Mehran Khajavi
http://mehran.khajavi.ir
[-- Attachment #2: Type: text/html, Size: 2116 bytes --]
next prev parent reply other threads:[~2011-09-25 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 14:32 Persian RTL problem mehran khajavi
2011-09-24 14:49 ` Eli Zaretskii
2011-09-24 15:06 ` mehran khajavi
2011-09-24 15:21 ` Eli Zaretskii
2011-09-25 3:58 ` Kenichi Handa
2011-09-25 4:57 ` Eli Zaretskii
2011-09-25 17:37 ` mehran khajavi [this message]
2011-09-25 18:06 ` Eli Zaretskii
2011-09-27 12:19 ` mehran khajavi
2011-09-27 14:16 ` mehran khajavi
2011-09-27 17:37 ` Eli Zaretskii
2011-09-28 17:50 ` 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='CAF=P4s1C8ai8Rq2OHU9bS1MQKhc7dTZM2Lum-DvAhaMCb4M6Qg@mail.gmail.com' \
--to=sinoohe.mkh@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).