[NTG-context] Capital number when onum=yes?
Hi all, I have `onum=yes' in my font features and it works great. But how can I type a capital number in this case? I want to use capital numbers in pagenumbers. Thanks! Corsair Sun -- There is no emotion; there is peace. There is no ignorance; there is knowledge. There is no passion; there is serenity. There is no death; there is the Force. pgp1ZuaiWNP5X.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] Capital number when onum=yes?
On Sun, May 10, 2009 at 09:44:58PM +0200, Hans Hagen wrote: Corsair wrote: Hi all, I have `onum=yes' in my font features and it works great. But how can I type a capital number in this case? I want to use capital numbers in pagenumbers. can you be a bit more explicit? to what extend smallcaps are implemented is font dependent Ok. Sorry for the vagueness. I use Adobe Caslon Pro as my body font, with XeTeX. And I enable the `onum' feature so that all numbers in my document appear as old-style numbers, which is good. But I also prefer some of them use the normal capital number glyphs, for example, in page numbers. How can I do that? -- There is no emotion; there is peace. There is no ignorance; there is knowledge. There is no passion; there is serenity. There is no death; there is the Force. pgpOtl2Tqe55f.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] Capital number when onum=yes?
On Mon, May 11, 2009 at 08:13:59AM +0200, Thomas A. Schmitz wrote: Not sure if this is the canonical way, but here's how I do it: If I have onum=yes enabled for my normal Roman font, I disable it for my smallcaps variant and set page numbers etc as \sc. Or am I misunderstanding something? Thanks you for the reply! But it doesn't work for me, because small cap numbers in Adobe Caslon Pro are themselves old-style... -- There is no emotion; there is peace. There is no ignorance; there is knowledge. There is no passion; there is serenity. There is no death; there is the Force. pgpUFSMTu0X9O.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] Capital number when onum=yes?
On Mon, May 11, 2009 at 08:35:12AM +0200, Wolfgang Schuster wrote: Am 10.05.2009 um 18:25 schrieb Corsair: Hi all, I have `onum=yes' in my font features and it works great. But how can I type a capital number in this case? I want to use capital numbers in pagenumbers. Something like (untested): \definefontfeature[header][default][lnum=yes] \definefont[HeaderStyle][Serif][features=header] \setupheader[style=HeaderStyle] This works great! Thanks! -- There is no emotion; there is peace. There is no ignorance; there is knowledge. There is no passion; there is serenity. There is no death; there is the Force. pgptTK0UoFvWr.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] Capital number when onum=yes?
On Mon, May 11, 2009 at 08:37:46AM +0200, Henning Hraban Ramm wrote: Am 2009-05-11 um 08:13 schrieb Thomas A. Schmitz: Ok. Sorry for the vagueness. I use Adobe Caslon Pro as my body font, with XeTeX. And I enable the `onum' feature so that all numbers in my document appear as old-style numbers, which is good. But I also prefer some of them use the normal capital number glyphs, for example, in page numbers. How can I do that? Not sure if this is the canonical way, but here's how I do it: If I have onum=yes enabled for my normal Roman font, I disable it for my smallcaps variant and set page numbers etc as \sc. Or am I misunderstanding something? Similarly you could define an additional variant, like noos. http://wiki.contextgarden.net/Font_Variants (Didn't check if font variants work ok in MkIV; I used them only for light and medium weights before.) Wow, I didn't know about this one. I'll see what I can do with it. Thank you! -- There is no emotion; there is peace. There is no ignorance; there is knowledge. There is no passion; there is serenity. There is no death; there is the Force. pgpXYyrAnk6Da.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] Capital number when onum=yes?
On Mon, May 11, 2009 at 08:37:46AM +0200, Henning Hraban Ramm wrote:
Similarly you could define an additional variant, like noos.
http://wiki.contextgarden.net/Font_Variants
(Didn't check if font variants work ok in MkIV; I used them only for
light and medium weights before.)
I tried this approach and failed. I compiled the following code with
texexec --xtx, and the resulting PDF contained nothing except an
old-style page number... Any idea?
# --- ConTeXt code ---
\definefontfeature [old] [onum=yes]
\definefontfeature [noos] [onum=no]
\definefontfeature [smcap] [smcp=yes]
\starttypescript [serif] [caslon]
\definefontsynonym [Caslon-Roman][file:ACaslonPro-Regular]
[features=old]
\definefontsynonym [Caslon-Roman-NoOs] [file:ACaslonPro-Regular]
[features=noos]
\definefontsynonym [Caslon-Bold] [file:ACaslonPro-Bold]
[features=old]
\definefontsynonym [Caslon-Italic] [file:ACaslonPro-Italic]
[features=old]
\definefontsynonym [Caslon-Bold-Italic][file:ACaslonPro-BoldItalic]
[features=old]
\definefontsynonym [Caslon-SmallCaps] [file:ACaslonPro-Regular]
[features=smcap]
\stoptypescript
\starttypescript [serif] [caslon] [name]
\definefontsynonym [Serif] [Caslon-Roman]
\definefontsynonym [SerifItalic] [Caslon-Italic]
\definefontsynonym [SerifBold] [Caslon-Bold]
\definefontsynonym [SerifBoldItalic] [Caslon-Bold-Italic]
\definefontsynonym [SerifCaps] [Caslon-SmallCaps]
\definefontvariant [Serif][noos][NoOs]
\definefontsynonym [SerifRegular] [Serif]
\definefontsynonym [SerifRegularNoOs] [Caslon-Roman-NoOs]
\definefontsynonym [SerifItalicNoOs] [Caslon-Italic]
\definefontsynonym [SerifBoldNoOs] [Caslon-Bold]
\definefontsynonym [SerifBoldItalicNoOs] [Caslon-Bold-Italic]
\stoptypescript
\usetypescript[caslon]
\starttypescript [prof]
\definetypeface [prof] [rm] [serif] [caslon] [default]
\stoptypescript
\usetypescript[prof]
\setupbodyfont[prof, 12pt]
\starttext
{\Var[noos] 1234567890}
\stoptext
# --- End of ConTeXt code---
%%% Local Variables:
%%% mode: context
%%% TeX-PDF-mode: t
%%% End:
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there is serenity.
There is no death; there is the Force.
pgpIhVDZK9yUP.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] Capital number when onum=yes?
On Mon, May 11, 2009 at 09:28:27AM +0200, Hans Hagen wrote:
you can try {\subff{oldstyle} 123} (this is kind of experimental and in
testing by idris)
Oops... Doesn't work. It just produces the word oldstyle followed
by 123. Maybe my ConTeXt is too old?
ConTeXt ver: 2008.05.21 15:21 MKII fmt: 2008.10.29
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there is serenity.
There is no death; there is the Force.
pgp5OYVPzp7ug.pgp
Description: PGP signature
___
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
___
[NTG-context] Chapter number in right margin?
Hi all,
I'm typesetting a double-sided document. And I want the chapter
numbers to be in the right margin, while the chapter titles remain in
the main text area. So I write
\def\MyChapter#1#2
{\inright{#1} #2}
\setuphead
[chapter]
[command=\MyChapter]
But it renders such that all the chapter numbers disappear while
chapter titles seem normal. Any idea?
Corsair Sun
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there is serenity.
There is no death; there is the Force.
pgp9XezukTQbR.pgp
Description: PGP signature
___
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
___
[NTG-context] \inmargin followed by \startlines = alignment fault?
Hi guys,
I find that the `lines' environment (or description, itemize, etc.)
after text in margin does not align right. Consider the following
code:
\starttext
\inmargin{What I want}
First line \crlf
Second line
\vskip 1cm
\inmargin{What it renders}
\startlines
First line
Second line
\stoplines
\stoptext
The \crlf approach is the effect I want while the `lines' approach
fails to do it. So is it a feature or a bug? Or I understand
something totally wrong? I know I can put the \inmargin in the
`lines' environment, but this time I really need it outside.
Thanks.
Corsair
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there is serenity.
There is no death; there is the Force.
pgp6rbvPLCobc.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] \inmargin followed by \startlines = alignment fault?
On Thu, May 14, 2009 at 09:11:04AM +0200, Hans Hagen wrote:
Corsair wrote:
Hi guys,
I find that the `lines' environment (or description, itemize, etc.)
after text in margin does not align right. Consider the following
code:
in that case you can try \margintext {...} which saves the note and
flushes it later
Wow~ It works. Thank you very much! I should read the manual more
carefully next time :-p.
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there is serenity.
There is no death; there is the Force.
pgpnVkv4QZZN1.pgp
Description: PGP signature
___
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
___
[NTG-context] MkIV italic correction?
Hi all,
Does MkIV support italic correction? Because the following code
produces two identical f)s
\starttext
{\it f})
{\it f\/})
\stoptext
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there is serenity.
There is no death; there is the Force.
pgpTLTfcXNdmo.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] MkIV italic correction?
On Wed, May 20, 2009 at 03:21:59PM +0800, Yue Wang wrote:
it supports italic correction by default.
Then what's your result of the code? Does it come with italic
correction?
On Wed, May 20, 2009 at 2:25 PM, Corsair chris.cors...@gmail.com wrote:
Hi all,
Does MkIV support italic correction? �Because the following code
produces two identical f)s
\starttext
{\it f})
{\it f\/})
\stoptext
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there is serenity.
There is no death; there is the Force.
pgp4GyvzAdf5U.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] MkIV italic correction?
On Thu, May 21, 2009 at 11:55:45AM +0200, Hans Hagen wrote: open type fonts have no italic correction info (except in math) But I notice that using the same fonts in XeTeX produces italic correction. Is it fake? -- There is no emotion; there is peace. There is no ignorance; there is knowledge. There is no passion; there is serenity. There is no death; there is the Force. pgpcsgfJ4LDhX.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] MkIV italic correction?
On Thu, May 21, 2009 at 01:59:14PM +0200, Taco Hoekwater wrote:
Corsair wrote:
On Thu, May 21, 2009 at 11:55:45AM +0200, Hans Hagen wrote:
open type fonts have no italic correction info (except in math)
But I notice that using the same fonts in XeTeX produces italic
correction. Is it fake?
I guess it is using the glyph boundingbox.
Thank you. This sounds reasonable. Is there any way I can achieve
this in MkIV? I'm currently using \def\/{\kern0.1em}, which is kinda
dirty...
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there is serenity.
There is no death; there is the Force.
pgpBwAEl15ODI.pgp
Description: PGP signature
___
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
___
[NTG-context] Space between description entries?
Hi all, Anyone knows how to adjust white space between description entries? I thought it was `inbetween', but it does not work. -- There is no emotion; there is peace. There is no ignorance; there is knowledge. There is no passion; there is serenity. There is no death; there is the Force. pgpvb841seHvO.pgp Description: PGP signature ___ 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 ___
[NTG-context] \setupcombinedlist ignores `level' argument?
Hi all,
If I understand this right, \setupcombinedlist[content][level=section]
tells ConTeXt to list up to section level when doing \completecontent.
But it seems no matter what I set for `level', \completecontent lists
however deeply it can. Here is a minimal example:
\setupcombinedlist[content][level=section]
\starttext
\completecontent
\chapter{Level 0}
\section{Level 1}
\subsection{Level 2}
\subsubsection{Level 3}
\subsubsubsection{Level 4}
\subsubsubsubsection{Level 5}
\stoptext
Is this a bug, or I did something wrong?
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there is serenity.
There is no death; there is the Force.
pgpQ7hjJ8kcBf.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] \setupcombinedlist ignores `level' argument?
On Sun, Sep 19, 2010 at 08:06:05AM +0200, Wolfgang Schuster wrote:
Am 19.09.2010 um 00:09 schrieb Corsair:
Hi all,
If I understand this right, \setupcombinedlist[content][level=section]
tells ConTeXt to list up to section level when doing \completecontent.
But it seems no matter what I set for `level', \completecontent lists
however deeply it can.
This option is gone in MkIV, the alternative is to use
\starttext
\title{Contents}
\placelist[chapter,section,...]
I see. That explains. Thank you very much!
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there is serenity.
There is no death; there is the Force.
___
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
___
Re: [NTG-context] tooltips and glossary
Hey Michael, I'm the author of that terrible document. On Tue, May 04, 2010 at 08:32:36AM -0500, Michael Saunders wrote: No, it's plain English. Unfamiliar phrases are just one consequence of a language becoming the world standard. Do you want to flame Italians or French for not adhering to the norms of classical Latin? You don't. There's no point at all in even mentioning somebody's stylistic idiosyncrasies on the internets. Just face it: the world won't adopt English as a global means of communication without interfering with its norms. If you don't understand something why don't you contact the author, his email adress is right there on the first page. I don't mind non-native speakers using bad grammar, strange usages, or odd constructions at all. �Things like that are usually no problem for native speakers to understand, although the two sentences I quoted were not plain English at all---one was completely indecipherable. The biggest problem with the docs is far more basic---it's the most basic mistake a beginning writer can make. �I'm sure documents like the ones I was shown on this thread make perfect sense to their authors---who already know what they mean---but they fail to communicate their message to anyone who doesn't already know it. �The reader isn't being given enough information to decode the message and what he is given is in no particular order: �it's whatever bits and pieces of the story the author thinks of in the order he happens to think of them. I'm sorry for my writing and the inconvenience it brings. However right now I cannot do anything about it. May be I will rewrite it in the summer. You can't tell the author this. �It makes sense to him and he can't understand the criticism. �He has to put himself in the place of the reader who doesn't already know the message. �If he can't do that, he can't communicate. �I'm sure that these documents would be just as bad in the native languages of the authors as they are in English. �The fault is far deeper than bad translation. Actually I do understand your feeling. Like I said, I may rewrite most part of it in the summer. And BTW, that document is *supposed* to be an extraction of some particular pieces of info in the official doc. Because I find the official doc too heavy for both my PDF viewer and me. And about the background, I just grabbed some random Asymptote file of mine. Though I find it pretty much ok, I may change that also in the future. Let's focus on the tooltip and external database issue you encountered, instead of discuss that document and my bad writing :-). -- There is no emotion; there is peace. There is no ignorance; there is knowledge. There is no passion; there is serenity. There is no death; there is the Force. ___ 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 ___
