« first day (4243 days earlier)      last day (706 days later) » 

3:04 AM
Hi, do you guys have an opinion on github.com/AnMnv/eBook?
 
 
2 hours later…
4:42 AM
@Dr.ManuelKuehner The zebra code not in a verbatim font make me feel sick, sorry
 
 
2 hours later…
7:04 AM
@barbarabeeton I keep thinking about active $ and whether I can pull that off safely ... I think I'm the 'team member most likely to be mad enough to try this'
 
7:27 AM
@CarLaTeX eeek
 
7:56 AM
@DavidCarlisle I see CTAN have processed last night's update: textcase is no more ...
 
@JosephWright vvvv
> Notes to CTAN maintainers:
> ----------------------------------------------------------------------
> Only took a quarter of a century but latex finally caught up with this package:-)
      ;-)
> ----------------------------------------------------------------------
8
 
@DavidCarlisle :)
@DavidCarlisle I hope they liked that - Petra?
 
@Dr.ManuelKuehner hard to get past that blurry green latex
 
@DavidCarlisle I might include that in my TUG talk - I was going to do one on case changing ...
@DavidCarlisle Yup - it's horrible
 
@JosephWright Oh I guess you mean the comment to Petra, I thought for a moment you meant the fuzzy logo
 
8:02 AM
@DavidCarlisle Yes, that one
 
yo'
8:18 AM
I wonder please, is the reason why sagetex isn't in TeX Live that it's not self-contained, or are there other issues like licenses etc.?
 
8:29 AM
@yo' licence is OK (GPL2) it may be that sage isn't available on all texlive platforms so they didn't add sagtex, I don't know, you could ask on texlive list..
 
yo'
@DavidCarlisle ok, thanks :-)
 
@JosephWright that's Petra's smiley quoting my upload form
 
@DavidCarlisle :)
First of my TU2022 abstracts sent
 
@UlrikeFischer we fixed T2... and LY1 encodings but puenc.def has: \DeclareTextCommand{\guillemotleft}{PU}{\80\253}% U+00AB
 
@DavidCarlisle oh. So another hyperref update. What should it do? Simply define \DeclareTextCommand{\guillemetleft}{PU}{\80\253} too?
 
8:39 AM
@UlrikeFischer yes in ly1 and cyrillic I simply copied the lines and added an e version (for left and right)
 
@DavidCarlisle I guess \DeclareTextCommand{\textflqq}{PD1}{\guillemotleft}% should then be redefined too?
 
@UlrikeFischer grr yes (or delete all legacy encodings and force Unicode everywhere....)
 
@JosephWright ooh
 
@DavidCarlisle I'm forcing unicode more or less ;-). I made the changes.
 
@PauloCereda «breakfast»
 
8:54 AM
@DavidCarlisle «oh no»
 
@Dr.ManuelKuehner They wrote Latex and use normal style for verbatim content. It's quite difficult to take things seriously. :)
5
 
@DavidCarlisle is it expected that I get an error here? Or is something not up-to-date:
\documentclass{article}
\begin{document}
\guillemetleft
\end{document}
 
@PauloCereda ohh :)
 
@DavidCarlisle ok, seems to error for the o too.
 
9:10 AM
@UlrikeFischer \textgui...
 
@DavidCarlisle ? I see not \textgui.. commands.
@DavidCarlisle babel provides a definition for OT1. I wonder if that should go into ot1 directly?
\ProvideTextCommand{\guillemotleft}{OT1}{%
  \ifmmode
    \ll
  \else
    \save@sf@q{\nobreak
      \raise.2ex\hbox{$\scriptscriptstyle\ll$}\bbl@allowhyphens}%
  \fi}
 
@UlrikeFischer Yes
@UlrikeFischer Add for PL1 I think
 
9:25 AM
\documentclass{article}
\usepackage[T1]{fontenc}
\begin{document}
\textguillemotleft

