Difference between revisions of "Publications/verna.19.tug"
From LRDE
(Created page with "{{Publication | published = true | date = 2019-11-06 | authors = Didier Verna | title = Quickref: Common Lisp Reference Documentation as a Stress Test for Texinfo | booktitle...") |
|||
(One intermediate revision by the same user not shown) | |||
Line 15: | Line 15: | ||
| lrdekeywords = Software Engineering |
| lrdekeywords = Software Engineering |
||
| lrdepaper = http://www.lrde.epita.fr/dload/papers/verna.19.tug.pdf |
| lrdepaper = http://www.lrde.epita.fr/dload/papers/verna.19.tug.pdf |
||
− | | abstract = Quickref is a global documentation project for the Common Lisp ecosystem. It creates reference manuals automatically by introspecting libraries and generating corresponding documentation in Texinfo format. The Texinfo files may subsequently be converted into PDF or HTML. Quickref is non-intrusive: software developers do not have anything to do to get their libraries documented by the system.par Quickref may be used to create a local website documenting your current, partial, working environment, but it is also able to document the whole Common Lisp ecosystem at once. The result is a website containing almost two thousand reference manuals. Quickref provides a Docker image for an easy recreation of this website, but a public version is also available and actively maintained.par Quickref constitutes an enormous and successful stress test for Texinfo. In this paper, we give an overview of the design and architecture of the system, describe the challenges and difficulties in generating valid Texinfo code |
+ | | abstract = Quickref is a global documentation project for the Common Lisp ecosystem. It creates reference manuals automatically by introspecting libraries and generating corresponding documentation in Texinfo format. The Texinfo files may subsequently be converted into PDF or HTML. Quickref is non-intrusive: software developers do not have anything to do to get their libraries documented by the system.par Quickref may be used to create a local website documenting your current, partial, working environment, but it is also able to document the whole Common Lisp ecosystem at once. The result is a website containing almost two thousand reference manuals. Quickref provides a Docker image for an easy recreation of this website, but a public version is also available and actively maintained.par Quickref constitutes an enormous and successful stress test for Texinfo. In this paper, we give an overview of the design and architecture of the system, describe the challenges and difficulties in generating valid Texinfo code automatically, and put some emphasis on the currently remaining problems and deficiencies. |
+ | | nodoi = |
||
| type = inproceedings |
| type = inproceedings |
||
| id = verna.19.tug |
| id = verna.19.tug |
||
Line 52: | Line 53: | ||
difficulties in generating valid Texinfo code |
difficulties in generating valid Texinfo code |
||
automatically, and put some emphasis on the currently |
automatically, and put some emphasis on the currently |
||
− | remaining problems and deficiencies.<nowiki>}</nowiki> |
+ | remaining problems and deficiencies.<nowiki>}</nowiki>, |
+ | nodoi = <nowiki>{</nowiki><nowiki>}</nowiki> |
||
<nowiki>}</nowiki> |
<nowiki>}</nowiki> |
||
Latest revision as of 19:08, 7 April 2023
- Authors
- Didier Verna
- Where
- TUGboat
- Type
- inproceedings
- Publisher
- TeX Users Group
- Projects
- Typesetting"Typesetting" is not in the list (Vaucanson, Spot, URBI, Olena, APMC, Tiger, Climb, Speaker ID, Transformers, Bison, ...) of allowed values for the "Related project" property.
- Keywords
- Software Engineering
- Date
- 2019-11-06
Abstract
Quickref is a global documentation project for the Common Lisp ecosystem. It creates reference manuals automatically by introspecting libraries and generating corresponding documentation in Texinfo format. The Texinfo files may subsequently be converted into PDF or HTML. Quickref is non-intrusive: software developers do not have anything to do to get their libraries documented by the system.par Quickref may be used to create a local website documenting your current, partial, working environment, but it is also able to document the whole Common Lisp ecosystem at once. The result is a website containing almost two thousand reference manuals. Quickref provides a Docker image for an easy recreation of this website, but a public version is also available and actively maintained.par Quickref constitutes an enormous and successful stress test for Texinfo. In this paper, we give an overview of the design and architecture of the system, describe the challenges and difficulties in generating valid Texinfo code automatically, and put some emphasis on the currently remaining problems and deficiencies.
Documents
Bibtex (lrde.bib)
@InProceedings{ verna.19.tug, author = {Didier Verna}, title = {{Quickref}: {Common} {Lisp} Reference Documentation as a Stress Test for {Texinfo}}, booktitle = {TUGboat}, volume = 40, number = {2}, pages = {119--125}, editor = {Barbara Beeton and Karl Berry}, organization = {\TeX{} Users Group}, month = sep, year = 2019, publisher = {\TeX{} Users Group}, issn = 0896320, abstract = {Quickref is a global documentation project for the Common Lisp ecosystem. It creates reference manuals automatically by introspecting libraries and generating corresponding documentation in Texinfo format. The Texinfo files may subsequently be converted into PDF or HTML. Quickref is non-intrusive: software developers do not have anything to do to get their libraries documented by the system.\par Quickref may be used to create a local website documenting your current, partial, working environment, but it is also able to document the whole Common Lisp ecosystem at once. The result is a website containing almost two thousand reference manuals. Quickref provides a Docker image for an easy recreation of this website, but a public version is also available and actively maintained.\par Quickref constitutes an enormous and successful stress test for Texinfo. In this paper, we give an overview of the design and architecture of the system, describe the challenges and difficulties in generating valid Texinfo code automatically, and put some emphasis on the currently remaining problems and deficiencies.}, nodoi = {} }