ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: tool for reviewing hyphenation
Date: Wed, 4 Feb 2009 09:56:24 +0100	[thread overview]
Message-ID: <6faad9f00902040056r40e2594bs504d123c4d9bdbd3@mail.gmail.com> (raw)
In-Reply-To: <49889E30.8050601@sil.org>

On Tue, Feb 3, 2009 at 8:42 PM, 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.

Which font do you use in the document?

I have an idea how to do it, but it may require changing the font. You
can either:
a) set hyphenchar to be whatever other character in the font (but it
has to be a numeric value between 0 and 255)
b) modify the font, so that hyphenchar becomes a big black box that
you can spot easily (even if it remains black; you can extend it to
become even bigger, you just need to make sure that the original
declared bounding box remains the same)

a) would be easiest to do, but only if you already have a suitable
character in the font for that purpose; which is most probably not the
case. I would most probably try to make a duplicate of the font and
try to change the hyphen character, though it's not necessary easy if
you don't have the right tools.

Maybe this will inspire someone else to propose some easier solution,
for example figureing out a way to make such constructs work:
\definefontcharacter 23 {\vrule width.5em} :) :) :)

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2009-02-04  8:56 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
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 [this message]
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=6faad9f00902040056r40e2594bs504d123c4d9bdbd3@mail.gmail.com \
    --to=mojca.miklavec.lists@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).