LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Transfer-Encoding:
7bit
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
From:
Joseph Wright <[log in to unmask]>
Date:
Sat, 7 Mar 2009 19:21:20 +0000
Content-Type:
text/plain; charset=ISO-8859-1
MIME-Version:
1.0
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments:
text/plain (44 lines)
Hello all,

I've made the following suggestion to the TUG Summer of Code list.  Any
thoughts? (I should add that I'm implicitly volunteering to mentor the
idea if there is a taker.)

Joseph

-------- Original Message --------
Subject: [tug-summer-of-code] Project idea: LaTeX3 "microkernel"
Date: Sat, 07 Mar 2009 17:04:24 +0000
From: Joseph Wright <[log in to unmask]>
To: [log in to unmask]

Hello all,

I've proposed in various places a LaTeX3 "microkernel", and I wonder if
this might be an interesting project for the Summer of Code.  The plan
would be to write something based on the existing expl3 code which could
typeset a minimal document:

\documentclass{minimal} % Or something similar
\begin{document}
\emph{Hello World!}
\end{document}

without using LaTeX2e at all. A lot of the work would involve finding
how to re-implement the LaTeX kernel in the expl3 syntax.

At the initial stage, the plan would not be to make major alterations to
the way LaTeX works (a lot of work needs to be done by the team on this
yet). Of course, there are lots of ideas that could be brought to the
project if initial progress was fast (for example, Will Robertson's
suggests about the catcodes of special characters in the document body).

While this would be somewhat separate to the official LaTeX3 work, I'd
hope that the team would be supportive of the idea. It would show up
problems with the current expl3 code, and would hopefully provide some
useful code for the team to eventually use.

Thoughts?
-- 
Joseph Wright

ATOM RSS1 RSS2