💾 Archived View for rawtext.club › ~sloum › geminilist › 002194.gmi captured on 2020-11-07 at 02:44:33. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Luke Emmet luke at marmaladefoo.com
Sun Jul 12 09:50:22 BST 2020
- - - - - - - - - - - - - - - - - - -
On 10-Jul-2020 17:38, Hannu Hartikainen wrote:
What is the correct mime type or encoding should be used for this?
text/x-ansi seems to be used for ANSI art. That's what
gemini://ansi.hrtk.in/ serves.
Thanks for all your replies
My reading of the situation now is as follows:
ANSI escape sequences should not be interpreted within text/gemini content (after all when would it stop - there could be embedded html or other markup that clients will become expected to interpret). Similarly they should not be stripped out - since how would one know they were there, and should be intepreted rather than just presented. |On a Gemini page I might say something like: "Is this the correct code to make all text black: \033[30m ?" But I dont want to make the rest of my page black by doing so
In terms of where these sequences may be interpreted or stripped out there seem to be 3 candidates:
1. content served as text/x-ansi - e.g. for ANSI art
2. content in a preformatted range with the label indicating it as text/x-ansi - we dont have a semantics or convention for this yet, but it would be nice, like this maybe:
3. content served as some hybrid gemini format like text/gemini+x-ansi I guess the general points of non-extensibility come up - would this become a de-facto expectation for clients to implement? Could there be other formats like text/gemini+html? Best Wishes - Luke|