Issue with @ifl@ter and expl3 date style











up vote
3
down vote

favorite












I use MiKTeX on windows and am currently having trouble loading expl3. I recently updated the LaTeX3 packages. The following code is sufficient to generate the error:



documentclass{article}
usepackage{expl3}
begin{document}
test
end{document}


To which latex replies:



! Missing = inserted for ifnum.
<to be read again>
-
l.3 begin
{document}


I uninstalled and reinstalled both l3kernel and l3packages. MiKTeX Package Manager reports that l3kernel is "Packaged on" 2018-11-22 and "Installed on" 2018-12-05 and that l3packages is "Packaged on" 2018-10-18 and "Installed on" 2018-12-05. Maybe the issue has to do with the different dates they are "Packaged on"? I haven't looked at the diff between the two versions.



Anyways, throwing a tracingall in before usepackage{expl3} I get:



.... 40 megabyes of text
@ifl@t@r #1#2->ifnum expandafter @parse@version #1//00@nil <expandafter
@parse@version #2//00@nil expandafter @secondoftwo else expandafter @firs
toftwo fi
#1<-ver@expl3.sty
#2<-
{ifnum: (level 1) entered on line 9}
{expandafter}

ver@expl3.sty ->2018-11-19 L3 programming layer (loader)

@parse@version #1/#2/#3#4#5@nil ->#1#2#3#4
#1<-2018-11-19 L3 programming layer (loader)
#2<-
#3<-0
#4<-0
#5<-
! Missing = inserted for ifnum.
<to be read again>
-


So the issue is that the innermost macro of @ifpackagelater called @ifl@ter is expecting expl3 to report its date as e.g., 2018/11/19 but it's reported as 2018-11-19 with dashes instead of slashes. For now, I can get code to run by saying:



documentclass{article}
makeatletter
letsave@ifl@ter@ifl@ter
def@ifl@ter#1#2#3#4#5{} % Temporarily dummy out @ifl@ter
usepackage{expl3} % load package
let@ifl@tersave@ifl@ter % Restore @ifl@ter
% This would break with the same error as before:
%@ifpackagelater{expl3}{10/10/2018}{message{yes}}{message{no}}
makeatother

begin{document}
test
end{document}









share|improve this question




















  • 1




    Tha LaTeX kernel got updated and replaced the date format from dd/mm/yyyy to dd-mm-yyyy. You probably should update the LaTeX kernel as well.
    – Phelype Oleinik
    Dec 6 at 18:41










  • How do I do that? Does mpm have an entry for the latex kernel? Searching for "kernel" the only package that turns up is l3kernel.
    – Hood Chatham
    Dec 6 at 18:44








  • 2




    @HoodChatham It will be listed just as latex
    – Joseph Wright
    Dec 6 at 18:47






  • 3




    run the update manager as user and as admin.
    – Ulrike Fischer
    Dec 6 at 18:47






  • 1




    Probably related: tex.stackexchange.com/q/422176/35864
    – moewe
    Dec 6 at 20:32















up vote
3
down vote

favorite












I use MiKTeX on windows and am currently having trouble loading expl3. I recently updated the LaTeX3 packages. The following code is sufficient to generate the error:



documentclass{article}
usepackage{expl3}
begin{document}
test
end{document}


To which latex replies:



! Missing = inserted for ifnum.
<to be read again>
-
l.3 begin
{document}


I uninstalled and reinstalled both l3kernel and l3packages. MiKTeX Package Manager reports that l3kernel is "Packaged on" 2018-11-22 and "Installed on" 2018-12-05 and that l3packages is "Packaged on" 2018-10-18 and "Installed on" 2018-12-05. Maybe the issue has to do with the different dates they are "Packaged on"? I haven't looked at the diff between the two versions.



Anyways, throwing a tracingall in before usepackage{expl3} I get:



.... 40 megabyes of text
@ifl@t@r #1#2->ifnum expandafter @parse@version #1//00@nil <expandafter
@parse@version #2//00@nil expandafter @secondoftwo else expandafter @firs
toftwo fi
#1<-ver@expl3.sty
#2<-
{ifnum: (level 1) entered on line 9}
{expandafter}

ver@expl3.sty ->2018-11-19 L3 programming layer (loader)

