| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
| |
Not used yet, though.
|
| |
|
|
|
|
|
|
| |
Now the boxes are "transparent" to the algorithm. This saves 5%
space on a uncompressed PDF, about 0.5% in a compressed one, but
may be a lot more for documents with a lot of boxes.
|
|
|
|
|
|
|
|
| |
Smaller pdf output. Some more optimizations could happen by a second
exploration, may come later.
The file doesn't work with LuaTeX 0.40 but seems ok for 0.44. Colors are
now disabled for versions <41.
|
|
|
|
|
| |
This fixes style checking for many correctly named fonts, but breaks
crappy fonts like LM and MnSymbol, both aren't a priority for me.
|
| |
|
| |
|
|
|
|
|
| |
Now LuaTeX can return proper TTF names, we no longer need these dirty
hacks.
|
| |
|
|
|
|
|
|
|
|
| |
Not relying on str:is_empty which is not in luaextra (yet?).
In pre_output_buffer, we shouldn't encounter sub_math but if
we encounter a sub_box we should explore it like we do for vlist
and hlist.
|
| |
|
|
|
|
| |
There still room for improvement.
|
|
|
|
| |
the callbacks are not registered if no font with colors is loaded, less verbose pdf output
|
| |
|
|
|
|
|
| |
Fixes bug with some fonts ("attempt to get length of local 'splt' (a nil
value)").
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We now support XeTeX's syntax, try:
\input luaotfload.sty
\font\termesr ={TeX Gyre Termes:+liga} at 10pt
\font\termesb ={TeX Gyre Termes/B:+liga} at 10pt
\font\termesi ={TeX Gyre Termes/I:+liga} at 10pt
\font\termesbi={TeX Gyre Termes/BI:+liga} at 10pt
\font\termesib={TeX Gyre Termes/IB:+liga} at 10pt
\termesr What a nice day fi fl ffi ffl ff\par
\termesb What a nice day fi fl ffi ffl ff\par
\termesi What a nice day fi fl ffi ffl ff\par
\termesbi What a nice day fi fl ffi ffl ff\par
\termesib What a nice day fi fl ffi ffl ff\par
\bye
|
| |
|
| |
|
|
|
|
|
| |
Only regular style is resolved for now, still need to pass the proper
style to the filename resolver function.
|
|
|
|
|
| |
Even if it is a single value (filename), to make our life easier in
matching process.
|
|
|
|
|
| |
We now use our own version number since we no longer compatible with
luatex-fonts' version.
|
|
|
|
|
|
|
|
| |
Remove spaces, hyphens etc. so that we don't have to deal with many
irregularities.
Now I seem to process all fonts included with TeXlive correctly, and my
+2000 files font collection with two errors only.
|
|
|
|
| |
Now this code is getting really ugly!
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now database looks like:
mappings = {
families = {
["familyname"] = {
["regular] = filename-regular.ttf
["bold"] = filename-bold.ttf
...
}
...
}
psnames = {
["psnameregular"] = filename-regular.ttf
["psnamebold"] = filename-bold.ttf
...
}
}
|
|
|
|
|
|
| |
If $OSFONTDIR is set, then it'll be appended to $OPENTYPEFONTS and
$TTFONTS anyway, so we are just rescanning fonts. To be replaced by
fontconfig based implementation.
|
|
|
|
|
|
| |
Instead of using (the faster) fontloader.info, we now fully open the
font to get more usable data, my be it is worth extending
fontloader.info to cover our needs?
|
| |
|
|
|
|
|
| |
Khaled, why not having luaotfload.colorize instead of local colorize
functions?
|
|
|
|
|
| |
$OSFONTDIR in not always set, so check it and the others too. Also index
only the base filename for files in texmf tree.
|
|
|
|
|
|
| |
Now we read $OSFONTDIR variable to load system fonts, $OPENTYPEFONTS and
$TTFONTS to load fonts in texmf tree. Fontconfig support might be added
later.
|
| |
|
| |
|
|
|
|
|
|
| |
Will moves |logs.report| to |otfl-luat-dumm.lua|.
This reverts commit 4479c85beec3b201db096d9320d203a58fd210d4.
|
| |
|
|
|
|
| |
Very crude, linux only.
|
|
|
|
|
|
| |
I'm abusing versioning, version number should be increased only after
making a release (since CTAN version is 1.06, git should be 1.07), we
should tag releases too.
|
| |
|
|
|
|
| |
For easier maintenance.
|
|
|
|
|
|
|
|
| |
Looks like the internal of the code changed in the mean time that the
mere existence of a feature in the features tables will enable it, so
now we nullify it instead.
closes #4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LaTeX expects that fontname is the tfm name, and thus use it to recall
the font, so we ought to store something that can be used the same way
here. `specification.specification' is the string used to define the
font.
Test:
\input luaotfload.sty
\font\xxx=file:lmroman10-regular.otf:+liga;+tlig\xxx
``\fontname\font'' should be: {\tt file:lmroman10-regular.otf:+liga;+tlig}
\bye
closes #3
|
|
|
|
| |
Now, we are on par with XeTeX's tex-text mapping.
|
|
|
|
| |
Now `x', ``x'', ``x,, and x's work as CM fonts.
|
| |
|
|
|
|
|
|
|
| |
Apparently, LuaTeX weren't happy by massive assignments to
tex.pdfpageresources (we were reassigning it for almost every node!).
Now the code seems to work, but it is just a big hack at best.
|
|
|
|
|
|
| |
Switch to pdfliteral default (indirect) mode which will make sure text
blocks are surrounded by BT ET (see PDFTeX manual, 7.12), which, for
some obscure reason, adobe reader needs for transparency to work.
|
| |
|
| |
|
| |
|