From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Looking for ConTeXt commands for ...
Date: Sun, 4 Jan 2009 20:50:44 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.00.0901042040070.27444@nqv-yncgbc> (raw)
In-Reply-To: <gjrm1h$oe5$1@ger.gmane.org>
On Mon, 5 Jan 2009, Mohamed Bana wrote:
> I'am trying to convert a doc to ConTeXt, and I'm also trying to make it as
> close to the original as possible. How do the command below translate to
> ConTeXt?
>
> 1. \geometry{a4paper, textwidth=5.5in, textheight=8.5in, marginparsep=7pt,
> marginparwidth=.6in}
For a4 paper use
\setuppapersize[a4][a4]
For setting geometry, see \setuplayout.
> 2. \scriptsize => \tfxx?
>
> 3. \LARGE and \Large
>
> 4. \Huge and \HUGE
Semantically, \scriptsize = \tfxx, \Large et. al. are \tfa \tfb \tfc \tfd
\tfe, but that may not give you visually the same appearance due to
different defaults in Latex and Context. In Latex, these sizes are set as
part of the documentclass, or size10.clo, size12.clo, etc. So, the most
reliable way to reconstruct the visual appearance will be to figure out
what sizes they correspond to in latex, and then set the context font
environmet to match the latex values.
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-01-05 1:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 0:59 Mohamed Bana
2009-01-05 1:50 ` Aditya Mahajan [this message]
2009-01-05 10:36 ` Wolfgang Schuster
2009-01-05 13:46 ` Aditya Mahajan
2009-01-05 18:36 ` Mohamed Bana
2009-01-05 19:56 ` Hans Hagen
2009-01-05 20:00 ` Wolfgang Schuster
2009-01-07 10:02 ` luigi scarso
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=alpine.LNX.2.00.0901042040070.27444@nqv-yncgbc \
--to=adityam@umich.edu \
--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).