Le lundi 28 d?cembre 2020, 14:16:27 CET Philip Linde a ?crit : > I understand the need for other document types to take other character > encodings. For example, I have a collection of old text files in IBM437 > encoding. For text/gemini, we pretty much have a blank slate, though, > and I see no reason that it should extend to support arbitrary > encodings when limiting to UTF-8 creates a much simpler situation for > implementers and is already the unspoken standard. The main reason I see for authorizing other encodings is to be future proof. When people designed old protocols they thought ASCII was here to stay. So, I think we should learn from the past and not set in stone that all files must use utf-8, maybe something else will arise and be better for some unsuspected reason, and people will want to use that. C?me
---
Previous in thread (1 of 29): 🗣️ Philip Linde (linde.philip (a) gmail.com)
Next in thread (3 of 29): 🗣️ Solderpunk (solderpunk (a) posteo.net)