From: Deepak Jois <deepak.jois@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Urdu with NotoNastaliqUrdu-Regular.ttf
Date: Sat, 28 Nov 2015 17:19:14 +0530 [thread overview]
Message-ID: <CABR1-XakoPy85bkqEscQ-unGB18i1_8E1MPe2Lzd8-6S_94d-A@mail.gmail.com> (raw)
In-Reply-To: <56598149.3080507@wxs.nl>
On Sat, Nov 28, 2015 at 3:56 PM, Hans Hagen <pragma@wxs.nl> wrote:
> something cursive but anyhow, there us no urdu language (dflt has to be
> used)
I reported the bug originally. I changed the fontspec directive in my
test file to not specify the language. I got a better output, but
still pretty bad.
Details w/ screenshot:
https://github.com/lualatex/luaotfload/issues/292#issuecomment-160283333
Deepak
PS: Btw fontspec does not complain about the language. In XeTeX, my
experience has been that if a language is not present, it logs a
message to stdout. I am not sure if fontspec on LuaLaTeX has the same
behavior, but I did not see a message complaining about language.
Also, here is the otfinfo output:
$> otfinfo -s NotoNastaliqUrdu-Regular.ttf
arab Arabic
arab.ARA Arabic/Arabic
arab.FAR Arabic/Farsi
arab.KSH Arabic/Kashmiri
arab.SND Arabic/Sindhi
arab.URD Arabic/Urdu
dflt <unknown script>
latn Latin
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-11-28 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 21:56 Philipp Gesang
2015-11-28 10:26 ` Hans Hagen
2015-11-28 11:49 ` Deepak Jois [this message]
2015-11-28 19:02 ` Hans Hagen
2015-11-29 1:36 ` Deepak Jois
2015-11-29 3:38 ` Deepak Jois
2015-11-29 10:09 ` Hans Hagen
2015-11-29 10:12 ` Hans Hagen
2015-11-29 11:46 ` Hans Hagen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABR1-XakoPy85bkqEscQ-unGB18i1_8E1MPe2Lzd8-6S_94d-A@mail.gmail.com \
--to=deepak.jois@gmail.com \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).