[P4-design] Converting P4_16 spec to html
jnfoster at cs.cornell.edu
Wed Oct 19 12:08:37 EDT 2016
I agree that having a textual markup format would work better for frenetic
editing by a larger group.
I would support porting the spec and am happy to help with the execution if
we decide to do it.
LaTeX or Markdown could work well. Daan Leijn's Makado framework is also
pretty slick (
On Wed, Oct 19, 2016 at 8:57 AM, Chris Dodd <chris at barefootnetworks.com>
> I think that would be even worse than word for seeing diffs and merging
> stuff, as html is unreadable without tools and tools tend to randomly munge
> If we want something that is diff-able and merge-able, latex is basically
> the only choice.
> On Wed, Oct 19, 2016 at 8:48 AM, Mihai Budiu <mbudiu at vmware.com> wrote:
>> Would it be a good idea to convert the spec to html + css? This would
>> make it easier to see diffs and accept contributions on github – especially
>> these days there are a lot of small edits. The html would probably have to
>> be hand-written and edited, since most tools generate very complicated
>> structures. I imagine there would be some significant one-time effort
>> converting from word.
>> Also, an html spec is easier to share on the web. However, html is
>> probably not as pleasant to convert to pdf.
>> P4-design mailing list
>> P4-design at lists.p4.org
> P4-design mailing list
> P4-design at lists.p4.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the P4-design