Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
45

LaTeX Packages A-M Symbol legend: BitBucket, GitHub, Launchpad, Google Code, GitLab abc: Enrico Gregorio (egreg) abraces: Werner Grundlingh (Werner) accents: Javier Bezos accsupp: Heiko Oberdiek acro: Clemens Niederberger (clemens) acronym: Heiko Oberdiek with Tobias Oetiker adforn: cfr [LaTeX support only] adfsymbols: cfr [LaTeX support only] ...


32

LaTeX Packages N-Z Symbol legend: BitBucket, GitHub, Launchpad, Google Code, GitLab nameref: Heiko Oberdiek with Sebastian Rahtz newfloat: Axel Sommerfeldt newunicodechar: Enrico Gregorio (egreg) newverbs: Martin Scharrer nfssext-cfr: cfr noindentafter: Michiel Helvensteijn (mhelvens) nopageno: David Carlisle notes2bib: Joseph Wright nowidow: ...


28

All posts to the site are made subject the the Creative Commons 'Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0)' license. The summary of this license says: You are free: to Share — to copy, distribute and transmit the work to Remix — to adapt the work to make commercial use of the work which is a key point of the site: you can take ...


24

Support Scripts Symbol legend: BitBucket, GitHub, Launchpad arara: Paulo Cereda, Marco Daniel, Nicola Talbot and Brent Longborough bib2gls: Nicola Talbot checkcites: Enrico Gregorio (egreg) and Paulo Cereda check-parens: Jaap Eldering (eldering) csv2latex: Alan Munn ctanupload: Martin Scharrer dosepsbin: Heiko Oberdiek jmakepdfx: Nicola Talbot ...


21

Biblatex Styles Symbol legend: BitBucket, GitHub, Launchpad biblatex-chem: Joseph Wright biblatex-phys: Joseph Wright biblatex-ieee: Joseph Wright biblatex-musuos: Tobias Weh (Tobi) biblatex-nature: Joseph Wright biblatex-nejm: Marco Daniel biblatex-publist: Jür­gen Spitzmüller biblatex-sbl: David Purton biblatex-trad: Marco Daniel


19

Generic Packages Symbol legend: BitBucket, GitHub, Launchpad apnum.tex: Petr Olšák (wipet) asapsym: Paul Gessler chemfig.tex: Christian Tellechea (unbonpetit) cnv.tex: Petr Olšák (wipet) code128, ean13 Petr Olšák (wipet) csplain (+opmac): Petr Olšák (wipet) ctustyle, custyle: Petr Olšák (wipet) dirtree: Jean-Côme Charpentier docbytex: Petr Olšák (wipet)...


17

ConTeXt Modules Symbol legend: GitHub filter: Aditya Mahajan gnuplot: Mojca Miklavec letterine: Taco Hoekwater mathsets: Aditya Mahajan simpleslides: Thomas Schmitz and Aditya Mahajan vim: Aditya Mahajan visualcounter: Aditya Mahajan


12

Recently, I couldn't come to terms with latexmk. After reading the available documentation and searching for a solution on the Internet, I posted a question here, to make sure that I wasn't missing anything. This way, I could avoid bothering the package author with a stupid question -- turned out it wasn't: When even a bounty couldn't get me an answer that I ...


11

You should first check the package manual and its README file (both usually under http://www.ctab.org/pkg/<packagename>) for an email address. Many of them have it included. Some package, like mine, also have a bug tracker which should be used for bug reports and feature requests if possible. Usually such a tracker is also mentioned either in the ...


10

This varies from package author to package author. If you can find a (working) e-mail address, then this is usually the best way. That can be done in parallel with a public query, for example by CCing the author on a Usenet or mailing list post, or by linking to a post here. If you cannot get hold of someone, then one approach is to 'ask around' to find out ...


3

I'm pretty in-favor of a single, CW question on Meta where everyone can list the packages they are actively working on if they so desire. While certainly not appropriate as a Main post, I can imagine that it may be appropriate as a Meta post. Considering it would not be about TeX syntax but rather about TeX happenings specifically as it pertains to users of ...


Only top voted, non community-wiki answers of a minimum length are eligible