The KOMA-Script Spin-off scrtime

Copyright © 2026 Markus Kohm

Release: 2026-05-19 v3.50

License: LPPL 1.3c

The time of the LaTeX run in 12h or 24h format.

The project is currently hosted and managed on Codeberg.

This work may be distributed and/or modified under the conditions of the LaTeX Project Public License, version 1.3c of the license. The latest version of this license is in https://www.latex-project.org/lppl.txt and version 1.3c or later is part of all distributions of LaTeX version 2005/12/01 or later.

The Current Maintainer and author of this work is Markus Kohm.

This work consists of the files README.md, LICENSE.md and scrtime.dtx.

Abstract

The package provides printing the time of the current LaTeX run either in 12h or 24h format.

Contributors/Collaborators

• Markus Kohm aka KOMA aka komascript:

Maintainer, Developer, “go-to guy”

Important Changes

This package is a KOMA-Script spin-off. It was part of the KOMA-Script collection up to version 3.49.2. Since version 3.50, it has been a standalone package.

• Version 3.50: The package does no longer support \KOMAoption and \KOMAoptions. So options 12h and 24h can only be set using either \usepackage (or \RequirePackage) or \scrtimesetup.

Installation for Users

If you are a user, you should usually wait until the package has been added to your preferred TeX distribution. Then you can use the package manager of your TeX distribution to install the package.

Unpacking for Distributors

Distributors should download the current release.

If distributors also want to distribute the whole unpacked work, they can unpack it using:

l3build unpack

Afterwards they can find the unpacked files in build/unpacked.

If distributors are interested in a correct TDS tree of the (unpacked) work, you can temporary install it into a TEXMF tree using:

l3build install --full --texmfhome <TDS root directory>
    

and then use the files from the selected <TDS root directory>.

Unpacking and Installation for Developers

Developers who want the current developer version of the code to be installed for testing, should clone the scrtime repository, e.g., using

git clone https://codeberg.org/komascript/scrtime.git

You can than unpack and install scrtime using (installation without documentation):

l3build install
	

or (installation with documentation):

l3build install --full
    

from within the main directory of the cloned respository.

Developers who need a specific release can do the same but need to switch to one of the release tags after cloning the repository and before running l3build. To see all available tags, run:

git tag

to checkout a specific tag, run:

git checkout <tag-name>

For example

git clone https://codeberg.org/komascript/scrtime.git
cd scrtime
git checkout v3.40
l3build install --full

would clone the repository, enter the working tree, checkout the release with tagged as v3.50 and installs it into your personal TEXMF tree.

To deinstall the local version of scrtime just run:

l3build uninstall

How to Contribute

To become a contributor, i.e., do heavy testing. If you find an issue, please report it. You can also become a developer and, e.g., make new test files to the package. See the l3build manual for more information about tests. If you've created a new test and think that it would be useful, please either do a pull request or add a new issue and include your test file.

How to Report Issues

If you think you have found a bug (or another kind of issue) using scrtime you should use the issue tracker. Please first search for similar issues already reported and maybe also already fixed and closed. Maybe the replies to such a similar report would help you too.

If your issue is new, you should report it also using the issue tracker. Please be kind, not only when writing the report but also when reading replies and commenting or answering. And please always add a minimal working example and usually the relevant parts of the log-file to your report. Please use the markdown for code to add such files into the text of your report. The correct language identifier for LaTeX code would be latex. For log-files you won't need any language identifier. Usually you should not use attachments for code or log-files unless you've been asked to do so. And please note, reports should always be self-containing. External links often break and so the report become useles.

How to Say Thank You for my Work

Hey, I'm doing this as a hobby. So no need to say thank you. But I'm a vain fop, so I'm certainly up for a quick thank you by email. However, you can find an explanation of my wishes if you want to give more.