@parse@version #1/#2/#3#4#5@nil ->#1#2#3#4
#1<-2018-11-19 L3 programming layer (loader)
#2<-
#3<-0
#4<-0
#5<-
! Missing = inserted for ifnum.
<to be read again>
-


So the issue is that the innermost macro of @ifpackagelater called @ifl@ter is expecting expl3 to report its date as e.g., 2018/11/19 but it's reported as 2018-11-19 with dashes instead of slashes. For now, I can get code to run by saying:



documentclass{article}
makeatletter
letsave@ifl@ter@ifl@ter
def@ifl@ter#1#2#3#4#5{} % Temporarily dummy out @ifl@ter
usepackage{expl3} % load package
let@ifl@tersave@ifl@ter % Restore @ifl@ter
% This would break with the same error as before:
%@ifpackagelater{expl3}{10/10/2018}{message{yes}}{message{no}}
makeatother

begin{document}
test
end{document}









share|improve this question




















  • 1




    Tha LaTeX kernel got updated and replaced the date format from dd/mm/yyyy to dd-mm-yyyy. You probably should update the LaTeX kernel as well.
    – Phelype Oleinik
    Dec 6 at 18:41










  • How do I do that? Does mpm have an entry for the latex kernel? Searching for "kernel" the only package that turns up is l3kernel.
    – Hood Chatham
    Dec 6 at 18:44








  • 2




    @HoodChatham It will be listed just as latex
    – Joseph Wright
    Dec 6 at 18:47






  • 3




    run the update manager as user and as admin.
    – Ulrike Fischer
    Dec 6 at 18:47






  • 1




    Probably related: tex.stackexchange.com/q/422176/35864
    – moewe
    Dec 6 at 20:32













up vote
3
down vote

favorite









up vote
3
down vote

favorite











I use MiKTeX on windows and am currently having trouble loading expl3. I recently updated the LaTeX3 packages. The following code is sufficient to generate the error:



documentclass{article}
usepackage{expl3}
begin{document}
test
end{document}


To which latex replies:



! Missing = inserted for ifnum.
<to be read again>
-
l.3 begin
{document}


I uninstalled and reinstalled both l3kernel and l3packages. MiKTeX Package Manager reports that l3kernel is "Packaged on" 2018-11-22 and "Installed on" 2018-12-05 and that l3packages is "Packaged on" 2018-10-18 and "Installed on" 2018-12-05. Maybe the issue has to do with the different dates they are "Packaged on"? I haven't looked at the diff between the two versions.



Anyways, throwing a tracingall in before usepackage{expl3} I get:



.... 40 megabyes of text
@ifl@t@r #1#2->ifnum expandafter @parse@version #1//00@nil <expandafter
@parse@version #2//00@nil expandafter @secondoftwo else expandafter @firs
toftwo fi
#1<-ver@expl3.sty
#2<-
{ifnum: (level 1) entered on line 9}
{expandafter}

ver@expl3.sty ->2018-11-19 L3 programming layer (loader)

@parse@version #1/#2/#3#4#5@nil ->#1#2#3#4
#1<-2018-11-19 L3 programming layer (loader)
#2<-
#3<-0
#4<-0
#5<-
! Missing = inserted for ifnum.
<to be read again>
-


So the issue is that the innermost macro of @ifpackagelater called @ifl@ter is expecting expl3 to report its date as e.g., 2018/11/19 but it's reported as 2018-11-19 with dashes instead of slashes. For now, I can get code to run by saying:



documentclass{article}
makeatletter
letsave@ifl@ter@ifl@ter
def@ifl@ter#1#2#3#4#5{} % Temporarily dummy out @ifl@ter
usepackage{expl3} % load package
let@ifl@tersave@ifl@ter % Restore @ifl@ter
% This would break with the same error as before:
%@ifpackagelater{expl3}{10/10/2018}{message{yes}}{message{no}}
makeatother

begin{document}
test
end{document}









share|improve this question















I use MiKTeX on windows and am currently having trouble loading expl3. I recently updated the LaTeX3 packages. The following code is sufficient to generate the error:



documentclass{article}
usepackage{expl3}
begin{document}
test
end{document}


