On 14 September 2012 17:30, Daniel Holth <dholth at gmail.com> wrote: > we strongly recommend it be named as README.* and be > utf-8 encoded text. I'd very strongly recommend that the encoding should be mandated. I'm happy with UTF-8 (although I expect a lot of "accidental" latin-1 files, particularly from Windows users) but I think it would be a mistake to have the specification leaving the encoding of *any* string data unclear. Without the encoding being specified, either in the metadata itself ("Description-File-Encoding: utf8"? Please, no) or by the specification mandating it, how is a program expected to read the description? Other than this point, I have no opinion on the proposal. Paul.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4