@JosephWright I got with David's longtable branch a latex 20201001, an the updates format failed. Can the content of the latex be older than the current latex-dev?
@JosephWright branched off develop (and claims to be 2010-10-01-pl1
@JosephWright @UlrikeFischer must admit I haven't used it as a real format other than temporary ones for l3build check. I could merge in develop again to bring the format up to date...
@UlrikeFischer try now should be same as develop apart from longtable and a few test files
@JosephWright yes I may merge next time rather than rebase:-) it'll be a throw away branch after it's finally merged back so it doesn't really matter if the history in this branch is a bit convoluted
@Skillmonlikestopanswers.xyz at least he's learned the basic rep harvesting mechanism, start with inserting a change that breaks your package then harvest rep fixing it.
I know that this question has been asked before. But I am having real trouble implementing the before-mentioned approaches into my document which is of IEEEtran class.
My code snippet is the following one:
\subsection{Testing the Image}
\begin{figure*}[h!]
\centerline{\fbox{\includegr...
@Skillmonlikestopanswers.xyz fixes for "float on same page as start of table", "shrink glue anywheer near start of table" increase chunksize t0 200 in case your machine has more than 500K of memory and a few other bits and pieces
@Skillmonlikestopanswers.xyz I might do that, not sure yet
@UlrikeFischer adjusting bm for Frank's color example. the expansion loop was not totally unexpected but I'm not sure why it crashed rather than just fill a normal tex input buffer stack.
@Skillmonlikestopanswers.xyz you do realise that win95 is modern compared to the longtable design (I could probably already have increased the limits for that:-)
\documentclass{article}
\usepackage{listings}
\usepackage{inconsolata}
\begin{document}
\texttt{This is a test}
\begin{lstlisting}[basicstyle=\ttfamily]
This is a test
\end{lstlisting}
\end{document}
@DavidCarlisle you just have to use the source code and see the result. The font of what I want I don't know how to send it, I used an image for reference
@manooooh you only provided a test file when we asked for that, prior to that you said you had an example "that produces Consolas...." but it appears that you have no such example. If you do not provide code and give wildly inaccurate descriptions of your problem it is hard to understand what your issue is.
I do not think that a `h`-type `figure*` has ever been supported in two column mode... I added a comment and a couple of links to your question. There is a package (`nidanfloat`) that let you use a `b` `figure*` on the first page, but its documentation is in a language I can't read...
@AlanMunn I think it is the solution! Why incosolata don't change normal text (inside document) but the text inside lstlisting does? That's very interesting
@UlrikeFischer opposite of the effect it's curing, the output routine being confused about the shrink on the page and making a page that assumes there is no shrink, when there is, so it ends short or more likely a possible page break is not taken or... I have no idea really, I'm not sure I have ever set it rather than read it before:-)
Does anyone here with an iPhone have any recommendations about software to transfer messages and other stuff from the phone to the Mac. E.g. PhoneView, TouchCopy, iMazing?
@UlrikeFischer not sure, there are lots of potentially page breaking changes here and I may end up with lots of options, there is always [=2020-01-01] )or maybe I'll allow [=v4] to use the current version
@UlrikeFischer but even if I don't make it an option I could pull it into a small internal macro so you wouldn't have to redefined the whole of LT@start
@DavidCarlisle that would be okay. I can read code ;-) And if it looks as if users would need the ability to switch it off, you can add an interface and something to the manual later.
@UlrikeFischer you can set checkengine to luahbtex then it actually makes a luahblatex format locally but it's Ok, I think, although in the end I build iftex on tl2019
@UlrikeFischer although to be honest I'm not sure it was building the right thing, need to get back to check that, I pushed the pageshrink longtable as you may have seen
@UlrikeFischer yes it moans a bit, I think l3build needs extending but I need to check exactly what the current possibilities are for mapping engine names to latex format names, unless @JosephWright wants to suggest the intended form...
@DavidCarlisle I can test for tl2020 with something like if string.find(kpse.find_file("article.cls"),"2020") then. But l3build doesn't compare with the luatex files, but with the pdftex files. Unless @JosephWright has a good idea it looks as if one has to make copies of all the xx.luatex.tpf to xx.luahbtex.tpf etc.
@UlrikeFischer can't be hard to make it ise .luatex. for the luahbtex tests, I was looking for something to test for 2020, the find-file works if you sue the standard form but wouldn't work eg for a linux packaged version installing in an undated texmf tree
@DavidCarlisle yes, will probably work. But currently I'm wondering if one can tell l3build to use the luahbtex engine even if one do "-eluatex" (and to use the .luatex extension).
@UlrikeFischer that's what killed me doing iftex under tl2020 it has latex and plain tests and getting both working seemed more work than I wanted just to delete that scrbase block, so i used tl2019 but planned to get back to it
@UlrikeFischer ah looking good (although once you have it working we should probably try to get the defaults to do that otherwise every build.lua is going to have to set up lualatex) @JosephWright
if string.find(status.banner,"2019") then
print("TL2019")
else
-- tl2020
print("TL2020 or later")
specialformats = specialformats or {}
specialformats["latex"] = specialformats["latex"] or {
luatex = {binary="luahbtex",format = "lualatex"}
}
end
@DavidCarlisle I was hoping the banner would show "luaHBTeX", but naturally l3build still uses luatex, not luahbtex. I switched the test, so that I don't have to restart in 2021. It looks now like this:
@UlrikeFischer yes I looked for 2019 originally but failed as my tl2019 tree has a self compiled luatex tl2020/dev in its bin directory:-) but that's probably better than testing the version string really I agree:-)