To which latex replies:



! Missing = inserted for ifnum.
<to be read again>
-
l.3 begin
{document}


I uninstalled and reinstalled both l3kernel and l3packages. MiKTeX Package Manager reports that l3kernel is "Packaged on" 2018-11-22 and "Installed on" 2018-12-05 and that l3packages is "Packaged on" 2018-10-18 and "Installed on" 2018-12-05. Maybe the issue has to do with the different dates they are "Packaged on"? I haven't looked at the diff between the two versions.



Anyways, throwing a tracingall in before usepackage{expl3} I get:



.... 40 megabyes of text
@ifl@t@r #1#2->ifnum expandafter @parse@version #1//00@nil <expandafter
@parse@version #2//00@nil expandafter @secondoftwo else expandafter @firs
toftwo fi
#1<-ver@expl3.sty
#2<-
{ifnum: (level 1) entered on line 9}
{expandafter}

ver@expl3.sty ->2018-11-19 L3 programming layer (loader)

@parse@version #1/#2/#3#4#5@nil ->#1#2#3#4
#1<-2018-11-19 L3 programming layer (loader)
#2<-
#3<-0
#4<-0
#5<-
! Missing = inserted for ifnum.
<to be read again>
-


So the issue is that the innermost macro of @ifpackagelater called @ifl@ter is expecting expl3 to report its date as e.g., 2018/11/19 but it's reported as 2018-11-19 with dashes instead of slashes. For now, I can get code to run by saying:



documentclass{article}
makeatletter
letsave@ifl@ter@ifl@ter
def@ifl@ter#1#2#3#4#5{} % Temporarily dummy out @ifl@ter
usepackage{expl3} % load package
let@ifl@tersave@ifl@ter % Restore @ifl@ter
% This would break with the same error as before:
%@ifpackagelater{expl3}{10/10/2018}{message{yes}}{message{no}}
makeatother

begin{document}
test
end{document}






packages expl3






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 6 at 18:39









Phelype Oleinik

21.3k54380




21.3k54380










asked Dec 6 at 18:37









Hood Chatham

4,0921227




4,0921227








  • 1




    Tha LaTeX kernel got updated and replaced the date format from dd/mm/yyyy to dd-mm-yyyy. You probably should update the LaTeX kernel as well.
    – Phelype Oleinik
    Dec 6 at 18:41










  • How do I do that? Does mpm have an entry for the latex kernel? Searching for "kernel" the only package that turns up is l3kernel.
    – Hood Chatham
    Dec 6 at 18:44








  • 2




    @HoodChatham It will be listed just as latex
    – Joseph Wright
    Dec 6 at 18:47






  • 3




    run the update manager as user and as admin.
    – Ulrike Fischer
    Dec 6 at 18:47






  • 1




    Probably related: tex.stackexchange.com/q/422176/35864
    – moewe
    Dec 6 at 20:32














  • 1




    Tha LaTeX kernel got updated and replaced the date format from dd/mm/yyyy to dd-mm-yyyy. You probably should update the LaTeX kernel as well.
    – Phelype Oleinik
    Dec 6 at 18:41










  • How do I do that? Does mpm have an entry for the latex kernel? Searching for "kernel" the only package that turns up is l3kernel.
    – Hood Chatham
    Dec 6 at 18:44








  • 2




    @HoodChatham It will be listed just as latex
    – Joseph Wright
    Dec 6 at 18:47






  • 3




    run the update manager as user and as admin.
    – Ulrike Fischer
    Dec 6 at 18:47






  • 1




    Probably related: tex.stackexchange.com/q/422176/35864
    – moewe
    Dec 6 at 20:32








1




1




Tha LaTeX kernel got updated and replaced the date format from dd/mm/yyyy to dd-mm-yyyy. You probably should update the LaTeX kernel as well.
– Phelype Oleinik
Dec 6 at 18:41




Tha LaTeX kernel got updated and replaced the date format from dd/mm/yyyy to dd-mm-yyyy. You probably should update the LaTeX kernel as well.
– Phelype Oleinik
Dec 6 at 18:41












How do I do that? Does mpm have an entry for the latex kernel? Searching for "kernel" the only package that turns up is l3kernel.
– Hood Chatham
Dec 6 at 18:44






