on trying to match a specified document layout via a class and/or package

[Peter Wilson]

Many years ago I did something similar for ISO Standards documents. You 
may want to have a look at those. Try "texdoc iso10303" and in 
particular the 1st and 14th pages. The package file of most general 
interest is "stepv13.sty" which may well be on your system (I use Ubuntu 
and "kpsewhich stepv13.sty" returns the location of the file). Of course 
all the files are available from CTAN.

Peter W.


On 24/04/21 07:44, Massimo Pinto wrote:
> I have used LaTeX for many years but not enough to be able to define a 
> document class, or a package.
> At my workplace, a National Standards Institute, Quality Management 
> includes documentation that is laid out on a pre-defined format that 
> was prepared in Word, but ultimately it’s for producing a .pdf. In 
> this format, the header of the first page includes a table of 
> specified height and width, listing several pieces of information such 
> as the document version number, the title of the document, the date of 
> its introduction in the quality system, the name of the institute, the 
> document format version number etc.
> A second table at the bottom of the page lists the name and signatures 
> of the person who wrote the document, any reviewers, and the Quality 
> Manager who approved it. These tables are shown only on the front 
> page, while on the following pages headers and footers are easier to 
> handle. All the rest is about margins, font family and size, table of 
> contents depth and other relatively simple items.
> If I wanted to use LaTeX to write documentation to be used for Quality 
> Management, what would be my best guess for a package and class?
> At a first guess I am considering fancyhdr, but I am debating whether 
> I should  follow the approach that was described by Niall Mansfield in 
> TUGBoat Volume 29 (2008). No. 3 - Proceedings of the 2008 Annual 
> meeting, page 356 and ff, 
> https://www.tug.org/TUGboat/tb29-3/tb93mansfield.pdf, that is using a 
> class that is already defined (article?) and making any necessary 
> modifications in a .sty file.
> I would be grateful for any advice to get me going.
> Thank you, Massimo
>
> Massimo Pinto
> ENEA Casaccia Research Centre
> Department of Fusion and Technology for Nuclear Safety and Security
> National Institute of Ionizing Radiation Metrology
> Dosimetry Division
> http://www.inmri.enea.it/
> =========================================
> personal: http://massimopinto.github.io
>
>
>
> ------------------------------------------------------------------------
>
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente 
> alle persone indicate e la casella di posta elettronica da cui è stata 
> inviata è da qualificarsi quale strumento aziendale.
>
> La diffusione, copia o qualsiasi altra azione derivante dalla 
> conoscenza di queste informazioni sono rigorosamente vietate (art. 616 
> c.p, D.Lgs. n. 196/2003 s.m.i. e GDPR Regolamento - UE 2016/679).
>
> Qualora abbiate ricevuto questo documento per errore siete 
> cortesemente pregati di darne immediata comunicazione al mittente e di 
> provvedere alla sua distruzione. Grazie.
>
> This e-mail and any attachments is confidential and may contain 
> privileged information intended for the addressee(s) only.
>
> Dissemination, copying, printing or use by anybody else is 
> unauthorised (art. 616 c.p, D.Lgs. n. 196/2003 and subsequent 
> amendments and GDPR UE 2016/679).
>
> If you are not the intended recipient, please delete this message and 
> any attachments and advise the sender by return e-mail. Thanks.
>
> ------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/texhax/attachments/20210424/d34cab84/attachment.html>