@JosephWright , @DavidCarlisle -- i thought i saw mention of a latexnews, later than 26, under construction. was i hallucinating, or is that actually happening? if true, when is it likely to be (close to) ready?
@barbarabeeton I checked in ltnews 27 yesterday, although it won't win any literary prizes yet. notional date is currently first of may but that may change basically "just before tl2017"
@DavidCarlisle -- okay, thanks. i'll take a look, but we won't try to get it into the in-process tugboat issue. (i like that "yet" in your description ...) will ask again when the next issue (proceedings of "bachotug") is imminent.
@egreg on verbatim hyphenchar I was going to use \language\no@hyphenation instead (and same in \verb) but then we'd have to reset the main document language in page headers without clashing with babel and every page header setup, so I'm thinking of just saving hyphenchar and resetting at end, which would still mean if you have a verbatim using \normalfont then page headings using the same font will have hyphenation disabled, but the chance that's actually an issue seems small?
@UlrikeFischer be interested in your thoughts as well ^^
@DavidCarlisle I doubt that hyphenation in page headers matter much. People who put a novel there could always add sensible language switches (and should as the main document could have another language active at the page break anyway, even if no verbatim is involved).
@UlrikeFischer so you'd use \language anyway? rather than set and reset hyphenchar? using \language in \verb makes lots of diffs in our test suite with extra language nodes, it may be that only affects us, but it makes me a bit nervous about it
@DavidCarlisle Imho changing the language sounds more logical, and thinking about it changing it to a configurable language perhaps even more -- then people could define a "verbatim" language which allows breaks e.g. at underscores. Regarding the language nodes: you could also correct the currently definitions with hyphenchar and define a new variant with languages and some command to activate it. Then one could test a bit and check the differences.
@JosephWright well there's no space changes just + ....\setlanguage1 (hyphenmin 2,3) so checking isn't too bad, but usual danger of extra whatsit nodes is they catch you out when doing weird unboxing tricks, like the way the tex-xet change in xetex broke breqn until it reverted to tex--xet. I couldn't actually think of a case where teh \language node is a problem though.
On the Internet there are no true type fonts mtpro2. I must pay to obtain. Yes David of course.
After writing in LaTeX in relation to my question, with adobe illustrator I can fit more easily insert images and colored rectangles and more. But they need the true type fonts. Of times I found them but for mtpro2 lite version not found them.tex.stackexchange.com/questions/355320/…
I hope you have a little more information about. Greetings and good work at all.
@Sebastiano shrug, there are plenty of times-like clones these days. If mtpro has what you need fine, but if not I wouldn't worry about it just use tex gyre or stix or newtxmath.
@Sebastiano I have some doubt that the complete set of mtpro2 contains true types. There is no indication on the pctex site, before you pay you should better ask.
@JosephWright yes well I think it's a real bug even in pdftex, so I should change something. (but currently setting hyphenchar seems safer as we delegate so much (all) language support to babel)
@PauloCereda How did I manage to disable the chat "ping" notification? The sound is there, and the setting is on "when mentioned" but it doesn't ping ;-(
@egreg -- on the topic of updating "old" questions, i've been slowly going through and trying to fix ones where the double backslash for line endings was clobbered. (trying to limit to 3 or so a day.) i've found one that i'm not sure how to fix, but since you were the last to edit the question, could you please take a look? tex.stackexchange.com/q/271916 and thanks.
here's another that looks like it's been clobbered in a different way: tex.stackexchange.com/q/117165 -- all & in the example in the question are rendered as \&, which can't possibly have resulted in the image shown. is this another example of "behind the scenes" unreported tinkering?
@yo' -- those are simply compromised instances of \\ . since there's a problem with both question and answer, i have refrained from changing anything until the question about the \& is answered, so all can be fixed at once, avoiding a multiple push to the front page. sigh.
@yo' -- oh, i agree entirely, but i'd really rather avoid the possibility of someone cutting and pasting an erroneous example, then wondering why it doesn't work. (i get enough problems from authors here that come from such cluelessness.)
@egreg -- but it doesn't agree with the image; the coding there now would leave a blank row in the middle. i think the two backslashes in that "row" should have been merged, but that's a different kind of problem than the one discussed on meta.
@DavidCarlisle It's a, I think well-known and somewhat mocked, feature of Welsh that the ordering of sentences is rather more flexible than in English. 'So fickle you are' rather than 'you are so fickle'. Only the second is grammatical in English, but both are grammatical in Welsh. At least, not quite, but almost. ('So fickle are you' would be grammatical.) The meaning is slightly different in terms of emphasis.
@DavidCarlisle 'So fickle are you', 'you are so fickle', 'are you so fickle' ... all kind of mean the same but also kind of mean slightly different things.
@cfr no I wasn't alluding to welsh:-) are you so fickle would be a question, I just used the inverted order in "so fickle are you" to give an old-time idiomatic (or one might now say yoda-ish) slant to it:-)
@DavidCarlisle So I figured from your earlier reply. 'Are you so fickle` is not intended as a question here. It is just 'he standard word order for an ordinary statement in Welsh. 'Are you so fickle?` gets a question mark ;). (More formally, it drops the prefix-thingy, whose grammatical name I forget.)
@JosephWright I asked Michael Sharpe. It is quite probable that he ran into the resolved bug below and only thought etoolbox was the problem. He will change the packages as the problem no longer exists. tex.stackexchange.com/questions/237188/corrupted-nfss-tables
tlb-verb-003 passes here (now) so if everything else passes will check something in...
@JosephWright sometimes I curse \IncludeInRelease can only update whole macros when I end up changing inconsequential macros like \@outputpage and \document
@JosephWright see Akira's msg? Confirms what I feared that harfbuzz experiments will be restricted to -shell-escape :( I suppose it's Ok while they are just experiments...
@JosephWright Not sure if I mentioned but I did some off list experiments with Luigi and Hans and almost got ffi half working with my cygwin build. That is I got some simple hello world C function to work but couldn't get their normal examples to run as it's a matter of picking through the minefield of choosing compatible native windows and/or cygwin dll. It's hard enough at best of times but as I didn't really understand what FFI was doing I gave up, and hoped it will just work by TL2017