Yaakov Stein schrieb:
I would say that getting always the same printout is a non-goal.
Why? As has been stated previously, in most SDOs the "printed page"
is the final word. One of the many inconveniences of xml2rfc is the need
to add "vspace blankLines" to avoid unfortunate page breaks.
Be
> I would say that getting always the same printout is a non-goal.
Why? As has been stated previously, in most SDOs the "printed page"
is the final word. One of the many inconveniences of xml2rfc is the need
to add "vspace blankLines" to avoid unfortunate page breaks.
>You're comparing apples a
[ follow-ups to IETF discussion list please]
Of the three possible ways forward suggested by this draft, I think that
the only one that's likely to get done is this one:
1. Agree that, apart from day to day efforts to improve efficiency,
the problems with the existing standards track a
Date:Sat, 17 Jun 2006 21:40:06 -0700
From:Joe Touch <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
| That's a problem when it changes page numbers (which end up being as
| useful as semantic tags) or figures. Or (as importantly) template or
| boilerplate tex
On Jun 15, 2006, at 9:13 AM, Keith Moore wrote:
PDF used to be a free (as in beer), well-documented, relatively
unencumbered, reasonably portable format. Nowadays there are a
number of compatibility problems between generators and viewers,
which appear to be mostly due to Adobe's introduc
Stephane Bortzmeyer wrote:
> On Fri, Jun 16, 2006 at 03:46:16PM -0700,
> Joe Touch <[EMAIL PROTECTED]> wrote
> a message of 85 lines which said:
>
>> - edit source code (argh - back to the stone age)
>
> I always assumed that most people involved in IETF edit source code
> daily (I did
Clement Cherlin schrieb:
...
Unicode Box Drawing
┌┐
│ This is a box │
├┤
│With another box│
│ underneath │
└┘
...
I like that. In fact I like it so much that I did add some machinery to
rfc2629.xslt that helps in producing those (based on e
Yaakov Stein schrieb:
How about Tex?
It is as old as the internet and you can use vi to read and edit.
You still can use grep to scan all old documents to find something.
It is also the only method to always get precisely the same printout,
has the best equation typesetting, makes perfectl
> How about Tex?
> It is as old as the internet and you can use vi to read and edit.
> You still can use grep to scan all old documents to find something.
It is also the only method to always get precisely the same printout,
has the best equation typesetting, makes perfectly good diagrams,
and
> From: Iljitsch van Beijnum [mailto:[EMAIL PROTECTED]
> There is a slight difference here: the earth hasn't seen any
> successful demolishion attempts in the last 4.5 billion
> years, while nearly any word processing document format from
> the 1990s can't be read properly. In many cases the t
On 18-jun-2006, at 16:20, Hallam-Baker, Phillip wrote:
It's not _that_ bizarre. Suppose that we decide to allow
publishing RFCs in PDF only. Suppose that within the next few
years some company comes up with a replacement for PDF that
is better is some important regard so that everyone switches
t
Dear IESG Members,
1. The proposed Draft is not about matching (it is absurd to say
that my Italian can "match" your Japanese in order for us to
understand each other better). It is about using pattern matching
techniques in order to filter lists against a langtag with two
results (max one a
On Fri, Jun 16, 2006 at 03:46:16PM -0700,
Joe Touch <[EMAIL PROTECTED]> wrote
a message of 85 lines which said:
> - edit source code (argh - back to the stone age)
I always assumed that most people involved in IETF edit source code
daily (I did not say "full-time", I said "at least daily
Peter Dambier schrieb:
>...
Unicode Box Drawing
??
? This is a box ?
??
?With another box?
? underneath ?
??
There were no boxes but a peculiar line below.
...
> From: Iljitsch van Beijnum [mailto:[EMAIL PROTECTED]
> It's not _that_ bizarre. Suppose that we decide to allow
> publishing RFCs in PDF only. Suppose that within the next few
> years some company comes up with a replacement for PDF that
> is better is some important regard so that everyone
On 18-jun-2006, at 13:23, Hallam-Baker, Phillip wrote:
Show me a PDF viewer written by a 16-year-old in BASIC, or
whatever it is that bored kids write software in these days.
I am more concerned about making a document readable and
intelligible by a 16 year old doing a high school class than
Clement Cherlin wrote:
On 6/17/06, Eliot Lear <[EMAIL PROTECTED]> wrote:
I do think that ASCII art has its limits, particularly when it comes to
mathematics. But I think a more gradual evolution is called for in this
case, with more consideration given to not only the normative issue but
all
> From: Jeffrey Hutzelman [mailto:[EMAIL PROTECTED]
>
> ... and, you've completely missed the point.
>
> Currently, RFC's are published and distributed in a form
> which is so straightforward that a child could write software
> to view or produce it.
>
> Show me a PDF viewer written by a 16-
On 6/17/06, Eliot Lear <[EMAIL PROTECTED]> wrote:
I do think that ASCII art has its limits, particularly when it comes to
mathematics. But I think a more gradual evolution is called for in this
case, with more consideration given to not only the normative issue but
all the others Joel raised.
On 17-jun-2006, at 16:59, Eliot Lear wrote:
I do think that ASCII art has its limits, particularly when it
comes to
mathematics.
I'm pretty sure I read as many RFCs as the next IETF participant
(well, the ones that don't have a three or four letter acronym
starting with "I" in their job
20 matches
Mail list logo
