<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>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.</p>
<p>Peter W.<br>
</p>
<br>
<div class="moz-cite-prefix">On 24/04/21 07:44, Massimo Pinto wrote:<br>
</div>
<blockquote cite="mid:6740B3BD-206A-468F-BCFF-384421C1D709@enea.it"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
I have used LaTeX for many years but not enough to be able to
define a document class, or a package.
<div class="">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. </div>
<div class="">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.</div>
<div class="">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?</div>
<div 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, <a
moz-do-not-send="true"
href="https://www.tug.org/TUGboat/tb29-3/tb93mansfield.pdf"
class="">https://www.tug.org/TUGboat/tb29-3/tb93mansfield.pdf</a>,
that is using a class that is already defined (article?) and
making any necessary modifications in a .sty file. </div>
<div class="">I would be grateful for any advice to get me going. </div>
<div class="">Thank you, Massimo</div>
<div class=""><br class="">
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; word-wrap: break-word;
-webkit-nbsp-mode: space; line-break: after-white-space;"
class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; word-wrap: break-word;
-webkit-nbsp-mode: space; line-break: after-white-space;"
class="">Massimo Pinto<br class="">
ENEA Casaccia Research Centre<br class="">
Department of Fusion and Technology for Nuclear Safety and
Security<br class="">
National Institute of Ionizing Radiation Metrology<br
class="">
Dosimetry Division<br class="">
<a moz-do-not-send="true" href="http://www.inmri.enea.it/"
class="">http://www.inmri.enea.it/</a><br class="">
=========================================<br class="">
personal: <a class="moz-txt-link-freetext" href="http://massimopinto.github.io">http://massimopinto.github.io</a></div>
</div>
</div>
<br class="">
</div>
<br>
<br>
<hr>
<p style="font-family: Arial, Helvetica, sans-serif; font-size:
13px">
</p>
<p style="font-family: Arial, Helvetica, sans-serif; font-size:
13px">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.
</p>
<p style="font-family: Arial, Helvetica, sans-serif; font-size:
13px">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). </p>
<p style="font-family: Arial, Helvetica, sans-serif; font-size:
13px">Qualora abbiate ricevuto questo documento per errore siete
cortesemente pregati di darne immediata comunicazione al
mittente e di provvedere alla sua distruzione. Grazie.
<br>
</p>
<p style="font-family: Arial, Helvetica, sans-serif; font-size:
13px">This e-mail and any attachments is confidential and may
contain privileged information intended for the addressee(s)
only.
</p>
<p style="font-family: Arial, Helvetica, sans-serif; font-size:
13px">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).
</p>
<p style="font-family: Arial, Helvetica, sans-serif; font-size:
13px">If you are not the intended recipient, please delete this
message and any attachments and advise the sender by return
e-mail. Thanks.
<br>
</p>
<hr>
</blockquote>
<br>
</body>
</html>