\textguillemetleft
\end{document}
@UlrikeFischer ^^ does not work either, I think that is the intnded command name? Something wrong somwhere...
@UlrikeFischer ignore me
 
@Dr.ManuelKuehner everything is wrong with the first code block on page 5!
 
@DavidCarlisle ;-)
 
@UlrikeFischer work calls...
 
\begin{equation∗}\label{eq1}
\resizebox{.4\textwidth}{!}{ % change .4 to 0.5...
$\dot{\rho}=\dfrac{x^3}{45a^9-23b}$}
\end{equation∗}
 
@JosephWright there is actually a rather large bunch of ot1 definitions in babel. I will sent a mail to the team list.
 
9:30 AM
@UlrikeFischer Cool
 
@Skillmon hi mr. rabbit! Miss you! <3
 
@DavidCarlisle Have fun
 
@JosephWright Englishmen having fun? Hmmmmm
 
@PauloCereda I Mr. Duck! Miss you, too! And thanks for the carrot! Here's one for you as well: <3
 
@Skillmon yaaaaay
 
9:33 AM
Case changing: LaTeX reaches Unicode-land

In 2015, I talked about my work exploring Unicode-land, particularly how to carry out case changing in XeTeX and LuaTeX 'properly'. Since then, expl3 has become a part of the LaTeX kernel, and LaTeX has adopted UTF-8 as the standard input encoding. The time has therefore become ripe to 'open up' Unicode-land to allow \MakeUppercase and \MakeLowercase to roam free.

In this talk, I'll remind us of what Unicode tells us about case changing, where the challenges are and how we've approached them in expl3. I'll then show how this has combined with some
@DavidCarlisle, @UlrikeFischer (@PauloCereda) ^^^ Like it?
@PauloCereda Unicode-land is back
 
@JosephWright oh no, the 21st century
@JosephWright yaaaay
@JosephWright you better use a cool theme and opening image. AND PLEASE STOP USING 4:3 :)
We ducks are very good at 21st century things
 
@PauloCereda I was thinking of the one you did for me for Darmstadt
 
@JosephWright ooh
 
@JosephWright Maybe we could add some new elements to it
 
9:35 AM
@PauloCereda duck emojis?
 
@UlrikeFischer ooh :) I was actually thinking of you in the middle of the battlefield slaying dragons :)
 
@PauloCereda Oh, what is wrong with 4:3? :=|
 
@mickep they are not 16:9 :)
 
@PauloCereda @samcarter fixed bemear so I can use whatever aspect ratio makes sense
 
@mickep you can add more ducks in 16:9 than 4:3 <3
 
9:38 AM
@PauloCereda :)
 
@JosephWright oh no, beamer fixes :)
 
@PauloCereda Even more in 16:12. :P
 
@mickep ooh
 
@PauloCereda My laptop is 16:10
 
@PauloCereda oh (4:3)²?
 
9:45 AM
@JosephWright ooh
@Skillmon OH MY
 
@JosephWright ... and then one prepares a talk for dante with a short video from the 1970ies of some English comedy bloke and suddenly one uses the very innovative 4:3 again :P
 
