On 1/12/2022 1:09 AM, jbf via ntg-context wrote:
For poetry that has non-regular indentations, I simply
\definelines[poem] and set that up the way I want, obviously, with
\setuplines[poem] e.g. [before={\blank
\setupinterlinespace[line=2.5ex]},after={\blank},indenting=first].
And then, but
,
I needed to typeset some poetry and noticed that
\startlines[space=on]
Some line with tab % doesn't work, no spaces added
Some line with spaces %work
\stoplines
Is there a way to make the "tab" render
On 1/11/2022 3:01 AM, Youssef Cherem via ntg-context wrote:
Hello,
I needed to typeset some poetry and noticed that
\startlines[space=on]
Some line with tab % doesn't work, no spaces added
Some line with spaces %work
\stoplines
Is there a way to make the "tab" render
Hello,
I needed to typeset some poetry and noticed that
\startlines[space=on]
Some line with tab % doesn't work, no spaces added
Some line with spaces %work
\stoplines
Is there a way to make the "tab" render
Hello,
How should the table be placed correctly ?
Thanks
Fabrice
\unexpanded\def\pcent#1{\math{#1\,\%}}
\startsetups [table:one]
\setupTABLE[start][align={middle,lohi},width=2.2cm,offset=0.8ex]
\setupTABLE[column][first][width=2cm,align={right}]
\setupTABLE[1][1][frame=off]
, and as mentioned in a previous
email, it fixes the \getmarking problem pretty well. However the same
beta has a fatal problem for us: lists using \tab are now broken.
MWE:
\starttext
\tab{AC}Autonomous Community\par
\tab{\it alt.}alternate name for\par
\stoptext
In the TeX Live 2013 version
On 11/27/2013 11:08 AM, Lars Huttar wrote:
I tried the beta of 2013.11.26, and as mentioned in a previous
email, it fixes the \getmarking problem pretty well. However the same
beta has a fatal problem for us: lists using \tab are now broken.
MWE:
\starttext
\tab{AC}Autonomous Community
.
Hans, I tried the beta of 2013.11.26, and as mentioned in a previous
email, it fixes the \getmarking problem pretty well. However the same
beta has a fatal problem for us: lists using \tab are now broken.
MWE:
\starttext
\tab{AC}Autonomous Community\par
\tab{\it alt.}alternate name for\par
On 3-12-2010 1:49, Peter Schorsch wrote:
Hi,
today I recognized that the tab parameter is not working in setuptyping
anymore (actual beta). As soon the tab paramter is set and a tabulator is
used in the text, ConTeXt breaks with following error message:
! LuaTeX error ...text/tex/texmf
Hi,
today I recognized that the tab parameter is not working in setuptyping
anymore (actual beta). As soon the tab paramter is set and a tabulator is
used in the text, ConTeXt breaks with following error message:
! LuaTeX error ...text/tex/texmf-context/tex/context/base/util
Hello,
The length of the tab is always 7:
% one tab before each bla:
\setuptyping[tab=2]
\starttext
\starttyping
12345678901234567890
bla bla
\stoptyping
\setuptyping[tab=4]
\starttyping
12345678901234567890
bla bla
\stoptyping
\stoptext
Cheers, Peter
--
Contact
On 10-5-2010 12:04, Peter Münster wrote:
Hello,
The length of the tab is always 7:
% one tab before each bla:
\setuptyping[tab=2]
\starttext
\starttyping
12345678901234567890
bla bla
\stoptyping
\setuptyping[tab=4]
\starttyping
12345678901234567890
bla bla
\stoptyping
On 7-4-2010 5:13, Hongwen Qiu wrote:
\startLUA
string.format(%s %d, person, total)
\stopLUA
space handling fixed in next beta
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 |
\startLUA
string.format(%s %d, person, total)
\stopLUA
produces the result as following:
string.format(%s%d, person, total)
while the following code has no such problem:
\starttyping
string.format(%s %d, person, total)
\stoptyping
$ context --version
MTXrun | current version: 2010.03.30 18:56
Mojca Miklavec wrote:
Hello,
Here's a tiny question. The following command complains about
undefined control sequence.
\starttext
\startluacode
print('a\tb')
print('a\\tb')
\stopluacode
hello
\stoptext
-
On Wed, Nov 26, 2008 at 8:28 PM, Wolfgang Schuster wrote:
Am 26.11.2008 um 20:07 schrieb Mojca Miklavec:
Hello,
Here's a tiny question. The following command complains about
undefined control sequence.
\starttext
\startluacode
print('a\tb')
print('a\t b')
But then I get some unwanted
OK, I will use external files next time. In this quick-and-dirty
approach I just added string.format since it was easier than
restructuring everything.
I thought that \startluacode should be behaving the same way as
verbatim environments where commands inside verbatim have no
influence, but
On Thu, Nov 27, 2008 at 9:29 AM, Mojca Miklavec
[EMAIL PROTECTED] wrote:
On Wed, Nov 26, 2008 at 8:28 PM, Wolfgang Schuster wrote:
Am 26.11.2008 um 20:07 schrieb Mojca Miklavec:
Hello,
Here's a tiny question. The following command complains about
undefined control sequence.
\starttext
On Thu, Nov 27, 2008 at 9:42 AM, luigi scarso [EMAIL PROTECTED] wrote:
OK, I will use external files next time. In this quick-and-dirty
approach I just added string.format since it was easier than
restructuring everything.
I thought that \startluacode should be behaving the same way as
On Thu, Nov 27, 2008 at 10:02 AM, Wolfgang Schuster
[EMAIL PROTECTED] wrote:
On Thu, Nov 27, 2008 at 9:42 AM, luigi scarso [EMAIL PROTECTED]
wrote:
OK, I will use external files next time. In this quick-and-dirty
approach I just added string.format since it was easier than
luigi scarso wrote:
Correction:
-- works as comments in luacode
% is used to format strings
It's a bit different: code below is ok, and TeX comment is seen before
lua comment .
Only Hello! is print on pdf
%%
\def\Foo{%
\startluacode
-- this is a
On Thu, Nov 27, 2008 at 1:03 PM, Hans Hagen [EMAIL PROTECTED] wrote:
luigi scarso wrote:
Correction:
-- works as comments in luacode
% is used to format strings
It's a bit different: code below is ok, and TeX comment is seen before
lua comment .
Only Hello! is
Correction:
-- works as comments in luacode
% is used to format strings
It's a bit different: code below is ok, and TeX comment is seen before lua
comment .
Only Hello! is print on pdf
%%
\def\Foo{%
\startluacode
-- this is a lua comment
%% this is a TeX comment
Mojca Miklavec wrote:
I thought that \startluacode should be behaving the same way as
verbatim environments where commands inside verbatim have no
influence, but apparently I was wrong.
no, more like MPcode where one can mix things
if the luacode would not expand macros, then we'd need
Hello,
Here's a tiny question. The following command complains about
undefined control sequence.
\starttext
\startluacode
print('a\tb')
\stopluacode
hello
\stoptext
There is a workaround:
print(string.format('a\t%s', 'b'))
but I find it weird. Even if the line above gets commented out with
Am 26.11.2008 um 20:07 schrieb Mojca Miklavec:
Hello,
Here's a tiny question. The following command complains about
undefined control sequence.
\starttext
\startluacode
print('a\tb')
print('a\t b')
\stopluacode
hello
\stoptext
There is a workaround:
Aditya Mahajan wrote:
Another bug:
\starttext
\starttablehead
\HL
\stoptablehead
\starttables[|l|l|]
\VL Some text \VL some text \VL \AR
\stoptables
\stoptext
gives Misplaced \noalign.
Bugfix:
\def\stoptables
{\chuckTABLEautorow %AM:Added. before the tail, else noalign
Hi Hans,
|| does not work with tables, and until now I thought that this was a
limitation of tables. But upon reading core-tab, it appears that you
make a lot of effort to make sure that || works correctly, but it does
not. I think that this is due to a mistake in the definition
Another bug:
\starttext
\starttablehead
\HL
\stoptablehead
\starttables[|l|l|]
\VL Some text \VL some text \VL \AR
\stoptables
\stoptext
gives Misplaced \noalign.
Bugfix:
\def\stoptables
{\chuckTABLEautorow %AM:Added. before the tail, else noalign problem
On 4/22/06, Peter Münster wrote:
On Sat, 22 Apr 2006, Mojca Miklavec wrote:
- [with luaTeX in mind] calculating sums of rows columns other
Excel-like calculations references accross tables ;) - well, that
one wasn't meant seriously.
Hello Mojca,
should be possible even without
Hi,
Here is a quick hack that converts csv to commalist values.
Perhaps it helpful for someone. Documentation blurb:
This module parses CSV data (somewhat) safely. After
\def\dataline{a,,\j,a,a\j a,t{f}ab}
\convertcsvdata\dataline\to \myascii
\message{\meaning\myascii}
output is:
to someone's mind); for
example \def\MyDef#1#2{\bTR\bTD#1\eTD\bTD#2\eTD\eTR}; the machinery
behind would only have to feed these macros properly according
- [important] possible to separate the data with different characters:
tab, comma, multiple spaces, ampersand (), ...
- [very useful] a possibility
On Sat, 22 Apr 2006, Mojca Miklavec wrote:
- [with luaTeX in mind] calculating sums of rows columns other
Excel-like calculations references accross tables ;) - well, that
one wasn't meant seriously.
Hello Mojca,
should be possible even without luaTeX:
\input realcalc % can be found on
33 matches
Mail list logo
