What exactly do you need? You can just process each component on its = own. With a makefile or shell script, batch file, that should be easy enoug= h.

Or, do you need to have correct cross references, page numbers, etc.?= I was asking a similar question two days ago, and Hans showed me how= to add information to the log file:

\writestatus{!!!!!}{SPLIT HE= RE: \the\realpageno}

You should be then able to extract the split points from the log file= and extract the components from the complete PDF.

Or, if you know that you will need to split your document at certain = structure elements (chapters, sections or so), it’s even simpler.

The lua script below will split your PDF at each chapter. It uses pdf= tk for splitting, but it should be easy to adapt this to context’s ow= n mechanism mentioned by Hans in the other thread.

Denis

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

-- mit we= lchen Dateien arbeiten wir?

&nbs= p;

local bas= e =3D assert(arg[1], "Keine Datei angegeben")

local pdf =3D base .. ".pdf"

local tuc =3D base .. ".tuc= "

-- import .tuc-file /extension lua

local utilitydata =3D dofile(tuc)

local breakpoints =3D {}

local last_page =3D utilitydata.structures.counters.collected["r= ealpage"][1][1]

print ("Letzte Seite: " .. last_page)

-- iterate over .tuc =3D> get breakpoints

for index, content in pairs(utilitydata.structures.lists.collected) d= o

if (content["titledata"]["label&quo= t;] =3D=3D "chapter")

then

table.insert(breakpoints,c= ontent["references"]["realpage"])

end

end<= /o:p>

&nbs= p;

-- welche= s sind die Breakpoints?

print(&qu= ot;Wir haben folgende Breakpoints:")

for index, content in pairs(breakpoints) do

print (content)

end<= /o:p>

&nbs= p;

-- wie vi= ele Breakpoint haben wir?

function tablelength(T)

local count =3D 0

for _ in pairs(T) do count =3D count + 1 end

return count

end

local breakpoints_length =3D tablelength(breakpoints)

print ("Wir haben " .. breakpoints_length .. " Breakpo= ints.")

-- Extraktionsbereiche festlegen

local extractions =3D {}

for index, breakpoint in pairs(breakpoints) do

region =3D {}

local startregion =3D breakpoint=

&nb= sp; local nextstartregion =3D breakpoints[index + 1]<= o:p>

&nb= sp; local stopregion;

&nb= sp; if (nextstartregion =3D=3D nil)

&nb= sp; then

&nb= sp; stopregion =3D last_page

&nb= sp; else

&nb= sp; stopregion =3D nextstartregion - 1

&nb= sp; end

&nb= sp; region["start"] =3D startregion<= /span>

&nb= sp; region["stop"] =3D stopregion

table.insert(extractions,region)=

end

print ("Wir extrahieren ...")

for index, region in pairs(extractions) do

print("von " .. region["start"] .. " = bis " .. region["stop"])

local outputfile =3D "article" .. index .. ".pd= f"

local extract_command =3D "pdftk " .. pdf .. " = cat " .. region["start"] .. "-" .. region["st= op"] .. " output " .. outputfile

os.execute(extract_command)

end

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Von: ntg-context <ntg-context-bounces@ntg.nl> Im Auftrag von Alan Bowen
Gesendet: Montag, 1. M=E4rz 2021 22:38 An: mailing list for ConTeXt users <ntg-context@ntg.nl>
Betreff: [NTG-context] outputting components in their own PDFs<= /o:p>

I have a project-component setup and need to pro= duce a single PDF file containing all the components as well as a PDF file = for each component. The single file is easy. Is there a way to automate the generation of the PDF files for the individual= components?

Alan