[rfc-i] RFC "source" format

Joe Touch touch at ISI.EDU
Thu Oct 9 08:44:21 PDT 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Dave CROCKER wrote:
...
> Hence, unfortunately, we have to distinguish between "submission"
> formats" and "publication input" format, as well as input vs. output.
> And the process of going from submission to publication input is not
> fully automated and often is quite labor-intensive.

While that is important, it is not relevant to the proposal to
transition from .txt to UTF-8.

> My interest in having the RFC Editor more formally and thoroughly
> embrace xml2rfc is that it permits generation of multiple presentation
> formats from a single source. 

So now you're adding yet another format to discuss:

	author source format

	submission format

	RFC Editor internal format

	archival format

	supplemental format (whether RFC Editor-generated or not)

I thought we were only discussing archival format, which currently
matches at least one submission format - and I would presume this would
follow if we went to UTF-8.

I don't care what the RFC Editor uses internally, so long as they accept
submissions in the same format as are archival.

Joe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjuJtUACgkQE5f5cImnZrtUGgCfS3WFNOWmKB7br/LCQDcCbCqa
QEUAoIGdLdXjA0dqSDnW/4k+8lyhFxva
=Jl2s
-----END PGP SIGNATURE-----


More information about the rfc-interest mailing list