10:09 AM
@DavidCarlisle did you see the texhax list? we broke color in eplain ;-(
 
10:33 AM
@PauloCereda powerpoint
@UlrikeFischer No Just got off my video call
 
@DavidCarlisle I just suggested to define \mathcolor before loading the style.
 
@UlrikeFischer I could add to miniltx
 
@DavidCarlisle that is probably the best.
 
@UlrikeFischer oh but does eplain use miniltx or its own pckage loader, let me check...
 
@DavidCarlisle it loads it.
@DavidCarlisle at least I see it in the log.
 
10:37 AM
@UlrikeFischer yes I'll fix there
 
10:50 AM
\ifx\mathcolor\@undefined
  % simplified version of \mathcolor
  \protected\def\mathcolor{\begingroup\@ifnextchar[\mlx@mathcolora\mlx@mathcolorb}
  \long\def\mlx@mathcolora[#1]#2#3{\color[#1]{#2}#3\endgroup}
  \long\def\mlx@mathcolorb#1#2{\color{#1}#2\endgroup}
\fi
@UlrikeFischer adding ^^ to the end of miniltx ?
 
@DavidCarlisle to basically it does the same a \textcolor? sounds fine.
 
@UlrikeFischer but with \begingroup not {} which is main advantage of \mathcolor, but I skip the lookahead for subscripts
 
@DavidCarlisle oh
DPC writing bug fixes... what's going on in the world nowadays
 
@PauloCereda not a bug fix, implementing a feature request
 
@DavidCarlisle sounds like a bug to me :P
 
11:05 AM
@Skillmon miniltx.ltx can't have a bug, it has my name at the top
 
@DavidCarlisle Out of curiosity, what is miniltx.ltx? Some file that is loaded "early"?
 
@mickep emulation of latex for people who want to say they use plain tex not latex but want to use latex color, graphics, picture mode, etc. totally brilliantly engineered package, and not at all the result of half an hour's playing adding random definitions unil \input graphicx.sty \includegraphics{example-image}\bye ran without error in 1993.
 
@DavidCarlisle Hehe, for people who wants to eat the cake and keep it.
 
11:57 AM
@yo' 70 to go....
 
yo'
@DavidCarlisle oh :D
 
 
2 hours later…
1:32 PM
@MarcelKrüger I got lost about state of the opacity/spot color implementation. I see that you changed some names but when I adapt the lua to use them I get invalid transparency setting.
 
1:54 PM
@UlrikeFischer really bad idea to test stuff:
! Undefined control sequence.
<argument> \@ehd
 
@DavidCarlisle what did you test?
 
@UlrikeFischer hmm I don't know, not reproducible, let me see.... (it was a bad use of \mathcolor, but....)
@UlrikeFischer I think this never worked
\input eplain

\beginpackages

\usepackage{color}
\endpackages
\long\def\red#1{{\color{blub}#1}}
\red{ab}


\bye
blub so must be your fault
 
@DavidCarlisle blub is dangerous stuff, not to be used by everyone.
 
I'll do same as @ehc: \ifx\@ehd\@undefined\def\@ehd{}\fi
 
yet another overleaf user ignoring compilation errors.....
 
2:19 PM
@UlrikeFischer ctan.org/incoming
 
@DavidCarlisle not miniltx but graphic-pln?
 
@UlrikeFischer that is where it lives
 
@DavidCarlisle ah
 
@daleif Wait, what? Should we care for them? :P
 
@DavidCarlisle uff
 
I need a label
4
 
2:48 PM
@mickep 78 errors on overleaf ...
 
@UlrikeFischer IIRC I renamed some stuff but adapted luaotfload-l3color to match, but also added the l3opacity stuff to that file. (Treating it as a dumping ground for "stuff that belongs elsewhere") So currently it should only be loaded if DocumentMetadata is active, but then it should work without further code.
 
@yo' why does the error markers left to the source code disappear as soon as one starts fixing the errors? That's rather annoying on a long document with many errors next to each other
 
@MarcelKrüger well I don't get it too work. If I use this with luaotfload-dev and fontspec from ctan (so without the patch) I have no error but also no opacity.
\DocumentMetadata{uncompress}
%\directlua{require("lua-opacity")}
\documentclass{article}
\usepackage{xcolor}
\usepackage{fontspec}
\setsansfont{Iwona}[Color=00FF0066]
\begin{document}
 TEXT \sffamily TEXT

\end{document}
In the lua-opacity I have exchanged the function names (so it uses luaotfload.set_transparent_colorstack. But when I activate it I get ! Invalid transparency value..
 
yo'
@daleif that's a good question. Are you Overleaf Beta?
 
@yo' I think it seems normal (I don't use OL that much, was just looking at a tex.SE users document)
 
3:00 PM
@MarcelKrüger and with the fontspec patch the error doesn't go away but additionally Color=red gives luaotfload | color : Invalid color part in color expression "red".
 
Sounds bad... I'll look into it when I'm back at my system.
 
@MarcelKrüger thanks ;-)
 
yo'
@daleif ah right. We're actually just discussing this, and it's all very tricky, because if you correct the error, you don't need to see the error message anymore, and it's hard to realize when to hide the error from the UI.
(btw, you can always access it in the "Logs and output files"
 
@JosephWright -- Eek! That is one way to approach it, but it could affect a lot of packages that would have to be tested. Maybe start by making a list of them. (I suspect it may be taking a howitzer to exterminate a cockroach.)
 
@daleif @yo' it might (depending how that's implemented) be hard to track which lines to flag once the file is edited and line numbers potentially change.
@JosephWright active & would be even more useful
 
3:22 PM
@Skillmon Oh, thx, good to know!
@PauloCereda Haha, understood :)
@DavidCarlisle I had a similar feeling :)
@CarLaTeX :)
 
