Difference between revisions of "Publications/verna.13.tug-2"

From LRDE

 
Line 5: Line 5:
 
| title = TiCL: the Prototype (Star TeX: the Next GenerationSeason 2)
 
| title = TiCL: the Prototype (Star TeX: the Next GenerationSeason 2)
 
| booktitle = TUGboat
 
| booktitle = TUGboat
  +
| nodoi =
 
| editors = Barbara Beeton, Karl Berry
 
| editors = Barbara Beeton, Karl Berry
 
| volume = 34
 
| volume = 34
Line 22: Line 23:
 
year = 2013,
 
year = 2013,
 
month = jan,
 
month = jan,
  +
nodoi = <nowiki>{</nowiki><nowiki>}</nowiki>,
 
editor = <nowiki>{</nowiki>Barbara Beeton and Karl Berry<nowiki>}</nowiki>,
 
editor = <nowiki>{</nowiki>Barbara Beeton and Karl Berry<nowiki>}</nowiki>,
 
volume = 34,
 
volume = 34,

Latest revision as of 10:40, 22 April 2023

Abstract

At TUG 2012, we presented some ideas about using one of the oldest programming languages (Lisp), in order to modernize one of the oldest typesetting systems (TeX). This talk was mostly focused on justifying the technical fitness of Lisp for this task. This time, we would like to take the opposite view and demonstrate a prototype, from the user's perspective. This involves showing what a TiCL document could look like, the implications in terms of typesetting vs. programmatic features, and also in terms of extensibility (relate this to class / style authoring).

Documents

Bibtex (lrde.bib)

@InProceedings{	  verna.13.tug-2,
  author	= {Didier Verna},
  title		= {{TiCL}: the Prototype ({Star \TeX}: the Next Generation,
		  Season 2) },
  booktitle	= {TUGboat},
  issn		= 0896320,
  year		= 2013,
  month		= jan,
  nodoi		= {},
  editor	= {Barbara Beeton and Karl Berry},
  volume	= 34,
  number	= 3,
  abstract	= {At TUG 2012, we presented some ideas about using one of
		  the oldest programming languages (Lisp), in order to
		  modernize one of the oldest typesetting systems (\TeX).
		  This talk was mostly focused on justifying the technical
		  fitness of Lisp for this task. This time, we would like to
		  take the opposite view and demonstrate a prototype, from
		  the user's perspective. This involves showing what a TiCL
		  document could look like, the implications in terms of
		  typesetting vs. programmatic features, and also in terms of
		  extensibility (relate this to class / style authoring). }
}