Marc
I opened the link on two different devices,
to see how the tables rendered.
On one (iPod touch with Safari), it worked reasonably.
The only problem was that the table columns were skewed
due to browser not using monospace fonts. Were the table more complex
or were there some truly wacky
That would work too. I added a third URL that returns
text/plain;format=fixed;line-length=72
http://ietf.implementers.org/fixed/rfc5928.txt
That is the worst option for my two devices.
On both devices the line wraps distort the tables beyond recognition.
Y(J)S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/28/2011 01:52 AM, Yaakov Stein wrote:
Marc
I opened the link on two different devices,
to see how the tables rendered.
On one (iPod touch with Safari), it worked reasonably.
The only problem was that the table columns were skewed
due
On 2011-11-27 17:20, Marc Petit-Huguenin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The problem here is that RFC and Internet-Drafts are not plain ASCII. They are
technically in a special format that I would call line-printer ready text
file, and ASCII is the encoding, not the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/28/2011 01:58 AM, Yaakov Stein wrote:
That would work too. I added a third URL that returns
text/plain;format=fixed;line-length=72
http://ietf.implementers.org/fixed/rfc5928.txt
That is the worst option for my two devices.
On both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The problem here is that RFC and Internet-Drafts are not plain ASCII. They are
technically in a special format that I would call line-printer ready text
file, and ASCII is the encoding, not the format. What is needed is:
- - A mime-type for
--On Sunday, November 27, 2011 08:20 -0800 Marc Petit-Huguenin
petit...@acm.org wrote:
The problem here is that RFC and Internet-Drafts are not plain
ASCII. They are technically in a special format that I would
call line-printer ready text file, and ASCII is the
encoding, not the format.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/27/2011 10:36 AM, John C Klensin wrote:
--On Sunday, November 27, 2011 08:20 -0800 Marc Petit-Huguenin
petit...@acm.org wrote:
The problem here is that RFC and Internet-Drafts are not plain
ASCII. They are technically in a special
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/27/2011 11:20 AM, Marc Petit-Huguenin wrote:
On 11/27/2011 10:36 AM, John C Klensin wrote:
--On Sunday, November 27, 2011 08:20 -0800 Marc Petit-Huguenin
petit...@acm.org wrote:
The problem here is that RFC and Internet-Drafts are not
--On Sunday, November 27, 2011 11:20 -0800 Marc Petit-Huguenin
petit...@acm.org wrote:
On 11/27/2011 10:36 AM, John C Klensin wrote:
--On Sunday, November 27, 2011 08:20 -0800 Marc Petit-Huguenin
petit...@acm.org wrote:
The problem here is that RFC and Internet-Drafts are not
plain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/27/2011 11:38 AM, John C Klensin wrote:
--On Sunday, November 27, 2011 11:20 -0800 Marc Petit-Huguenin
petit...@acm.org wrote:
On 11/27/2011 10:36 AM, John C Klensin wrote:
--On Sunday, November 27, 2011 08:20 -0800 Marc
On 27 November 2011 20:38, John C Klensin john-i...@jck.com wrote:
I'm willing to write up either an extension/update to RFC3676 or
a new subtype if there is enough expression of interest (not
just the two of us) to indicate that such a proposal would be
likely to go somewhere.
As Gmail web
12 matches
Mail list logo