How do I do that? Does mpm have an entry for the latex kernel? Searching for "kernel" the only package that turns up is l3kernel.
– Hood Chatham
Dec 6 at 18:44






2




2




@HoodChatham It will be listed just as latex
– Joseph Wright
Dec 6 at 18:47




@HoodChatham It will be listed just as latex
– Joseph Wright
Dec 6 at 18:47




3




3




run the update manager as user and as admin.
– Ulrike Fischer
Dec 6 at 18:47




run the update manager as user and as admin.
– Ulrike Fischer
Dec 6 at 18:47




1




1




Probably related: tex.stackexchange.com/q/422176/35864
– moewe
Dec 6 at 20:32




Probably related: tex.stackexchange.com/q/422176/35864
– moewe
Dec 6 at 20:32










1 Answer
1






active

oldest

votes

















up vote
7
down vote













The LaTeX kernel got updated in April, 2017 to use the ISO 8601 date format yyyy-mm-dd instead of a format Frank invented :)



You have to update your LaTeX kernel to a newer version so that the date format in expl3 works. It's always better to update all packages together, or these conflicts might happen.





If you can't update for whatever reason, you can use the newer date parser (code tested with an up-to-date (Dec 6th, 2018) expl3 with the LaTeX kernel of TeXLive 2015):



documentclass{article}

makeatletter
def@ifl@t@r#1#2{%
ifnumexpandafter@parse@version@#1//00@nil<%
expandafter@parse@version@#2//00@nil
expandafter@secondoftwo
else
expandafter@firstoftwo
fi}
def@parse@version@#1{@parse@version0#1}
def@parse@version#1/#2/#3#4#5@nil{%
@parse@version@dash#1-#2-#3#4@nil
}
def@parse@version@dash#1-#2-#3#4#5@nil{%
ifrelax#2relaxelse#1fi#2#3#4 }
makeatother

usepackage{expl3}

begin{document}

hello

end{document}





share|improve this answer























  • begin{nitpick}You did mean yyyy-mm-dd, didn't you? end{nitpick}
    – Harald Hanche-Olsen
    Dec 6 at 19:26












  • @HaraldHanche-Olsen begin{thanks} Oops, you're right :) end{thanks}
    – Phelype Oleinik
    Dec 6 at 19:34










  • I think the YYYY-MM-DD format has been supported since 2017 (latex-project.org/news/latex2e-news/ltnews27.pdf). latexrelease may also help here.
    – moewe
    Dec 6 at 20:33










  • @moewe Indeed. I hadn't found this ltnews before. Thanks :)
    – Phelype Oleinik
    Dec 6 at 21:29






  • 1




    nice to see my inventions being commented on :-) but I made more important ones I hope
    – Frank Mittelbach
    Dec 8 at 13:18











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f463566%2fissue-with-iflter-and-expl3-date-style%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
7
down vote













The LaTeX kernel got updated in April, 2017 to use the ISO 8601 date format yyyy-mm-dd instead of a format Frank invented :)



You have to update your LaTeX kernel to a newer version so that the date format in expl3 works. It's always better to update all packages together, or these conflicts might happen.





If you can't update for whatever reason, you can use the newer date parser (code tested with an up-to-date (Dec 6th, 2018) expl3 with the LaTeX kernel of TeXLive 2015):



documentclass{article}

makeatletter
def@ifl@t@r#1#2{%
ifnumexpandafter@parse@version@#1//00@nil<%
expandafter@parse@version@#2//00@nil
expandafter@secondoftwo
else
expandafter@firstoftwo
fi}
def@parse@version@#1{@parse@version0#1}
def@parse@version#1/#2/#3#4#5@nil{%
@parse@version@dash#1-#2-#3#4@nil
}
def@parse@version@dash#1-#2-#3#4#5@nil{%
ifrelax#2relaxelse#1fi#2#3#4 }
makeatother

usepackage{expl3}

begin{document}

hello

end{document}





