ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <gesang@stud.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re:  “bodyfont %s is defined (can better be done global)”
Date: Sun, 3 Jun 2012 22:30:13 +0200	[thread overview]
Message-ID: <20120603203013.GB15076@phlegethon> (raw)
In-Reply-To: <FA1D9AAA-197A-4083-B671-2F20B8555890@googlemail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1650 bytes --]

Hi Wolfgang!

···<date: 2012-06-03, Sunday>···<from: Wolfgang Schuster>···

> Am 03.06.2012 um 16:27 schrieb Philipp Gesang:
> > It’s about decrementing font size and interlinespace until the
> > content fits a predefined box.
> > https://bitbucket.org/phg/context-stellen/src/3568dc7470fa/tex/context/third/bstellen/t-bibelstellen.mkiv#cl-158
 
> Look at the definition for \FittingText in supp-fun.mkiv:
> 
> \starttext
> \ruledvbox{\FittingText{\hsize}{100pt}{Serif}{16pt}{1pt}{1}{\raggedright\input knuth\par}}
> \stoptext

That’s the only thing that bothers me about Context: whenever you
come across a neat problem you think you should go about
implementing, you can be dead sure there’s already a
full-fledged, highly optimized solution in the core somwhere.
(Unless, of course, it’s something related to bibliography ;-) .)

On a more serious note: thanks for the pointer, this is good
reading! All the camel casing makes it look oldish, though.

Philipp



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

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 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
___________________________________________________________________________________

  reply	other threads:[~2012-06-03 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-02 18:13 Philipp Gesang
2012-06-03  0:47 ` S Barmeier
2012-06-03  8:31 ` Wolfgang Schuster
2012-06-03 10:01   ` Philipp Gesang
2012-06-03 13:58     ` Wolfgang Schuster
2012-06-03 14:27       ` Philipp Gesang
2012-06-03 15:12         ` Wolfgang Schuster
2012-06-03 20:30           ` Philipp Gesang [this message]
2012-06-03 17:28         ` Hans Hagen
2012-06-03 20:20           ` Philipp Gesang

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=20120603203013.GB15076@phlegethon \
    --to=gesang@stud.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).