Add quotes to the RFC #16

Closed
opened 7 months ago by Supernova · 5 comments

What about using quotes in a reply, on the next line below the link to the source tinylog? For example:

## 2021-07-12 18:00 EDT

=> gemini://gmi.bacardi55.io/tinylog.gmi Re: @bacardi55 2021-07-12 22:34 CEST
> gtl is not compatible with hedy's tinylog because he uses many line break.
First, I'm testing out how a quote would work in a tinylog.  Does this help give some context without needing to always go back to the original source?  Is it helpful?
Second, replying to the actual subject quoted; couldn't you just ignore empty lines?

See in practice:
gemini://tilde.team/~supernova/tinylog.gmi

image

What about using quotes in a reply, on the next line below the link to the source tinylog? For example: ``` ## 2021-07-12 18:00 EDT => gemini://gmi.bacardi55.io/tinylog.gmi Re: @bacardi55 2021-07-12 22:34 CEST > gtl is not compatible with hedy's tinylog because he uses many line break. First, I'm testing out how a quote would work in a tinylog. Does this help give some context without needing to always go back to the original source? Is it helpful? Second, replying to the actual subject quoted; couldn't you just ignore empty lines? ``` See in practice: gemini://tilde.team/~supernova/tinylog.gmi ![image](/attachments/014ad31c-f2e8-45b9-9e67-123c386be54d)
Owner

Hi,
Thanks for the feedback.
Although, I'm not sure I understand?
Quotes can definitely be used in tinylog entry in any line of the content. If you look at my tinylog, there are many quote blocks (starting with ">"):
gemini://gmi.bacardi55.io/tinylog.gmi

But maybe I misunderstood your point?

Regarding your response to your second point. Yes, i'll improve the parser soon to make it more robust. First version is aligned almost "too closely" to the rfc.

Hi, Thanks for the feedback. Although, I'm not sure I understand? Quotes can definitely be used in tinylog entry in any line of the content. If you look at my tinylog, there are many quote blocks (starting with ">"): gemini://gmi.bacardi55.io/tinylog.gmi But maybe I misunderstood your point? Regarding your response to your second point. Yes, i'll improve the parser soon to make it more robust. First version is aligned almost "too closely" to the rfc.
Owner

FYI, your tinylog entry with quote formated in gtl as well (previous capture was from Lagrange)
Are you expecting something different?

FYI, your tinylog entry with quote formated in gtl as well (previous capture was from Lagrange) Are you expecting something different?
Poster

OK I wasn't sure if it would work, there was no mention of quoting in the RFC. Maybe adding a quote to one of the examples at the bottom just to mention that quoting is possible and should be rendered by clients the same as the gemini spec.

For that matter, what about third level headers (###), bullets (*) and code (```)? Might be a good idea to mention these as well. Since (#) and (##) have special purposes in tinylog those cannot be used in the content sections but the others can.

OK I wasn't sure if it would work, there was no mention of quoting in the RFC. Maybe adding a quote to one of the examples at the bottom just to mention that quoting is possible and should be rendered by clients the same as the gemini spec. For that matter, what about third level headers (###), bullets (*) and code (```)? Might be a good idea to mention these as well. Since (#) and (##) have special purposes in tinylog those cannot be used in the content sections but the others can.
Owner

Tinylog is still a text/gemini format and thus you can indeed use ### or ```, lists or whatever.

It is then the role of the browser/client to display them correctly.

I'm going to leave this ticket open until I commit a change that will be more explicit about this.

Tinylog is still a text/gemini format and thus you can indeed use ### or ```, lists or whatever. It is then the role of the browser/client to display them correctly. I'm going to leave this ticket open until I commit a change that will be more explicit about this.
Poster

Yes, I think that is the best course, to just mention somewhere in the spec that all gemini formatting can be used normally except for # and ## which must only be used for specific purposes in the tinylog format. Thanks for your consideration.

Yes, I think that is the best course, to just mention somewhere in the spec that all gemini formatting can be used normally except for # and ## which must only be used for specific purposes in the tinylog format. Thanks for your consideration.
bacardi55 referenced this issue from a commit 6 months ago
bacardi55 closed this issue 6 months ago
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.