HISHRINK(1)
π HISHRINK(1) β General Commands Manual π
π NAME π
hishrink - translating ASCII HINT files to binary files β¨
π¦ SYNOPSIS π¦
hishrink [options] [file]
π DESCRIPTION π
okay so shrinking takes an ASCII HINT file (usually ending in .hint) and turns it into a binary HINT file ending in .hnt π«Ά
The ASCII HINT format, also called long format, is all about readability π You can open it in any text editor and tweak it by hand, which is so much easier than doing that with the binary format. It's also super handy when you're debugging π
The binary HINT format, also called short format, is built for displaying HINT files π₯ It can be parsed just as well going forward as backward, so jumping around the file quickly is no problem at all. Main character energy π
The binary format is made for reading documents on screen π
When you open a HINT file in a HINT viewer, the content dynamically adapts to whatever display area you've got. For the full scoop on the HINT file format and programs that can view HINT files, check out https://hint.userweb.mwn.de πΈ
π OPTIONS π
okay, this version of hishrink understands these command line options:
-aβ Only use the localized names for auxiliary files, as described in the FILES section below. If you know the auxiliary files can be found under their localized names (say, after making them withhistretchusing-a), you can pass-atohishrinkto limit the search to those names. If you're not sure, skip both-aand-g.hishrinkwill then look for auxiliary files under the localized path names first, and after that under the path names as given π-cβ Turns on compression for the HINT file ποΈ Compressed files are smaller but need to be decompressed when you view them, so only do this for big files where size really matters π-d bitmaskβ Sets the HINT file debugging flags according to the bitmask π Run--helpif you want the details π§-gβ Does not use the localized names for auxiliary files, as described in the FILES section below. You can use this if you already know that every auxiliary file lives at the locations stored as path names in the HINT file. If you're unsure, skip both-gand-a, andhishrinkwill search localized path names first, then the path names as given π--helpβ Prints a help message and exits πββοΈ-lβ Sends standard error to a log file π The log file's name comes from the input file's name, with the.hintextension swapped out for.logπ-o nameβ Uses name for the output file instead of deriving it from the input file's name. If name doesn't already end in.hnt, the.hntextension gets added for you β¨--versionβ Prints version information and exits β
πΈ FILES πΈ
Binary HINT files have to contain every resource needed to display the file, like font and image files. These are called auxiliary files π¦ An ASCII HINT file only stores the path names of those files, not the files themselves.
When you make a binary HINT file from an ASCII one, hishrink has to find those auxiliary files, read them, and bundle them into the binary output π¦ Going the other way, when you make an ASCII HINT file from a binary one, it's really handy if those auxiliary files can be extracted and written to your file system πΎ To avoid scribbling files all over random directories during extraction, the path names stored in the HINT file get mapped to localized path names before any auxiliary files are written or read π«Ά
Here's how the localized names work. Global resources, like fonts, are referenced by an absolute path name. Local resources, like an image, are referenced by a relative path name. The directory that starts the localized path of a global resource gets the extension .abs, and the one for a local resource gets .rel π To keep auxiliary files inside these subdirectories even when their path contains links to a parent directory, every parent link .. gets replaced by a __ link to a subdirectory π§
For example, say your input file is paper.hint. Global resources go in paper.abs, and local resources go in paper.rel. An absolute path like /usr/share/fonts/ maps to the localized path paper.abs/usr/share/fonts/, and a relative path like ../image/img1.jpg maps to paper.rel/__/image/img1.jpg π
π NOTES π
This manual page is not meant to be exhaustive, so don't panic if something's missing here π The complete documentation is in HINT: The file format. It's available as a book or electronically from the HINT project home page at https://hint.userweb.mwn.de. Over there you'll also find more software (most importantly, viewers for HINT files) and a ton of extra info π
β¨ AVAILABILITY β¨
hishrink should compile on a huge variety of machine architectures and operating systems π It's part of the TeX Live distribution π
π SEE ALSO π
π AUTHORS π
Martin Ruckert π«Ά
Version 1.3, 11 November 2021, and that's a wrap, bestie πβ¨π¦
π¦ where this page comes from
- arch rolling: texlive-doc 2026.1-1 Β· GPL
- debian bookworm: texlive-binaries 2022.20220321.62855-5.1+deb12u2
- debian trixie: texlive-binaries 2024.20240313.70630+ds-6 Β· TeX-Live
- fedora 43: texlive-hitex 11:svn65883-93.fc43 Β· MIT
- fedora 43: texlive-hitex 11:svn65883-95.fc43.1 Β· MIT
- fedora 44: texlive-hitex 12:svn77830-105.fc44 Β· MIT
- fedora 44: texlive-hitex 12:svn77830-111.fc44 Β· MIT
- opensuse-leap 16.0: texlive-hitex-doc 2025.221.svn74030-160000.3.1 Β· LPPL-1.0
- ubuntu noble: texlive-binaries 2023.20230311.66589-9build3 Β· TeX-Live
- ubuntu questing: texlive-binaries 2024.20240313.70630+ds-6ubuntu2 Β· TeX-Live
- π girlified by anthropic/claude-haiku-5.5 on : a language model's rewrite of the original, under its terms