Support reflowed text for gemini #103

Closed
opened 2019-11-28 19:53:51 +00:00 by sloum · 3 comments
Owner

Blocked until consensus is reached by the gemini working group re: how to handle this

At present we are wrapping gemini text. The spec is in flux currently but looks to be rallying around reflowing text and adding syntax to have unflowed lines (whose behavior is still up in the air).

This should NOT get solved until things get settled on. However, I wanted to open this issue in preparation as I had some ideas about how to handle it without disrupting other content:

  • Parse the document, removing all newlines and multiple spaces in any rows that are not links or unflowed rows
  • parse links as normal
  • Pass the resulting document on to client.go as the raw result. This will allow our regular wrapping to function.

Doing things that way will make it so that we do not have to alter any structs or change how wrapping works. It should all just get handled in the gemini module and the result should be wrapable.

**Blocked until consensus is reached by the gemini working group re: how to handle this** At present we are wrapping gemini text. The spec is in flux currently but looks to be rallying around reflowing text and adding syntax to have unflowed lines (whose behavior is still up in the air). This should NOT get solved until things get settled on. However, I wanted to open this issue in preparation as I had some ideas about how to handle it without disrupting other content: - Parse the document, removing all newlines and multiple spaces in any rows that are not links or unflowed rows - parse links as normal - Pass the resulting document on to `client.go` as the raw result. This will allow our regular wrapping to function. Doing things that way will make it so that we do not have to alter any structs or change how wrapping works. It should all just get handled in the gemini module and the result should be wrapable.
sloum added the
enhancement
non-urgent
gemini
rendering
labels 2019-11-28 19:53:52 +00:00
sloum added the
blocked
label 2019-12-01 03:39:17 +00:00
Collaborator

Are unflowed lines the equivalent of

 in HTML?

Are unflowed lines the equivalent of <pre> in HTML?
Author
Owner

Yes :) Right now the default is unflowed (but wrapped). There is no consensus currently regarding how to mark flowed vs unflowed lines nor which should be the default for the protocol. The web flows by default and gopher does not flow by default. I have argued in favor of unflowed by default, but with the ability to do something like this:

This    is    an unflowed line.
  This one too! They allow arbitrary
spaces        and newlines.
.FLOW
This
will   all get   put
into one   line with
no more than  one space separating a word
.UNFLOW

Now   back to   regular!

Note: the .FLOW & .UNFLOW is for communicating the conceptual purpose and not a recommendation for what marker to use.

We'll see what people think and what gets adopted.

Yes :) Right now the default is unflowed (but wrapped). There is no consensus currently regarding how to mark flowed vs unflowed lines nor which should be the default for the protocol. The web flows by default and gopher does not flow by default. I have argued in favor of unflowed by default, but with the ability to do something like this: ``` This is an unflowed line. This one too! They allow arbitrary spaces and newlines. .FLOW This will all get put into one line with no more than one space separating a word .UNFLOW Now back to regular! ``` Note: the `.FLOW` & `.UNFLOW` is for communicating the conceptual purpose and not a recommendation for what marker to use. We'll see what people think and what gets adopted.
Author
Owner

The gemini spec has dropped the proposal for reflowed text in favor of wrapped text and an instruction to just use long lines if you want text treated as a flow group.

This story is being closed in recognition of that.

The gemini spec has dropped the proposal for reflowed text in favor of wrapped text and an instruction to just use long lines if you want text treated as a flow group. This story is being closed in recognition of that.
sloum closed this issue 2020-03-05 05:39:36 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sloum/bombadillo#103
No description provided.