@AlanMunn -- I've just tried out several words, with these results: "hon-our", "cen-tre", and "favour" with the us patterns (using Knuthian TeX) and "hon-our", "centre", and "fa-vour" with the British patterns (using pdflatex with [british]{babel}). My copy of the mini-dictionary used to derive the British patterns is in an inaccessible box, so I can't check that, but I don't find "cen-tre" to be objectionable. But this does show that checking (and some in-document overrides) is a good idea.
@barbarabeeton you get some different results but (present company excepted) it's not as if people really expect any particular hyphenation, so long as it looks OK, I the US patterns match UK spelling well enough
@DavidCarlisle -- I suspect that's true, but there are at least a few very odd items in the British dictionary. See my disquisition on "alternate" at tex.stackexchange.com/a/171155. I should really check on the progress of getting new British patterns based on an updated dictionary. Dominik was working on that.
@DavidCarlisle and @AlanMunn -- There's a new question about patterns on the main site (tex.stackexchange.com/q/524791); I'm about to answer it.
@barbarabeeton alternate: the stress varies according to use (and the north american use is just weird) so altern-ate or al-ter-nate would look OK to me, according to the context.
@DavidCarlisle -- I'm used to two different pronunciations, one for adjective/noun, and the other for verb, but the stress is the same (first syllable), and so is the hyphenation (al-ter-nate). The only situation in which I can accept a hyphen after "n" is for the word al-tern-a-tive. British hyphenation is allegedly etymological, but (@AlanMunn, please correct me if I'm mistaken) "altern-ate" is etymologically nonsensical.
My conjecture for the presence of that entry is a frequent ploy among publishers of lists, to salt in occasional phony entries to trap re-publishers or users who have stolen the material without proper credit or payment.
the adjective is pronounced more or less as altern-at so hyphen after the n seems OK to me and al-tern-at-ive for the noun, which just leaves the verb form as al-ter-nate, but I don't think my reading would be disturbed by hyphenating the adjective as alter-nate either although I like that form less as I can't read alter-nate without it sounding like al-ter-nate
@barbarabeeton Yes, this was the question that prompted mine here. But I agree with @DavidCarlisle, who really cares... :) If a copy editor complains about my hyphenation they're welcome to change it.
@barbarabeeton Yes altern- is definitely etymologically non-sensical to the extent that the word is "borrowed" from Latin. (Not really borrowing in the proper sense.)
@DavidCarlisle No, even with that pronunciation the 'n' should stay with the 'ate' since that's how it is in the pronunciation too.
@DavidCarlisle -- I've honestly never heard "alternate" pronounced with the stress on the second syllable. Can you point me to any recording that uses the word in context? Granted, the person asking the question I cited is located in Germany, so is probably not a native speaker of any dialect of English, so can't be taken as an authority.
@barbarabeeton if I google for it then google shows a box with two definitions plus the north american usage as a noun the actual sound will depend on your browser but google.com/search?client=firefox-b-d&q=alternate the top one is clearly three sylables al-ter-nate but the second is almost two altern-at being the closest ascii rendition that I could show to highlight the difference. while I agree the etymology is dodgy I think alter-nate suggests the first form
@DavidCarlisle (and @AlanMunn) -- I've found a site with UK/US pronunciations: dictionary.cambridge.org/us/pronunciation/english/alternate ; the UK pronunciation of the adjective is quite different from all the others, and indeed, it has the stress on the second syllable, so "al-tern-ate" would be appropriate. That's a new one for me. So I concede.
@egreg No idea why I didn't see your answer to tex.stackexchange.com/q/524796 before I posted mine. Sorry about that, didn't mean to steal the green tick. I know how much they mean to you. ;-)
$ pdfinfo zz4.pdf
Title:
Subject:
Keywords:
Author:
Creator: LaTeX with hyperref
Producer: pdfTeX-1.40.21
CreationDate: Sun Jan 19 11:29:43 2020 GMT
ModDate: Sun Jan 19 11:29:43 2020 GMT
Tagged: no
UserProperties: no
Suspects: no
Form: none
JavaScript: no
Pages: 1
Encrypted: no
Page size: 612 x 792 pts (letter)
Page rot: 0
File size: 12126 bytes
Optimized: no
PDF version: 2.0
@UlrikeFischer but I can't get latex-dvips-ps2pdf to work without specifying 2.0 on the commandline for ps2pdf I thought <</CompatibilityLevel 2.0>> setdistillerparams would work but it's accepted by gs but seems to be ignored (and the helpful manual for setdistillerparams says "PostScript language programs that use these operators must not assume that any particular key is present in the dictionary returned by currentdistillerparams, or that setdistillerparams has any particular side effects."
@HaraldHanche-Olsen clean and very modern: This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020) (preloaded format=pdflatex 2020.1.19) 19 JAN 2020 11:29
@UlrikeFischer can I blame you? ..texmf-dist/tex/luatex/luaotfload/luaotfload-features.lua:252: bad argument #1 to 'stringgsub' (string expected, got boolean).
@yo' next you are going to tell me that helping users, or earning stack exchange revenue with increased user numbers are more important than hitting palindromic rep values.
@barbarabeeton luatex or xetex don't need a tex interface, you can just use the font
@UlrikeFischer because it seems less than clear to have hyperref set a default that is not used and then a system wide .cfg sets it to something else and if the user actually wants to use a .cfg to have a local configuration they ave to fight with texinputs search order to pick up the right one.
@DavidCarlisle -- But I really don't like to downvote, unless something is really egregious, rather than simply ignorant. Mostly, people on this site simply lack the proper information or training, as opposed to being hostile or vindictive.
@barbarabeeton oh you don't have to downvote, to make sure that I am on track for 555,555 all I have to do is mention emacs in answers to vim questions and someone will give the needed -2
@UlrikeFischer yes sure but that reminded me about that system wide cfg file, if it really needs to be there it should be distributed as part of hyperref, but also if it is always there no point in hyperref doing an \IfFileExists test to look for it, it may as well simply input it always.
@DavidCarlisle -- I guess I don't look for controversy either. Indeed, the last question I answered was soon closed for being opinion-based, but it's been nominated for reopening since a factual answer exists.
@barbarabeeton you see you are valuing the content of the posts more than the numeric games to be played with voting, this is setting a terrible precedent:-)
@DavidCarlisle We could set hdvips instead of hypertex as the default driver in hyperref - it is so long the de facto default driver that probably nobody will notice. Then miktex and texlive could remove the cfg.
@UlrikeFischer hmm <</CompatibilityLevel 2.0>> setdistillerparams doesn't work with distiller either, perhaps I'm putting it in the wrong place rather than it being a gs issue
@UlrikeFischer that was expected as I checked in the tlg with the pdf version not set, it would matter if we built with l3build ctan as it would refuse, but mktan script doesn't care what rubbish it zips up, so that's Ok.
@UlrikeFischer that is the only failure (after I changed the default in hyperref.dtx and deleted the texlive cfg)
@DavidCarlisle https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/pdf_creation_settings.pdf says "a number of settings cannot be modified during a job using setdistillerparams. Their values are always taken from the settings file or the default values:" and `CompatibilityLevel` is in the list.
@UlrikeFischer there are too many separate documents:-) That's fairly rubbish so the only way to make it work would be to do as xetex does and run dvips and ps2pdf via shell escape and control the commandline :(
@DavidCarlisle could be worth it. I have no idea if the "real" pdf 2.0 stuff can be done with dvips, but it would make tests easier (and perhaps also the ps2pdf scripts).
@Skillmon it's a newish feature, added so i could build the oberdiek bundle with l3build:-)
@Skillmon the one there is a longer list than needed as I simply took the existing manifest of all files. Actually you only need list the ones that go to a non-standard place, so if you are defaulting to tex/latex... you could just list the ones that go to generic
@Skillmon not really exclusion, but everything build first in a directory and if the filename matches the basename of an entry in tdslocations it is copied there, otherwise it does whetever it would have done using its default heuristics
@DavidCarlisle I've yet to fully understand how to create the bulid.lua files of a project. Maybe I'll stick to GNU make in the end, that one I at least partly understand.
@DavidCarlisle why did you include all the dtx files into the installfiles variable, I thought that one should only hold the files going into tex/.
@Skillmon l3build is usefully cross platform, and it handles tex-specific testing which would need extra support if using make. (we used to use make for latex2e tests but they didn't work on windows and needed a lot of custom sed and perl to handle the testing, but with l3build it's a lot more streamlined
@Skillmon actually it may not be needed, I had several attempts to force the existing (bizarre) oberdiek layout to get built using l3build before we gave up and added tdslocations, currently it works and since the bundle is scary enough to build anyway I'm happy to leave it as it is for now:-)
@Skillmon we need to edit and normalize and compare log files, do you do that in pure shell scripting without using perl?
@Skillmon This is exactly the sentence from your doc I referred to. I was just curious, and for the case you would change your mind I wanted to point you to this other serious bug of keycommand. Your assumptions about it are informing, thx. (BTW I could yesterday not open the chat, I had in general problems with the whole stackexchange site.)
Ehm, “other bug“ in sense of different from the keyvalbug feature.
@DavidCarlisle no, the tests of that can all be done by comparing the outcome with \ifx, so the majority of the test-part is done in LaTeX and the script only has to grep a few things.
Oh, cool, doesn't work (not even finding the incomplete build.lua:
archie@thinkarch ~/Code/LaTeX/Own_packages/expkv (git)-[master] % l3build doc
Running l3build with target "doc" for module .git
Error: Cannot find configuration build.lua
@Skillmon ah OK that's Ok for test that are expected, but we have a lot with \showbox output that caught many unexepected changes as for example luatex changed
@DavidCarlisle I just run l3build doc in the main folder of the project (in which there is a build.lua) and for reasons I don't understand it did something strange.
-- Build script for expkv
installfiles={"expkv.sty", "expkv.tex"}
typesetfiles={"*.dtx"}
-- make sure that expkv.tex ends up in the generic path
tdslocations={
"tex/generic/expkv/expkv.tex",
}
@JosephWright @UlrikeFischer @AlexG I posted a feature request to gs-devel list (doesn't show in the archives yet, probably held up for moderation as I'm not a subscriber)
@JosephWright asking if it is possible (or if not could they add) to put anything in a ps file so that ps2pdf generates the specified PDF version so \usepackage[pdfversion=2.0]{hyperref} can work for dvips as it does for pdftex, currently requires you to call ps2pdf with a commandline option to set the version
@JosephWright meanwhile you'll be pleased to know I rebuilt all the texlive sources this morning so I now have a pdftex with \pdfmajorversion (again, I think I built it at the time but didn't hang on to that version)
@UlrikeFischer better to just have ./Build as the --without-x bit is just because I can't be bothered to install exactly the right X Windows SDK, as it is only used for xfvi and the metafont preview window.
@Skillmon I think this works, you shouldn't get complicated with the TDS structure, just put a note in README.md and make the comment about it when uploading the package to CTAN. I have excluded .tex, .sty because they are generated from the .dtx file (and the CTAN maintainers don't like it, check the pkgcheck utility)
@UlrikeFischer The bitmaps in luaotfload's tests do no longer correspond to the upstream font, but nothing significant (aka. no font metrics) changed as far as I can remember. Why?
@MarcelKrüger I got lots of errors. The testsuite ran, but as soon as I tried to call the font in some external document it failed. After deleting the cache and copying the font to a local texmf it worked again, but the font doesn't appear in the logs, and windows claims it can't install the ttf.
@MarcelKrüger I'm just running the latex2e test suite with a new luatex and get a failure here tlb-callbacks-001 (40/380) and tlb-extraprimitives-001 (47/380). Do you know why? (I'm in the develop branch)
@UlrikeFischer tlb-callbacks is mostly because of the new callbacks glyph_info (introduced in reation to harfbuzz) and the replacement of page_objnum_provider by page_order_index (That's stability in the LuaTeX world...) Also there is a new provide_charproc_data callback which will probably allow for creative use of Type3 fonts at soem points, but currently it isn't actually implemented. The extraprimitives failure are because of new primitives eTeXglueshrinkorder and eTeXstretchorder.
@MarcelKrüger so more or less harmless. I think we should try to release a new luaotfload. I can try to expand the docu but I would need a few words about the multiscript ...
@UlrikeFischer Right, harmless. I agree, but I currently have a lot on my plate and don't find the time to work on the documentation. But I'll try to write down the general idea this evening.
Good evening! I have tried circuitikz with my TeXLive2019 up-to-date version (althoug I still have ` LaTeX2e <2020-02-01> pre-release-2 (development 2019-12-1 branch)` when calling pdflatex-dev and I have an error on siunitix:
@MarcelKrüger I can do the documentation (and the upload), it would be enough if I have a few more examples to understand the ideas. Simply send me some test files or so.
Have a rushed question that I'm embarassed to ask, but I'm on a tight deadline: Using the Caption package how do I set the figure numbering to move from 1,2,3 to S1,S2,S3, etc for the whole document?
I mean, it doesn't have to use caption, but would hopefully not break it, though if it does, I can probably just deep six caption now that I think about it
@UlrikeFischer those two almost always fail after a luatex update, if anything is added or removed at the primitive level. Often it's only way we find out about undocumented changes:-)