Dear all,
I would like to continue this thread from April.
At Hostsharing we produce all PDFs with ConTeXt. As we have to comply
with standards I would like to ask in how far ConTeXt supports the
PDF/UA standard and/or WTPDF. I saw PDF/UA-1 in setupbackend but I have
no idea what it does
Hello,
Thanks Hans and everyone who has worked on it for the new upload!
I have noticed a change which seems to break XML/html export for inline
equations; although I don't know if the issue is with the new version or
with how I'm using it.
Minimal example:
```
\setupbackend[
ou cna try this:
\setupinteraction
[title=TITLE,
subtitle=SUBTITLE,
author=AUTHOR,
keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
\setupbackend
[format={pdf/a-2a},
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}]
\setuptagging
[state=start]
\enabledirectives
[backe
ction
[title=TITLE,
subtitle=SUBTITLE,
author=AUTHOR,
keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
\setupbackend
[format={pdf/a-2a},
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}]
\setuptagging
[state=start]
\enabledirectives
[backend.usetags=mkiv]
\starttext
\ch
o time for validation / tagging now but you can try
% \setupbackend[format=pdf/ua-2]
% \setuptagging[state=start]
pdf/A-2a is not pdf/ua-2. pdf/A-2a is for pdf 1.7 or less, so you
would need pdf/ua-1 as accompanying accessibility standard and not
ua-2 which is for pdf 2.0.
But if context
anyone else have any tips or ideas? Is it not that important?
>
> i have no time for validation / tagging now but you can try
>
> % \setupbackend[format=pdf/ua-2]
> % \setuptagging[state=start]
pdf/A-2a is not pdf/ua-2. pdf/A-2a is for pdf 1.7 or less, so you
would need pdf/ua-1 a
On 9/12/2024 7:01 PM, Thomas Meyer wrote:
Hello Hans,
thank you for your answer for now.
\setupbackend[format=pdf/ua-2] should work but validation test via
verapdf failed.
I hope for the future.
Because we don't want a bloated pdf by default, if you want tagging then
you also need t
Hello Hans,
thank you for your answer for now.
\setupbackend[format=pdf/ua-2] should work but validation test via
verapdf failed.
I hope for the future.
Greetings
Thomas
Am 12.09.24 um 18:05 schrieb Hans Hagen:
On 9/12/2024 5:50 PM, Thomas Meyer wrote:
Thank you, Jakob, for your answer
tips or ideas? Is it not that important?
i have no time for validation / tagging now but you can try
% \setupbackend[format=pdf/ua-2]
% \setuptagging[state=start]
we will pick up on tagging etc in a couplke of months ... the pdf
standard is not as stable as one thinks nor are these validators so
any experience or advice on how to make pdf/A-2a valid?
Greetings Thomas
\setupinteraction
[title=TITLE,
subtitle=SUBTITLE,
author=AUTHOR,
keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
%% For PDF/A
\setupbackend[
format={pdf/a-2a}, validation fails
%format={pdf/a-2b},
that ConTeXt can output? Does it require a
significant rewrite of ConTeXt document code to be produced or is there
a simple way to output this format?
Yes, I stopped working on ePub and updating the wiki pages, but did you
even try?
You need
\setupbackend[export=yes] (see https://wiki.contextgarde
Dear list,
My goal is to generate a PDF/A-conformant document using ConTeXt.
I’m encountering the same error as Sylvain with version 2024.06.21 23:45 on
macOS.
Sample file:
\setupbackend[export=yes]
\starttext
a
\chapter{b}
$c$
\stoptext
I remember my actual document compiling without errors
ConTeXt LMTX version: 2024.05.27 18:16
Sample tex file:
\setupbackend[export=yes]
\starttext
x
\startsectionlevel
\startitemize
\item
\startitemize
\item
\startitemize
\item
\stopitemize
\stopitemize
\stopitemize
\stopsectionlevel
\stoptext
Error log:
tex error > tex error on line 1
xt/colorprofiles.xml'
backend > profiles > error, couldn't locate profile
'ISOcoated_v2_300_eci.icc'
backend > profiles > invalid output intent 'ISO Coated v2 300%
(ECI)'
Here is a MWE that generates these errors:
setupinteraction
[ti
ofile
'ISOcoated_v2_300_eci.icc'
backend > profiles > invalid output intent 'ISO Coated v2 300% (ECI)'
Here is a MWE that generates these errors:
setupinteraction
[title=TITLE,
subtitle=SUBTITLE,
author=AUTHOR,
keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
#x27;)
stack traceback:
...ocal/share/texmf-dist/tex/context/base/mkxl/node-ext.lmt:31: in
local 'code'
...ocal/share/texmf-dist/tex/context/base/mkiv/util-lua.lua:96: in
field 'loadedluacode'
...ocal/share/texmf-dist/tex/context/base/mkiv/lu
>
>> On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:
>>> Hi all,
>>>
>>>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>>>>
>>>> Here's a tiny test document, I disabled PDF compression but it al
also
>>> doesn't work with the default settings.
>>>
>>> \setupbackend[level=0,compresslevel=0]
>>> \starttext
>>> Just a line of text.
>>> \stoptext
>>>
>>> When I print this "directly" (i.e. sending the raw PDF to
On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:
Hi all,
I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.
\setupbackend[level=0,compresslevel=0]
\startt
Hi all,
> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>
> Here's a tiny test document, I disabled PDF compression but it also
> doesn't work with the default settings.
>
> \setupbackend[level=0,compresslevel=0]
> \starttext
> Just a line of t
On 10/3/22 20:57, Leah Neukirchen via ntg-context wrote:
>> [...]
>> \setupbackend[level=0,compresslevel=0]
>> \starttext
>> Just a line of text.
>> \stoptext
>> [...]
>
> On Acrobat DC on macOS, there is a visible difference between the two files:
Hi
Hans Hagen via ntg-context writes:
> On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote:
>> Hi,
>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>> Here's a tiny test document, I disabled PDF compression but it also
>> doesn't work with t
On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote:
Hi,
I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.
\setupbackend[level=0,compresslevel=0]
\starttext
J
Leah Neukirchen via ntg-context writes:
> Hi,
>
> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>
> Here's a tiny test document, I disabled PDF compression but it also
> doesn't work with the default settings.
>
> \setupbackend[level=0,compressleve
Hi,
I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.
\setupbackend[level=0,compresslevel=0]
\starttext
Just a line of text.
\stoptext
When I print this "directly
on how to resolve this?
As you like challenges ... you can way more narrow it down ...
\setupbackend[export=yes]
\starttext
{
\forgetall
% \forgeteverypar
x\strut\par
}
\stoptext
the problem is that you basically loose *all* par related tagging now so
you need to bring that back,
>
> > gives the fuzzy paragraph warning. Any hints on how to resolve this?
> As you like challenges ... you can way more narrow it down ...
>
> \setupbackend[export=yes]
>
> \starttext
> {
> \forgetall
>% \forgeteverypar
> x\strut\par
> }
> \
to the attached MWE (which does not depend on
the t-vim module at all). Compiling it using
$context --trackers=export\* lines
gives the fuzzy paragraph warning. Any hints on how to resolve this?
As you like challenges ... you can way more narrow it down ...
\setupbackend[export=yes]
\sta
Hi Pablo and Rik
many thanks, much appreciated.
attachment works like a charm to include the source files in the delivered PDF.
Rik pointed me to the longterm archive standard, which is also desirable. PDF/A
is possible with setupbackend\setupbackend[format={pdf/a-3a}]
but needs fixing with
Hi Pablo
Many thanks. That is exactly what I need, ie. to deliver the source code
embedded in the PDF.
attachment works like a charm
Rik pointed me — additionally — into the direction of being PDF/A compliant.
PDF/A is possible with
setupbackend\setupbackend[format={pdf/a-3a}]
but needs
ot;, though.
— html-test.tex —
\definefontfamily [mainface][math][stix]
\setupbodyfont[mainface,10pt]
\setupinteraction[state=start, click=yes, focus=standard, color=darkblue]
\setupbackend[export=yes] % Exporting HTML/XML
\defineregister [index]
\setupregister [index] [indi
PDF/A
<https://wiki.contextgarden.net/PDF/A>:
---
\setupinteraction[title=MyTitle,state=start]
\setupinteractionscreen[option={title}]
\setupbackend[
format={pdf/a-1a:2005},
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc},
intent=ISO coated v2 300\letterpercent\spac
F/A>:
---
\setupinteraction[title=MyTitle,state=start]
\setupinteractionscreen[option={title}]
\setupbackend[
format={pdf/a-1a:2005},
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc},
intent=ISO coated v2 300\letterpercent\space (ECI)]
%% Tagged PDF
%% method=auto ==> defaul
On 5/22/21 12:25 PM, Hans Hagen wrote:
> On 5/22/2021 11:28 AM, Pablo Rodriguez wrote:
>> [...]
>> Using SumatraPDF-3.1.2 and current latest (from 2021.05.21 15:07),
>> spacing is only right when I disable font expansion.
>>
>> Would it be possible that spacing be the same with and without font
>>
On 5/22/2021 11:28 AM, Pablo Rodriguez wrote:
Hi Hans,
I have the following sample:
\definefontfeature
[default]
[default]
[expansion=quality]
\setupalign
[hz]
\setuppapersize[A6]
\setupbodyfont[pagella]
\setupbackend [space=yes]
\starttext
\input
Hi Hans,
I have the following sample:
\definefontfeature
[default]
[default]
[expansion=quality]
\setupalign
[hz]
\setuppapersize[A6]
\setupbodyfont[pagella]
\setupbackend [space=yes]
\starttext
\input zapf
\stoptext
Using SumatraPDF-3.1.2 and current latest
On 5/10/21 9:36 AM, Hans Hagen wrote:
> [...]
> but at the cost of runtime you can try \setupbackend [space=yes]
It works perfectly fine, but not with font expansion:
\definefontfeature
[default]
[default]
[expansion=quality]
\setupalign
[hz]
\setuppapers
7;s tricks,
and think that a widely--praised program,
called up on the screen, will make every-
thing automatic from now on.
but at the cost of runtime you can try \setupbackend [space=yes]
Hans
-
On 4/26/2021 7:04 PM, Pablo Rodriguez wrote:
Dear list,
I have the following sample:
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB, default_gray.icc},
level=0]
\setuptagging[state=start]
\setupcolors[cmyk=no, pagecolormodel=auto
Dear list,
I have the following sample:
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB, default_gray.icc},
level=0]
\setuptagging[state=start]
\setupcolors[cmyk=no, pagecolormodel=auto]
\definefontfamily[mainface][rm][TeX Gyre Heros
On 2/28/2021 11:42 AM, a badin wrote:
% \setupbackend[export=example.xml,css=example.css]
\usebtxdataset[default][ref.bib]
\starttext
\cite[Arrow][Arrow]
\placelistofpublications
\stoptext
my ref.bib file:
@ARTICLE{Arrow,
author = {Andrej Arrow},
title = {The Font Name Mess},
journal
gt; Dear gardeners,
>
> I'm new to ConTeXt and would like to share a possible bug with you.
>
> If I have the \setupbackend[export=example.xml,css=example.css] entry in
> my .tex file, then my bibliography renders in a strange way (text copied
> from pdf): 1 bfldcategor
Dear gardeners,
I'm new to ConTeXt and would like to share a possible bug with you.
If I have the \setupbackend[export=example.xml,css=example.css] entry in my
.tex file, then my bibliography renders in a strange way (text copied from
pdf): 1 bfldcategoryarticle: [author: Andrej Arrow] [jo
tree:
test.tex
styles/mystyle.css
where test.tex is:
```
\setupbackend[export=yes]
\setupexport[cssfile=styles/mystyle.css]
\starttext
\startparagraph
This is a test
\stopparagraph
\stoptext
```
and
styles/mystyle.tex is (the content doesn't matter, listing it for complet
uckerei
%% nachfragen.
\setupbackend[
%format=PDF/X-1a:2001,
%format=PDF/X-1a:2003,
%format=PDF/X-3:2002,
format=PDF/X-3:2003,
%format=PDF/X-4,
%format=PDF/X-4p,
intent={ISO Coated v2 300\letterpercent\space (ECI)},
]
\stopmode
%% FOGRA 39 Coated
%% Bestimmung der CMYK-We
iggers \the \outputpenalty
\endcsname \lastnamedcs \else \page_otr_command_routine
\fi
{\inotrtrue \the \everybeforeoutput \page_otr_triggered_output_routine
\relax \the \everyafteroutput }
...
\stopproduct
Are there changes with modes or setupbackend in lmtx?
My configuration is:
\setup
[bidi=global,method=unicode]
\setupbackend[export=yes]
\setupstructure[state=start,method=auto]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input ward
\NC\input ward
\NC\NR
\stoptabulate
\stoptext
==
Why is that?
The export can lead to
]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input ward
\NC\input ward
\NC\NR
\stoptabulate
\stoptext
==
But, this here fails:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\setupbackend[export
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input ward
\NC\input ward
\NC\NR
\stoptabulate
\stoptext
==
But, this here fails:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\setupbackend[export=yes]
\setupstructure[state=start,method=auto
ward
\NC\input ward
\NC\NR
\stoptabulate
\stoptext
==
But, this here fails:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\setupbackend[export=yes]
\setupstructure[state=start,method=auto]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC
\stoptext
==
But, this here fails:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\setupbackend[export=yes]
\setupstructure[state=start,method=auto]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input
, minor) work in LMTX?
It does not give an error, but it doesn't change the minor version
either.
1. A better solution for this is to add a key to \setupbackend.
2. It doesn't work because when you set the version it's too late
because ConTeXt already wrote the PDF header (the r
> they state "Ensure that you are using a CMYK workflow and export to
> PDF/X-1a:2001" . I can set the pdf format using \setupbackend but I'm
> unsure as to what to do about CMYK workflow. The book has no colour pages
> so I'm not sure if I really need to worry about
> Am 23.06.2020 um 22:28 schrieb Keith McKay :
>
> Colleagues
>
> I'm getting ready to send a book to the printers and in their blurb they
> state "Ensure that you are using a CMYK workflow and export to PDF/X-1a:2001"
> . I can set the pdf format usin
Colleagues
I'm getting ready to send a book to the printers and in their blurb
they state "/Ensure that you are using a CMYK workflow and export to
PDF/X-1a:2001" . /I can set the pdf format using \setupbackend but I'm
unsure as to what to do about CMYK workflow. Th
{xmpfile}}\ifempty
\p_file \else
\clf_setxmpf...
\setup_backend ...end [#1]\the \everysetupbackend
l.11 ...ISO coated v2 300\letterpercent\space (ECI)]
mtx-context | fatal error: return code: 1
Removing either of the \setupbackend
{xmpfile}}\ifempty
\p_file \else
\clf_setxmpf...
\setup_backend ...end [#1]\the \everysetupbackend
l.11 ...ISO coated v2 300\letterpercent\space (ECI)]
mtx-context | fatal error: return code: 1
Removing either of the \setupbackend
\p_file \else
\clf_setxmpf...
\setup_backend ...end [#1]\the \everysetupbackend
l.11 ...ISO coated v2 300\letterpercent\space (ECI)]
mtx-context | fatal error: return code: 1
Removing either of the \setupbackend instructions still results in the
same error
mmand][name=whatever]
should work (there are some such examples in the texmf tree), but it does
not.
epub-mkiv.pdf states that I need `\setupexport[properties=yes]`, but that
doesn't work either:
```
\setupbackend[export=xml]
\setupexport [properties=my]
\setelementbackendtag
rt is
...
(or some variant of that). I thought that
\startelement[mycommand][name=whatever]
should work (there are some such examples in the texmf tree), but it does not.
```
\setelementbackendtag[mycommand]
\setelementnature[mycommand][mixed]
\setupbackend[export=xml, level=0]
\star
On 5/18/2020 9:09 AM, Aditya Mahajan wrote:
Hi,
What is needed to enable export of user defined macros? Consider the
following example:
```
\def\startmycommand{\dostarttagged{mycommand}\empty}
\def\stopmycommand {\dostoptagged}
\setupbackend[export=xml, level=0]
\starttext
\startsection
Hi,
What is needed to enable export of user defined macros? Consider the following
example:
```
\def\startmycommand{\dostarttagged{mycommand}\empty}
\def\stopmycommand {\dostoptagged}
\setupbackend[export=xml, level=0]
\starttext
\startsection[title={Sample document}]
\startparagraph
etuplayout[location=middle, marking=on]
\setupinteraction
[title={TestDoc},
author={Anon}]
\setupbackend
[format=PDF/X-1a:2003,
intent={ISO Coated v2 300\letterpercent\space (ECI)}]
\setupinteractionscreen[width=max,height=max]
\startluacode
moduledata.mystuff={}
respecify_pdf_boxes
t; time
> now: one input (often quite advanced) and multiple output for
> publishing
> ane educational purposes. And it looks pretty good too.
>
Thank you very much i will do. You are refering to Thomas Schmitz?
\setupbackend[
export=yes,
xhtml=yes
]
\setupexport[
title={linenu
ot;block" or "flex" (not jet decided" which).
> 2) How can i predefine the white-space css attribute to pre-wrap
> 3) Is there a way to tell context to include the resulting class
> inside
> the *.default.css or *.styles.css or should that be done via the css
re-wrap
3) Is there a way to tell context to include the resulting class inside
the *.default.css or *.styles.css or should that be done via the css
parameter of the \setupbackend macro only?
Best
Xristoph
___
If y
Instructions for creating the .epub from the export are contained in the
log file.
On 3/3/2020 15:58, Hans van der Meer wrote:
I followed your advice and added the setup:
You need
\setupbackend[export=yes]
in your document.
This, however, does not result in an .epub file but an export
On Tue, 3 Mar 2020 21:58:16 +0100
Hans van der Meer wrote:
> I followed your advice and added the setup:
>
> > You need
> > \setupbackend[export=yes]
> > in your document.
>
> This, however, does not result in an .epub file but an export directory
> contai
I followed your advice and added the setup:
> You need
> \setupbackend[export=yes]
> in your document.
This, however, does not result in an .epub file but an export directory
containing an html and xhtml file (only partially conformant to the equivalent
pdf).
Can I get the out
et without
> that mode.
You need
\setupbackend[export=yes]
in your document. When you put the setup above in a "epub"
mode you create a epub-document only when you enable the mode
which is recommended because it can have side effects for
the normal PDF.
To avoid these side effects make an ex
On 2/27/2020 3:19 PM, Robin Schwab wrote:
Hi,
I am looking for a LaTeX system that can create accessible PDF so I
tried ConTeXt.
In current ConTeXt it seems to be impossible to specify more than one
\setupbackend[format
Minimal example:
\setupbackend[format={pdf/a-3a,pdf/ua-1,pdf/x-4
Hi,
I am looking for a LaTeX system that can create accessible PDF so I
tried ConTeXt.
In current ConTeXt it seems to be impossible to specify more than one
\setupbackend[format
Minimal example:
\setupbackend[format={pdf/a-3a,pdf/ua-1,pdf/x-4}]
\starttext
\input knuth
\stoptext
I get an
>> Colors that you define in TeX or Metapost are a different problem. I
>> *think* they should use the output intent as their profile. But I
>> don’t know if the intent option of \setupcolors and/or \setupbackend
>> really works this way. (My only means to check was Acrobat P
to CMYK with the above cited profile chain?
Or shall I tell the designer: These are the values I need as CMYK, just
do it.
> Colors that you define in TeX or Metapost are a different problem. I
> *think* they should use the output intent as their profile. But I
> don’t know if the intent option
intent as their profile. But I don’t know if the
intent option of \setupcolors and/or \setupbackend really works this way. (My
only means to check was Acrobat Pro 9, and that won’t run on a current macOS
any more.)
Hope that helps a bit and doesn’t confuse you more…
Color management *is* hard
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 backing.
Copy the icc-profile into the same folder as the shipped profiles. Call
"context --make" to m
gging[state=start]
\setupinteraction[state=start]
%setupbackend [format={pdf/a-3u},
\setupbackend[format={pdf/a-3a},
level=0,
profile={default_gray.icc},
intent={ISO coated v2 300
Am 12.02.2020 um 09:41 schrieb juh:
> Hi all,
>
> again I have a question concerning color profiles.
>
> I have this to load the ISO Coated v2 300% profile.
>
> \setupbackend[
>format=PDF/X-3:2003,
>intent={ISO Coated v2 300\letterpercent\space (ECI)},
>]
Hi all,
again I have a question concerning color profiles.
I have this to load the ISO Coated v2 300% profile.
\setupbackend[
format=PDF/X-3:2003,
intent={ISO Coated v2 300\letterpercent\space (ECI)},
]
\setupcolors[cmyk=yes,rgb=no,]
But is this profile part of the new lmtx version
pdf-1.5.18 and the following
>> sample:
>>
>> \setuptagging[state=start]
>>
>> \setupbodyfont[30pt]
>>
>> \setupbackend
>> [format=PDF/A-3a,
>> intent=sRGB IEC61966-2.1,
>> profile={sRGB.icc,default_gray.icc},
&g
fail validation with the same issues.
Hi Rik,
it has way less issues, at least using verapdf-1.5.18 and the following
sample:
\setuptagging[state=start]
\setupbodyfont[30pt]
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB.icc
dation with the same issues.
Hi Rik,
it has way less issues, at least using verapdf-1.5.18 and the following
sample:
\setuptagging[state=start]
\setupbodyfont[30pt]
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB.icc,defaul
=\endash~,
% midsentence=~\endash,
rightsentence=~\endash]
\define\quotedash{\emdash\endash}
%\setupbackend[export=yes]
\starttext
\startsection[title=Introduction]
Any of you able to help me get my quotation dashes into line when
automatically
inserted by the semantic commands? I'm s
On 1/10/2020 10:59, Rik Kabel wrote:
Here ya go, about as minimal as I can imagine:
\setupbackend [export=yes]
\setupexport []
\starttext
!
\stoptext
and in the resulting export styles directory, I get:
g:\yoiks-export\styles>grep "namespace\|weight.*ital
}
which incorrectly assigns italic to font-weight when of course it is
a font-style as far as css is concerned. This can be seen in file
export-example.css in the distribution.
can you make a mwe ...
Here ya go, about as minimal as I can imagine:
\setupbackend [export=yes]
=~\endash,
rightsentence=~\endash]
\define\quotedash{\emdash\endash}
%\setupbackend[export=yes]
\starttext
\startsection[title=Introduction]
Any of you able to help me get my quotation dashes into line when
automatically
inserted by the semantic commands? I'm sure a number of you lo
if I
>> try to make an PDF/X.
>>
>> I hope that is solvable...
>>
>> \setupbackend[format=PDF/X-1a:2001]
>>
>> \starttext
>> \externalfigure[kinder/esel_kl]
>> \stoptext
>>
>>
>> Best, Hraban
>>
>> _
parency.
>
>
> Peter
>
>
confirmed, this is ok.
\setupbackend[format=PDF/X-4p]
\starttext
\externalfigure[esel_kl.png]
\stoptext
>
--
luigi
___
If your question is of interest to others as well, pleas
Henning Hraban Ramm writes:
> I think this is the same problem that I had in Bassenge:
> The transparent part of PNGs like the attached one becomes black if I try to
> make an PDF/X.
>
> I hope that is solvable...
>
> \setupbackend[format=PDF/X-1a:2001]
AFAIK PDF/X-1a:
this is the same problem that I had in Bassenge:
> The transparent part of PNGs like the attached one becomes black if I
> try to make an PDF/X.
>
> I hope that is solvable...
>
> \setupbackend[format=PDF/X-1a:2001]
>
> \starttext
> \externalfigure[kinder/esel
I think this is the same problem that I had in Bassenge:
The transparent part of PNGs like the attached one becomes black if I try to
make an PDF/X.
I hope that is solvable...
\setupbackend[format=PDF/X-1a:2001]
\starttext
\externalfigure[kinder/esel_kl]
\stoptext
Best, Hraban
ng it only to the K channel.
I’d regard that a misconfiguration on their side.
Maybe it helps to define the output intent:
https://wiki.contextgarden.net/Command/setupbackend
https://wiki.contextgarden.net/PDFX
>> If you need more control you can create your own marks and add them as
>> backgroun
e
> attachment.
>
> \setuplanguage [en]
> \setuptagging [state=start]
> \setupinteraction [state=start]
> \setupbackend [format={pdf/a-3a},profile={default_gray.icc},
> intent={ISO coated v2 300\letterpercent\space
> (
Hello list,
The following document fails PDF/A-3a validation. It passes without the
attachment.
\setuplanguage [en]
\setuptagging [state=start]
\setupinteraction [state=start]
\setupbackend [format={pdf/a-3a},profile={default_gray.icc
on of \vI, then
we get every elements (but of course we get unnecessary "a" also).
- bSample
\setupbackend[export=yes]
\definemathmatrix[vmatrix][matrix:bars]
[simplecommand=Vmatrix]
\define[1]\vsym{\text{\math{\bi #1}}}
\define\vI{\vsym{i}}
% \define\vi{\vsy
ode[fogra39]
>
>\doiffileelse{CoatedFOGRA39.icc}{}{\farbprofilnichtgefunden}
>% This will be printed in log if context does not find the profile for
>% some reason
>
>\definecolor [hs-logoblau] [c=1.000, m=0.735, y=0.279, k=0.160]
>
>\definecolor [hs-dunkelblau] [c=0.844, m=0.54
=0.070, k=0.000]
\definecolor [hs-hellblau] [c=0.468, m=0.220, y=0.086, k=0.002]
\definecolor [hs-orange] [c=0.127, m=0.832, y=1.000, k=0.042]
\setupcolors[cmyk=yes,rgb=no,]
\setupbackend[
format=PDF/X-3:2003,
intent={Coated FOGRA39 (ISO 12647-2:2004)},
]
\stopmode
If you call c
On 5/22/2019 10:30 PM, Procházka Lukáš Ing. wrote:
Hello,
suppose having "Main.mkiv":
\setupbackend[export=yes]
\starttext
\startsection[title={Sec},MyPar=MyVal]
\input knuth
\stopsection
\stoptext
Some questions concerning XML export:
1. Normally, with \se
Hello,
suppose having "Main.mkiv":
\setupbackend[export=yes]
\starttext
\startsection[title={Sec},MyPar=MyVal]
\input knuth
\stopsection
\stoptext
Some questions concerning XML export:
1. Normally, with \setupbackend[export=yes], Ctx creates "Main-exp
On 2/6/2019 7:31 PM, Pablo Rodriguez wrote:
On 2/5/19 8:07 AM, Jan U. Hasecke wrote:
Hola Pablo,
Hallo Jan-Ulrich,
I inserted this in the setupbackend command so that ConTeXt stops with
the unknown command \colorprofilenotfound I inserted in the else clause.
But more and more I think that
1 - 100 of 447 matches
Mail list logo