@JosephWright -- Eek! That is one way to approach it, but it could affect a lot of packages that would have to be tested. Maybe start by making a list of them. (I suspect it may be taking a howitzer to exterminate a cockroach.)
 
4:05 PM
@JosephWright I would definitely be in favor of active $. Maybe start by making it active at \begin{document} to avoid breaking packages, then move it to the beginning later?
 
@DavidCarlisle active <every-strange-character>?
 
@MarcelKrüger Yes, that was my plan
@Skillmon Yup
 
4:32 PM
@DavidCarlisle -- Ah, yes. The poor maligned guillemots thank you. As do I.
 
5:05 PM
Hi
I have a small question regarding using \fontsize{}{} in the anyfontsize package. There how to choose values to be inside the second bracket in \fontsize{}{}, if I need to have text similar to "font size =16, double spacing in MS word"?
Times New roman font
 
yo'
@DavidCarlisle that's only a part of the issue.
 
5:29 PM
@DavidCarlisle I imagine much harder is the problem of detecting follow-up errors.
 
5:40 PM
@Dr.ManuelKuehner it was meant as: I'd not trust this in any way, putting \label in equation* is pretty pointless, resizing maths with \resizebox is just plain evil, and then putting spurious spaces in the \resizebox adds the last missing cherry on top of it.
 
@BuddhiniAngelika I would suggest using the single space line distance in \fontsize, and then use a package (like setspace) to change the line spacing.
 
Thank you @Rmano then can I get the font size 16 without change?
It should be \fontsize{16}{1} right?
 
@BuddhiniAngelika ` \fontsize` isn't from a package, it is a core latex command. about 20% more than the first argument
@BuddhiniAngelika no that would be 16pt text on lines 1pt apart, which can not work
 
I don't understand " about 20% more than the first argument" @DavidCarlisle does that mean 16*0.2 ?
 
@BuddhiniAngelika the default is \fontsize{10}{12} so 10pt text on 12pt baseline space
 
5:49 PM
Does \renewcommand{\baselinestretch}{2} make the lines double spaced same as in MS Word? I've put that command at the begining
 
@BuddhiniAngelika no, use smaller amount,or better usesetspacepackage and its doublespace command
 
Base line is the lower line on which the Letters stand. What is the baseline stretch exactly
 
@daleif -- Not an overleaf user, but this sounds like a file that had a real error, was "processed to completion", then fixing the first error makes many (possibly all!) of the subsequent errors go away because they were only caused by the first error. (Which is why I always run from the command line, and make interactive corrections as I go.)
 
@BuddhiniAngelika the space specified by \fontsize second argument is muliplied by that
 
I'm sorry @DavidCarlisle but I'm still bit confused. Multiplied by what exactly?
Do you mean that when we mention {12} in \fontsize{10}{12} and if we have \baselinestretch{2}, the total space beween two lines is 12*2 pt?
 
