: 150, direct: 2, late: 0,
function 1062, total: 1336
mkiv lua stats > randomizer: resumed with value 0.82539481794329
mkiv lua stats > result saved in file: t.pdf, compresslevel 3,
objectcompresslevel 1
mkiv lua stats > loaded patterns: en::1, load time: 0.000
mkiv lua stats > lo
of the directories in OSFONTDIR, e.g.
~/Library/Fonts, or into the project directory, it works.
I don’t see a pattern which fonts are found and which not (except that the only
Type 1 font family I tried didn’t work, i.e. only after I installed the TTF
version in ~/Libraray/Fonts).
I already
On 4/11/2020 11:44 PM, Tomas Hala wrote:
Hi all,
in the following code
\starttext
\type{6\az12}% \az = \anycommand
\bTABLE
\bTR\bTD\type{6\az12}\eTD\eTR
\eTABLE
\stoptext
there is a different behaviour of \type: while its parametr
in normal text is printed out as is (expected
Hi all,
in the following code
\starttext
\type{6\az12}% \az = \anycommand
\bTABLE
\bTR\bTD\type{6\az12}\eTD\eTR
\eTABLE
\stoptext
there is a different behaviour of \type: while its parametr
in normal text is printed out as is (expected), in the TABLE
the extra space is displayed after
gt; fonts > defining > forced type 'otf' of
> 'fontawesome5brandsregular400' not found
> fonts > defining > font with asked name
> 'fontawesome5brandsregular400' is not found using lookup 'file'
>
> Le sam. 11 avr. 2020 à 16:12, kaddour kard
ar400.otf' as 'thedefinedfont--0'
fonts > defining > forced type 'otf' of
'fontawesome5brandsregular400' not found
fonts > defining > font with asked name
'fontawesome5brandsregular400' is not found using lookup 'file'
Le sam. 11 avr. 2020 à 16:12, ka
thor={Xristoph}
]
\definetyping[mine][numbering=line,tab=4,location=left]
\starttext
This is a small example trying to use verbatim linenumbering in xml export
\startmine
#!python
a=12
def hellow_world(hello):
print("simon says: {}".format(hello))
hallo_welt("how do youdo&quo
t; warn( "STRING.FORMAT TeX-ed \"%s\"", tmpString)
> warn( "STRING.FORMAT Replaced \"%s\"", lpeg.replacer(rep):match(tmpString))
> return lpeg.replacer(rep):match(tmpString)
> end
>
> function warnAndConTeXt( ...)
> warn( ...)
rep):match(tmpString)) return lpeg.replacer(rep):match(tmpString)endfunction warnAndConTeXt( ...) warn( ...) context( ...)endfunction moduledata.test( filename) local labelString context( "The string to typeset is:\\par\\type-{Label} \"a\" [Text]!-") context( "\\par The att
n lpeg.replacer(rep):match(tmpString)
end
That works. Then, in METAPOST the vardef ‘ApplicationComponentLogo’ calls a
vardef makeTeXLabel
draw makeTeXLabel( w, h, name) shifted (w/2,0);
which, for now, simplified does this:
vardef makeTeXLabel( expr w, h, name) =
save p; picture p ;
save
eXlive 2019 on macOS 10.15.3.
>
> I'm sorry for the bad news but without a patch for the font (which can
> probably applied with a goodies file) there is nothing which can be
> done. As the Type 1 version of the Lucida fonts had a few problems in
> the last few years with ConTeXt MkIV I don
be
done. As the Type 1 version of the Lucida fonts had a few problems in
the last few years with ConTeXt MkIV I don't think Hans has much
interest to fix them again (especially when you can expect new problems
in the future).
The best way here is to use another font or spend the money
ble to use (almost) any character in that variable.
I can adapt the strings, if I know what I have to replace things with. I can
manipulate the strings while still in lua. But if I change it and then via MP
hand it to a \type{} statement in ConTeXt the replacement will be typeset
literally. So, it
tex.
I’m using MetaFun actually.
An example string in texcommands would in the end be something like
string texcommands;
texcommands := "\type-{Hello}, [World]!-";
Minimum example of my vardef that fails (the outcommented alternative to the
scantokens line works and typesets “{Hello},
ore Bar and not “ which is the problem.
Yes, I am aware that that is my problem. It is just that I do not have
the luxury to decide myself what will be put in the string. It must work
for any string. So, I will have to be putting that string to \type and
make sure that is used as the label.
e to change al “ instances into something else by walking
>> through the string and building a new one.
>
> Your example uses " before Bar and not “ which is the problem.
Yes, I am aware that that i
annot access the components of the picture anymore with pathpart.
>>
>> I found metapost vardef returning multiple values on StackExchange but that
>> is about returning multiple values of the same numeric type. Is it possible
>> to have vardef return a set of (picture, p
t.
>
> I found metapost vardef returning multiple values on StackExchange but that
> is about returning multiple values of the same numeric type. Is it possible
> to have vardef return a set of (picture, path) or (picture, picture) in some
> way? If not, I need to make two vard
Subject: [NTG-context] Source Code with Bolded Keywords
> Message-ID:
> j5f28-8qv3ykrp+ev+ukrf0q+sp3mabskapxbkvn956...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> I am trying to typeset source code for a custom progr
tps://tex.stackexchange.com/questions/448740/metapost-vardef-returning-multiple-values>
on StackExchange but that is about returning multiple values of the same
numeric type. Is it possible to have vardef return a set of (picture, path) or
(picture, picture) in some way? If not, I need to make two vardef
\stopbuffer
\startxmlsetups xml:initialize
\xmlsetsetup{#1}{date}{xml:date}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:date
\xmldoifelse {#1}{.[@type='divDate']} {
\def\docdate{\ctxlua{
local tyear = string.sub('\xmlatt{#1}{when-iso}',1,4)
local tmonth = string.sub('\xmlatt{#1
>>
>> 10.I.08
>>
>>
>> 19 Mar '08
>>
>>
>>
>>
>>
>> \stopbuffer
>> \startxmlsetups xml:initialize
>> \xmlsetsetup{#1}{date}{xml:date}
&
= 'tomas_hala',
factor = 1,
}
fonts.protrusions.vectors.tomas_hala = table.merged (
fonts.protrusions.vectors.quality,
{
[0x002D] = { 0.4, 0.7 }, -- hyphen
}
)
\stopluacode
\definebreakpoints [czcompound]
\definebreakpoint [czcompound] [-] [nleft=3,nright=3,type=4
[czcompound]
\definebreakpoint [czcompound] [-] [nleft=3,nright=3,type=4]
\startsetups [czech]
\setbreakpoints [czcompound]
\stopsetups
\setuplanguage
[cz]
[setups=czech]
\definefontfeature [default] [default] [protrusion=tomas_hala]
%\def\mylanguage{cs} \appendtoks \ifx\mylanguage\currentlanguage
\se
efinebreakpoint [czcompound] [-] [nleft=3,nright=3,type=4]
\startsetups [czech]
\setbreakpoints [czcompound]
\stopsetups
\setuplanguage
[cz]
[setups=czech]
\definefontfeature [default] [default] [protrusion=tomas_hala]
\setupalign [hanging]
\mainlanguage [cz]
\showframe [text] [text]
\st
Hi all,
in composed words in Czech and Slovak languages, the hyphen must be repeated
at the beginning of the new line. How can I make it hanging at the left margin?
Tomáš
% for repeating the hyphen
\definebreakpoints[czcompound]
\definebreakpoint[czcompound][-][nleft=3,nright=3,type=4]
\def
-server-ctx-startup.lua
mtx-server | loading script:
/home/vm/data/context/tex/texmf-context/scripts/context/lua/mtx-server-ctx-startup.lua
mtx-server | return type: function
mtx-server | saving script: function
mtx-server | running script:
/home/vm/data/context/tex/texmf-context
led. I think I can do this in Gimp.
✔︎
>> For type and logos I still rely on (device dependend) CMYK colors and
>> my experience how they’ll come out in Euroscale printing.
> Device depended means what?
Not profiled.
I.e. the actual resulting color depends on the device, if it’s only d
ke Adobe RGB or one of the profiles
> that shrink the RGB color space to printable colors.
1. All my images should be profiled. I think I can do this in Gimp.
> For type and logos I still rely on (device dependend) CMYK colors and
> my experience how they’ll come out in Euroscale printing.
Device
> Hi,
> > >
> > > One can easily enable small caps when using lucida, see the old
> mail
> > > https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
> > >
> > > Could this be added to the type script
is the same.
That means you should keep your photos in (profiled) RGB. Probably best use
sRGB to stay device independend, because that’s default for monitors, even if
printshops like Adobe RGB or one of the profiles that shrink the RGB color
space to printable colors.
For type and logos I still
mail
> https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
>
> Could this be added to the type script file?
best use \smallcaps or somethign equivalent
Ah, so it was the \sc that was the problem. Thanks!
\sc is more somthing mkii ... when type1 fonts (in an
On 2/15/2020 4:34 PM, Mikael P. Sundqvist wrote:
Hi,
One can easily enable small caps when using lucida, see the old mail
https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
Could this be added to the type script file?
best use \smallcaps or somethign equivalent
Hi,
One can easily enable small caps when using lucida, see the old mail
https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
Could this be added to the type script file?
/Mikael
___
If your question
achment
> in my example hinges on the handling of the attachment mime type. I have
> filed a defect report with VeraPDF, which appears to be rejecting valid
> mime type that includes a charset clause.
If this is a bug, they should fix it. They may have missed a valid M
it as the attachments tab.
What is more troublesome on the ConTeXt side is the validation issue
with the appearance dictionary for visible attachments.
The difference between validators when looking at the hidden attachment
in my example hinges on the handling of the attachment mime type. I have
filed
, xx xxx xxx xx
\type{yyy}.
xx x x xx x xx xxx.
\stopframedtext
\stoptext
```
while the following works:
```
\setupframedtext[
width=broad,
align={verytolerant, stretch}
]
\starttext
\startframedtext[align
iles.xml putting it in
> texmf-local/colors/icc/context/ with this additional xml:
>
>
> PSO_Uncoated_ISO12647_eci.icc
> CMYK
> prtr
> Custom
> PSO Uncoated ISO12647 ECI
> ae81087e1c54c6fdda2f93bd2d47cfaf
> 200
>
doesn't contain an entry, and fails VeraPDF for clauses 6.8-1
and 6.3.3-1.
Hi Rik,
as for 6.8-1, did you set MIME type of the attached file (such as in
"type={application/pdf}")?
Oddly, the bookmarks do not appear either way under MkIV, and they do
not appear when the attachment is vis
n entry, and fails VeraPDF for clauses 6.8-1
> and 6.3.3-1.
Hi Rik,
as for 6.8-1, did you set MIME type of the attached file (such as in
"type={application/pdf}")?
> Oddly, the bookmarks do not appear either way under MkIV, and they do
> not appear when the attachment is visible
CMYK
prtr
Custom
PSO Uncoated ISO12647 ECI
ae81087e1c54c6fdda2f93bd2d47cfaf
200
http://www.eci.org
Commercial and specialty offset, paper type 4,
uncoated white paper, positive plates, tone value increase curves C
(CMY) and D (K), white
>
>
> ISOcoated_v2_300_eci.icc
> CMYK
> prtr
> FOGRA39
> ISO Coated v2 300% (ECI)
> e14f5db955711d914d877df35ad7a1b5
> 2400
> http://www.color.org
> Offset printing, according to ISO
inting, according to ISO 12647-2:2004/Amd 1,
OFCOM, paper type 1 or 2 = coated art, 115 g/m2, tone value increase curves A
(CMY) and B (K)
Is there a linux tool to test if the correct profile is part of the pdf?
Any hints?
TIA
juh
--
Autoren-Homepage: . http://literatur.hasecke.com
Satiren &a
example).
In that cases, renaming actual files could be both undesirable and a lot
of work.
It is mainly a question of consistency. Also across applications.
Consider the following sample:
\setupinteraction[state=start]
\starttext
\startTEXpage[offset=1em]
attachment\attachment[file=xm
Am 08.02.2020 um 09:31 schrieb Pablo Rodriguez:
> Hi Peter,
>
> here you have a minimal sample with file name changed inside the
> attachment command:
>
>\setupinteraction[state=start]
> \starttext
> an attachment\attachment[file=secret-name.pdf,
>
ray.icc},
>> level=0]
>>
>> \setupcolors[pagecolormodel=auto]
>>
>> \setupinteraction[state=start]
>> \starttext
>> \startTEXpage[offset=1em]
>> an attachment\attachment[file=xml-mkiv.pdf,
>> type={application/pdf}]
>&g
Hi Peter,
here you have a minimal sample with file name changed inside the
attachment command:
\setupinteraction[state=start]
\starttext
an attachment\attachment[file=secret-name.pdf,
type={application/pdf},
%~ method=hidden,
name=other-name]
\stoptext
,default_gray.icc},
level=0]
\setupcolors[pagecolormodel=auto]
\setupinteraction[state=start]
\starttext
\startTEXpage[offset=1em]
an attachment\attachment[file=xml-mkiv.pdf,
type={application/pdf}]
\stopTEXpage
\stoptext
With "method=h
t_gray.icc},
level=0]
\setupcolors[pagecolormodel=auto]
\setupinteraction[state=start]
\starttext
\startTEXpage[offset=1em]
an attachment\attachment[file=xml-mkiv.pdf,
type={application/pdf}]
\stopTEXpage
\stoptext
With "method=hidden" (no attachment anno
]
a\attachment[file=abdfaeasd.txt, name=hola, method=hidden]
\contextversion
\stopTEXpage
\stoptext
File name is changed:
2 0 obj
<<
/AFRelationship /Unspecified
/EF <<
/F 1 0 R
>>
/F (hola.txt)
/Type /Filespec
/UF
in file: t-Font.pdf, compresslevel 3,
objectcompresslevel 1
mkiv lua stats > loaded patterns: en::1, load time: 0.000
mkiv lua stats > loaded fonts: 4 files: lmroman10-bold.otf,
lmroman10-bolditalic.otf, lmroman10-italic.otf, lmroman10-regular.otf
mkiv lua stats > font engine: otf 3.1
erant,broad},width=%sbp]{%s}")
shifted center AllNodes[%i] ;',w,name,i)
as command to draw a node and the node type is defined like this:
context("save ApplicationComponent ; path ApplicationComponent ;
ApplicationComponent := unitsquare ; ")
For a quick example this works, but ‘uni
Hello Pablo,
also Lua might be useful for you - some code like the one bellow, which
is based on an answer in this forum years ago:
assert(not figures.getinfo2)
figures.getinfo2 = function(name, page) -- [ [NTG-context] Pdf info with
Lua/Ctx API ]
if type(name) == "s
Another set of columnset issues: columnset areas
(1)
In the columnsets manual, there’s a type key or a second optional parameter to
\definecolumnsetarea that’s actually missing (commented code in page-cst.mkiv).
The manual doesn’t explain the setup keys; I assume x/nx is in columns, y/ny
of paragraphs.
\endash~he continued.
\stopsection
\startsection[title=Actual output]
\speech{Speech should always have a dash at the start, but none at the
end of a
paragraph.}
\speech{Dialog asides should not duplicate dashes, \aside{he said.}}
Also, note
the spacing isn't removed despite \type
continued.
\stopsection
\startsection[title=Actual output]
\speech{Speech should always have a dash at the start, but none at the
end of a
paragraph.}
\speech{Dialog asides should not duplicate dashes, \aside{he said.}}
Also, note
the spacing isn't removed despite \type{\removeunwantedspaces
function document.myfunction(n,x)
local S
S = math.sin(n*x)
return S
end
\stopluacode
\starttext
Here \type{document.myfunction(n,x)} is $\sin(nx)$. For instance when $n = 2$
and $x = 355/113$ we have:
\type{document.myfunction(2,355/113
)
local S
S = math.sin(n*x)
return S
end
\stopluacode
\starttext
Here \type{document.myfunction(n,x)} is $\sin(nx)$. For instance when $n = 2$
and $x = 355/113$ we have:
\type{document.myfunction(2,355/113)}
$=\cldcontext{document.myfunction(2,355/113
]
\definefontfeature [TestB] [default][kern=no]
\definefontfeature [TestC] [default][kern=no,xkern=yes]
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
type = "kern",
data = {
[" "] = { ["X"] = 4000 }
}
}
fonts.handl
]
[features=default]
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
type = "kern",
data = {
["x"] = { ["x"] = -300 },
[" "] = { ["A"] = 1000
]
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
type = "kern",
data = {
["x"] = { ["x"] = -300 },
[" "] = { ["A"] = 1000 }
}
}
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 --
ompresslevel 1
mkiv lua stats > loaded patterns: en::1, load time: 0.000
mkiv lua stats > loaded fonts: 3 files: almfixed.otf, latinmodern-math.otf, lmroman12-regular.otf
mkiv lua stats > font engine: otf 3.110, afm 1.513, tfm 1.000, 8 instances, 3 shared in backend, 3 common vectors, 0 commo
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
}
}
which does not share the problem.
As Henri's answer hints, I was a bit unclear in my request. It is a kern
between a word space and the cap J that is the issue. Perhaps a font
feature file is the place to do such a thing.
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
ation is welcome. This is just for a sampler -- the
font with just three weights when used in a real project is fine. I do
not know if the problem is with the font or with ConTeXt or with my
expectations.
i donloaded the fonts from
https://github.com/indestructible-type/Jost/tree/master/Finishe
Henning Hraban Ramm schrieb am Fr., 20. Dez. 2019, 07:50:
> Hi,
> I setup a layer to the size of the typearea and expect the corner presets
> to place my figures into the corners, but \makeupwidth/height are smaller
> than the typearea (same with \textwidth). Why?
> Hraban
>
>
> \setuplayout[
>
Hi,
I setup a layer to the size of the typearea and expect the corner presets to
place my figures into the corners, but \makeupwidth/height are smaller than the
typearea (same with \textwidth). Why?
Hraban
\setuplayout[
width=120mm,
backspace=16mm,
height=192mm,
","\n"
local file,err = io.open( filename, "wb" )
if err then return err end
-- initiate variables for save procedure
local tables,lookup = { tbl },{ [tbl] = 1 }
fi
This is the text of an index term, that is normally justified,
but I'd like the page numbers to be flushed to the right from
their second line}
\def\Pages{34, 57, 101-104, 276, 345, 401, 403, 512.}
\type{\PlaceIndexTerm[margin=1em,distance=1em,minwidth=1em]{text}{pages}}
\startitemize
\item margin
-104, 276, 345, 401, 403, 512.}
\type{\PlaceIndexTerm} has 6 parameters:
\startitemize[n]
\item the main text
\item the pages' numbers
\item the text width
\item the left margin of the lines made only of page numbers
\item the width of the separator (an hbox) before the first page
number, when
This is a good-enough solution to my problem:
\setupalign[stretch]
\starttext
\def\Text{This is the text of an index term, that is normally justified,
but I'd like the page numbers to be flushed to the right from
their second line}
\def\Pages{34, 57, 101-104, 276, 345, 401, 403, 512.}
\type
c =
str =
i = 0
#12 0x00503a25 in expand () at
../../../source/texk/web2c/luatexdir/tex/expand.c:259
t =
p =
---Type to continue, or q to quit---
cur_ptr =
cv_backup = 0
cvl_backup = 0
radix_backup = 0
mf schrieb am 10.12.2019 um 12:27:
Hello list, is there a way to achieve this?
\def\FlushRightFromNextLine{\relax}
\setupnarrower[left=0cm,right=11cm]
\setupalign[stretch]
\starttext
This is what I'd like to type in my source:\par
\blank
\type{This is the text of an index term, that is normally
Hello list, is there a way to achieve this?
\def\FlushRightFromNextLine{\relax}
\setupnarrower[left=0cm,right=11cm]
\setupalign[stretch]
\starttext
This is what I'd like to type in my source:\par
\blank
\type{This is the text of an index term, that is normally justified,
but I'd like the page
Hi Otared,
Hi Dalyoung,
May be you could do the following steps (I recently had some issues too with
installing the new beta, and these are what I did):
Can you add this to the wiki someplace?
• In Terminal type:
which luametatex
in order to see whether
/context
Hi Dalyoung,
May be you could do the following steps (I recently had some issues too with
installing the new beta, and these are what I did):
• In Terminal type:
which luametatex
in order to see whether
/context-osx-64/tex/texmf-osx-64/bin/luametatex
is present
Am 06.12.2019 um 16:56 schrieb Hans Hagen:
> On 12/6/2019 4:21 PM, Peter Rolf wrote:
>> Hi Rik,
>>
>> I guess it's not supported yet.
>>
>> In "lpdf-fmt.lua" it says:
>> [..]
>> ["pdf/a-3a"] = { -- untested; NEW: any
On 12/6/2019 4:21 PM, Peter Rolf wrote:
Hi Rik,
I guess it's not supported yet.
In "lpdf-fmt.lua" it says:
[..]
["pdf/a-3a"] = { -- untested; NEW: any type of attachment is allowed
[..]
I remember adding the "a-2a" and "a-3a" versions back wh
Hi Rik,
I guess it's not supported yet.
In "lpdf-fmt.lua" it says:
[..]
["pdf/a-3a"] = { -- untested; NEW: any type of attachment is allowed
[..]
I remember adding the "a-2a" and "a-3a" versions back when Hans and I
added experimental support for
thanks for an answer.
\starttext
\section{One}
\startitemize
\item \type{\displaystyle}: $\displaystyle\sum\lim$
\item \type{\textstyle}: $\sum\lim$
\item \type{\scriptstyle}: $\scriptstyle\sum\lim$
\stopitemize
\section{Two}
$\underbrace{xyz}_{n}$
\section{Three}
also posted at https
[file=test.tex,
% type={text/plain;charset=UTF-8}]
% The \ConTeXt\ source code for this document is attached here.
\attachment [file=testa.pdf,
type={application/pdf}]
A successfully validated pdf/a-3a file is attached here
from the same line, they have the same /Rect), as
shown in the excerpt:
21 0 obj
<<
/Type /Annot
/NM (attachment:3)
/Subtype /FileAttachment
/Rect [ 35.54572 493.13349 41.52002 499.1078 ]
>>
endobj
22 0 obj
<<
/Typ
contain photos
of
same height with respect to center horizontally all columns at end of page.
can be done in tex of lua
- To complete abbreviations of long picture names; it's rather annoying doing
this by copy and paste with hundreds of photo names; instead I'd like to type
a short
layers, if neighboured layers should contain photos
of
same height with respect to center horizontally all columns at end of page.
- To complete abbreviations of long picture names; it's rather annoying doing
this by copy and paste with hundreds of photo names; instead I'd like to type
a shor
make the lot more robust for file names, environment variables,
> command line options etc that (at the tex/lua end utf8) have characters
> other than ascii. Another improvement in lmtx is support for ancient
> type 1 fonts (like the type 1 lucidas) but that's more 'being complete'
,
command line options etc that (at the tex/lua end utf8) have characters
other than ascii. Another improvement in lmtx is support for ancient
type 1 fonts (like the type 1 lucidas) but that's more 'being complete'
than a 'real need' (when such fonts are used wiping the cache is
needed). Both
Hello,
many thanks again, especially \type[compact=absolute] and
\typeinlinebuffer solve my problem!
Best regards,
Lukas
On 2019-11-08 09:52, Hans Hagen wrote:
On 11/8/2019 12:11 AM, Aditya Mahajan wrote:
On Thu, 7 Nov 2019, Wolfgang Schuster wrote:
A way to avoid this problem
{\APPDATA{file.txt}}
or ...
\footnote{\type[compact=absolute]{%APPDATA%\file.txt}}
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53
> Hello,
>
> thanks Aditya and Wolfgang for "deep" explanation in several last
> mails.
>
> We are approaching the goal...
>
> Aditya's ocde:
>
>
> \starttext
>\startasciimode
> \footnote{\type{%APPDATA%\file.txt}}
>\stopasc
Hi,
in the following code example the result from \type lacks the space
between \cmd and the following left bracket.
\starttext
\starttyping
\cmd [...]
\stoptyping
\type{\cmd [...]}
\stoptext
Wolfgang
Hello,
thanks Aditya and Wolfgang for "deep" explanation in several last mails.
We are approaching the goal...
Aditya's ocde:
\starttext
\startasciimode
\footnote{\type{%APPDATA%\file.txt}}
\stopasciimode
\stoptext
gives (in the footnote):
"
1 %APP
Aditya Mahajan schrieb am 04.11.2019 um 15:05:
On Mon, 4 Nov 2019, Aditya Mahajan wrote:
That should have been:
As Hans' mentioned, use:
\startasciimode
\footnote{\type{%APPDATA%\file.txt}}
\stopasciimode
In a longer document setting \asciimode at the begin can be the better
solution
On Mon, 4 Nov 2019, Aditya Mahajan wrote:
That should have been:
As Hans' mentioned, use:
\startasciimode
\footnote{\type{%APPDATA%\file.txt}}
\stopasciimode
Aditya
___
If your question is of interest to others
t;\letterpercent") - if possible.
My attepmts with \text or \asciimode fail:
\starttext
\type{%APPDATA%\file.txt}
\footnote{%
%\type{%APPDATA%\file.txt}
%\asciimode{%APPDATA%\file.txt}
}
\stoptext
Even plays with
%\catcode\commentasciicode=\othercatcode
%\catc
\text or \asciimode fail:
\starttext
\type{%APPDATA%\file.txt}
\footnote{%
%\type{%APPDATA%\file.txt}
%\asciimode{%APPDATA%\file.txt}
}
\stoptext
Even plays with
%\catcode\commentasciicode=\othercatcode
%\catcode\backslashasciicode=\othercatcode
don't give
On Sat, 2 Nov 2019, cont...@vivaldi.net wrote:
Hello,
OK, thanks for reaction.
One more example - \text instead of ascii mode:
\starttext
\type{%@$}
A\footnote{\type{*\$%
}}
B\footnote{\type{*\$\%
}}
\stoptext
gives:
"
*\$
*\$\%
"
in the footnote.
IOW, I can
Hello,
OK, thanks for reaction.
One more example - \text instead of ascii mode:
\starttext
\type{%@$}
A\footnote{\type{*\$%
}}
B\footnote{\type{*\$\%
}}
\stoptext
gives:
"
*\$
*\$\%
"
in the footnote.
IOW, I cannot simply print "%": "%&quo
rocessed images, 1 unique asked, 1 bad names
mkiv lua stats > font embedding time: 0.014 seconds, 1 fonts
mkiv lua stats > used platform: linux, type: unix, binary subtree:
texmf-openbsd6.5-amd64
mkiv lua stats > used engine: luametatex version 2.0, functionality
level 20190729, f
801 - 900 of 6736 matches
Mail list logo
