This repository has been archived by the owner on Sep 27, 2019. It is now read-only.
forked from khaledhosny/luaotfload
-
Notifications
You must be signed in to change notification settings - Fork 8
typographic quotes ligaturing with ? #397
Comments
If I comment out lines 1293 and 1294 in
the result of the test file
seems correct. Using |
By the way, also the ligatures
seem wrong; XeLaTeX doesn't do them. |
enabling tex ligatures appears to set up ligatures with
typographic quotes as well as the ascii ones which seems
unexpected.
[…]
By the way, also the ligatures
[0x201C] = {0x2018, 0x2018}, -- quotedblleft
[0x201D] = {0x2019, 0x2019}, -- quotedblright
seem wrong; XeLaTeX doesn't do them.
Very interesting! Btw. these have been in the “tlig” set for a
long time:
https://github.com/lualatex/luaotfload/blob/a34ba70ee4bf463c2ef499710bc319169c4d766b/otfl-font-otc.lua#L26
and frankly I’ve been wondering why. Does this come closer to
what you expect?
phi-gamma@7250ac9#diff-953368baba679fc9279c9cac25b74051L1291
Thanks,
Philipp
|
phi-gamma
added a commit
to phi-gamma/luaotfload
that referenced
this issue
Feb 7, 2017
V2 of 7250ac9 commit 7250ac9 Author: Philipp Gesang <[email protected]> Date: Thu Feb 2 07:38:03 2017 +0100 [features] remove unneeded tlig features Fix lualatex#397 These four features should not be inserted automatically. which was reverted in commit 9b70f2e Author: Philipp Gesang <[email protected]> Date: Mon Feb 6 21:21:48 2017 +0100 Revert "[features] remove unneeded tlig features" addressing issues lualatex#397, lualatex#405.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Originally a user question on stackexchange
http://tex.stackexchange.com/a/351436/1090
enabling tex ligatures appears to set up ligatures with typographic quotes as well as the ascii ones
which seems unexpected.
produces ¡ for both of lines 3 and 4, which is unexpected and differs from the equivalent tex mapping of xetex which only produces ¡ on line 4.
I'm using
David
The text was updated successfully, but these errors were encountered: