ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [OT] Full-width justification (xkcd)
Date: Mon, 9 May 2016 12:02:26 +0200	[thread overview]
Message-ID: <60978dbe-ae0c-d0dd-d5e0-b5258564e51c@wxs.nl> (raw)
In-Reply-To: <5067E2AA-F6FB-429C-BC2F-A48BC313C473@elvenkind.com>

On 5/9/2016 11:12 AM, Taco Hoekwater wrote:
> Hi,
>
>> Mojca:
>> Wasn't in obvious that I was joking?
>> (Even though deep down I feared someone would reply with "here it is”.)
>
> I actually thought about doing just that ;) But it will take more work
> than is justified for simply an email reply. And it is a nice teaching
> opportunity, so we plan to get back on this topic during the upcoming
> ConTeXt meeting in Kalenberg.
>
>
>> Luigi:
>> metapost ,head-body-tail or tail-body-head for the filler, lenght of the snake
>> node programming...not bad.
>> I could be useful when one has numbers, and wants to be sure that nobody prepend or append something.
>
> Actually I had a use case for this some years back when I was attempting
> to reproduce old-fashioned woodblock print. But that predated most luatex
> development, and I ended up faking the whole thing using \hboxes.

there's actually already quite some in place to deal with such issues 
but the question often is what criteria to use and what interfacing and 
for criteria you need to know a bit about what a line is internally in 
terms of spacing ... i'm pretty sure that Taco will cover that aspect 
but you have to wait till Kalenberg to learn the details

Hans




-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2016-05-09 10:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09  7:41 Mojca Miklavec
2016-05-09  8:28 ` Hans Hagen
2016-05-09  8:42   ` Mojca Miklavec
2016-05-09  8:51     ` Hans Hagen
2016-05-09 15:15       ` Alan BRASLAU
2016-05-09 15:32         ` Mohammad Hossein Bateni
2016-05-09  8:53     ` luigi scarso
2016-05-09  9:12       ` Taco Hoekwater
2016-05-09  9:33         ` luigi scarso
2016-05-09 10:02         ` Hans Hagen [this message]
2016-05-09  9:23 ` Mikael P. Sundqvist
2016-05-09  9:31   ` luigi scarso
2016-05-09 10:15 ` Arthur Reutenauer
2016-05-09 12:13   ` Hans Åberg
2016-05-09 10:35 ` Ulrike Fischer
2016-05-09 10:52   ` Mojca Miklavec

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=60978dbe-ae0c-d0dd-d5e0-b5258564e51c@wxs.nl \
    --to=pragma@wxs.nl \
    --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).