From: Philipp Gesang <Philipp.Gesang@alumni.uni-heidelberg.de>
To: ntg-context@ntg.nl
Subject: Re: copy&paste from pdf bug (smallcaps, text figures)
Date: Fri, 2 Aug 2013 00:12:37 +0200 [thread overview]
Message-ID: <20130801221237.GB29570@phlegethon> (raw)
In-Reply-To: <20130801220108.GD8003@homerow>
[-- Attachment #1.1: Type: text/plain, Size: 1786 bytes --]
···<date: 2013-08-02, Friday>···<from: Marco Patzer>···
> On 2013–08–01 Philipp Gesang wrote:
>
> > ···<date: 2013-08-01, Thursday>···<from: Otared Kavian>···
> >
> > > I tested your example: no problem here on Mac OS X 10.8.4, with
> > > either TeXShop, Adobe Redaer or Preview, with the latest beta
> > > (ConTeXt ver: 2013.08.01 01:31 MKIV beta fmt: 2013.8.1 int:
> > > english/english).
> >
> > x64 linux here, but it’s the same with the windows version in
> > wine32. I get the bad output with okular (poppler), acroread, and
> > mupdf, but strangely not with zathura (mupdf-based).
>
> Just to add to the list:
>
> x64 linux here, and it works with the following poppler based
> viewers (zathura-poppler, xpdf, evince)
For those who want to test the git version, the commits are:
last good: a61813ccdd4b7bcc81932317e1360fda6c79962d
first bad: 6b2f7c5fd7a3e465f4e2662b1e5bd2c9d5cce8f8
Don’t forget to delete the cache.
I suspect I found the troublesome changes. The problem vanishes
if I revert this modification to font-map.lua:
-local separator = S("_.")
-local other = C((1 - separator)^1)
-local ligsplitter = Ct(other * (separator * other)^0)
+local ligseparator = P("_")
+local varseparator = P(".")
+local namesplitter = Ct(C((1 - ligseparator - varseparator)^1) * (ligseparator * C((1 - ligseparator - varseparator)^1))^0)
and then further down:
- local split = lpegmatch(ligsplitter,name)
<...>
+ local split = lpegmatch(namesplitter,name)
For convenience I repeat the link to the changeset:
http://repo.or.cz/w/context.git/commitdiff/6b2f7c5fd7a3e465f4e2662b1e5bd2c9d5cce8f8
Best,
Philipp
[-- Attachment #1.2: Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2013-08-01 22:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 17:33 Philipp Gesang
2013-08-01 20:23 ` Otared Kavian
2013-08-01 21:46 ` Philipp Gesang
2013-08-01 22:01 ` Marco Patzer
2013-08-01 22:12 ` Philipp Gesang [this message]
2013-08-02 11:09 ` Hans Hagen
2013-08-02 11:37 ` Philipp Gesang
2013-08-02 12:02 ` Marco Patzer
2013-08-02 12:28 ` Philipp Gesang
2013-08-02 14:59 ` Hans Hagen
2013-08-02 15:56 ` Philipp Gesang
2013-08-02 16:04 ` Arthur Reutenauer
2013-08-02 18:21 ` Philipp Gesang
2013-08-01 21:38 ` Marco Patzer
2013-08-01 22:08 ` Jannik Voges
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=20130801221237.GB29570@phlegethon \
--to=philipp.gesang@alumni.uni-heidelberg.de \
--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).