« first day (5084 days earlier)      last day (146 days later) » 

05:27
@cfr The VLE? Yes, but I never upload TeX-related files
cfr
cfr
05:55
@JosephWright the very same. it doesn't provide any details beyond ris, bib or (translated to english) references but the former means pdf, I think. but it insists my .bib has no data.
this bit of it is new. and it might be some kind of plugin for reading lists - it is hard to tell.
@cfr Can you send me a screenshot? I can try something out if I know what exactly you are doing
06:37
Arg, people exploiting. abug in v2 I fixed in v3 :)
cfr
cfr
@JosephWright I can ... but I'm no sure what you want a screen shot of. Here's the error:
@cfr I meant where are you uploading :)
cfr
cfr
@JosephWright it looks exactly the same?
@cfr Hmm, I'm not at all sure where you are uploading - so I'm a bit stuck
cfr
cfr
The only thing in between is the system file selection dialogue. this is why I said I could send a screenshot, but I think it would help.
06:49
@cfr ^^ The standard upload page I'm used to - which looks nothing like what you are seeing :)
@cfr I assume you are using BlackBoard 'classic' no the new Ultra version? We've switched this year, but I can still get at the older interface (which is what I've shown above)
cfr
cfr
@JosephWright no we're using ultra. we switched last year.
@JosephWright do you have anything which looks like this ^^?
but in english, probably ...
@cfr I'm looking :)
cfr
cfr
@JosephWright it is not the standard file upload. this is specific to reading lists. and it wasn't like this last year.
@cfr Ah, reading lists - we use another product for those (Tallis), that links to BlackBoard
cfr
cfr
@JosephWright I think it would help -> I didn't think it would help ...
@JosephWright yes, I'm not sure this is blackboard. we were using leganto. I am not sure if this is a new version or something else.
if I knew what it was, i might be able to search, but it is just labelled "Reading Lists" everywhere (even in welsh).
and the help link takes me to cu's learning & teaching academy, which doesn't even have an option to search?!
it wasn't great before, but you could get to blackboard's site and you could search cu's own resources.
@JosephWright sorry. I thought i said that, but I just checked and I didn't.
07:28
@cfr :)
@cfr I'm pretty sure this is an add-in - I can't find anything 'native' in Ultra
@cfr At UEA I'd ask our library contact and/or teaching technology people (we have a dedicated group to support Bb, etc.)
08:12
@JosephWright I feel that way every time I see an afterpage question
cfr
cfr
@JosephWright I spent a good many hours last year trying to get help from IT and I still can't access eduroam on my laptop. I can't even get them to restore power which we've not had since before the summer. but the library is generally better. (IT are centralised and just ignore tickets.)
@JosephWright I'm also pretty sure it is an add-in.
08:30
Anyone else getting a lot of emails from CTAN? I normally only get a daily summary, but not I get a heck load of emails.
08:44
Is there a reason why the low level coffin stuff described in interface3, does not have a \coffin_ht_plus_dp:N similar to the one boxes has, \box_ht_plus_dp:N, at least just to be consistent with the box tools.
@daleif probably my fault :)
09:05
@JosephWright It might also be nice with a \coffin_typeset:Nnn same as \coffin_typeset:Nnnnn but the last two args are 0pt. At least in my uses I rarely need to offset. I just use it as if I was using \parbox.
09:37
Regarding replacing \parbox and minipage with coffins. What is the equivalent of this \begin{minipage}[t][13.7mm][t]{\linewidth} in coffin terms? As far as I can see there is no tools to set a coffin of a specific height.
@daleif if you are writing something that at some time will need tagging support then minipage and coffins are not equivalent, as the first is tagging aware but the second not. There you would have to add the support manually.
 
