[Tex/LaTex] How to “stamp” the same text on each page of a document

tools

I want to have drafting information appear on each page of document.

I have seen something similar in the Kluwer document class where it defines \@oddfoot and \@evenfoot for a lot of possibilities.

Is there an easier way than this?
Is there a way to do it without overwriting existing headers?

Best Answer

You can use the everypage module to execute Latex code just before each page is shipped. You can use PS specials to put in things like watermarks in the page (cf. the watermark package in the ncctools bundle, which I belive uses this technique), or overlay graphics on the page using PS drawing packages.

Related Solutions

[Tex/LaTex] Command-line tools for some bibtex database manipulations

Have a look at biber which in the current 1.5 dev version on SourceForge has a new "tool" mode which allows you to use biber's reencoding and source mapping features independently of biblatex. The source mapping features are what you mainly need from your description and this is all documented in the PDF manual. I can provide specific examples if you have specific questions. biber will do everything you mention above apart from the @string expansion which would be possible to add but as you say, it's fairly idiosyncratic.

Of course, you can do this dynamically with biber too - with the changes being applied as the .bib is read but the .bib is not touched. The new tool mode allows you to write the changed .bib to another file without writing a .bbl.

For example, here is how in tool mode to tackle points 2, 3 5 and 6 in your examples. Point 1 is better handled semantically with biblatex and its max/min names options. Create a biber.conf with:

<config>
  <sourcemap>
    <maps datatype="bibtex" map_overwrite="1">
      <map>
        <map_step map_field_set="issn" map_null="1"/>
      </map>
      <map>
        <per_type>ARTICLE</per_type>
        <map_step map_field_set="title" map_null="1"/>
      </map>
      <map>
        <per_type>ARTICLE</per_type>
        <map_step map_field_source="pages" map_final="1"/>
        <map_step map_field_set="archiveprefix" map_null="1"/>
        <map_step map_field_set="eprint" map_null="1"/>
        <map_step map_field_set="primaryclss" map_null="1"/>
      </map>
    </maps>
    <map>
      <map_step map_field_source="doi" map_match="[\\;]" map_final="1"/>
      <map_step map_field_set="doi" map_null="1"/>
    </map>
  </sourcemap>
</config>

Then run biber with

biber --tool file.bib

Which will look in the default locations for your biber.conf and will output a file called file_bibertool.bib.

This is also all possible, as I said, dynamically using the biber.conf as you process the file normally into a .bbl with biber and also the whole mapping functionality is available in biblatex through macros (see \DeclareSourcemap in the biblatex documentation) if you wanted to do this on a per-document basis dynamically.

[Tex/LaTex] Can Lyx syntax files override document class defaults

This is not the "more principled" solution you have asked for, but another workaround that has been working pretty well for me when editing foreign articles:

I technically do create an own layout file, but do not put any effort into it. I just take a copy of article.layout (or one of its descendants) and edit the class file inside the copy and that's all.
I do live with ERT boxes for everything that is nonstandard

The issue with ERT boxes is that changes inside them are not tracked by LyX's change tracking system. However, in my experience (with classes for scientific articles) most, if not all, incompatibilities to the standard classes affect only the front matter, that is, macros such as \title, \author, \thanks and so on. So I usually end up with one big ERT box at the beginning that contains a verbatim copy of the front matter from the LaTeX source and use tex2lyx to convert only the body of the article. As edits to the front matter are relatively rare, this is an acceptable low-effort workaround.

Best Answer

Related Solutions

[Tex/LaTex] Command-line tools for some bibtex database manipulations

[Tex/LaTex] Can Lyx syntax files override document class defaults

Related Question