惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
U
Unit 42
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
The GitHub Blog
The GitHub Blog
Microsoft Azure Blog
Microsoft Azure Blog
有赞技术团队
有赞技术团队
Stack Overflow Blog
Stack Overflow Blog
爱范儿
爱范儿
博客园 - 司徒正美
Vercel News
Vercel News
I
InfoQ
GbyAI
GbyAI
C
Check Point Blog
B
Blog RSS Feed
Martin Fowler
Martin Fowler
B
Blog
MyScale Blog
MyScale Blog
腾讯CDC
博客园 - Franky
Blog — PlanetScale
Blog — PlanetScale
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Hugging Face - Blog
Hugging Face - Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 三生石上(FineUI控件)

Some TeX Developments

ltx-talk: Progress ltx-talk: A new class for presentations ConTeXt in TeX Live The tagging project and beamer LearnLaTeX in more languages The mythical LaTeX3 Engine news from the LaTeX Project Tagging project progress Get the Jag: from x-type to e-type Uncertainties in siunitx
Moving on from achemso
Joseph Wright · 2025-09-22 · via Some TeX Developments

The achemso package has provided the standard BibTeX styles following the American Chemical Society (ACS) guidelines since before I started using LaTeX. I’ve looked after achemso since 2008, and took it from a simple BibTeX .bst to a bundle including submission class, a demo document and other goodies.

I started the class many years ago, and with hindsight some of it was not such a great plan. More importantly, the ACS have never used LaTeX in production, which has always meant that using a dedicated class was a bit awkward: getting things into a specific class only for them to strip that out again. I’ve therefore recently agreed with the ACS to move from a dedicated class to a simple template, now available on GitHub and soon to appear on the ACS website. Authors can then simply use article with minor adjustments and get something that is suitable for production.

At the same time, classical BibTeX styles, whilst still widely used, are better replaced by biblatex methods. That opens up a lot of flexibility to the user, and avoids needing add-on packages to provide control or compound citations.

So I’m marking achemso as for historical support only, and recommending all new content shifts to updated approaches. I’ll keep achemso working of course: not that there should be much to do! But it’s time for people to move away from what was a rather rigid approach in new documents.