2 hours later…
11:49
@UlrikeFischer these are for letters and letter like, so not sure if taggeing will be relevant.
12:26
@daleif Added for next release
@daleif letter like documents are imho quite important. Think only at bank account reports (I already get tagged versions here), invoices, confirmations for reservations, invitations. Most PDF-documents that I get per mail currently are of this type, and lots of them are sent to a larger audience. And once I find some time I will certainly try to tag my own invoices.
@yannisl If you want to you can send me your custom PGF handlers and I'll take a look at them (not to add them to l3keys, which I can't, but to take a look at them, help you define l3keys-based alternatives via non-handlers, and finally to consider them as pseudo feature requests to expkv-def). If you don't know how to reach out to me: One of my mail addresses can be found in expkv-bundle.pdf.
12:46
@UlrikeFischer I don't think I've even seen a tagged PDF in the wild (though haven't looked for them either).
@Skillmon @Skillmon thanks, I will prepare something and send it to you.
13:07
@yannisl But don't expect me to be fast, my week is quite full. Maybe I'll manage today's late evening, but no promises.
Given that I don't use xelatex, at all, are there any specific pitfalls one need to be careful with? My converted class works just fine with pdflatex and lualatex, but xelatex gives a Missing } inserted with no apparent cause.
@daleif Without context, 'no'
@daleif XeLaTeX has some quirks, but that sounds rather odd.
13:23
Xelatex is just too annoying to work with, considering to just drop support for it. For the fonts I'm using we have a special encoding for it to work with pdflatex, for xelatex and lualatex we use fontspec. But apparently xelatex still reads pdftex.map and try to make sense of it and fails as it is a custom encoding for one of the files. So I get xdvipdfmx:warning: Creating ToUnicode CMap failed for ..., xdvipdfmx:warning: Invalid map record in fontmap line 4805 from pdftex.map
@Skillmon Thanks I will send them some time next week, and send you a message here when I do and take your time
As I guessed font related. Sign.
@daleif Yes, best option is not to use fonts.
@daleif changing fonts is easy, as long as the font is named Computer Modern and looks like this: <image of Computer Modern glyph table>
@mickep Here it is the custom encoded one, it has four chars, and we already had to do nasty tricks to get xelatex to access it it in the first palce.
13:29
@daleif Is the font different from other fonts?
@mickep Quite, the chars live in the private area. But we have had it working. Need to check the archives.
Will debug.
@daleif Good luck!
13:57
That was an interesting one. Say we have the following
\ifxetex
\NewDocumentCommand\AULogo{}{{\tracinglostchars=-1\AULogofont\XeTeXglyph\XeTeXglyphindex "uniF030" }}
\NewDocumentCommand\AUSeal{}{{\tracinglostchars=-1\AULogofont\XeTeXglyph\XeTeXglyphindex "uniF031" }}
\NewDocumentCommand\AUBSSLogo{}{{\tracinglostchars=-1\AULogofont\XeTeXglyph\XeTeXglyphindex "uniF032" }}
\NewDocumentCommand\AUBSSLogoInverted{}{{\tracinglostchars=-1\AULogofont\XeTeXglyph\XeTeXglyphindex "uniF033" }}
\fi
Running under Expl3.
When, in a clean document under xelatex I use \AULogo and then \AUSeal, then xelatex complain about simple group levels that haven't been closed. If I enclose the whole thing in \ExplSyntaxOff ... \ExplSyntaxOn, then there it no warning, and the original missing } goes away.
So it is the missing spaces that \XeTeXglyphindex needs that are missing.
And the space after " is important. That was an annoying one
Probably haven't tested this package under xelatex after I converted it into Expl3
@daleif Oh, that - yup :)
14:43
@JosephWright not an easy error msg to deciffer
15:00
@daleif I'd make a thin wrapper to avoid the issue
cfr
cfr
@UlrikeFischer so coffins should be avoided?
@cfr they are good for zombies
15:23
@cfr no, but if you want to write tagging aware code you need to understand the difference and perhaps add tagging code directly.
cfr
cfr
@DavidCarlisle you mean the non-philosophy kind?
@UlrikeFischer hmm. thanks. I'll try to remember that. (I'm not yet trying.)
@UlrikeFischer I'm sure my answer was quicker and more helpful
16:27
Did somebody say zombies? i.sstatic.net/Cabt7.gif
3
16:51
I like coffins! There are a bit similar to nodes, so a good extension to l3draw.
I wonder whether someone comes up with an l3urn package …
cfr
cfr
17:37
@JasperHabicht they are very nice when you need precise non-standard alignment. I wonder if there is a specific problem tagging them ....
17:59
@cfr boxes are generally not easy to tag, e.g. if you move them around or if you use them twice or if you create them only to measure something you have to think what happens with structure commands inside and around the box. And to make think more complicated luatex and pdftex behaviour differs.
cfr
cfr
18:18
@UlrikeFischer thanks. I can see that would be complicated. (actually, the whole enterprise seems incredibly complicated along many different measures of complexity.) so not specific to coffins?
 
