ssor. Which will cost a lot, and use a lot of
> > power which has to be cooled, which uses even more power
>
> Startup time can be improved quite a bit with an SSD. Even a cheap
> SATA SSD is already much faster than a traditional harddisk. Doesn’t
> help with longer doc
)
these kind of performance things are demand driven (read: i need a
pretty good reason to spend time on it)
I can’t comment on how to speed up the rest of what you are doing,
but generally multi-threading TeX typesetting jobs is so hard as to
be impossible in practise. About the only step that can
a cheap SATA
SSD is already much faster than a traditional harddisk. Doesn’t help
with longer documents, but it could be a fairly cheap upgrade.
I can’t comment on how to speed up the rest of what you are doing,
but generally multi-threading TeX typesetting jobs is so hard as to
be impossible in
t; this approach.
> >
> > The principle problem is, as you suggested below, "stopping" the
> > pipeline at the PDF stage (using for example the
> > `pre_output_filter`) corrupted the `*.tuc` data which is for my
> > purposes, critical.
> >
> > Your
ent it in ANSI-C wrapped in Lua (so that
> > it can be used from *inside* ConTeXt).
>
> I would have to see the 'kind of code involved' in order to comment
> on that.
>
> An option is to do most in lua and maybe some helpers for crititical
> code in C.
> Hans
>
>
>
have to see the 'kind of code involved' in order to comment on
that.
An option is to do most in lua and maybe some helpers for crititical
code in C.
Hans
-
Hans Hagen | PRAGMA ADE
overall
is not really significant enough to bother with this approach.
The principle problem is, as you suggested below, "stopping" the
pipeline at the PDF stage (using for example the `pre_output_filter`)
corrupted the `*.tuc` data which is for my purposes, critical.
Your comment was:
to bother with this approach.
The principle problem is, as you suggested below, "stopping" the
pipeline at the PDF stage (using for example the `pre_output_filter`)
corrupted the `*.tuc` data which is for my purposes, critical.
Your comment was:
> but keep in mind that multipass da
ementation}\\
\hyphenatedword{reimplementation}
\stopTEXpage
\stoptext
If you comment the first line, only "||" allows hyphenation.
Another option is to add \setbreakpoints[compound] to the document.
Wolfgang
plementation}
\stopTEXpage
\stoptext
If you comment the first line, only "||" allows hyphenation.
I hope it helps,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add
apport_maitriser-l-empreinte-carbone-de-la-france.pdf
>
> Any feedback is welcome (even if source code is not really clean)
Congratulations, Garulfo.
It’s a really good work.
Just a comment, to get clean bookmarks and PDF info, use:
\enabledirectives[references.bookmarks.prer
ctures for ConTeXt Wiki
filename
reference
owner
comment
http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
the problem is
different, but I couldn’t reproduce it in a MWE. I guess the interference of
different note types is the cause of both problems.
I tried using the same custom note for the last comment as a workaround, but it
gets placed twice: once at the bottom of the current page (i.e. like a normal
ce TeXpage with a
> "page"
> >> layout.
> >>
> >> \startlayout[page]
> >> \dorecurse{\noffigurepages}{\externalfigure[...][page=\recurselevel]}
> >> \stoplayout
> >
> > Thanks for the comment (also I didn't know about \startla
/context-blog/post/include-multi-page-pdf/
When both document have the same size you can replace TeXpage with a "page"
layout.
\startlayout[page]
\dorecurse{\noffigurepages}{\externalfigure[...][page=\recurselevel]}
\stoplayout
Thanks for the comment (also I didn't know about \s
ttps://adityam.github.io/context-blog/post/include-multi-page-pdf/
>
> When both document have the same size you can replace TeXpage with a "page"
> layout.
>
> \startlayout[page]
> \dorecurse{\noffigurepages}{\externalfigure[...][page=\recurselevel]}
> \stoplayout
Tha
TeX Gyre Pagella Math]
\setupbodyfont[mainface]
-
ConTeXt loads the [rm] and the [mm] but not the [ss]. Be assured that
the ss typeface is available. So if, for example, I comment out the
first line ([rm]) and change the Libris to rm instead, I am told:
mkiv lua stats >
---
>
> ConTeXt loads the [rm] and the [mm] but not the [ss]. Be assured that
> the ss typeface is available. So if, for example, I comment out the
> first line ([rm]) and change the Libris to rm instead, I am told:
>
> mkiv lua stats > loaded fonts: 2 files: librisadfs
So if, for example, I comment out the
first line ([rm]) and change the Libris to rm instead, I am told:
mkiv lua stats > loaded fonts: 2 files: librisadfstd-regular.otf,
texgyrepagella-math.otf
In other words, only two, not three definitions are working at any one
time. Or is it not accepti
-module-basic.mkiv)
which is used to create the formatted source.
The same has to be done to disable the frame where you have to comment
the \showframe line in the module mentioned above.
Wolfgang
___
If your question
n fault".
> I append the console outputs of the context runs.
>
> If i comment out the input of luametafun-axis and luametafun-followtext
> i get a readeable pdf.
>
> So perhaps only the code is changing too rapidly.
>
> Greetings Lutz
>
> Am 14. August 2020 13:0
uns.
If i comment out the input of luametafun-axis and luametafun-followtext
i get a readeable pdf.
So perhaps only the code is changing too rapidly.
i found the issue ... i switched to a more efficient method of piping a
path back to mp
Hi all
I have a similar problem compiling luametafun.tex in the doc sources.
It fails with different errorcodes on win64 and linux aarch64. On linux aarch64
i get a bonus "Segmentation fault".
I append the console outputs of the context runs.
If i comment out the input of luame
\setfirstline is
not applied at all, i.e., there are no small caps. If I comment out the
first \setfirstline, then the second one does produce small caps, but
again, a whole paragraph is set in small caps, not just the first line.
$ context --version
mtx-context | ConTeXt Process Management 1.03
mtx
it in the main body for 'chapters' that I don't want
numbered, and of course, have ensured that such \title items can appear
in the TOC. But I want to add a one-word comment in brackets to the
title that appears in the TOC, so that I get:
Chapter title (comment).. 5 or whatever the page
' that I don't want
numbered, and of course, have ensured that such \title items can appear
in the TOC. But I want to add a one-word comment in brackets to the
title that appears in the TOC, so that I get:
Chapter title (comment).. 5 or whatever the page number is.
Is there are way I can
> The luatools script was there to offer some kpse like functionality but it
> has been obsolete for ages (the generate was in mtx-base at that time). Just
> use
>
> mtxrun --generate
Should the comment in the engine file change?
Context is called with:
mtxrun -
hing:
Please look at environment variables starting with TEX and comment them, they
will cause problems.
And another one:
Please look into the home directory for a local .texlive2020 folder.
There shouldn’t be any and it shouldn’t contain
On 8/9/20 9:59 PM, Joseph Canedo wrote:
> Hi Pablo,
> I've reported similar issue to Hans 2 days ago, from my checks he fixed
> it in LMTX version 2020.08.07 23:37. I have not downloaded more recent
> version yet.
> Hoping it helps
Hi Joseph,
many thanks for your comment and your
example below.
Best regards: Otared
%%% sidenotes, or footnotes in the margin
%%% example given by Hraban:
%%% here the tweaking of the width of the sidenote is turned off
%%% remove the comment where there is \ColWidth
%%% in order to adapt to your layout
\showframe
\setuplayout
[cutspace
On Fri, 3 Jul 2020 08:40:22 +0200
Fabrice Couvreur wrote:
> Thanks, it works but only for a comment and a picture. Indeed, if I
> add a comment and an image, the first image is placed on the second
> comment. Fabrice
>
> \starttext
> \startuserdata[margintext]
> \input
Hi Marco,
Thanks, it works but only for a comment and a picture. Indeed, if I add a
comment and an image, the first image is placed on the second comment.
Fabrice
\starttext
\startuserdata[margintext]
\input ward
\stopuserdata
\marginfigure{\externalfigure[dummy][width=\rightmarginwidth,location
out (in much older messages) that you're not fully relying
on an answer based on ConTeXt Mk II, because many of those
solutions no longer work in the newer versions.
... which has accidentally led me to another documentation
comment. Hans's programming philosophy is not something I'm an
expe
Jan-Erik Hägglöf schrieb am 24.06.2020 um 21:05:
Hello All!
In the page https://wiki.contextgarden.net/Labels
I’ve tried with no success to run those examples given at the page. The
error complaint as the log shows below
Can you comment (or remove) the following two lines which load the IBM
On 6/24/2020 7:59 PM, Wolfgang Schuster wrote:
Hans Hagen schrieb am 24.06.2020 um 19:06:
On 6/24/2020 6:33 PM, Wolfgang Schuster wrote:
Hi,
when asciimode is enabled the \type command ignores double comment
symbols.
\starttext
\quotation{\type{%}}
\quotation{\type{%%}}
\asciimode
Hans Hagen schrieb am 24.06.2020 um 19:06:
On 6/24/2020 6:33 PM, Wolfgang Schuster wrote:
Hi,
when asciimode is enabled the \type command ignores double comment
symbols.
\starttext
\quotation{\type{%}}
\quotation{\type{%%}}
\asciimode
\quotation{\type{%}}
\quotation{\type
gt; systems and these don't translate; recently i was playing with some css
> setup for a rather complex xml -> html mapping and things that would
> have taken me 5 minutes in tex costs me plenty of time in css due to all
> kind of interactions; just as with tex, one can end up with hacks foun
On 6/24/2020 6:33 PM, Wolfgang Schuster wrote:
Hi,
when asciimode is enabled the \type command ignores double comment symbols.
\starttext
\quotation{\type{%}}
\quotation{\type{%%}}
\asciimode
\quotation{\type{%}}
\quotation{\type{%%}}
\stoptext
It's actually a feature: in ascimode
Hi,
when asciimode is enabled the \type command ignores double comment symbols.
\starttext
\quotation{\type{%}}
\quotation{\type{%%}}
\asciimode
\quotation{\type{%}}
\quotation{\type{%%}}
\stoptext
Wolfgang
On 6/17/20 11:26 PM, Henning Hraban Ramm wrote:
> [...]
> Pablo, do I understand right that you’re converting XML and the
> comment comes last in that structure, but you need it first?> I.e.
> the real question is how to process the XML structure in a different
> order, r
t; \setupinterlinespace[1sp]
>>\stopsetups
This was from a previous form of the sample. If the paragraph is really
tiny, it would be easier not to have a page break between that paragraph
and the
>>\setupinteraction[state=start]
>>\showframe\showgrid
>>
; \setupinterlinespace[1sp]
>> \stopsetups
>
> ???
>
>> \setupinteraction[state=start]
>> \showframe\showgrid
>> \starttext
>> \blank[force, 10em]
>> \section{Move comment above this heading}
>> \startparagraph[setups=tinytiny]
\blank[force, 10em]
\section{Move comment above this heading}
\startparagraph[setups=tinytiny]
\dontleavehmode
\comment[location={rightmargin}, color=orange]
{comment}
\stopparagraph
\stoptext
Is there a way to move the comment above the heading
Dear list,
I have the following sample:
\startsetups[tinytiny]
\setupwhitespace[-2em]
\setupbodyfont[0.01pt]
\setupinterlinespace[1sp]
\stopsetups
\setupinteraction[state=start]
\showframe\showgrid
\starttext
\blank[force, 10em]
\section{Move comment above
On 6/16/20 8:00 PM, Wolfgang Schuster wrote:
> Pablo Rodriguez schrieb am 16.06.2020 um 19:20:
>> [...]
>> I think it might be a bug. Could anyone confirm this?
>
> Why is everything a bug?
>
> Some elements like margin blocks or register entries need an anchor.
Sorry, Wolfgang, I discovered
Pablo Rodriguez schrieb am 16.06.2020 um 19:20:
Dear list,
when trying to report another issue, I found the following one (using
latest from 2020.06.12 17:43):
\setupinteraction[state=start]
\starttext
a\contextversion
\comment[location={rightmargin}]{comment}
\stoptext
another approach. This sample reflects my problem:
\setupinteraction[state=start]
%~ \showframe\showgrid
\starttext
\dorecurse{41}{one line\par}
\ \comment[location={rightmargin}]{comment}
\stoptext
Since layers are problematic for the task, I insert the comments right
after the text
.
I need another approach. This sample reflects my problem:
\setupinteraction[state=start]
%~ \showframe\showgrid
\starttext
\dorecurse{41}{one line\par}
\ \comment[location={rightmargin}]{comment}
\stoptext
Since layers are problematic for the task, I insert the comments right
af
Dear list,
when trying to report another issue, I found the following one (using
latest from 2020.06.12 17:43):
\setupinteraction[state=start]
\starttext
a\contextversion
\comment[location={rightmargin}]{comment}
\stoptext
For some strange reason, \comment isn’t added when
> \setupbackgrounds[page][background=pgnumber]
> \starttext
> \placelist[section][alternative=d]
> \dorecurse{16}{\section{Section}}
> \pagenumber/\lastpagenumber
> \setlayer[pgnumber]
> {\comment{\pagenumber}}
> \stoptext
>
> Could anyone confirm the iss
]
\starttext
\placelist[section][alternative=d]
\dorecurse{16}{\section{Section}}
\pagenumber/\lastpagenumber
\setlayer[pgnumber]
{\comment{\pagenumber}}
\stoptext
Could anyone confirm the issue?
\pagenumber is only reliable headers/footer texts or page backgrounds
]
\dorecurse{16}{\section{Section}}
\pagenumber/\lastpagenumber
\setlayer[pgnumber]
{\comment{\pagenumber}}
\stoptext
Could anyone confirm the issue?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
os.execute("locale") from context is different from that from my shell. But I
don't know why locale should affect UTF characters in R. Perhaps someone with more
knowledge of R can comment on that.
\starttext
\startluacode
lfs.mkdir("output/")
\stopluacode
\st
would need to recompile the document again for each new required
/PrintPageRange.
Another approach would be to add PDF annotations (outside page
boundaries) to store the desired information.
So I created text annotations (using \comment) with author information
composed from unit number
: \hideblocks[NLblok]%\hideblocks[ENblok] For the titles I use another method: %\def\NL#1{#1}\def\NL#1{{}}%\def\EN#1{}\def\EN#1{#1} You have to comment and uncomment, depending on the language, but I think you can put them in the NLblok or ENbloks instead. \definecomplexenumeration[Casus]… definition
to comment and uncomment, depending on the language, but I think you
can put them in the NLblok or ENbloks instead.
\definecomplexenumeration[Casus]
… definition
\def\refno#1{{\em{(no. \small #1})}}
My files look like this:
\starttext
\startCasus[casus-349][\NL{Een moeilijke zaak}\EN{A complicated case
t;
>
> Index statistics:
>
> 4085 files processed, 178 skipped, 3744 with matches
> 120733 words found
> 119154 words exported to word.idx
> 37928 comment words found
> 36880 words exported to comm
sList{>>> \page[yes] \stopmode>>> }>>> \definestartstop[Questions][>>> before=\StartQuestionsList,>>> after=\StopQuestionsList>>> ]>>> >>> >>> \startQuestions>>> Question A….>>> Question B….>>> \stopQu
;>> \page[yes] \stopmode
>>>> }
>>>> \definestartstop[Questions][
>>>> before=\StartQuestionsList,
>>>> after=\StopQuestionsList
>>>> ]
>>>>
>>>>
>>>> \startQuestions
>>>> Question A….
>>>> Question B….
>>
tions
Question A….
Question B….
\stopQuestions
Some other text...
%
One of the oldest mechanism available ... blocks:
\enablemode[classroom] % comment this
\defineblock[Question]
\doifmode {classroom} {
\keepblocks[Question]
}
\starttext
Text A
:
4085 files processed, 178 skipped, 3744 with matches
120733 words found
119154 words exported to word.idx
37928 comment words found
36880 words exported to comment.idx
26756 documentation words found
26018 words exported to docs.idx
The word.idx is roughly 11 megabytes.
Have fun,
Taco
On Sat, 16 May 2020, Aditya Mahajan wrote:
On Sat, 16 May 2020, Nicola wrote:
On 2020-05-16, Aditya Mahajan wrote:
On Sat, 16 May 2020, Aditya Mahajan wrote:
Moreover, if you comment line line 126 of `2context.vim`
"let s:id = synIDtrans (s:id)
[If you make a local
On Sat, 16 May 2020, Nicola wrote:
On 2020-05-16, Aditya Mahajan wrote:
On Sat, 16 May 2020, Aditya Mahajan wrote:
Moreover, if you comment line line 126 of `2context.vim`
"let s:id = synIDtrans (s:id)
[If you make a local copy of 2context.vim, then you need to run the
On 2020-05-16, Aditya Mahajan wrote:
> On Sat, 16 May 2020, Aditya Mahajan wrote:
> Moreover, if you comment line line 126 of `2context.vim`
>
> "let s:id = synIDtrans (s:id)
>
> [If you make a local copy of 2context.vim, then you need to run the
> file with
highlighting element, which in this case is `Function`. So, there is no tag
generated for `rubyMethodName` and that is why changing the syntaxhighlight
for that doesn't change anything.
Moreover, if you comment line line 126 of `2context.vim`
"let s:id = synIDtrans (s:id)
[If you
,19.935*cm);
for xord = 0 step 0.1 until 25:
show xord;
fails at xord = 13.5%
yord := ((-0.000268117) * pow(xord,4)) +(0.0136949 * pow(xord, 3)) +
((-0.16608) * sqr(xord)) + ((-0.771743) * xord) + 19.935;
%comment out above and uncomment below and it works
% yord1
scaled .1cm ;
path pat;
pat := (0.0*cm,19.935*cm);
for xord = 0 step 0.1 until 25:
show xord;
fails at xord = 13.5%
yord := ((-0.000268117) * pow(xord,4)) +(0.0136949 * pow(xord, 3)) +
((-0.16608) * sqr(xord)) + ((-0.771743) * xord) + 19.935;
%comment out above
or[nearlywhite] [r=0.988, g=0.988, b=0.988]
\setupinteraction[state=start]
\setupcolors[textcolor=colorone]
\setupbackgrounds[page][background=color,backgroundcolor=nearlywhite]
\usemodule[vim]
\unprotect
\startcolorscheme[oceansunset]
\definesyntaxgroup[Comment][\c!color={co
\hskip 1em
>> \vtop{\hsize\dimexpr\textwidth-3em\relax#2}
>> \egroup \par}
>>
>> % Comment out this next line to regain section hyperlinks in the ToC
>> \setuplist[section][alternative=command,command=\SectionListEntry]
>
> alternative
[option=bookmark]
\define[3]\SectionListEntry
{\par \leftaligned\bgroup
\hbox to 2em{#3}%
\hskip 1em
\vtop{\hsize\dimexpr\textwidth-3em\relax#2}
\egroup \par}
% Comment out this next line to regain section hyperlinks in the ToC
\setuplist[section][alternative
etupinteraction[state=start]
> \setupinteractionscreen[option=bookmark]
>
> \define[3]\SectionListEntry
> {\par \leftaligned\bgroup
> \hbox to 2em{#3}%
> \hskip 1em
> \vtop{\hsize\dimexpr\textwidth-3em\relax#2}
> \egroup \par}
>
> % Comment o
{\par \leftaligned\bgroup
\hbox to 2em{#3}%
\hskip 1em
\vtop{\hsize\dimexpr\textwidth-3em\relax#2}
\egroup \par}
% Comment out this next line to regain section hyperlinks in the ToC
\setuplist[section][alternative=command,command=\SectionListEntry]
\starttext
Table
On Thu, 14 May 2020, Nicola wrote:
Quick question: Is \startcolorscheme... \stopcolorscheme (still)
supported by t-vim?
In a template I wrote long time ago to typeset code, I have:
\usemodule[vim]
\unprotect
\startcolorscheme[oceansunset]
\definesyntaxgroup[Comment][\c!color
Quick question: Is \startcolorscheme... \stopcolorscheme (still)
supported by t-vim?
In a template I wrote long time ago to typeset code, I have:
\usemodule[vim]
\unprotect
\startcolorscheme[oceansunset]
\definesyntaxgroup[Comment][\c!color={colortwo},\c!style=italic
local c1, c2 = string.find(xml, "", c2 + 1, true)
if c3 then
-- Remove comment.
xml = string.sub(xml, 1, c1 - 1) .. string.sub(xml, c4
+ 1, -1)
-- Search for next comment.
c1, c2 = string.find(xml, "
t;pdftex"]=true,
["xetex"]=true,
},
["formats"]={
["cont-en"]=true,
["cont-nl"]=true,
["metafun"]=true,
},
["info"]={
["comment"]="this file contains the settings of the last 'mtxrun --script
update' run&quo
They are just an option. The tilde (~) is added after the percent sign
(%), because “Geany” (the text editor I use) adds it after the comment
sign in different programming languages. It has no special meaning.
> What I try to do is to have english as the default (and fallback)
> language and
issue of the journal in one go. (I
would simply comment out the \input line and add \startproject \startcomponent
etc lines as necessary from each received article.)
Problem:
I've created a custom chapter heading, but the font size changes depending on
whether I'm processing the \input version
comment out the \input line and add \startproject \startcomponent
etc lines as necessary from each received article.)
Problem:
I've created a custom chapter heading, but the font size changes depending on
whether I'm processing the \input version of the article or the \component
version and I
d
> % !TEX root=../prd_\mystring.tex
Processing single components won’t work in your project, since I defined
several metadata macros in the product. More off list.
> with, e.g., \def\mystring{Name01} in the prd_Name01.tex file, but that does
> not seem to work—the various .tex files re not foun
Mark]{4}(4) \input knuth\par
> > \marking[TestMark]{5}(5) \input knuth\par
> > \marking[TestMark]{6}(6) \input knuth\par
> > \marking[TestMark]{7}(7) \input knuth\par
> > \marking[TestMark]{8}(8) \input knuth\par
> > \stoppagecolumns
> > \st
with
TeXLive 2020. As my comment in the MWE points out, there also seems to
be a bug in the key-value parsing of \definepagecolumns that causes it
not to parse the direction=reverse input unless it is followed by a comma.
Is there some way I can improve my syntax to avoid this issue
\marking[TestMark]{6}(6) \input knuth\par
\marking[TestMark]{7}(7) \input knuth\par
\marking[TestMark]{8}(8) \input knuth\par
\stoppagecolumns
\stoptext
```
I typeset this using ConTeXt version 2020.03.10, as released with TeXLive
2020. As my comment in the MWE points out, there also
generate a perfect ConTeXt
source to build the file as some things are missing.
Annotations and eg. your classify.lua might be a second approach to
achieve what I want.
So thanks a lot for your work.
@all: Feel free to comment
mplex. And this would be
the best way to scare newcomers.
If you aren’t scared, t-handlecsv.lua contains a complete list of
defined commands (as a huge comment near the end of the file). You might
be interested in reading them.
Or feel free to ask here for help, if you don’t find the com
= fullsquare xysized (w, h);
>%pth2 = fullsquare xysized (h/4, h/8)
>pic := image (
>draw pth;
>%draw pth2 shifted (-w/2, -h/4);
>% all kind of stuff here
>);
>setbounds pic to pth;
>pic
> enddef ;
>
> As soon as I unco
here
);
setbounds pic to pth;
pic
enddef ;
As soon as I uncomment the bold line (first comment) a mtxrun fails. Whatever I
try, a single save statement, etc., I fail in getting a second local variable.
The METAPOST manual is no help.
The error shown is:
metapost log> ! Ex
gt;> that
>> it is a bug.
>
> This one is for Aditya who knows more about these math alignments (needs)
> than I
> do.
>
> Aditya: when we comment the \aligntab it's ok but i'm hesitant to do that
> patch
> ... so do you see bad co
ere is in pdfm is pretty weird and
> actually can make viewers bark. Irr the current approach we follow is
> kind of a compromise.
Just a comment on one of the issues.
Maybe the simplest way to avoid the issues with the annotation flag is
not including it at all.
Once annotations have ap
linenumbering
# \blank [line]
#\startlinenumbering[translation]
#\input klein
#\stoplinenumbering}
#
# \stoptext
#
# If you compile it, you will see that the “color” key of the two defined
linenumbering environments is not followed. If you comment out the first line
\setbreakpoints [comp
oplinenumbering
\blank [line]
\startlinenumbering[translation]
\input klein
\stoplinenumbering}
\stoptext
If you compile it, you will see that the “color” key of the two defined
linenumbering environments is not followed. If you comment out the first line
\setbreakpoints [compound], you will get tw
ound
>
> then the second(?) paragraph of the second enumeration is not indented.
>
> Here is a small example (see what lines to comment to avoid the problem).
>
> %%%
> \defineenumeration[losning][
> text=Lösning,
> title=yes,
> alternative=serried,
> width=fit,
> number=no,
rhaps a font
feature file is the place to do such a thing.
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
type = "kern",
data = {
[" "] = {
["J"] = 1000 % exaggerated value
Should of course be a Lua com
to do such a thing.
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
type = "kern",
data = {
[" "] = {
["J"] = 1000 % exaggerated value
Should of course be a Lua comment
["J"] = 1000 --
acode
fonts.handlers.otf.addfeature {
name = "kern",
type = "kern",
data = {
[" "] = {
["J"] = 1000 % exaggerated value
Should of course be a Lua comment
["J"] = 1000 -- exaggerated value
}
}
what lines to comment to avoid the problem).
%%%
\defineenumeration[losning][
text=Lösning,
title=yes,
alternative=serried,
width=fit,
number=no,
headstyle={\em},
titlestyle=,
indentnext=no,% another way to get indentation is to comment this line
indenting={yes,medium},
]
\defineframedtext
Wolfgang answered this a while back. See Re: [NTG-context] Room
for comment on the backside of form. .
--
Rik
Replace the \hphantom{...} with \dontleavehmode.
--
Rik
___
If your question is of interest to others
tex output didn't look any better in a display of some
80 summaries at some meeting (the, oh, look how bad that table looks
experience).
(I'm sure Arthur, when reading this, can comment as we sort of had this
at a theme of a talk!)
(And, yes I consider myself a happy tex user, but I also admit
Wolfgang answered this a while back. See Re: [NTG-context] Room
for comment on the backside of form. .
--
Rik
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg
ntext@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
>>
>> webpage :
>> http://www.pragma-ade.nl / http://context.aanhet.net
>>
>> archive :
>> https://bitbucket.org/phg/context-mirror/commits/
>>
>> wiki :
>> http://contextgarden.net
>>
>>
301 - 400 of 2237 matches
Mail list logo
