|
Tue Oct 12 07:47:17 2021, comment #9:
Fix confirmed. Thanks, all!
|
Tue Oct 12 05:53:32 2021, comment #8:
Thanks for the explanation, Karl. I understand it's a challenging endeavor, and I am very grateful the two of you invest so much time to keep this running!
As for the bug, I'll report back as soon as the update landed here.
|
Mon Oct 11 21:09:29 2021, comment #7:
Sorry, I failed to notice the scr*.4ht changes were there in addition to the stmary.htf fix. Updated for tonight. Closing this bug, though feel free to reply if problems persist.
The story on CTAN is that we update only the source files. That's why the ChangeLog was updated, and -noncjk.tex, but not any .htf or *.4ht. The lack of updating tex4ht-4ht.tex was the (my) error.
As Michal says, we haven't delved into making full releases. (it's not clear to me that this would be especially useful or desirable, anyway.) Therefore this updating of source files seemed better than just letting Eitan's last release stand forever. (It's in CTAN:obsolete/ now.)
I added another paragraph to https://ctan.org/pkg/tex4ht to try to explain the situation better. Let me know about any suggestions/corrections there. --thanks, karl.
|
Mon Oct 11 08:36:58 2021, comment #6:
Karl updates TeX Live directly, updates don't end up on CTAN. TeX4ht distribution is quite complicated and we still don't have a method for the CTAN release. This is why the latest update on CTAN is from 2008.
|
Mon Oct 11 08:04:27 2021, comment #5:
tex4ht-4ht.tex for that matter.
|
Mon Oct 11 08:03:55 2021, comment #4:
Sure, I just thought as there qwas a tex4ht update today. Also, on CTAN, the Changelog lists the fix, but the respective file (tex4ht-fonts-noncjk.tex IIRC) doesn't contain them. In fact, the only updated file, next to the ChangeLog, is tex4ht-fonts-noncjk.tex.
|
Mon Oct 11 07:01:04 2021, comment #3:
Jürgen, it can take few days before changes come to TeX Live.
|
Mon Oct 11 06:41:37 2021, comment #2:
Thanks, Michal. I understand this didn't make it into today's release (60725 in TL) although it is mentioned in the ChangeLog.
I'll wait and report back.
|
Sun Oct 10 18:07:58 2021, comment #1:
Hi Jürgen, thanks for the report. This error appeared in the past and it seems that it is back again. Koma classes now contain some code that should be executed with TeX4ht:
\BeforePackage{tex4ht}{%
\let\scr@defineobsoletefonts\thr@@
}
Due to a recent change, TeX4ht is now loaded before document classes. It is necessary to prevent other bugs. So the above code doesn't take any effect, as TeX4ht is already loaded when it is executed. I've took this code and added it to the .4ht files for Koma script classes. It seems that it fixes this issue.
|
Sat Oct 9 09:55:08 2021, original submission:
Spin-off from bug #507:
Trying to compile a KOMA class document (e.g., the MWE of #507) exposes the following problem:
Note that \tt is not used anywhere in the file itself (and the file compiles without error with pdflatex) so it must be used by a file included by tex4ht.
|
Related Recipes:
tex4ht - Bugs: bug #529, Error about undefined \tt with...