}:\space \currentdate \quad \donefalse \ifcstok \currentproject
\currentproduct \ifcstok \currentproduct \currentcomponent \donetrue \fi
\fi \ifdone \donefalse \else \ifempty \
\page_info_add_to_box
#1->\scratchdimen \wd #1\setbox \b_page_versions \vpack to \ht #1{\vfill
\settexthoff
On 3/10/2021 5:56 PM, Wolfgang Schuster wrote:
Hi,
when the wildcard symbol is used as argument to \startcomponent (or
\startproduct) the name of the folder is now used and not the file name.
\startcomponent *
\quotation{\currentcomponent}
\stopcomponent
it's programmed that way (must
Hi,
when the wildcard symbol is used as argument to \startcomponent (or
\startproduct) the name of the folder is now used and not the file name.
\startcomponent *
\quotation{\currentcomponent}
\stopcomponent
Wolfgang
; christmas, children, medieval &
>> fantasy, some author...).
>> They all use [name=\currentcomponent]. If I could avoid the JOBNAME part of
>> the file name, all booklets would use the same note PDFs. Now, the temp
>> directory contains literally thousands of files.
em in different
> songbooklets with the same layout. E.g. there’s one containing all the songs
> and several with a subject (e.g. winter & christmas, children, medieval &
> fantasy, some author...).
> They all use [name=\currentcomponent]. If I could avoid the JOBNAME part of
&
d compile runs if I could influence the naming:
I got ~500 songs in their own component files, and I use them in different
songbooklets with the same layout. E.g. there’s one containing all the songs
and several with a subject (e.g. winter & christmas, children, medieval &
fantasy, some
;>
>>>> Thanks Tomás! Indeed \jobname does the job :-)
>>> In case you need the current component file in a project environment:
>>> \currentcomponent
>
> In some case \inputfilename is the better choice, e.g. when you process xml
> files with a
16:20 schrieb Otared Kavian :
Thanks Tomás! Indeed \jobname does the job :-)
In case you need the current component file in a project environment:
\currentcomponent
In some case \inputfilename is the better choice, e.g. when you process
xml files with a environment file for the style and proce
Kavian :
>>
>> Thanks Tomás! Indeed \jobname does the job :-)
>
> In case you need the current component file in a project environment:
> \currentcomponent
>
> Hraban
> ___
> If your
> Am 01.12.2020 um 16:20 schrieb Otared Kavian :
>
> Thanks Tomás! Indeed \jobname does the job :-)
In case you need the current component file in a project environment:
\currentcomponent
Hraban
__
nsively, but then I recognized, I can’t
refer to the component filename with \currentcomponent any more. (I use it for
filter-generated contents like LilyPond music.)
Just as a warning, in case you stumble upon that.
Hraban
_
hould be able to copy and adapt to your needs. There are lot of things which can be improved in your example. 1. Pass the filename of the component/product to \startcomponent and not some dummy name (or just use *), this allows you to print the filename with \currentcomponent or \currentproduct 2.
filename of the component/product to \startcomponent and not
some dummy name (or just use *), this allows you to print the filename
with \currentcomponent or \currentproduct
2. Use \setvariables or \setupdocument to set the document title,
revision etc.
3. Use \startsectionblockenvironment to move
[][numbers]\definestructureconversionset [appendix:pagenumber] [][numbers]= The fm-frontpage.tex file\startcomponent currentcomponent \product product % Front page layout\startstandardmakeup % Place logo centered on page\framed[height=5cm,width=broad,frame=off]{\ext
mbers]
\definestructureconversionset
[appendix:pagenumber] [][numbers]
=
*The fm-frontpage.tex file*
\startcomponent currentcomponent
\product product
% Front page layout
\startstandardmakeup
% Place logo centered on page
\framed[height=5cm,width=broad,frame=off]
{\externalf
\startcomponent currentcomponent \product product % Front page layout\startstandardmakeup % Place logo centered on page \framed[height=5cm,width=broad,frame=off] {\externalfigure[frontpage-logo.png][width=12cm]} % Place course titles\blank[6*big]\color[Modu_Blue]{\midaligned{\bfc \MyManual
ilename{\currentcomponent}}]
\def\maybeendnotes
{\subsubject{Notes} \placenotes[endnote] \subsubject{Bibliography}
\switchtobodyfont[9pt]
\placepublications[criterium=all]}
\appendtoks \maybeendnotes \to \everystoptext
\stopmode
%
\setupcaption[figure][style=small]
\setupinteractio
> end up at the end of the chapter) so I can work on separate chapters.
>>
>> luna:chapters gerben$ make -n c_loosely.pdf
>> texexec --pdf --mode=standalone c_loosely.tex
>> luna:chapters gerben$ make -n prd_book.pdf
>> make MODE="--mode=editor" ONCE
make -n c_loosely.pdf
> texexec --pdf --mode=standalone c_loosely.tex
> luna:chapters gerben$ make -n prd_book.pdf
> make MODE="--mode=editor" ONCE="" ../products/prd_book.pdf
>
> The latter turns into
>
> texexec --pdf --mode=editor ../products/prd_book.
texexec --pdf --mode=editor ../products/prd_book.tex
And the environment file has:
\startmode[standalone]
\setupfootertexts[pagenumber][{\jobname->\filename{\currentcomponent}}]
\def\maybeendnotes
{\subsubject{Notes} \placenotes[endnote] \subsubject{Bibliography}
\switchtob
antly, that catches ^ and _,
>> but what about whitespace etc. Isn;t there a true verbatim that I can use on
>> a macro like \currentcomponent? Something along the lines of
>> \verbatimexpand{\currentcomponent}?
>
> Untested: \filename{\currentcomponent}
Works. When outs
on a macro like \currentcomponent? Something along the lines of
\verbatimexpand{\currentcomponent}?
Untested: \filename{\currentcomponent}
Aditya
___
If your question is of interest to others as well, please add an
t;
>>>> \startbodymatter
>>>> \component chapter1
>>>> \component chapter2
>>>> \component chapter3
>>>> \stopbodymatter
>>>>
>>>> And I want "chapter1.tex" (maybe full path) in the footer.
>>>
&
at, that’s exactly what I meant. Since I would normally set
[name=\currentcomponent], can I make that default?
Unfortunately no. The name key is reset at every `\startexternalfilter`;
otherwise it will be difficult to mix `name=` with normal usage.
There are some more enhancements that I
he
> scenes)
Oh, so simple? Great, that’s exactly what I meant. Since I would normally set
[name=\currentcomponent], can I make that default?
>> There are some more enhancements that I’d like to implement, e.g. checking
>> the resulting files if there are several pages or using si
e
>>> chapter file names (e.g. "chapter1.tex") in the footer.
>>>
>>> So, prd_book contains:
>>>
>>> \startbodymatter
>>> \component chapter1
>>> \component chapter2
>>> \component chapter3
>>> \stopbodymatter
;> \startbodymatter
>> \component chapter1
>> \component chapter2
>> \component chapter3
>> \stopbodymatter
>>
>> And I want "chapter1.tex" (maybe full path) in the footer.
>
> If the component identifier matches the file name
> And I want "chapter1.tex" (maybe full path) in the footer.
If the component identifier matches the file name (e.g. if you
use the asterisk instead of a name), you can use
\currentcomponent. So the main file foo.tex would look like:
\setuppagenumbering[location=]
%
ove the \mainlanguage
>> call to the corresponding language setup.
>>
>>
>> Marco
>
> Hello Marco,
>
> It looks like \usepath is the key to what I want, thank you. I don't
> quite understand your overall structure. Is the "*" a literal &q
Wolfgang wrote:
> You can use \currentcomponent, \currentproduct and \currentproject to print
> the name of the file.
Another secret unearthed! All wikified, together with \processedfile
and \processedfiles. Sans examples, but at least the info's there.
Thank you, Wolfgang.
Che
/startcomponent. This
> trick also works for startproject, startenvironment, and startproduct,
> I assume?
>
> And for the general case, what about
> `\ctxlua{commands.processedfile}`? That looks like it should print the
> current filename, as long as any inclusions use the ConTeXt
ot;alternative=comment“ more appropriate?
>> 3. Is it possible to save the FiXme-list in a external text file? Something
>> like \savebuffer[expanded list of fixmes][list.txt]
>
> Do you want a separate file for each entry or one file with all entries?
I thought of one file wit
On Fri, 14 Nov 2008, Alan STONE wrote:
> Another debugging question: how do you return the filename of the file being
> compiled ?
\jobname
There is also
\currentproject
\currentproduct
\currentenvironment
\currentcomponent
\@@pushedmacro
\endcsname ...
\doprevlevel ->\popmacro \currentcomponentpath
\popmacro
\currentcomponent \...
l.129 \stopcomponent
I'm forgetting what you said and using zero instead.
! You can&
t; e.g. abc.mp and abc.1 in 1/chap/ since each chapter has many figures,
> and I edit and test one chapter at a time.
>
untested extension: \currentcomponentpath
\def\currentcomponentpath{.}
\def\donextlevel#1#2#3#4#5#6#7\\%
{\pushmacro\currentcomponent
\pushmacro\curren
oiect
\stopvariables
\unprotect
\let\currentcomponent\v!text
\def\donextlevel#1#2#3#4#5#6#7\\%
{\pushmacro\currentcomponent
\let\currentcomponent#1
\setsystemmode\currentcomponent
\beforesplitstring#7\at.\to#2\relax
\ifcase\filelevel\relax
\starttext
\def\project ##1 {#3{##1}}%
36 matches
Mail list logo
