@DavidCarlisle One more log change question on the LuaTeX list: other than those three, I think everything else can be normalised or arises in cases that use a .luatex.tlg anyway (so have to be updated as the \discretionary changes aren't normalised in those)
@DavidCarlisle I guess I could try to either normalise out \discretionary after a -` line generally or 'add back in' for LuaTeX: not sure this is a 'good idea'
@JosephWright if you are down to a reasonable number of luatex.tlg I'd say stop, if the normalisation gets too inventive then likely to generate false results or be harder to debug the results later. It's a shame as you can I think reliably convert the luatex logging of a discretionary to tex format but I don't think you can reliably know when they will display unused discretionaries.
@DavidCarlisle Of the above, one is I think a new callback, one is the hyphenation business, one is the zero belowdisplayskip and the rest are the digit business
@DavidCarlisle I'll wait to see what I get back on the LuaTeX list
Since you gave no clue of what format, font you wanted, here is something for you to start with:
The \employee command scales the name to cover the whole text width. To go on adding more names just follow the lead. Font choosing is of your picking, there is the nice Latex Font Catalogue or you c...
@Johannes_B, don't be so harsh on the guy... He's only lazy to research, I gave him something to start with.
@UlrikeFischer thanks will test : @JosephWright Hans' option (3) in the mail Ulrike links to would also explain the hyphenation test failure if he's switched that (again)
@ulrike oh it's reversed! You said there that it breaks after the first and not the rest, now it only doesn't break after the first
@DavidCarlisle and it is not some hyphenmin side effect. 99999999-99999999-99999999-99999999 behaves similar (I also tried in context where I have 1.0.1)
Although arguably in other cases (for both plain and latex) we've opted not to tweak the format for compatibility (eg name changes) and just document the incompatibility and make the test suite cope..
@DavidCarlisle Yes, not trivial to decide what is best here
@DavidCarlisle Also reminds me we should probably do something about latex.ltx and e-TeX (and remove all the TeX2, etc., stuff)
@DavidCarlisle This is though a setting that the user can decide to alter in their document: I guess the question is whether we alter the 'out of the box' value (we do after all for e.g. Unicode code point set up)
@JosephWright but obviously not for fonts to match:-) apart from compatibility it's not obviously a bad thing that long words abutting an hbox hyphenate. I'd be tempted to leave this (like leaving first word of a para hyphenating)
@FaheemMitha The new years resolution is to get a tikz gold badge by answering tikz question with tex primitives, picture mode, or if really pushed pstricks, doing quite well so far this year.
@JosephWright don't think so, at least not the ones that came up before (looking at the names) I'd guess it's to do with subscripts rather than atopwithdelims worth adding a
@DavidCarlisle me too. Imho compability doesn't work anyway (even if luatex stays put for a while ...). But some document which demonstrates how hyphenation behaves and can be altered would be usefull. Btw: there is a question on the context list "Changes in hyphenations with 2016-10-12 beta".
Anyone know which colormodel xcolor uses by default under pdflatex? I need to find some rgb colors that work when the printing office convert our images to CMYK (I cannot use CMYK as the colormodel as I suspect that Tikz still have a tendency to force RGB in some circumstances). If I explicitly give the rgb option to xcolor the colors changes (as seen in evince) compared to without the rgb option.
@daleif tikz has no preference AFAIK, but you shall stick to user-defined colors as the predefined colors need not to convert properly (but I may be wrong).
@yo' at least earlier for some of the shadings, colors was forcefully converted into rgb even if you used CMYK, so and edge mighh end up in one color, and the shading would not match.
@DavidCarlisle then what is the default when we have not specified anything? In color proofs (test) I got bach all my blue was purple.
@DavidCarlisle Very much carefully, I believe if not so careful one might see himself at manual's very last page and still unaware of such file extension...
@yo' yes. This color model stuff is a bunch of trouble. At the moment there are some of our images they cannot process and so far they haven't told us exactly which, just pointed to some pages (which contains more than one image).
As for the colors, I'll just prepare a bunch of color series and have them convert and print it in their end, then we'll choose the colors that match our vision the best
@daleif that's a common thing (remember I typeset a journal, working with external source images all the time. It knows to be painful, and ImageMagick is my friend.)
___________________________________
/ David is using a broken operating \
\ system, if we can call it an OS /
-----------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||