5:55 PM
@BuddhiniAngelika after \fontsize{10}{12} the font size is 10pt and the baseline space is 12*\baselinstretch
@BuddhiniAngelika yes
 
So to have double spacing, which we use for thesis and formal reports, we have to put \fontsize{10}{1} and baselinestretch{2}?
 
@BuddhiniAngelika no, the second argument of \fontsize should always be larger than the first.
 
@BuddhiniAngelika no. no normal document should ever need \fontsize or \baselinestretch commands. Just use named sizes like \normalsize and \large and for double spacing use the setspace package.
@BuddhiniAngelika as I just said above \fontsize{10}{1}is 10pt text on lines 1pt apart which makes no sense.
 
@DavidCarlisle you have a spacing problem too ;-)
 
6:02 PM
@UlrikeFischer I complained but rather than fix it they sent me a wireless fullsize keyboard, but my laptop is on my lap....
 
@UlrikeFischer Your example should work if you either don't use \DocumentMetadata or replace %\directlua{require("lua-opacity")} with \directlua{require"luaotfload-l3color"}. Depending on whether you have the fontspec patch you either get arbitrary or only RGB colors.
 
@barbarabeeton this doc has a massive amount of real compilation errors and really bad habits
 
Thank you @DavidCarlisle I tried using \doublespacing at the beginning of the document
It worked.
But I need to get some text of different font size
As I mentioned earlier.
But I can't understand what to put in the second argument of \fontsize to maintain the double spacing as it is?
 
@BuddhiniAngelika \fontsize{16}{19.2} (20% more than the type size), but it will work only for the basic font. Much better to use a package like ` \usepackage{newtxtext}` (which set Times as the base font), and then at the start you go \Large\doublespacing.
 
@l3team Is it too late to point to less-than-ideal formulations in ltnews35?
 
6:16 PM
@Skillmon blame @barbarabeeton
@BuddhiniAngelika sorry too many quesions, make a real example and post a question on the question site. But no normal document should ever need \fontsize
 
Look for example tex.stackexchange.com/a/317559/38080 @BuddhiniAngelika
 
@DavidCarlisle one of your many typos I guess. That should've been @UlrikeFischer shouldn't it?
 
@Skillmon I believe @barbarabeeton did proof read it for tugboat
 
\documentclass{article}
\usepackage[T1]{fontenc}
\usepackage{newtxmath,newtxtext}
\usepackage{setspace}
\usepackage{lipsum} % just to generate dummy text
\begin{document}
\Large\doublespace
\lipsum
\end{document}
 
@Rmano why making everything \Large? I'd prefer extsizes or KOMA-classes or something like that.
 
6:18 PM
@BuddhiniAngelika ^^^^^
 
@Skillmon did you want to report bad tex or bad english?
 
Thank you @DavidCarlisle and @Rmano its not exactly normal doc. I need to use font sizes 24, 18,16, 14 where \documentclass[12pt,fleqn,usenames,dvipsnames]{report} is used.
 
@Skillmon Yes, better, but in a pinch...
 
@DavidCarlisle so it's @UlrikeFischer's fault for not proofreading herself?
 
I saw that font sizes are different under different definitions of \documentclass[12] , \documentclass[11] etc.
 
6:20 PM
@BuddhiniAngelika So, please, preapre a minimun document similar to the one I used and post it as a question on the main site.
 
@Skillmon the important point is that it is not my fault
 
That's why I'm not using commands like \Large etc at once
 
@DavidCarlisle the subsection about \IfBlankTF reads as if you could use it to test for a value-less key, but I guess it should've been \IfNoValueTF for that.
 
@MarcelKrüger uff. This seems to work ok:
\DocumentMetadata{uncompress}
\directlua{require"luaotfload-l3color.lua"}
\documentclass{article}
\usepackage{xcolor}
\usepackage{fontspec}
\setmainfont{Iwona}[Color=red]
\setsansfont{Iwona}[Color=00FF0066]

