@JosephWright (@egreg) did we change \font_suppress_not_found_error: some code that I say I got from @egreg was reported as not working this morning, I just changed to set \suppressfontnotfounderror directly. The \font_suppress_not_found_error: is in l3trial/xfont/l3font but did it used to work as posted?
This works in both xelatex and lualatex and sets the document in Pagella for me:
\documentclass[11 pt, a4paper]{article}
\usepackage[T1]{fontenc}
\usepackage{fontspec}
\ExplSyntaxOn
\NewDocumentCommand{\onlywarniffontnotfound}{}
{
\suppressfontnotfounderror = \c_one
%\font_suppress_not_fou...
@JosephWright odd thing is OP reported it working at the time and I thought I had tested egreg's addition but I couldn't see any relevant changes in the log. Oh well it works now:-)
Is there a way to set different fonts to different scripts so that my document can contain mixed Japanese, English, Czech, without font switching? XeLaTeX or LuaLaTeX.
@wilx In XeTeX you can use interchartoks, in LuaTeX it is doable from Lua, but there's a lot of concern about the idea: you can't get hyphenation right that way, for example. For typesetting you do need language mark-up.
@wilx in particular while you can probably reliably switch between say english and japanese, it's much harder to switch between english and french so while the fonts may be OK, hyphenation (which browsers, by default, don't do) will all be wrong
@JosephWright @DavidCarlisle please, (English question) do you have money in your account, on your account or at your account? I suppose it's in but I'm never sure...
@yo' in (also on but that means something different)
@yo' I remember a long time ago when I was a phd student a german visitor asked a similar question, but whether money was in or on a bank, I replied that of course it was in, because a bank was a building that you walked in to, but he correctly pointed out that we stole the german word for bench/counter without understanding it, and you put money on a counter. I decided it was best not to know too many foreign languages, just leads to confusion:-)
@DavidCarlisle Of course the German visitor was wrong: the word bank in the modern sense he was referring to comes from Italian; we stole the word from German.
@DavidCarlisle Gday. I have more issues with longtable. The problem is that hacking that line into the output routine leads to problems with a never converging Table widths have changed cycle upon large tables.
I can force widths of the columns in which case I get loads of overfull and underful boxes, which would be acceptable for the guy I am helping. However the last column doesn't let me specify width and orientation. This breaks in \LT@hline for some reason
Hmm it appears that it doesn't recognize the last column specifier. If I remove the \hlines then it complains about extra alignment tabs
@Max sorry no time to debug that but the chunk logic looks suspicious you are injecting a new chunk but I'm not sure that the chunk counter is reliably set (and LT needs to know which chunk the widest entry in each column is from, so it can detect changes.
@David @Joseph I'm afraid you'll start to hate me for my English questions, but is 740-meter-long train the proper equivalent of 740\,m long train (it's for article titles where I prefer to omit SI shorthands for units)
@DavidCarlisle ok thanks :) I'll just have to decide on the re-er business (basically, look for signs of British vs American English preference elsewhere in the article, which is going to be tough given the authors are Czech :-D )
@yo' The dictionary says it's written ad hoc, adjective or adverb.
@DavidCarlisle Yes: we use banco for the counter and banca for the institution or building. Although some banks are called Banco for historical reasons.
Let's say there's an article or a book titled solutions for ad hoc problems in foobar. How is ad hoc title-cased? As a preposition ad with a pronoun hoc or as an adjective? I mean, which of these four is correct?
Solutions for Ad Hoc Problems in Foobar
Solutions for Ad hoc Problems in Foobar
So...
@DavidCarlisle I'll see what the true English speakers think :-)
@DavidCarlisle also, this seems to be the "let's not capitalize short words" track; hoc is clearly a pronoun an shall be capitalized the same way it is
@yo' It's only clearly a pronoun if you choose to think of it that way (which few English speakers would) "ad hoc" is treated as an opaque latin word that happens to have a space in the middle for historical reasons.
@yo' but it's no longer treated as a foreign word that you'd write in italics, so I think going back to the original translation to explain the usage is also wrong, "ad hoc" is just being used as an adjective for problem in your example.
@yo' And this book, in which all the paper titles have 'ad hoc' in them, took the same route in its table of contents: books.google.com/…
@yo' I don't have a strong intuition on this, but I think since it's treated as an adjective, then it makes sense to capitalize it. So then the options are Ad Hoc or Ad hoc. And the links just seem to support the idea that others who may have thought about it went for Ad Hoc
@DavidCarlisle Thank you. I wonder if there is a market for a module that would define some of these Unicode fancy characters to something useful like the above. :)
@wilx you usually need to do the same with soft hyphen to \let it equal to \- arguably the format ought to do these things but it's a bit hard to gradually introduce luatex support, the format doesn't even default to a unicode font with luatex and xetex
@JosephWright yes also came up in discussion with someone the other day switching from xetex to luatex (as a trial) complained about lots of hyphens appearing, turned out the source has "unknown" soft hyphens but xetex doesn't show them (but i guess they are characters so in fact break hyphenation) whereas luatex shows them as visible hyphens (which looks worse, but actually gives better indication of what's happened) having the format make it active by default would avoid a lot of confusion....
@wilx but you can ignore the actual line breaking algorithm itself (just defer to tex) but the tables list for example that zero width space should allow breaking, but zero width space non joiner should not. So the tables of character properties can be mapped easily to tex definitions of the form above
@PauloCereda I had ice on my car window this morning
@DavidCarlisle I guess I could add to the Unicode data: despite the font business, the format is setting up a lot of things on a 'expect Unicode' basis
@DavidCarlisle it is good that format doesn't default to Unicode fonts, as users can use alternative fontloader with LuaTeX (Harfbuzz), or suppress them completely (tex4ht).
@michal.h21 using harfbuzz by default would be even better:-), but the uses that you mention are specialist ones that could easily be provided with some switch to get teh right behaviour, but the current situation is that 99% of people who try (lua)(la)tex for the first time do so using 8bit fonts and so completely broken hyphenation as the format as only loaded unicode tables (which is fixable in luatex, but not currently fixed in the default setup)
@michal.h21 did you see harfbuzz is getting math support?
@DavidCarlisle I only saw some tweets, I am not really following it at the moment. I am also curious about variable fonts, Hans seems to be not too much excited :)
@DavidCarlisle I think I've done some tests with hyphenation for 8-bit fonts. but of course it would be easier for casual users to just use Fontspec by default in the background
@michal.h21 luatex you can of course load the 8bit patterns later but xetex you can not and it is currently built with unicode patterns so arguably defaulting to 8 (actually 7) bit fonts is just wrong.
@michal.h21 I don't see how that makes much difference: surely you end up simply overwriting stuff anyway
@michal.h21 There's currently no release HarfBuzz/LuaTeX combination, is there, so this is very much a developer thing (as @DavidCarlisle says, if we could have HarfBuzz + LuaTeX this would be excellent)
@michal.h21 BTW, any move to non-TFM fonts would of course mean not loading them as part of the format (you can't build OTF files in)
@DavidCarlisle -- actually, i agree partially. what i insist on is consistency. if an author shows a tendency or preference for one or the other (uk or us), i'll settle on that. if there's a mixture, and the author is clearly european, i'll probably settle on uk, but if the author is from the western hemisphere, i'm more likely to settle on us. or -- when in serious doubt, ask; doesn't usually take that long, and authors generally appreciate that you care.
@PauloCereda -- cars do have thermometers, and some even have specialized ones that can determine whether the road surface ahead is at a low enough temperature to be possibly ice-glazed, hence a potential danger. but even better, our car has a radio "weather band" that tunes into the national weather service, so that we can almost always (when we're at home, and mount washington is on line) learn what the weather is on mount washington. almost always makes us feel better about the local weather.
@PauloCereda -- and it isn't even a new car (2001 model year). but saabs come (originally) from an area where it's advantageous to know when the road surface is freezing, but not apparent by just looking at it.
@AlanMunn -- yes, you are definitely a challenge. if i know you're canadian, and i have a question, i will ask. and i have easy access to a former tugboat proceedings and associate editor who is canadian, and is quite happy to set me straight when i goof. (maybe i've just been lucky that the mixture you refer too hasn't happened very often in practice. i suppose now you'll want to put that to the test ...)
@barbarabeeton Mainly joking, although I'm sure it must be tricky. Also, I suspect that since Canadians are so bombarded with US English as well, they may be more variable on their spellings. Personally it's one of the things that I try to hang on to, despite being in the US. So my students have dissertation defences. ('c' vs. 's' in nouns/verbs is another difference).
@AlanMunn -- well, i know a couple of canadian residents who were raised in the u.s., and they tend to hang onto u.s. spelling. i think you're the only native canadian i know at the moment who's active with tex and living/working in the u.s.; pierre mackay was canadian by upbringing, but he pretty much adopted u.s. usage. but either situation is easier to handle than trying to make sense of something written by someone whose native language is not indo-european. that can be a real challenge!
@DavidCarlisle Do you mean for consistency? I added the condition when I noticed because I somehow thought the existing definition might somehow be better. :)