Re: [NTG-context] latest beta, problem with natural tables and alignment character
On Jun 26, 2014, at 5:24 PM, Hans Hagen pra...@wxs.nl wrote: On 6/26/2014 10:48 PM, Hans Hagen wrote: On 6/26/2014 5:06 AM, Brian Landy wrote: On Jun 25, 2014, at 6:53 PM, Hans Hagen pra...@wxs.nl wrote: On 6/25/2014 11:26 PM, Brian R. Landy wrote: When you say next beta do you mean a subsequent minimals release (i.e., this fix should be the 2014.06.22 release)? Or do you mean a new beta that you announce more formally on the list? I'm not sure what I should look for before I test again, so I don't end up testing a version without the fix. netx beta == next upload == already done Great, thanks. I wanted to make sure before mentioning I'm still seeing problems. When you have a combination number/character sequence (i.e., 1D or 11-22+) and specify an alignment (flushleft/middle/flushright) spaces get inserted between the final digit and the first trailing character. So 1D might print as 1 D, 11-22+ prints as 11-22 +, etc. This happens using . or , for alignment, it's not exclusive to aligning on a hyphen. i now have two methods, number and text and {-} triggers text you can force a method with text- and number- no upload yet I'll also add \nocharacteralign so that one can disable this mechanism in a table cell. This is all great, thank's so much for handling this so quickly! I like the idea of keeping the old behavior as an alternative. And now that I see what your new mode is attempting to accomplish, I think it will prove very useful. It looks like you want to parse out the number from any preceding and following text, align the number on the alignment character, and pad out any text that precedes a number (like a currency symbol) to align on the left rather than be flush with the number. I just wanted to point out that this only works if identical preceding and/or trailing text exists in every cell. For example, this table doesn't align using flushleft, middle, or flushright (it will if you force text-{.}, but of course the parens won't align vertically): \starttext \bgroup \setupTABLE[1,2][3,4,5,6][aligncharacter=yes,alignmentcharacter={.}] \bTABLE[align={flushright}] \bTR \bTD \eTD \eTR \bTR \bTD x\eTD \eTR \bTR \bTD 1.2 \eTD \eTR \bTR \bTD (1.2)\eTD \eTR \bTR \bTD 11.22 \eTD \eTR \bTR \bTD (11.22) \eTD \eTR \eTABLE \egroup \stoptext Without having looked through the code, I wonder if in number mode you could first run the existing logic, and then finish off using the existing text logic to pad the outside (i.e., to the left of the left-hand text and to the right of the right-hand text)? Anyway, for my purposes restoring the old mode as an option is perfect, I just wanted to mention this in case this wasn't the behavior you intended. Thanks again! Best regards, Brian signature.asc Description: Message signed with OpenPGP using GPGMail ___ 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] latest beta, problem with natural tables and alignment character
On 6/27/2014 8:04 PM, Brian Landy wrote: On Jun 26, 2014, at 5:24 PM, Hans Hagen pra...@wxs.nl wrote: On 6/26/2014 10:48 PM, Hans Hagen wrote: On 6/26/2014 5:06 AM, Brian Landy wrote: On Jun 25, 2014, at 6:53 PM, Hans Hagen pra...@wxs.nl wrote: On 6/25/2014 11:26 PM, Brian R. Landy wrote: When you say next beta do you mean a subsequent minimals release (i.e., this fix should be the 2014.06.22 release)? Or do you mean a new beta that you announce more formally on the list? I'm not sure what I should look for before I test again, so I don't end up testing a version without the fix. netx beta == next upload == already done Great, thanks. I wanted to make sure before mentioning I'm still seeing problems. When you have a combination number/character sequence (i.e., 1D or 11-22+) and specify an alignment (flushleft/middle/flushright) spaces get inserted between the final digit and the first trailing character. So 1D might print as 1 D, 11-22+ prints as 11-22 +, etc. This happens using . or , for alignment, it's not exclusive to aligning on a hyphen. i now have two methods, number and text and {-} triggers text you can force a method with text- and number- no upload yet I'll also add \nocharacteralign so that one can disable this mechanism in a table cell. This is all great, thank's so much for handling this so quickly! I like the idea of keeping the old behavior as an alternative. in fact, the old behaviour is the default for number related seperators but in your case the - so not a number separator so then it assumes text And now that I see what your new mode is attempting to accomplish, I think it will prove very useful. It looks like you want to parse out the number from any preceding and following text, align the number on the alignment character, and pad out any text that precedes a number (like a currency symbol) to align on the left rather than be flush with the number. I just wanted to point out that this only works if identical preceding and/or trailing text exists in every cell. indeed, this mechanism was meant for numbers For example, this table doesn't align using flushleft, middle, or flushright (it will if you force text-{.}, but of course the parens won't align vertically): \starttext \bgroup \setupTABLE[1,2][3,4,5,6][aligncharacter=yes,alignmentcharacter={.}] \bTABLE[align={flushright}] \bTR \bTD \eTD \eTR \bTR \bTD x\eTD \eTR \bTR \bTD 1.2 \eTD \eTR \bTR \bTD (1.2)\eTD \eTR \bTR \bTD 11.22 \eTD \eTR \bTR \bTD (11.22) \eTD \eTR \eTABLE \egroup \stoptext Without having looked through the code, I wonder if in number mode you could first run the existing logic, and then finish off using the existing text logic to pad the outside (i.e., to the left of the left-hand text and to the right of the right-hand text)? not today ... things take time Anyway, for my purposes restoring the old mode as an option is perfect, I just wanted to mention this in case this wasn't the behavior you intended. maybe you can wikify these variants Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___
Re: [NTG-context] latest beta, problem with natural tables and alignment character
On 6/26/2014 5:06 AM, Brian Landy wrote: On Jun 25, 2014, at 6:53 PM, Hans Hagen pra...@wxs.nl wrote: On 6/25/2014 11:26 PM, Brian R. Landy wrote: When you say next beta do you mean a subsequent minimals release (i.e., this fix should be the 2014.06.22 release)? Or do you mean a new beta that you announce more formally on the list? I'm not sure what I should look for before I test again, so I don't end up testing a version without the fix. netx beta == next upload == already done Great, thanks. I wanted to make sure before mentioning I'm still seeing problems. When you have a combination number/character sequence (i.e., 1D or 11-22+) and specify an alignment (flushleft/middle/flushright) spaces get inserted between the final digit and the first trailing character. So 1D might print as 1 D, 11-22+ prints as 11-22 +, etc. This happens using . or , for alignment, it's not exclusive to aligning on a hyphen. i now have two methods, number and text and {-} triggers text you can force a method with text- and number- no upload yet - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___
Re: [NTG-context] latest beta, problem with natural tables and alignment character
On 6/26/2014 10:48 PM, Hans Hagen wrote: On 6/26/2014 5:06 AM, Brian Landy wrote: On Jun 25, 2014, at 6:53 PM, Hans Hagen pra...@wxs.nl wrote: On 6/25/2014 11:26 PM, Brian R. Landy wrote: When you say next beta do you mean a subsequent minimals release (i.e., this fix should be the 2014.06.22 release)? Or do you mean a new beta that you announce more formally on the list? I'm not sure what I should look for before I test again, so I don't end up testing a version without the fix. netx beta == next upload == already done Great, thanks. I wanted to make sure before mentioning I'm still seeing problems. When you have a combination number/character sequence (i.e., 1D or 11-22+) and specify an alignment (flushleft/middle/flushright) spaces get inserted between the final digit and the first trailing character. So 1D might print as 1 D, 11-22+ prints as 11-22 +, etc. This happens using . or , for alignment, it's not exclusive to aligning on a hyphen. i now have two methods, number and text and {-} triggers text you can force a method with text- and number- no upload yet I'll also add \nocharacteralign so that one can disable this mechanism in a table cell. - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___
Re: [NTG-context] latest beta, problem with natural tables and alignment character
On Tue, 17 Jun 2014, Hans Hagen wrote: anyhow, i made it work a bit better with tables (extra pass needed) \starttext \enabletrackers[typesetters.characteralign] \bgroup \setupTABLE[column][1][aligncharacter=yes,alignmentcharacter={,}] \bTABLE \bTR \bTD 1,2 \eTD \bTD 1,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD - 1,2 \eTD \bTD -1,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD -1,2 \eTD \bTD -1,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD 11,2 \eTD \bTD 11,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD 11,224 \eTD \bTD 11,22 \eTD \bTD xxx \eTD \eTR \eTABLE \egroup \bgroup \setupTABLE[column][1][aligncharacter=yes,alignmentcharacter={-}] \setupTABLE[column][2][aligncharacter=yes,alignmentcharacter={\endash}] \bTABLE \bTR \bTD 1-2\eTD \bTD 1\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-2\eTD \bTD 11\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-22 + \eTD \bTD 11\endash22 + \eTD\bTD xxx \eTD \eTR \eTABLE \egroup \stoptext the next beta can handle this When you say next beta do you mean a subsequent minimals release (i.e., this fix should be the 2014.06.22 release)? Or do you mean a new beta that you announce more formally on the list? I'm not sure what I should look for before I test again, so I don't end up testing a version without the fix. Brian ___ 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] latest beta, problem with natural tables and alignment character
On 6/25/2014 11:26 PM, Brian R. Landy wrote: On Tue, 17 Jun 2014, Hans Hagen wrote: anyhow, i made it work a bit better with tables (extra pass needed) \starttext \enabletrackers[typesetters.characteralign] \bgroup \setupTABLE[column][1][aligncharacter=yes,alignmentcharacter={,}] \bTABLE \bTR \bTD 1,2 \eTD \bTD 1,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD - 1,2 \eTD \bTD -1,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD -1,2 \eTD \bTD -1,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD 11,2 \eTD \bTD 11,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD 11,224 \eTD \bTD 11,22 \eTD \bTD xxx \eTD \eTR \eTABLE \egroup \bgroup \setupTABLE[column][1][aligncharacter=yes,alignmentcharacter={-}] \setupTABLE[column][2][aligncharacter=yes,alignmentcharacter={\endash}] \bTABLE \bTR \bTD 1-2\eTD \bTD 1\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-2\eTD \bTD 11\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-22 + \eTD \bTD 11\endash22 + \eTD\bTD xxx \eTD \eTR \eTABLE \egroup \stoptext the next beta can handle this When you say next beta do you mean a subsequent minimals release (i.e., this fix should be the 2014.06.22 release)? Or do you mean a new beta that you announce more formally on the list? I'm not sure what I should look for before I test again, so I don't end up testing a version without the fix. netx beta == next upload == already done - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___
Re: [NTG-context] latest beta, problem with natural tables and alignment character
On Jun 25, 2014, at 6:53 PM, Hans Hagen pra...@wxs.nl wrote: On 6/25/2014 11:26 PM, Brian R. Landy wrote: When you say next beta do you mean a subsequent minimals release (i.e., this fix should be the 2014.06.22 release)? Or do you mean a new beta that you announce more formally on the list? I'm not sure what I should look for before I test again, so I don't end up testing a version without the fix. netx beta == next upload == already done Great, thanks. I wanted to make sure before mentioning I'm still seeing problems. When you have a combination number/character sequence (i.e., 1D or 11-22+) and specify an alignment (flushleft/middle/flushright) spaces get inserted between the final digit and the first trailing character. So 1D might print as 1 D, 11-22+ prints as 11-22 +, etc. This happens using . or , for alignment, it's not exclusive to aligning on a hyphen. I included a sample and some output below (good.pdf is from 2013.06.10, bad.pdf is 2014.06.22) Regards, Brian \starttext %\enabletrackers[typesetters.characteralign] \bgroup \setupTABLE[1,2][3,4,5,6,7,8][aligncharacter=yes,alignmentcharacter={-}] \bTABLE[align={flushleft}] \bTABLE \bTR \bTD \eTD \bTD \eTD\bTD \eTD \eTR \bTR \bTD x \eTD \bTD x\eTD\bTD x \eTD \eTR \bTR \bTD 1D \eTD \bTD 5D\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2+ \eTD \bTD 1-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-2\eTD \bTD 11-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-22+ \eTD \bTD 11-22+ \eTD\bTD xxx \eTD \eTR \eTABLE \egroup \bgroup \setupTABLE[1,2][3,4,5,6,7,8][aligncharacter=yes,alignmentcharacter={-}] \bTABLE[align={middle}] \bTR \bTD \eTD \bTD \eTD\bTD \eTD \eTR \bTR \bTD x \eTD \bTD x\eTD\bTD x \eTD \eTR \bTR \bTD 1D \eTD \bTD 5D\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2+ \eTD \bTD 1-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-2\eTD \bTD 11-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-22+ \eTD \bTD 11-22+ \eTD\bTD xxx \eTD \eTR \eTABLE \egroup \bgroup \setupTABLE[1,2][3,4,5,6,7,8][aligncharacter=yes,alignmentcharacter={-}] \bTABLE[align={flushright}] \bTR \bTD \eTD \bTD \eTD\bTD \eTD \eTR \bTR \bTD x \eTD \bTD x\eTD\bTD x \eTD \eTR \bTR \bTD 1D \eTD \bTD 5D\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2+ \eTD \bTD 1-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-2\eTD \bTD 11-2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-22+ \eTD \bTD 11-22+ \eTD\bTD xxx \eTD \eTR \eTABLE \egroup \stoptext good.pdf Description: Adobe PDF document bad.pdf Description: Adobe PDF document signature.asc Description: Message signed with OpenPGP using GPGMail ___ 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] latest beta, problem with natural tables and alignment character
On 6/17/2014 5:49 AM, Brian Landy wrote: Almost all of the tables I generate via code, not by hand, so I found it more convenient to include a trailing % because I occasionally did run across an instance where it mattered, and wasn't (and am not) sufficiently skilled at TeX/ConTeXt to know how to predict those occurrences. It's somewhat similar for always wrapping the contents in {}, I thought I had run into some cases in the past where it was necessary, so just include them always rather than manually add them with the content when they are required. Are there negative consequences (performance, memory usage, ...) to writing it as I did? Or is the difference just cosmetic? the empty [] always has a performance hit, for {} it depends what extra restores have to happen Best regards, Brian On Jun 16, 2014, at 6:57 PM, Hans Hagen pra...@wxs.nl wrote: so instead of \bTD[]{Bond}\eTD% use this: \bTD Bond \eTD - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___ ___ 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 ___ -- - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___
Re: [NTG-context] latest beta, problem with natural tables and alignment character
On 6/16/2014 11:51 PM, Brian Landy wrote: Hi, I was testing the latest beta (2014.06.15) and noticed I am getting incorrect output using natural tables with alignment characters. I produced a small example that demonstrates the problem, and attached output created with the version I'm testing (bad.pdf) and my prior version (good.pdf, ConTeXt 2013.06.10). You can see in the bad file that ConTeXt doesn't properly align on the - and it introduces spurious spaces. i assume you haven't updated in a while as this is not something last beta specific the alignment code has been redone some time ago (the general mechanism is more clever now) and it was mostly made for aligning numbers (not so much for your case as - is seen as minus) anyhow, i made it work a bit better with tables (extra pass needed) \starttext \enabletrackers[typesetters.characteralign] \bgroup \setupTABLE[column][1][aligncharacter=yes,alignmentcharacter={,}] \bTABLE \bTR \bTD 1,2 \eTD \bTD 1,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD - 1,2 \eTD \bTD -1,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD -1,2 \eTD \bTD -1,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD 11,2 \eTD \bTD 11,2 \eTD \bTD xxx \eTD \eTR \bTR \bTD 11,224 \eTD \bTD 11,22 \eTD \bTD xxx \eTD \eTR \eTABLE \egroup \bgroup \setupTABLE[column][1][aligncharacter=yes,alignmentcharacter={-}] \setupTABLE[column][2][aligncharacter=yes,alignmentcharacter={\endash}] \bTABLE \bTR \bTD 1-2\eTD \bTD 1\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 1-2\eTD \bTD 1\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-2\eTD \bTD 11\endash2\eTD\bTD xxx \eTD \eTR \bTR \bTD 11-22 + \eTD \bTD 11\endash22 + \eTD\bTD xxx \eTD \eTR \eTABLE \egroup \stoptext the next beta can handle this Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___
Re: [NTG-context] latest beta, problem with natural tables and alignment character
On 6/16/2014 11:51 PM, Brian Landy wrote: Hi, I was testing the latest beta (2014.06.15) and noticed I am getting incorrect output using natural tables with alignment characters. I produced a small example that demonstrates the problem, and attached output created with the version I'm testing (bad.pdf) and my prior version (good.pdf, ConTeXt 2013.06.10). You can see in the bad file that ConTeXt doesn't properly align on the - and it introduces spurious spaces. i'll check it ... btw, you don't need all these %'s after a multi-char \cs - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___
Re: [NTG-context] latest beta, problem with natural tables and alignment character
so instead of \bTD[]{Bond}\eTD% use this: \bTD Bond \eTD - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___
Re: [NTG-context] latest beta, problem with natural tables and alignment character
Almost all of the tables I generate via code, not by hand, so I found it more convenient to include a trailing % because I occasionally did run across an instance where it mattered, and wasn't (and am not) sufficiently skilled at TeX/ConTeXt to know how to predict those occurrences. It's somewhat similar for always wrapping the contents in {}, I thought I had run into some cases in the past where it was necessary, so just include them always rather than manually add them with the content when they are required. Are there negative consequences (performance, memory usage, ...) to writing it as I did? Or is the difference just cosmetic? Best regards, Brian On Jun 16, 2014, at 6:57 PM, Hans Hagen pra...@wxs.nl wrote: so instead of \bTD[]{Bond}\eTD% use this: \bTD Bond \eTD - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___ signature.asc Description: Message signed with OpenPGP using GPGMail ___ 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] latest beta problem?
Am 30.06.2012 um 22:34 schrieb Alan Bowen: A file that used to process without complaint now fails because \definetext is not recognized . Do I need to revise my macros or is there a problem in the latest beta? It’s a bug regarding commands with seven arguments. syst-aux.mkiv: % missing “_yes” at the end of the commands %\def\syst_helpers_seventuple_empty_one#1[#2]% \def\syst_helpers_seventuple_empty_one_yes#1[#2]% {\firstargumenttrue \doifnextoptionalelse {\syst_helpers_seventuple_empty_two_yes#1{#2}}% {\syst_helpers_seventuple_empty_two_nop#1{#2}}} %\def\syst_helpers_seventuple_empty_two#1#2[#3]% \def\syst_helpers_seventuple_empty_two_yes#1#2[#3]% {\secondargumenttrue \doifnextoptionalelse {\syst_helpers_seventuple_empty_three_yes#1{#2}{#3}}% {\syst_helpers_seventuple_empty_three_nop#1{#2}{#3}}} %\def\syst_helpers_seventuple_empty_three#1#2#3[#4]% \def\syst_helpers_seventuple_empty_three_yes#1#2#3[#4]% {\thirdargumenttrue \doifnextoptionalelse {\syst_helpers_seventuple_empty_four_yes#1{#2}{#3}{#4}}% {\syst_helpers_seventuple_empty_four_nop#1{#2}{#3}{#4}}} %\def\syst_helpers_seventupleempty_four#1#2#3#4[#5]% \def\syst_helpers_seventupleempty_four_yes#1#2#3#4[#5]% {\fourthargumenttrue \doifnextoptionalelse {\syst_helpers_seventuple_empty_five_yes#1{#2}{#3}{#4}{#5}}% {\syst_helpers_seventuple_empty_five_nop#1{#2}{#3}{#4}{#5}}} %\def\syst_helpers_seventuple_empty_five#1#2#3#4#5[#6]% \def\syst_helpers_seventuple_empty_five_yes#1#2#3#4#5[#6]% {\fifthargumenttrue \doifnextoptionalelse {\syst_helpers_seventuple_empty_six_yes#1{#2}{#3}{#4}{#5}{#6}}% {\syst_helpers_seventuple_empty_six_nop#1{#2}{#3}{#4}{#5}{#6}}} %\def\syst_helpers_seventuple_empty_six#1#2#3#4#5#6[#7]% \def\syst_helpers_seventuple_empty_six_yes#1#2#3#4#5#6[#7]% {\sixthargumenttrue \doifnextoptionalelse {\seventhargumenttrue#1[{#2}][{#3}][{#4}][{#5}][{#6}][{#7}]}% {\syst_helpers_seventuple_empty_seven_nop#1{#2}{#3}{#4}{#5}{#6}{#7}}} % the “spaced” and “normal” string should be at the end of the command name %\def\syst_helpers_seventuple_empty_spaced_two #1#2{#1[{#2}][][][][][][] } %\def\syst_helpers_seventuple_empty_normal_two #1#2{#1[{#2}][][][][][][]} %\def\syst_helpers_seventuple_empty_spaced_three #1#2#3{#1[{#2}][{#3}][][][][][] } %\def\syst_helpers_seventuple_empty_normal_three #1#2#3{#1[{#2}][{#3}][][][][][]} %\def\syst_helpers_seventuple_empty_spaced_four #1#2#3#4{#1[{#2}][{#3}][{#4}][][][][] } %\def\syst_helpers_seventuple_empty_normal_four #1#2#3#4{#1[{#2}][{#3}][{#4}][][][][]} %\def\syst_helpers_seventuple_empty_spaced_five #1#2#3#4#5{#1[{#2}][{#3}][{#4}][{#5}][][][] } %\def\syst_helpers_seventuple_empty_normal_five #1#2#3#4#5{#1[{#2}][{#3}][{#4}][{#5}][][][]} %\def\syst_helpers_seventuple_empty_spaced_six #1#2#3#4#5#6{#1[{#2}][{#3}][{#4}][{#5}][{#6}][][] } %\def\syst_helpers_seventuple_empty_normal_six #1#2#3#4#5#6{#1[{#2}][{#3}][{#4}][{#5}][{#6}][][]} %\def\syst_helpers_seventuple_empty_spaced_seven#1#2#3#4#5#6#7{#1[{#2}][{#3}][{#4}][{#5}][{#6}][{#7}][] } %\def\syst_helpers_seventuple_empty_normal_seven#1#2#3#4#5#6#7{#1[{#2}][{#3}][{#4}][{#5}][{#6}][{#7}][]} \def\syst_helpers_seventuple_empty_two_spaced #1#2{#1[{#2}][][][][][][] } \def\syst_helpers_seventuple_empty_two_normal #1#2{#1[{#2}][][][][][][]} \def\syst_helpers_seventuple_empty_three_spaced #1#2#3{#1[{#2}][{#3}][][][][][] } \def\syst_helpers_seventuple_empty_three_normal #1#2#3{#1[{#2}][{#3}][][][][][]} \def\syst_helpers_seventuple_empty_four_spaced #1#2#3#4{#1[{#2}][{#3}][{#4}][][][][] } \def\syst_helpers_seventuple_empty_four_normal #1#2#3#4{#1[{#2}][{#3}][{#4}][][][][]} \def\syst_helpers_seventuple_empty_five_spaced #1#2#3#4#5{#1[{#2}][{#3}][{#4}][{#5}][][][] } \def\syst_helpers_seventuple_empty_five_normal #1#2#3#4#5{#1[{#2}][{#3}][{#4}][{#5}][][][]} \def\syst_helpers_seventuple_empty_six_spaced #1#2#3#4#5#6{#1[{#2}][{#3}][{#4}][{#5}][{#6}][][] } \def\syst_helpers_seventuple_empty_six_normal #1#2#3#4#5#6{#1[{#2}][{#3}][{#4}][{#5}][{#6}][][]} \def\syst_helpers_seventuple_empty_seven_spaced#1#2#3#4#5#6#7{#1[{#2}][{#3}][{#4}][{#5}][{#6}][{#7}][] } \def\syst_helpers_seventuple_empty_seven_normal#1#2#3#4#5#6#7{#1[{#2}][{#3}][{#4}][{#5}][{#6}][{#7}][]} 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 ___
Re: [NTG-context] latest beta problem?
On 1-7-2012 09:47, Wolfgang Schuster wrote: Am 30.06.2012 um 22:34 schrieb Alan Bowen: A file that used to process without complaint now fails because \definetext is not recognized . Do I need to revise my macros or is there a problem in the latest beta? It’s a bug regarding commands with seven arguments. ah .. indeed ... after six such renaming sets at seven my brain got overheated .. fixed in next (not yet done) upload Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 ___
Re: [NTG-context] latest beta problem?
Wolfgang, Hans—many thanks. Alan On Sun, Jul 1, 2012 at 9:53 AM, Hans Hagen pra...@wxs.nl wrote: On 1-7-2012 09:47, Wolfgang Schuster wrote: Am 30.06.2012 um 22:34 schrieb Alan Bowen: A file that used to process without complaint now fails because \definetext is not recognized . Do I need to revise my macros or is there a problem in the latest beta? It’s a bug regarding commands with seven arguments. ah .. indeed ... after six such renaming sets at seven my brain got overheated .. fixed in next (not yet done) upload Hans --**--**- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | 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 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/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] latest beta problem (minimals)
Bowen Alan C. wrote: The installation process is interrupted by report I can't find file `core-dat.tex'. i'll fix it; in contex.mkii remove the line that loads it - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] latest beta problem (minimals)
That’s got it. Many thanks! Alan On May 29, 2009, at 17;35,03 , Hans Hagen wrote: Bowen Alan C. wrote: The installation process is interrupted by report I can't find file `core-dat.tex'. i'll fix it; in contex.mkii remove the line that loads it - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | 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 : https://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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___