[rfc-i] IETF RFC format <-> W3C pubrules

Phillip Hallam-Baker hallam at gmail.com
Wed May 9 09:17:09 PDT 2012

We can certainly do everything with tex that we can do with HTML and
everything we want with HTML.

Problem with TeX is that it is a Turing complete language which means
that it provides way more flexibility than we would want. I would
expect that we ended up using LaTeX which is not quite the same thing.

For my thesis I had examples in TeX that compiled and executed during
the document production process. That is baaaaad precedent.

On Wed, May 9, 2012 at 12:01 PM, Joe Hildebrand <jhildebr at cisco.com> wrote:
> On 5/9/12 9:40 AM, "Phillip Hallam-Baker" <hallam at gmail.com> wrote:
>> Note: a third non responsive response.
>> Are you actually going to answer the question?
>> What are the other formats that you think should be considered and why?
> https://datatracker.ietf.org/meeting/83/materials.html#wg-rfcform
> - Just add UTF-8
> - Just add URLs
> - TeX input
> - PDF/A
> Note: Personally, I think all of these but the TeX input do not meet the
> requirements for which we're starting to see a little bit of emerging
> consensus.  I'm only interested in the HTML output of the TeX input, to
> ensure that it meets the requirements.  As such, TeX could be just one more
> precursor toolchain for those that like it.
> --
> Joe Hildebrand

Website: http://hallambaker.com/

More information about the rfc-interest mailing list