@texdr.aft \verb and other verbatim type environments can't be the arguments of another macro because of how they mess with catcodes. See texfaq.org/FAQ-verbwithin for some discussion.
the computer modern lambda has its stress inverted from how they usually look
vs computer modern
this variant is more consistent with the uppercase form
but i feel like the "normal" one may blend in better with roman text when pretty-printing code in programming languages that have the concept of a lambda function
@texdr.aft for overall conformity. The stroke direction if you'd draw those characters decides how fat the stroke gets, just take a look at other Greek letters of the same font.
@UlrikeFischer seems to work I pushed that diff to required/graphics, which means I can probably remove the unquote calls from the def files since we are not adding quotes
@texdr.aft it's not about stroke length, only about stroke direction. In CM the strokes from upper left to lower right are thick, the ones from upper right to lower left are thin.
@JosephWright hmm, so the " were added around ginn@base which meant 'hello world.eps' test worked but that broke epstopdf and is the wrong place really the quoting ought to be just at the filesystem end in the def files.... I could put a copy of dvips.def in the testfiles/support in the develop branch test?
@JosephWright or I suppose we make sure the .def files work with either format and update them on ctan now....
@JosephWright OK, (but tests fail here anyway, looking....)
END-TEST-LOG
)
(\end occurred inside a group at level 4)
### semi simple group (level 4) entered at line 44 (\begingroup)
### semi simple group (level 3) entered at line 44 (\begingroup)
### semi simple group (level 2) entered at line 39 (\begingroup)
### semi simple group (level 1) entered at line 39 (\begingroup)
### bottom level
(\end occurred when \ifx on line 44 was incomplete)
(\end occurred when \ifx on line 44 was incomplete)
(\end occurred when \ifx on line 39 was incomplete)
(\end occurred when \ifx on line 39 was incomplete)
@texdr.aft no, not really. I mean sure it looks nice generally speaking. I like cursive and I like calligraphy too, although I do also like the fixed-width typewriter-style aesthetic. but it doesn't immediately look like code (which is probably fine) and there's a practical/functional reason why it's usually done that way. It's not really a big deal, and you're probably just experimenting, plus i don't wana tell you what to do, but if its for other people to read, i'd just go with tradition.
@tjt263 note that (unless I misunderstand) it's more psuedo-code than code, in that the lambda will not be in greek script in actual code (unless common lisp is more unicode aware than other lisps that I know better)
@texdr.aft i think i understand completely. i just wouldn't do it that way. i have a few books where it's done that way and in practice it's just not all that conducive
what's literate programming? kanji is arguably more elegant than english and latin letter forms, it's not necessarily very easy to read though. i don't think. actually i don't read kanji, so i don't actually know, but you get it
essentially you write your code organized as a collection of what Knuth called "modules" according to the logical order of human understanding and then software makes it machine-readable by re-ordering it. So for instance you might outline the whole program at the beginning and then progressively "fill in" parts of it. Each module also has text explaining it, and another program formats the code and explanations
in TeX, for example, as various data structures are introduced, global variables and types are progressively defined, instead of having to do it all at once
@UlrikeFischer on travis it doesn't use the new graphics-def unless they are copied to the graphics testfiles support area, but I'm getting issues with the rolled back code not working (actually the tlg file I suspect capture some non-working rollback as "foo bar".eps used to work but doesn't in the rollback version for me
What I am up to is to write some exercises dealing with logical formulas for my students, like:
And the students should draw these formulas on Venn diagrams. At the end of the lesson, I really would like to print the correct answer for them. I found a great resource on a forum thread at latex...
@DavidCarlisle when I copy dvips.def it fails, but only because of different log messages. You could sent me the log of l3build check -eetex utf8-filenames-002, then I could compare. Is it normal/intented that the test loads dvips.def also with luatex?
yes there are different log I fixed that but `\openin\@inputcheck"#1" %` for example in luatex.def can't work unless the `"` have been removed from `#1` which as far as I can see they will not be in the rollback cases, I'm wondering about defining \def\quote@name#1{"\quote@@name#1\@gobble""} \def\quote@@name#1"{#1\quote@@name} \def\unquote@name#1{\quote@@name#1\@gobble"} in the rollback version of graphicx so you can replace `"#1"` by `\quote@name{#1} ` in the def files, might need to leave it until later today though....
@DavidCarlisle a lot work for spaces and a lot work for a rollback ;-(.
@DavidCarlisle if one of these has duck hidden in it: L‘Affine au Champagne Rosé, Chèvre Crottin en Piment d‘Esplette, Trou de Cru avec Marc de Bourgogne, Tomme Morgé refined with hops and beer, Morbier „paysan“ du Jura, Le Vigneron d‘Alsace refined with Gewürztraminer, Gouda, five years old, „Belper Knolle“ - No way to translate that. Something really special from Switzerland.
@JosephWright yes, I was only surprised that it then uses dvips as driver as you can't really use the dvi with dvips, but thinking about it, none of the other drivers makes sense too.
@MarcelKrüger Date values used in a PDF shall conform to a standard date format, which closely follows that of the international standard ASN.1 (Abstract Syntax Notation One), defined in ISO/IEC 8824-1. A date shall be a text string containing no whitespace, of the form: (D:YYYYMMDDHHmmSSOHH'mm).
@MarcelKrüger do you need more?
@MarcelKrüger there is a note at the end: PDF versions up to and including 1.7 defined a date string to include a terminating apostrophe. PDF processors are recommended to accept date strings that still follow that convention.
@UlrikeFischer Thanks. Nice to hear that they added a note about the change, I just discovered that the trailing apostrophe is specified in the Adobe 1.7 reference but not in the ISO version, so I got a bit confused.
@JosephWright well yes and no, some of the other ,def files are not right (they just don't get well tested) so if people try the advertised feature of spacy filenames they will be disapointed, so I hope to fix up the quoting in the def files for "normal" formats then just do whatever is needed to make the tests pass. Should be done this afternoon
I've searched, but I can't find a previous question sufficiently close to this one to find an answer. At the same time, this problem seems like it must have been solved by someone before now, so apologies if it's a duplicate.
I want to clip a path (particularly a circle, but a general solution w...
Almost always if you use up the save stack you have some construct making local and global assignments to the same thing, which uses up an arbitrary amount of stack, so increasing TeX's stack size (if that is possible on the ipad implementation) probably won't help and you will need to correct th...
@JosephWright I'm working on these in the rollback case, they used to work, and they work with the new code but currently rolling back graphics but using new def files kills them (\includegraphics{"foo bar".png} should be fixable though (the old fix quoted earlier, but broke epstopdf...
@JosephWright hmm not as fixed as I thought I wonder how bad it would be to not offer rollback it's adding a lot of complication for little gain, unless we also want to roll back the def files
@JosephWright well.... they only work in plain as it loads miniltx which was half of latex as it was in 93, so that could be updated for at least the space handling, but yes, I need to check they still work in plain b@@gr (who's idea was it to offer plain tex support for graphics...)
@DavidCarlisle well let's say it this way: I never used a rollback and never saw someone using it. Also as we are uploading a dev-format, whatever rollback is perhaps needed could also be added later if someone complains ...
@JosephWright I'll drop out a bit realtime update not working:-) if you want realtime updates follow apolloinrealtime.org/11
@UlrikeFischer yes but as Joseph says it relates to plain tex support as well as we don't want to inflict the utf8 support on plain so graphics needs to work without that at least
@UlrikeFischer related yes as the rolled back format is more or less what the miniltx code for plain sets up, but it's actually different in other ways too so that's three different cases:(
I used to have a FF script that implemented a "copy the code" link in the upper right corner of code blocks on the site. It seems to have disappeared. I thought it was a Greasemonkey script, but I guess it wasn't. Does anyone use it and have a link? I have no idea where I got it.
@Skillmon I know you're not working at Overleaf anymore, but do you know why files created with filecontents don't show up in the project area (even though they are created properly)?
@DavidCarlisle Just remembered: the test failing on Travis-CI is one I have to disable locally anyway (the Windows command_line_utf8 business), so I can in principal build for release
@AlanMunn Ulrike's right. But I'm not that familiar with Overleaf's exact inner workings, Most of my work was debugging LaTeX projects. I know that Overleaf doesn't completely clear the virtual machine that compiles your project, it does have a cache (and most likely your file is stored inside that cache). But I don't know enough about that to be of real help here, best would be to contact the support directly.
@CarLaTeX I see. Yes, the clearing works somewhat differently from the way we're used to on a local installation. So stuff can appear to persist longer than you would expect unless you explicitly clear the cache.
Luatex has what looks to me like nice support for this, having primitives for traversing over the contents of boxes (which it represents internally using the more general concept of typed nodes).
If you have a smattering of Lua and read the first three chapters and section 4.10 of the Luatex m...
@FaheemMitha that is what tagpdf is doing to inject literals: it traverse the shipout box. lua-visual-debug is doing the same. ctan.org/pkg/lua-visual-debug.
if anybody here happens to be familiar with common lisp i have a question
it seems that the order of (let ...) (labels ...) (macrolet ...) etc. in a function doesn't matter, but is there a "standard" order?
i get that if functions defined in (labels ...) refer to variables defined in (let ...) then the let has to come first, but what happens in the case that everything's independent
What I am up to is to write some exercises dealing with logical formulas for my students, like:
And the students should draw these formulas on Venn diagrams. At the end of the lesson, I really would like to print the correct answer for them. I found a great resource on a forum thread at latex...
I want to add a footer to my document displaying the current number out of total number of pages. How do I do that?
Luatex has what looks to me like nice support for this, having primitives for traversing over the contents of boxes (which it represents internally using the more general concept of typed nodes).
If you have a smattering of Lua and read the first three chapters and section 4.10 of the Luatex m...
