ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Lars Huttar <lars_huttar@sil.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: tool for reviewing hyphenation
Date: Tue, 03 Feb 2009 15:03:31 -0600	[thread overview]
Message-ID: <4988B123.3040208@sil.org> (raw)
In-Reply-To: <4988A782.8080407@wxs.nl>

On 2/3/2009 2:22 PM, Hans Hagen wrote:
> Lars Huttar wrote:
>> On 2/3/2009 1:29 PM, Hans Hagen wrote:
>>> Lars Huttar wrote:
>>>
>>>> But the hyphenation is by nature somewhat volatile, so whenever we
>>>> change something we would like to be able to easily recheck the
>>>> hyphenation.
>>>> And our book is over 1200 pages, so it would be very helpful to have
>>>> tools to make the checking more efficient.
>>> so, you only want to highlight hyphens?
>>
>> Yes. Especially hyphens introduced by TeX for line-breaking.
> 
> in mkiv it probably takes me a couple of hours to implement such a feature
> 
> Hans


Unfortunately at this point I believe we are restricted to mkii.


However, I have made progress implementing a tool like this in Adobe
javascript. The obstacle I am facing now is that the PDF (produced by
xdvipdfmx) is not configured to allow Adobe Reader users to manipulate
comments; thus my js code to add highlighting throws an exception.
If we had an Adobe Acrobat license it probably would not be a problem;
but our current reality is that we don't.
Does anyone know how to tell xdvipdfmx to enable commenting rights in
the PDF it creates? Or how to add these rights afterwards, without Adobe
Acrobat?

Thanks,
Lars


___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-02-03 21:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 17:00 Lars Huttar
2009-02-03 19:29 ` Hans Hagen
2009-02-03 19:42   ` Lars Huttar
2009-02-03 20:22     ` Hans Hagen
2009-02-03 21:03       ` Lars Huttar [this message]
2009-02-03 21:53         ` Martin Schröder
2009-02-03 22:20           ` Lars Huttar
2009-02-03 22:27             ` Hans Hagen
2009-02-03 22:44               ` Lars Huttar
2009-02-03 23:13                 ` Hans Hagen
2009-02-04  9:10           ` Alan BRASLAU
2009-02-04 16:16             ` Lars Huttar
2009-02-04 18:08               ` Alan BRASLAU
2009-02-04 21:41                 ` Lars Huttar
2009-02-04  8:56     ` Mojca Miklavec
2009-02-04  9:03       ` Hans Hagen
2009-02-04  9:11         ` Mojca Miklavec
2009-02-04 18:47 Alan BRASLAU

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=4988B123.3040208@sil.org \
    --to=lars_huttar@sil.org \
    --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).