\ExplSyntaxOn
 \color_model_new:nnn { sepblue } { Separation }
    {
      name = PANTONE~3005~U ,
      alternative-model = cmyk ,
      alternative-values = {1, 0.56, 0,0},
    }
  \color_set:nnn{blue}{sepblue}{1}
\ExplSyntaxOff
\usepackage{transparent}
\begin{document}
 TEXT {\sffamily TEXT}
 
@Rmano Yes sure. Will do @Rmano and @DavidCarlisle
 
6:21 PM
But I shouldn't forget to use latex-dev ... Why do one have to load the color lua explicitly?
 
@Skillmon both are an approximation to \ifx aren't they? Too modern for me
 
@Skillmon -- Well, I did proofread it for TUGboat, but I may not have caught a code error. What's the problem -- since it won't be printed in TUGboat for a couple of months, there's time to fix it for that purpose
 
@Skillmon more seriously better to raise as an issue as that gives a hook to document any post release in-place updates
 
@UlrikeFischer Mostly because I don't see it as a real part of luaotfload but as something which should be integrated into l3color/l3opacity once the interface is stable enough.
 
@MarcelKrüger fine for me. What is the low-level structure of the color key? How does the code decide if the value is a hex number or a color name? And does it test if the color exist?
 
6:27 PM
@DavidCarlisle in the LaTeX2e or the LaTeX3 repo?
 
@UlrikeFischer Currently: 8 hex digits are HTML colors with transparency, otherwise if the field contains a comma everything before the comma is the color, everything after it the transparency. If the color consists of 6 hex digits then it's assumed to be a HTML color, otherwise a color name. If a colorname exists which consists of 6 hex digits, then this can't easily be selected. All parts of this can be customized though callbacks.
We could make the comma form always assume color names to avoid issues with such colors.
 
@MarcelKrüger hm. If I do \addfontfeature{Color=red,Opacity=0.2} XXXXXXXX I get ! LaTeX3 Error: Unknown color 'red,32'.. Somewhere this is passed to l3color.
 
6:44 PM
@Skillmon 2e,as that hosts ltnews
 
7:02 PM
@UlrikeFischer There was a typo which broke parsing but it should be fixed with the commit I just pushed.
 
7:19 PM
Dear @DavidCarlisle and @Rmano I've posted a question now tex.stackexchange.com/questions/647660/…
 
