Hi @PhelypeOleinik. I'm been reading about your President. He sounds absolutely horrendous. Commiserations. If you've been keeping up with the news, you know we have our troubles here too. Greetings from the other side of the planet. :-)
@PauloCereda That's right, one question... will the new version of arara be available only for TeXLive 2019? ... Or will you wait until TeXLive 2020 comes out?
In syntax
\tl_set:Nf <tl var> {<tokens>}
if <tokens> begins with a space (input as ~), then this space does not appear in the definition of <tl var>. If a space appears in the middle or at the end of <tokens>, then it is kept in <tl var>.
Version info:
latex2e 2019-10-01
expl3 2020-01-12
...
@Speravir Do you mean with all those benchmark-pics I posted earlier and/or the expkv documentation? Your assumption is right, the main reason why I didn't benchmark it is, because its a wrapper around xkeyval using internals of kvsetkeys. Also it is not a classical key=val package in that sense but introduces a limited scope for the key=val interface.
@Speravir If you want to hear my two cents about it: I don't intend to benchmark it, but if I had to guess I'd say it has at least O(n²) run-time because it uses a multi-pass model similar, using internals of kvsetkeys to sanitize the kv-list, then runs through the kv-list again, adding braces, and then uses the slow parser of xkeyval on that sanitized and protected list. To be clear, that's just what I've grasped from its documentation when I looked at it to consider benchmarking it.
@Speravir However I didn't look at its code. All those benchmarks were done for the documentation of expkv and from that documentation:
> I tried to compare expkv to every ⟨key⟩=⟨value⟩ package listed on CTAN, however, one might notice that some of those are missing from this list. That’s because I didn’t get the others to work due to bugs, or because they just provide wrappers around other packages in this list.
@PabloGonzálezL hmm reading the manual? that will get us nowhere:-)
2
@PabloGonzálezL but what to do with minitoc-hyper.sty in the hyperef distrib? leave it, delete it, make it a stub that just includes minitoc with a warning, ??? (@JosephWright, @UlrikeFischer)
@PabloGonzálezL yes but you are not volunteering to check every file in arxiv to see how many break.... Current plan I think is to make it say (in total)
% Copyright 2020 LaTeX3 Project
\ProvidesPackage{minitoc-hyper}[2020/01/14]
\PackageWarningNoLine{minitoc-hyper}{This package is obsolete\MessageBreak please use minitoc instead}
\RequirePackage{minitoc}
@DavidCarlisle I'd also take a look at 'intheorem-hyper' ... I have the impression that it does nothing ...But there would be a shortage of volunteers to do the tests :(
@PabloGonzálezL ah OK I may leave that today, I'd ping the ntheorem maintainers I guess. that was last updated in 2011, are they still active I wonder?
I know that there was a way to do this, but don't remember how and where I read it, does anybody know how to set up text that gets displayed as stringA but gets copied as stringB? E.g., say I want to print \LaTeX, but want the copied text to read LaTeX, instead of LATEX.
@PauloCereda I saw no footnote but then realise that texdoc had helpfully substituted texdate, and I tried again while writing this and it shows texmate2manual
[...] it is always your fault when something terribly wrong happens in your code [1].
[1] This statement is suspiciously Carlislean. Also, since we are on the subject, make sure to never read documentation, as bad things happen.
Although there are no hard limitations on a template name, it is advisable to keep it short and concise, with no spaces whatsoever [5].
[5] Another Carlislean statement would remind us that people that put spaces in their file names deserve no sympathy. At all.
Hi all! If anyone has a minute or two, I think I have spotted a typo in Why conflict between mathtools and Gonzalo's solution for auto-adjusting description environment? There are two temporary names in use \@tempdimb and one below \@tempdima, which makes no sense and breaks the example. It's just one character, I don't have the rep to do that, and the author has disassociated his/her account, so leaving a comment seems useless. Thanks.
@PauloCereda seldom, my wife and I used to watch a lot of Dr. Who, but somehow stopped for a while, I think I have seen 8 episodes with her as the Doctor, or so.
@PauloCereda I don't think I saw any with Tennant or Capladi, current one is OK, but isn't John Pertwee, and Bradley Walsh certainly isn't Louise Jameson
Who invented the stupid datatypes of Matlab? And why did the guy who's code I am to use introduce such a weird data-layout with those stupid datatypes :(
When the sole reason you're using Matlab is that you have to reuse undocumented code somebody else wrote, you start to ask yourself the important questions of life...
@PauloCereda MATLAB is the antagonist, Mathematica is the murderer that you only get to see in the end. Maple is the guy who gets killed in the first 5 minutes. Octave is the girl to be saved.
@Skillmon I think like many systems that start off with a design aimed for a brutally simple syntax for a fixed range of features, that adding features later means you have to have lots of special cases to avoid the syntax shortcuts built in to the original design
@Skillmon Are those really pythons, though? They look too skinny for that. They look almost like cobras to me, except I don't think they grow quite that big. And I wouldn't want to be the instructor if that is what they are.
@PauloCereda and the composite words are one of the reasons for this
@UlrikeFischer there is one problem with this. You can't put tshirt into one word in German. It is T-Shirt, as the T is an abbreviation, same goes for E-Mail. So a better one would be "Weltschneemanntagsbärenkurzärmelhemd".
@UlrikeFischer no I thought since every test fails (the pattern I wondered if you would spot:-) I thought best not to commit:-) The existing pdfversion tests are ... "interesting" how hard can it be to add a pdfmajorversion ....
@UlrikeFischer I have checked 87-pdf2.tlg in as passing although it currently is wrong output in pdftex until the \pdfmajorversion` primitive appears. the checked in .luatex.tlg does show 2.0 though.
@UlrikeFischer I really don't like the style of hiding all the primitives (that's what confused me before) although I have kept it this time, the old code \Hy@pdfminorversion=\Hy@pdfversion means if the current value if \pdfminorversion is the setting of \Hy@pdfversion from the option setting then... so my original plan to change \Hy@pdfversion to \Hy@pdfminorversion failed at that point and I had to use a different name:-)
@UlrikeFischer you home?
it should work to use pdfversion=2.0 as a hyperref key now
@DavidCarlisle Where part of the "hyperref" is loaded with "minitoc"...when running $ grep -rn 'minitoc' --include="*.*" hyperref/ hyperref/minitoc-hyper.sty:3:\ProvidesPackage{minitoc-hyper}[2020/01/14] hyperref/minitoc-hyper.sty:4:\PackageWarningNoLine{minitoc-hyper}{% hyperref/minitoc-hyper.sty:6:please use minitoc instead} hyperref/minitoc-hyper.sty:7:\RequirePackage{minitoc} hyperref/manifest.txt:17:minitoc-hyper.sty hyperref/manifest.txt:18: Patched version of `minitoc.sty' to work with `hyperref.sty'.
@DavidCarlisle Yes, the same goes for "ntheorem-hyper"
$ grep -rn 'ntheorem-hyper' --include="*.*" hyperref/ hyperref/manifest.txt:19:ntheorem-hyper.sty hyperref/build.lua:78:"hyperref/ntheorem-hyper.sty", hyperref/build.lua:132:"tex/latex/hyperref/ntheorem-hyper.sty", hyperref/doc/manual.tex:2810: ntheorem-hyper.sty is an old patched version of ntheorem.sty. hyperref/ntheorem-hyper.sty:48:\def\basename{ntheorem-hyper} hyperref/ntheorem-hyper.sty:65:\ProvidesPackage{ntheorem-hyper}[\filedate \space\fileversion]
I think that over the years they became obsolete and the changes were not added to ChangeLog.txt
@UlrikeFischer yes but I think the dvips back end file is supposed to put add a suitable \special, I'll check
@PabloGonzálezL they are not intended to be included into hyperref, they are/were intended for users to use in documents to avoid conflicts between the packages
@PabloGonzálezL same as xr-hyper isn't included into hyper but if you are using hyperref you should use xr-hyper instead of xr (because the maintainers of xr, xr-hyper and hyperref can't agree on a sensible interface to avoid the conflict)
@PabloGonzálezL ntheorem one I have no idea, as I say once this is on ctan so they can easily test, I'll mail the ntheorem maintainers and ask them....
@DavidCarlisle Hopefully the "maintainers" will get their act together someday :)
@DavidCarlisle I tried several forum files... even the message in manual.pdf "But there are still unsolved problems (options thref, ...)" is fixed and the only problem that persists is in the documentation of ntheorem.
@DavidCarlisle yes, but with the new version it works fine. Is \Hy@pdfversion still used somewhere? Or why do you have \let\Hy@pdfversion\Hy@pdf@minorversion?
The PostScript setdistillerparams and currentdistillerparams operators are also recognized when the input is PostScript, and provide an equivalent way to set these parameters from within a PostScript input file.
So you should be able set the pdf output version by putting some literal postscript into a dvips special, I'll experiment
@DavidCarlisle Just as a note for the future, I think I've understood a little bit of the history of ntheorem-hyper.sty. The package ntheorem has all versions documented (in the .dtx file) and it skips from v1.13 to v1.15, this is because ntheorem-hyper.sty has v1.14 assigned to it [1998/12/03] and Heiko appears as a contributor in ntheorem.
@DavidCarlisle That said, since version v1.17 [1999/09/06] the hyperref option was added to ntheorem and from that date until the last version v1.33 it has been directly maintained by ntheorem.
@Skillmon You would also be correct. My former supervisor came up with that transliteration. It's used on all my documents, so I kept it, even though what you propose is the more accurate pronunciation...
@Martin-マーチン the macro and its definition. Only 478 lines of code :)
@Martin-マーチン I don't remember all the input rules, as I never wrote a documentation for it. Upper case input is translated to Katakana, lowercase to Hiragana. Where there can be special glyphs based on context which can't (to my knowledge) be directly transcribed to Romaji a : should switch to the alternative (iirc).
@Martin-マーチン I have no idea, I stopped studying Japanese due to my busy schedule after I had learned it for around half a year, and forgot almost everything. And by that time I didn't do much on computer in Japanese only by hand, so haven't had any contact to other transcription systems.
\romaji{MAATIN:wa doitsugo hanashimasu.} results in マーティンはどいつごはなします。
I know the feeling. I gave up on learning the language while I was still there, mostly because I was too busy. Mostly I've used my phone and computer at the time, as that was part of my workplace.
Yes and no. It is hard to express some things where it is much easier in other languages... on the other hand, repetition is quite common in japanese, so that makes things easier again. You just say something like 'that happens. then that happens. then that happens...'
I need to run to the shops before they close. It's been nice talking. :D
The question complaining about the small (to the OP) number of hyphenation patterns has got me thinking: do the American patterns hyphenate words spelt with British spelling correctly? (for example, "honour", "centre" ?) I'm assuming the British English patterns do.
This actually matters because Canadian English uses American hyphenation but with mixed British/American spellings.
In syntax
\tl_set:Nf <tl var> {<tokens>}
if <tokens> begins with a space (input as ~), then this space does not appear in the definition of <tl var>. If a space appears in the middle or at the end of <tokens>, then it is kept in <tl var>.
Version info:
latex2e 2019-10-01
expl3 2020-01-12
...