1 hour later…
19:42
@cfr generally boxing and "trial typesetting" are issues for tagging as you usually only want one set of tags and tex doesn't allow you to change box contents once set. It's not so bad in controlled cases like tabularx or ams trial typesetting when you know in advance when you are setting the final version but an arbitrary \setbox that might or might not be used any number of times later is a bit tricky, so probably higher level structures you build from coffins might be easy to tag ...
@cfr ... but an arbitrary coffin with no context of how it's being exhumed it's not so easy
@DavidCarlisle Indeed, life is easier with context. :P
@mickep context, lurking in the shadows with the zombies?
@DavidCarlisle Oh, lurking...
20:07
At least, coffin seems to be a very old word … earliest form being 𐀒𐀠𐀙
cfr
cfr
@DavidCarlisle but that's true of an arbitrary box, too, isn't it?
is there any way to figure out which line 58 tex's error refers to?
@cfr yes exactly, as I say it applies to a simple \setbox as well.
@cfr scan up over matching () to find (this-is-the-file-with-an-error
@cfr or use pdflatex --file-line-error
Is is just me that recently CTAN-ann Digest emails are no longer sent but replaced with emails one for each CTAN announcement?

Even worse, I'm unable to open https://lists.dante.de/mailman/listinfo/ctan-ann right now.
The CTAN page on announcements and the mailing list:
https://ctan.org/ctan-ann?lang=en
20:24
@muzimuzhiZ About the dante mailing list: there recently was an announcement that they are moving servers and there might be an interruption
> Zusammen mit einigen engagierten Mitgliedern ist die Umstellung weit
gediehen. Die letzten Arbeiten werden in den kommenden Stunden und Tagen
angegangen. Dazu gehört u.a. der Mailserverbetrieb. Ich bitte Euch/Sie
daher um Verständnis, dass es bei Mailinglisten wie dieser hier oder
auch der Zustellung an @dante.de-Adressen ggf. zu kurzen Ausfällen oder
Unregelmäßigkeiten kommen kann.
cfr
cfr
@muzimuzhiZ ctan moved over the weekend, so uploads were unavailable. they resumed on sunday, but I suspect the announcements are rather screwed up. the mess is most likely a temporary blip. (I don't know this - I'm just guessing what might make sense given the general disruption.) I'm guessing they may have had an influx of uploads to deal with, too.
Thanks. That's good news (for getting accompanied).

BTW the last Digest email I received had the "Ctan-ann Digest, Vol 1049, Issue 5" topic and was received at Fri, 27 Sep 2024 03:00:51 -0700 (PDT).

But three weeks ago per-announcement emails were already sent
- "[Ctan-ann] CTAN update: verifycommand" received at Wed, 4 Sep 2024 11:57:15 -0700 (PDT), from petra at ctan.org
- "[Ctan-ann] CTAN update: heria" received at Wed, 4 Sep 2024 23:18:25 -0700 (PDT) from petra too
cfr
cfr
20:41
@DavidCarlisle thanks. (it doesn't help as much as I hoped, but at least I know which file.)
@muzimuzhiZ sorry. I'm slightly lost. the 27 makes sense - the final announcements on ctan's frontpage prior to the move were dated 26. something like 'commalists' was the last package listed. (that one subsequently got a 'package removed' page, but maybe sorted by now.) what's the stuff from the 4th?
commalists-tools was last and is still the latest listed on the homepage (ctan.org), though packages I submitted later are already updated on ctan - just not included in the listing).
@muzimuzhiZ what's 'accompanied'?
@samcarter ah, secret coded messages
cfr
cfr
@DavidCarlisle I'm sure you decode them perfectly?
20:56
@cfr well naturally we linguists are good at decyphering
cfr
cfr
@DavidCarlisle wrth gwrs.
@DavidCarlisle just for you :)
cfr
cfr
the error occurs only when I use l3build doc? if I pdflatex the file directly, it's fine ...
21:57
@cfr are you allowing the doc and tests to search the standard tex tree, or using a normalised texinputs (like the l2e tests that sandbox themselves from the standard tree)
yo'
yo'
22:21
5 years at Overleaf as of today yesterday
5
22:40
@yo' congratulations, do they give you an overleaf duck for long service?
@cfr I have no idea about such per-CTAN-ann emails before the last weekend too.
yo'
yo'
@DavidCarlisle I'm afraid that I already have more Overleaf ducks than years served :D
@cfr The situation that I was not the solely affected user. (me accompanied with affected others). Sometimes it gives me more confidence that the noticed issue will soon be resolved.
@yo' I have done more than 27 years here and they never gave me a duck, so I can be thankful for that at least
cfr
cfr
@DavidCarlisle the former. I haven't figured out how to do the latter. this is not a great idea because I'm using hackery to get compilation to pick up the new files and if I do something I didn't expect me to do I end up picking up the old ones. then it works fine, but will break when tex live pick it up.
(I know this because 'works fine' doesn't always work fine.)
@yo' llongyfarchiadau!
@muzimuzhiZ there is often safety in numbers. it is an open question which numbers.
yo'
yo'
22:56
@cfr diolch yn fawr
cfr
cfr
@DavidCarlisle I seem to have eliminated the error ... but I have no idea how.
@cfr well anyway if it fails in one context and not the other grabbing the two log files and comparing with a diff program usually helps
cfr
cfr
@yo' <3
@cfr just thank me? Perhaps I fixed it remotely...
cfr
cfr
@DavidCarlisle I'll try to remember that. I've never actually thought of using diff.
@DavidCarlisle I'll be happy to if you can explain the fix.
If somebody can explain github, that'd be even better ;).
23:00
@cfr Cyfrinachau'r derwyddon
cfr
cfr
@DavidCarlisle hmm ... well 'da fi hudlaeth eglur :-). but thank you anyway.
23:20
@cfr the cauldron helps, I suppose
cfr
cfr
@DavidCarlisle you'd think, but most people use microwaves these days. only rich witches have kitchens big enough for cauldrons.
[one of the welsh words for microwaves is far better than the english, but I'm not sure how to write it and I doubt it's the kind of thing I'd find in the Academi's dictionary.]

« first day (5084 days earlier)      last day (146 days later) »