[rfc-i] Byte order marks

Joe Touch touch at ISI.EDU
Wed Nov 5 12:40:52 PST 2008

Hash: SHA1

Tony Hansen wrote:
> Some more random thoughts:
> While it would best if we could just say ".txt means utf8", I'm becoming
> convinced that we won't get there. If we went the path of a .utf8 file,
> the .txt file *could* be considered secondary to the .txt and even
> auto-generated from the .utf8. Consider this scenario:
>   *	I-D upload accepts .utf8 files as a primary source
>   *	the .txt version is auto-generated,
> 	o replacing each utf8 sequence with U+####
> 	o add a note somewhere (say, as the very first line) indicating
> 	  that the authoritative version is the UTF8 version
> This could be a potential way forward.

You can replace a UTF-8 with a #, but if you replace it with anything
longer you run the risk of going over the line length limit.


> 	Tony Hansen
> 	tony at att.com
> Tony Hansen wrote:
>> Here's random thought prompted by Paul's inadvertent use of a .utf8
>> extension on his attachment:
>> Just like we can have a .pdf alternative to the .txt file, could we also
>> have a .utf8 alternative to the .txt file?
>> This would allow the .txt files to remain ASCII, while allowing a richer
>> experience to be enjoyed by those who can use the .utf8 version.
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> http://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the rfc-interest mailing list