💾 Archived View for rawtext.club › ~sloum › geminilist › 000332.gmi captured on 2020-11-07 at 01:25:00. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Text reflow woes (or: I want bullets back!)y

Michael Lazar lazar.michael22 at gmail.com

Thu Jan 16 20:38:23 GMT 2020

- - - - - - - - - - - - - - - - - - - ```

On Thu, Jan 16, 2020 at 12:41 PM Aaron Janse <aaron at ajanse.me> wrote:
>
> On Thu, Jan 16, 2020, at 7:10 AM, solderpunk wrote:
> 
> Then again, making text/gemini easy to write with "normal" editors
> 
> arguably isn't worth much if the next step is anyway "now use sftp or a
> 
> git push to get your content on the server".
>
> In my experience, though, hard-wrapping text doesn't work well with git
> anyway. And I don't know of any text editors that re-hard-wrap automatically
> when the beginning of a paragraph is edited.
>
> Maybe gemini files could be authored in either wrapped or unwrapped format,
> then the server could hard-wrap intelligently before sending it to the
> reader? Would that be bad practice?
>
> Cheers!

I see no reason we can't let each server decide this on a case-by-case basis,based on the needs of their users.

If you're hosting shared gemini content for a group of non-technical users, itmight make sense for your server to automatically reformat gemini files beforesending them. On the other hand, if you're running a home-grown gemini serverand writing all of your own content, this step might be unnecessary or invasiveto your preferred workflow.

If we're adopting the proposed format with ``` for preformatted blocks, therules can be totally ambiguous for server-side line wrapping.

  1. preformatted blocks are not touched by the server  2. links are not touched by the server  3. everything else can be wrapped by the server to the preferred width

Content authors should not expect their non preformatted text to have linelengths / indents / etc. preserved.

- mozz