vlasakm / mmtex Goto Github PK

Im using Debian 11.

After compiling with test.tex:

abc \bye

I've obtained:

! Font \_ten_tenrm=nullfont at 10pt not loadable: metric data not found or bad.
[1
Missing character: There is no a (U+0061) in font nullfont!
Missing character: There is no b (U+0062) in font nullfont!
Missing character: There is no c (U+0063) in font nullfont!
Missing character: There is no 1 (U+0031) in font nullfont!
]
WARNING l.3: Unicode font was not loaded.

When I use \fontfam[lm] at the beginning of the preamble, the result is:

luaotfload | db : Reload initiated (formats: otf,ttf,ttc); reason: File not found: "lmroman10-regular".
WARNING l.7: Family [Latin Modern] skipped, font "[lmroman10-regular]" not found.
Missing character: There is no a (U+0061) in font nullfont!
Missing character: There is no b (U+0062) in font nullfont!
Missing character: There is no c (U+0063) in font nullfont!
Missing character: There is no 1 (U+0031) in font nullfont!

The PDF is always blank.

With the recent conceptual changes to the repository, there is now no option for manually building the packages for Debian / Arch Linux (formerly through the package-builder script and a few support files).

There are now two ways for installing mmtex:

• Through normal distro specific package manager (from OBS repositories or in the case of Arch Linux, from AUR.
• By building from source and installing manually with meson to arbitrary directory (with any combination of prefix and destdir the user pleases).

OBS covers a lot of distributions and architectures, that I wasn't able to cover before, but still doesn't allow all (#4). Should there still be a way for the users to build the packages? Is it OK to require them to acquire the files from OBS and use its tooling?

The problem is that currently three distinct types of package building are supported - Arch Linux (PKGBUILD -> .pkg.zst), RPM (.spec -> .rpm) and Debian (? -> .deb). The packaging files that are now in the OBS, could theoretically be included in this repository. But the conceptual ways the packages are built for Arch + RPM vs Debian are just different.

The former requires a single file describing the build including the sources, which are downloaded.

The latter requires weird combination of two tarballs (one with the normal sources, other one adds debian subdirectory with some control files) and a special file, that extracted to a directory from which one can build the package by executing one of the many debian helper commands.

The old package-builder script just packaged a directory into a package, but this wasn't possible for .rpm packages and is not a way forward (I want the sources to be packagable in distributions normally).

@itmm If you have any needs, please comment here (provided that you still use/need mmtex).

I am using Debian Buster (stable).
Package mmtex_20210102_amd64 tries to overwrite the TeX Live luatex binary, and fails.

# apt install ./mmtex_20210102_amd64.deb
...
Unpacking mmtex (20210102) ...
...
trying to overwrite '/usr/bin/luatex', which is also in package texlive-binaries 2018.20181218.49446-1

Just calling it mmluatex solves the problem.

Im using Tails 5.22 OS, a Debian 11 based.

After using

meson setup builddir --prefix ~/.mmtex --buildtype release

I get 3 warnings and 1 error in the following log:

meson.build:19: WARNING: Passed invalid keyword argument "env".
WARNING: This will become a hard error in the future.
WARNING: Unknown keyword arguments in target mmoptex.fmt: env
meson.build:37:0: ERROR: Unknown function "install_symlink".

meson-log.txt

Would you consider supporting Harfbuzz in mmtex. LuaTeX already supports it (when compiled with an optional flag), and so does luaotfload. I imagine the changes in this repo would be to download some additional source files and then build them.