It appears the -p option is not working with evince on CentOS 6

The open function is not doing what is expected.

Currently the default output PDF from build is not added to .gitignore of new documents created with --new. It should be.

PDF digital signature fields are now commonplace, and can be signed with PIV credentials.

I tried the digsig package described here: https://tex.stackexchange.com/questions/51090/how-do-i-create-a-pdf-file-that-can-be-digitally-signed, and the resulting PDF did prompt me to use PIV and save the signed version.

Could these fields be an option for the Prepared By and Approved By sections of the tech-memo form?

There are already packages that do this namely cleveref but we can update and add nasa-latex-logic to play nicely with that package. A simple extension method in nasa-latex-docs would make this possible as follows:

\refrange{fig:labelA}{fig:label}

produces:

Figure 1-10

FYI @karenBibb

Templates should have the option of adding the yellow SBU cover sheet with options properly filled out.

This file appears to have current electronic form for vertical layouts.
NF1686.pdf

Note that the last security training I did hinted that they would be revamping the SBU and other designations. Not sure how long the current process will be valid for. Might need to research the stability of the current designation requirements.

Currently the referencing does not support this level of sectioning.

Add capability.

Once a document is created using --new there is no good way, besides manually copy/paste, to update the support/ directory in the event that nasa-latex-docs has been updated and the user wants those new features in an existing document.

Add capability to allow that. Maybe using the following command directly within an existing document:

./support/buildPDF.py --update

Current no template is defined by default for all new documents. Select a document template as the default - better than nothing.

In the tech-memo template, I need to add more signature lines for additional approvers. How can I do this?

Currently there is no snippet or example. It would we good to have so that users do not need to look it up each time.

Would it be possible to add a command that creates a list of listings in the doc. Similar to the List of Tables and List of Figures in the preamble.

In one of the recent commits, there were a couple of print statements in buildPDF.py that added some bullet point characters.

At line 276:

      # Check the return status of the TeX version call
      if tex_which_out.returncode > 0:
         print_error("""No TeX distribution installation found, check PATH environment
Standard TeX installation locations can be found in:
  • Linux: /usr/local/texlive/2025/bin/x86_64-linux
  • macOS: /usr/local/texlive/2025/bin/x86_64-darwin
  • Windows: C:\\texlive\\2025\\bin\\win32"""
            )

and at line 435:

      # Print path to created template and exit
      if not self._quiet:
         print("""Template created in:
  • {0}
To build PDF run the following:
  • cd {0}
  • ./support/buildPDF.py {1}
""".format(tc.BLUE+structure_path+tc.ENDC,self.input_tex))

It seems that when buildPDF.py is used to build a report and your python version is recent enough, this doesn't cause an issue. However, when using a python version of 2.7.5, for example, I get this error when trying to generate a report using buildPDF.py:

 File "./support/buildPDF.py", line 280
SyntaxError: Non-ASCII character '\xe2' in file ./support/buildPDF.py on line 281, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details

I confirmed replacing the bullet point characters with simple hyphens ('-') resolved the issue.

Currently there is no way to suppress outputs during an buildPDF.py operation

Currently nasa-latex-docs/support does not match <new document>/support. This can be a little confusing to navigate.

Proposal to update this structure so that they match.

can you please add a License file at the root of your repo?

Adding the following at the top of each file allows users to call the build command on any input TeX file throughout the document tree. Without this special syntax, errors will occur when trying to call build on one of the child files.

%!TEX root = ../<main-tex-file-name>.tex

Add capability and docs for building standalone reports for snippets. This will include standalone PDF or option to convert to PNG.

For example if you have a snippet in a file example.tex file with ONLY the following content and no other boilerplate:

\begin{figure}[H]
   \centering
   \includegraphics[height=1in]{NASA_Logo}
   \caption{Example LaTeX Figures} 
   \label{fig:NASA_Logo}
\end{figure}

You would be able to do this:

./buildPDF.py example.tex --standalone

Will produce a PDF for you, cropped and sized appropriately for that snippet content. You can also do the following to seamlessly create a PNG:

./buildPDF.py example.tex --standalone-convert

This is a nice and easy way to take latex code and convert into cropped PDF or PNG with minimal effort. It is important to note that under the hood, the convert logic used by latex's native standalone functionality utilizes imagemagick. This will need to be installed for users who want to utilize the convert option for PNG.

http://www.imagemagick.org/script/convert.php

Citations in document abstracts are not displayed correctly. See the sample code below, and the attached generated PDF file.
Note that the citation in the abstract prints to [nasa-latex-docs], as opposed to [1].

% Define Class: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\documentclass[template=tech-memo]{nasa-latex-docs} 

% Preamble Section: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


% Add bibliogrpahy file
\addbibresource{test-document.bib}

\docAbstract[
    \cite{nasa-latex-docs}
]

% Main Document Content: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{document}

\input{tex/sample_content.tex}

\printbibliography

\end{document}
% End of Document %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

test-document.pdf