share|improve this answer























  • begin{nitpick}You did mean yyyy-mm-dd, didn't you? end{nitpick}
    – Harald Hanche-Olsen
    Dec 6 at 19:26












  • @HaraldHanche-Olsen begin{thanks} Oops, you're right :) end{thanks}
    – Phelype Oleinik
    Dec 6 at 19:34










  • I think the YYYY-MM-DD format has been supported since 2017 (latex-project.org/news/latex2e-news/ltnews27.pdf). latexrelease may also help here.
    – moewe
    Dec 6 at 20:33










  • @moewe Indeed. I hadn't found this ltnews before. Thanks :)
    – Phelype Oleinik
    Dec 6 at 21:29






  • 1




    nice to see my inventions being commented on :-) but I made more important ones I hope
    – Frank Mittelbach
    Dec 8 at 13:18















up vote
7
down vote













The LaTeX kernel got updated in April, 2017 to use the ISO 8601 date format yyyy-mm-dd instead of a format Frank invented :)



You have to update your LaTeX kernel to a newer version so that the date format in expl3 works. It's always better to update all packages together, or these conflicts might happen.





If you can't update for whatever reason, you can use the newer date parser (code tested with an up-to-date (Dec 6th, 2018) expl3 with the LaTeX kernel of TeXLive 2015):



documentclass{article}

makeatletter
def@ifl@t@r#1#2{%
ifnumexpandafter@parse@version@#1//00@nil<%
expandafter@parse@version@#2//00@nil
expandafter@secondoftwo
else
expandafter@firstoftwo
fi}
def@parse@version@#1{@parse@version0#1}
def@parse@version#1/#2/#3#4#5@nil{%
@parse@version@dash#1-#2-#3#4@nil
}
def@parse@version@dash#1-#2-#3#4#5@nil{%
ifrelax#2relaxelse#1fi#2#3#4 }
makeatother

usepackage{expl3}

begin{document}

hello

end{document}





share|improve this answer























  • begin{nitpick}You did mean yyyy-mm-dd, didn't you? end{nitpick}
    – Harald Hanche-Olsen
    Dec 6 at 19:26












  • @HaraldHanche-Olsen begin{thanks} Oops, you're right :) end{thanks}
    – Phelype Oleinik
    Dec 6 at 19:34










  • I think the YYYY-MM-DD format has been supported since 2017 (latex-project.org/news/latex2e-news/ltnews27.pdf). latexrelease may also help here.
    – moewe
    Dec 6 at 20:33










  • @moewe Indeed. I hadn't found this ltnews before. Thanks :)
    – Phelype Oleinik
    Dec 6 at 21:29






  • 1




    nice to see my inventions being commented on :-) but I made more important ones I hope
    – Frank Mittelbach
    Dec 8 at 13:18













up vote
7
down vote










up vote
7
down vote









The LaTeX kernel got updated in April, 2017 to use the ISO 8601 date format yyyy-mm-dd instead of a format Frank invented :)



You have to update your LaTeX kernel to a newer version so that the date format in expl3 works. It's always better to update all packages together, or these conflicts might happen.





If you can't update for whatever reason, you can use the newer date parser (code tested with an up-to-date (Dec 6th, 2018) expl3 with the LaTeX kernel of TeXLive 2015):



documentclass{article}

makeatletter
def@ifl@t@r#1#2{%
ifnumexpandafter@parse@version@#1//00@nil<%
expandafter@parse@version@#2//00@nil
expandafter@secondoftwo
else
expandafter@firstoftwo
fi}
def@parse@version@#1{@parse@version0#1}
def@parse@version#1/#2/#3#4#5@nil{%
@parse@version@dash#1-#2-#3#4@nil
}
def@parse@version@dash#1-#2-#3#4#5@nil{%
ifrelax#2relaxelse#1fi#2#3#4 }
makeatother

usepackage{expl3}

begin{document}

hello

end{document}





share|improve this answer














The LaTeX kernel got updated in April, 2017 to use the ISO 8601 date format yyyy-mm-dd instead of a format Frank invented :)



You have to update your LaTeX kernel to a newer version so that the date format in expl3 works. It's always better to update all packages together, or these conflicts might happen.





If you can't update for whatever reason, you can use the newer date parser (code tested with an up-to-date (Dec 6th, 2018) expl3 with the LaTeX kernel of TeXLive 2015):



documentclass{article}

