Re: [NTG-context] \triangledown placed too low in Palatino
Instead of \triangle you "should" use \Delta for the laplacian (as you should use \nabla for the gradient). Mikael On Fri, Apr 11, 2014 at 6:06 AM, Sanjoy Mahajan wrote: >> I cannot say whether the wrong placement is due to the wrong font >> metrics or the wrong mapping (mathop vs mathord) by ConTeXt. > > I tried '\triangle T' (often used as the Laplacian operator, instead of > writing it out as \nabla^2). That one comes out fine, even though > \triangledown does not. But they seem to have similar kinds of > defintions/mappings: > > From luatex-math.tex : > > \def\triangle {\Umathchar "0"0"0025B3 } > \def\triangledown {\Umathchar "2"0"0025BD } > > So it must be a wrong font metric? > > -Sanjoy > ___ > 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 > ___ ___ 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] \triangledown placed too low in Palatino
On Fri, 11 Apr 2014, Aditya Mahajan wrote: On Fri, 11 Apr 2014, Sanjoy Mahajan wrote: I cannot say whether the wrong placement is due to the wrong font metrics or the wrong mapping (mathop vs mathord) by ConTeXt. I tried '\triangle T' (often used as the Laplacian operator, instead of writing it out as \nabla^2). That one comes out fine, even though \triangledown does not. But they seem to have similar kinds of defintions/mappings: From luatex-math.tex : \def\triangle {\Umathchar "0"0"0025B3 } \def\triangledown {\Umathchar "2"0"0025BD } So it must be a wrong font metric? AFAIU, ConTeXt does not use luatex-math.tex. The mappings are defined in char-def.lua. triangle is defined as a mathord (like nabla) while bigtriangleup is a mathop (like triangledown). Sorry, bigtriangleup is a mathbin. (As I said, I don't understand how the mathclass of different triangle operators is determined). 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \triangledown placed too low in Palatino
On Fri, 11 Apr 2014, Sanjoy Mahajan wrote: I cannot say whether the wrong placement is due to the wrong font metrics or the wrong mapping (mathop vs mathord) by ConTeXt. I tried '\triangle T' (often used as the Laplacian operator, instead of writing it out as \nabla^2). That one comes out fine, even though \triangledown does not. But they seem to have similar kinds of defintions/mappings: From luatex-math.tex : \def\triangle {\Umathchar "0"0"0025B3 } \def\triangledown {\Umathchar "2"0"0025BD } So it must be a wrong font metric? AFAIU, ConTeXt does not use luatex-math.tex. The mappings are defined in char-def.lua. triangle is defined as a mathord (like nabla) while bigtriangleup is a mathop (like triangledown). 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \triangledown placed too low in Palatino
> I cannot say whether the wrong placement is due to the wrong font > metrics or the wrong mapping (mathop vs mathord) by ConTeXt. I tried '\triangle T' (often used as the Laplacian operator, instead of writing it out as \nabla^2). That one comes out fine, even though \triangledown does not. But they seem to have similar kinds of defintions/mappings: >From luatex-math.tex : \def\triangle {\Umathchar "0"0"0025B3 } \def\triangledown {\Umathchar "2"0"0025BD } So it must be a wrong font metric? -Sanjoy ___ 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] \triangledown placed too low in Palatino
On Thu, 10 Apr 2014, Sanjoy Mahajan wrote: Jannik, You are right. \nabla looks much nicer and is placed correctly. (I still think the \triangledown placement is slightly off.) My environment files from MkII days have \def\nabla{\triangledown}, so I never tried the true \nabla until your suggestion. In MkIV: \triangledown is mapped to 0x25BD while nabla is mapped to 0x2207. These are different glyphs. IIUC, the difference in placement is because \triangledown is defined as a mathop (and hence centered on the math-axis) while \nabla is defined as a mathord. Compare: \startformula \nabla T \quad \triangledown T \quad \mathop{\nabla} T \stopformula From what I remember, I was the one who added the mappings for triangledown as a mathop based on, I believe, unicode-math package in LaTeX. I don't understand what all the "triangle operators" are supposed to do. As such, I cannot say whether the wrong placement is due to the wrong font metrics or the wrong mapping (mathop vs mathord) by ConTeXt. 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \triangledown placed too low in Palatino
Jannik, You are right. \nabla looks much nicer and is placed correctly. (I still think the \triangledown placement is slightly off.) My environment files from MkII days have \def\nabla{\triangledown}, so I never tried the true \nabla until your suggestion. Thank you. -Sanjoy Jannik Voges writes: > I think you are using the wrong symbol. Or at least I would prefer > \nabla as gradient operator. > > > Jannik ___ 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] \triangledown placed too low in Palatino
I think you are using the wrong symbol. Or at least I would prefer \nabla as gradient operator. Jannik Am 10.04.2014 um 23:49 schrieb Sanjoy Mahajan : > I just noticed that the gradient operator (\triangledown) ends up too > low when using Palatino: > > \setupbodyfont[palatino] > \starttext > $\triangledown T$ > \stoptext > > It seems about 3pt too low. Without the \setupbodyfont[palatino], the > placement is fine. > > (tested with 2013.05.28 and 2014.03.27 betas) > > -Sanjoy > ___ > 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 > ___ ___ 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 ___
[NTG-context] \triangledown placed too low in Palatino
I just noticed that the gradient operator (\triangledown) ends up too low when using Palatino: \setupbodyfont[palatino] \starttext $\triangledown T$ \stoptext It seems about 3pt too low. Without the \setupbodyfont[palatino], the placement is fine. (tested with 2013.05.28 and 2014.03.27 betas) -Sanjoy ___ 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] another issue with PDF bookmarks
On 04/09/2014 09:33 PM, Aditya Mahajan wrote: > On Wed, 9 Apr 2014, Aditya Mahajan wrote: > >> One possibility is to add: >> >> \appendtoks \let\footnote \gobbleoneargument \to \everysimplifycommands >> >> to your style. >> >> Perhaps this should be added to the definition of definenote. > > Hmm... simplifycommands needs an overhaul: > >>From typo-del.mkiv: > > \appendtoks > \def\quotation#1{"#1"}% > \def\quote#1{'#1'}% > \to \everysimplifycommands > > and from buff-ver.mkiv: > > \appendtoks > \def\type#1{\letterbackslash\checkedstrippedcsname#1}% or maybe > detokenize > \def\tex #1{\letterbackslash#1}% > \to \everysimplifycommands > > > The simplification of \type assumes that a user will always use > \type{\command} and gives the wrong result for \type{text} and fails for > \type{text\undefined}. > > The simplification of \quote and \quotation should not be hardcoded, but > rather be a part of \definedelimitedtext. > > Apart from notes and delimited text, are there other commands that need to > be simplified for bookmarks, etc? Many thanks for your reply, Aditya. If I don’t get it wrong, I guess all language and style commands should be ignored. And all braces, when not explicitly invoked (such as in \{). But this only would affect to PDF bookmarks. Many thanks again, Pablo -- http://www.ousia.tk ___ 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 ___
[NTG-context] Wrong pagenumber in index
Try 1: \starttext \section{Hello}\index{Hello} \page \index{world}world \page \completeindex \stoptext Result 1: hello 2 <- must be 1! world 2 Try 2: \starttext \section{Hello}\index{Hello} some text <- putting some text here \page \index{world}world \page \completeindex \stoptext Result 2: hello 1 <- ok world 2 It is ok but I didn't want to put text "some text" there. Try 3: Workaround: I put a tilde "~" instead of "some text": \starttext \section{Hello}\index{Hello} ~ <- putting the tilde here \page \index{world}world \page \completeindex \stoptext Result 3: hello 1 <- ok, with the tilde as a workaround world 2 I don't like such tricks - is there a ConTeXt-way? ___ 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] Rotating two lines in a table
Am 10.04.2014 um 12:10 schrieb jahei...@gmx.de: > There is a bug(?) with > > \starttext > \bTABLE > \bTR > \bTD[orientation=90]{first line\crlf second line}\eTD > \bTD{first line\crlf second line}\eTD > \eTR > \eTABLE > \stoptext > > The second cell is partially written over the first cell. > How can I say: Don't do that :-) > ?___ Unrelated to your problem but why do you add braces around the text in the cells? 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 ___
[NTG-context] Rotating two lines in a table
There is a bug(?) with \starttext \bTABLE \bTR \bTD[orientation=90]{first line\crlf second line}\eTD \bTD{first line\crlf second line}\eTD \eTR \eTABLE \stoptext The second cell is partially written over the first cell. How can I say: Don't do that :-) ?___ 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 ___