Notes about issue fonts_in_pdf_files in experimental
| Identifier: | fonts_in_pdf_files |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / experimental |
| Description: |
The internally used names/identifiers of fonts embedded into PDF files varies. The order of embedded fonts can also be different. . The order is only different if the date differs (set by TZ environment variable for example). If the date is the same, then the font name is reproducible. Difference in hour/minute/second resolution seems to be irrelevant. . The font name occurs in the /BaseFont field and in the /Fontname field. The name is of the form XXXXXX+YYY where the XXXXXX part is the one that varies and is called the subset_tag. It is generated in texk/web2c/pdftexdir/utils.c function make_subset_tag() from an MD5 sum over the font glyphs. |
|
Packages in 'experimental' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
|
|
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise). |
|
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
A # sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+ sign indicates there is a
patch available, a P means a
pending bug while # indicates a
closed bug. In cases of several bugs, the symbol is repeated.