makeatletter
def@ifl@t@r#1#2{%
ifnumexpandafter@parse@version@#1//00@nil<%
expandafter@parse@version@#2//00@nil
expandafter@secondoftwo
else
expandafter@firstoftwo
fi}
def@parse@version@#1{@parse@version0#1}
def@parse@version#1/#2/#3#4#5@nil{%
@parse@version@dash#1-#2-#3#4@nil
}
def@parse@version@dash#1-#2-#3#4#5@nil{%
ifrelax#2relaxelse#1fi#2#3#4 }
makeatother

usepackage{expl3}

begin{document}

hello

end{document}






share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 6 at 21:28

























answered Dec 6 at 18:55









Phelype Oleinik

21.3k54380




21.3k54380












  • begin{nitpick}You did mean yyyy-mm-dd, didn't you? end{nitpick}
    – Harald Hanche-Olsen
    Dec 6 at 19:26












  • @HaraldHanche-Olsen begin{thanks} Oops, you're right :) end{thanks}
    – Phelype Oleinik
    Dec 6 at 19:34










  • I think the YYYY-MM-DD format has been supported since 2017 (latex-project.org/news/latex2e-news/ltnews27.pdf). latexrelease may also help here.
    – moewe
    Dec 6 at 20:33










  • @moewe Indeed. I hadn't found this ltnews before. Thanks :)
    – Phelype Oleinik
    Dec 6 at 21:29






  • 1




    nice to see my inventions being commented on :-) but I made more important ones I hope
    – Frank Mittelbach
    Dec 8 at 13:18


















  • begin{nitpick}You did mean yyyy-mm-dd, didn't you? end{nitpick}
    – Harald Hanche-Olsen
    Dec 6 at 19:26












  • @HaraldHanche-Olsen begin{thanks} Oops, you're right :) end{thanks}
    – Phelype Oleinik
    Dec 6 at 19:34










  • I think the YYYY-MM-DD format has been supported since 2017 (latex-project.org/news/latex2e-news/ltnews27.pdf). latexrelease may also help here.
    – moewe
    Dec 6 at 20:33










  • @moewe Indeed. I hadn't found this ltnews before. Thanks :)
    – Phelype Oleinik
    Dec 6 at 21:29






  • 1




    nice to see my inventions being commented on :-) but I made more important ones I hope
    – Frank Mittelbach
    Dec 8 at 13:18
















begin{nitpick}You did mean yyyy-mm-dd, didn't you? end{nitpick}
– Harald Hanche-Olsen
Dec 6 at 19:26






begin{nitpick}You did mean yyyy-mm-dd, didn't you? end{nitpick}
– Harald Hanche-Olsen
Dec 6 at 19:26














@HaraldHanche-Olsen begin{thanks} Oops, you're right :) end{thanks}
– Phelype Oleinik
Dec 6 at 19:34




@HaraldHanche-Olsen begin{thanks} Oops, you're right :) end{thanks}
– Phelype Oleinik
Dec 6 at 19:34












I think the YYYY-MM-DD format has been supported since 2017 (latex-project.org/news/latex2e-news/ltnews27.pdf). latexrelease may also help here.
– moewe
Dec 6 at 20:33




I think the YYYY-MM-DD format has been supported since 2017 (latex-project.org/news/latex2e-news/ltnews27.pdf). latexrelease may also help here.
– moewe
Dec 6 at 20:33












@moewe Indeed. I hadn't found this ltnews before. Thanks :)
– Phelype Oleinik
Dec 6 at 21:29




@moewe Indeed. I hadn't found this ltnews before. Thanks :)
– Phelype Oleinik
Dec 6 at 21:29




1




1




nice to see my inventions being commented on :-) but I made more important ones I hope
– Frank Mittelbach
Dec 8 at 13:18




nice to see my inventions being commented on :-) but I made more important ones I hope
– Frank Mittelbach
Dec 8 at 13:18


















draft saved

draft discarded




















































Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f463566%2fissue-with-iflter-and-expl3-date-style%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

mysqli_query(): Empty query in /home/lucindabrummitt/public_html/blog/wp-includes/wp-db.php on line 1924

How to change which sound is reproduced for terminal bell?

Can I use Tabulator js library in my java Spring + Thymeleaf project?