You mean the mega font? That's actually 207M
uncompressed :)
That should probably go to a different package (and depend on it). I
don't see why it couldn't fallback to another available font if it's not
available, though.
The point is that the change of the font has to happen inside a
run of
LaTeX compiler. I tried that and it sometimes works but often the
compiler does not produce any output if I do that. So the best is to
give the compiler one font for the whole document and let run with that.
It seems you're creating it from wqyzenhei + unifont + freeserif fonts.
Why do you need to merge them?
I merged them because changing the font in LaTeX
does not always work,
especially inside headings which become part of the table of contents.
I essentially
did the tmp trick in order to get
around the work of researching where to install each file and to
properly fix the path names in the code and to test that.
In case of doubt, you
should have placed the folder in /usr/lib
A number of would be better placed at /usr/share, though.
But I'm not sure what are many files.
For instance, what's the purpose of geturl and pa programs?
The main part of
the program is written in the wonderful and easy to
learn purely functional programming language Haskell. Some minor parts
are written in Python3, these two parts need to communicate. Currently
pa and geturl are binaries created by the Haskell Compiler ghc. pa is
essitially a compiler for the mediawiki language, it parses to a tree
and writes it down as LaTeX. The problem with the mediawiki language is
that it allows improper bracketing of tags and thus is not context free
and thus there is no BNF for it and thus all normal parsers are ruled
out and thus you need to use a more obscure technology like monadic
parser combinators in Haskell.
But since you seem to have a good idea where to put which file, you
maybe could give me some hints on that, since that would make my work
much easier.
And why do you have copies at bin/ and dist/build?
Furthermore, why are
they different?
Build artifacts are also common there.
I will remember this for future versions of
the deb file. Essentially I
only need the stuff in the bin directory. The stuff in the build
directory is just created by the ghc build tools.
Yours Dirk