@BuddhiniAngelika you can use ``` to mark the code block
@BuddhiniAngelika you do realise that in a ideal world a latex document would have no font size commands and no explicit space commands. The whole point of the system is that such layout is specified separately to the text content. Of course you can force every line to be individually styled, but really you are fighting latex, not letting it help you
 
@DavidCarlisle Okay thanks :)
@DavidCarlisle Yeah that's true
But I really need to do it now, is there no way?
 
7:35 PM
@BuddhiniAngelika probably but there was so much code with so much explicit spacing I really am not going to try to adjust spacing all over. a reasonable document using spacing set up in the class can be double spaced with a couple of declarations in the preamble, but if you have explicit space everywhere, you need changes everywhere,
@BuddhiniAngelika you posted over 300 !! lines of code but no one can run it as no \documentclass Do you really use all those packages?
 
There was a documentclass but it has got deleted when doing the edit. I edited it now again. Yes, I've used the packages...
I'm in trouble @DavidCarlisle because I really have to edit the font sizes in this doc..
 
@BuddhiniAngelika \fontsize{12}{-42} ??????????????? as we said above 1 was too small, what do you want -42 to do and what do you expect to happen if you double that ????
 
@DavidCarlisle That part was edited by just looking at the changes by putting different values
I really need to change that too by properly learning about that command now
 
@BuddhiniAngelika Sounds like a very strange document you are working on.
 
Sorry about that :)
Anyway I'm in real trouble if I can't change the font sizes..
 
7:49 PM
@DavidCarlisle been there, done that: github.com/latex3/latex2e/issues/857
 
@BuddhiniAngelika I would start by removing every package that you do not use and every package that does nothing (eg inputenc), then remove very definition that breaks latex (\let\clearpage\relax) then remove every explicit space. I would not even think of adding doublespace declarations before doing that.
 
@mickep I had to do this document as instructed by someone. Even though I explained at the beginning to him, it was no use and I was made to do this, this way. But now I have to change the font sizes, and he won't be helping me either
@DavidCarlisle Okay. After that what should I do next to get the font sizes changed?
 
@Skillmon thanks
@BuddhiniAngelika someone may answer, but as I say I personally would not consider changing anything before making the changes I suggest above
 
@BuddhiniAngelika at first clean up. As David says: in the state your document is now it is hopeless.
 
Okay I will change in the question posted
 
7:55 PM
10 to go....
 
@DavidCarlisle Oh, so close.
(fishing for an upvote, aren't you?) :P
 
@UlrikeFischer With the parsing bug fixed, is the luaotfload code ready to be released or do you want some additional testing?
 
@mickep would I game the system in such an unscrupilous way?
 
@DavidCarlisle Oh no, of course not. (There is also a risk that two of us go and upvote...)
 
@MarcelKrüger I will test it now, and I can perhaps add a few testfiles with the color things.
 
7:58 PM
@UlrikeFischer That would be great, it's a rather bad sign that the parsing issue didn't trigger any tests.
 
@MarcelKrüger what can we do about the dependency from a fontspec patch? Do you know how to update fontspec if needed?
 
8:16 PM
@UlrikeFischer For the time being that's not that urgent since we first need to get luaotfload and the l3color/l3opacity changes out. Then I would like go get the Variable font and name: lookup stuff into fontspec before doing a release. (BTW do you have an opinion on VariationInstance vs Instance?)
 
user image
11
@yo' as requested
 
@DavidCarlisle -- The comma is still i the wrong place.
 
@barbarabeeton yes I know, they should use\cdot as the grouping symbol
 
@DavidCarlisle -- Good idea.
 
@DavidCarlisle Cannot adopt British standards everywhere.
 
8:27 PM
@DavidCarlisle and @UlrikeFischer I've edited the post by integrating the suggestions.
Please kindly let me know whether it's ok now and further changes if ay.
*any
Please be kind enough to help me with this.
Thanks a lot in advance :)
 
@MarcelKrüger Sorry that PR came in our holiday and so I looked only in passing, but it looked good. Regarding the instance: It seems to be not documentated? Is there an example somewhere?
@MarcelKrüger if one sets opacity twice, one gets lots of warnings from fontspec:
\DocumentMetadata{uncompress}
\directlua{require"luaotfload-l3color"}
\documentclass{article}
\usepackage{fontspec}
\setmainfont{texgyretermes}[Opacity=0.5]
\begin{document}
TTT \addfontfeature{Opacity=0.2} XXX
\end{document}
Package fontspec Warning: Opacity set twice, in both Colour and Opacity.
(fontspec)                 Using specification "Opacity=0.2".
Not dramatic, but should be addressed.
 
8:56 PM
@UlrikeFischer The fontload-variable test contains an example. Will raised the question about the naming if it should be more explicit that it's variable font related...
 
@MarcelKrüger I would say Instance, we don't have VariableWeight or similar neither. But it should be documented.
 
9:55 PM
@marcel what about color without the l3color code? When I do (with the patched fontspec)
\documentclass{article}
\usepackage{fontspec}
\usepackage{xcolor}
\colorlet{test}{red!50!blue}
\setmainfont{texgyretermes}[Color=test]
\setsansfont{texgyretermes}[Color=red]
\begin{document}
TTT \sffamily MMM
\end{document}
then I get warnings like luaotfload | color : Invalid color part in color expression "test".
 

« first day (4243 days earlier)      last day (706 days later) »