I can't find any reference that just shows some example Gemini markup page sources. I am confused by the => vs [..|..] link markup. I was just going to throw up a server on sdf and see, but im not ready to depend that kind of time on it yet. The Gemini project web page would be improved if you showed what gemini looks like, IMO. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
On Mon, May 18, 2020 at 11:21:53AM -0700, peteyboy at sdf.org wrote: > I can't find any reference that just shows some example Gemini markup page sources. I am confused by the => vs [..|..] link markup. I was just going to throw up a server on sdf and see, but im not ready to depend that kind of time on it yet. The Gemini project web page would be improved if you showed what gemini looks like, IMO. Well, there are several examples of the link syntax in the specification. But you make a good point: having a single, short example text/gemini document which fits on a single screen and shows off all the supported features in a clear and beginner-friendly way would be a really useful thing to have. If anybody wants to write one and send it to me, I'll gladly put it in the documentation folder of the project page. I might also update the FAQ to make it very clear that text/gemini is
Here's my attempt: # Heading 1 ## Heading 2 ### Heading 3 Paragraphs and text are written normally. They are wrapped, so one paragraph should be written on one line. This line is part of the same paragraph This line will not be added to the ones above, it will always be on a new line. Spaces are not collapsed, there will always be two spaces above. => gemini://example.com/ Link text here => gemini://example.com/link/with/no/text =>gemini://example.com/ Spaces after the => is optional There are no inline links. ``` Preformatted text goes inside backticks, similar to markdown. Another line. ``` There can also be unordered lists, using an asterisk:
Isn't document text all treated as "pre-formatted" anyway? -- gemini://kwiecien.us/
No, clients are free to format it, wrap it, apply fonts and colours, etc. If it was preformatted, then links wouldn't work, for example. There's a difference between this: => gemini://gus.guru/ GUS and this: ``` => gemini://gus.guru/ GUS ``` In the second one, a client will not form a link, it will just show the raw text. It should also show the text in a monospace font, whereas it might apply some other font for the first example. makeworld ??????? Original Message ??????? On Monday, May 18, 2020 3:44 PM, Ben <benulo at systemli.org> wrote: > Isn't document text all treated as "pre-formatted" anyway? > > ----------------------------------------------------------- > > gemini://kwiecien.us/
On 5/18/20 6:59 PM, colecmac at protonmail.com wrote: > Paragraphs and text are written normally. They are wrapped, so one paragraph should be written on one line. This line is part of the same paragraph > This line will not be added to the ones above, it will always be on a new line. Did we do this part in the spec? I know we have the ``` for preformatted, but I thought all other text was up to the client. If someone wanted to write in an editor that hard-wraps to 80col, that text would still reflow in clients that reflow.
It is part of the spec, to my understanding. Section 1.3.5.3.1 (jeez) states: > Text lines which are longer than can fit on a client's display device SHOULD be "wrapped" to fit, i.e. long lines should be split (ideally at whitespace or at hyphens) into multiple consecutive lines of a device-appropriate width. This wrapping is applied to each line of text independently. Multiple consecutive lines which are shorter than the client's display device MUST NOT be combined into fewer, longer lines. To me, this is in agreement with what I said before. makeworld
On 5/18/20 7:53 PM, colecmac at protonmail.com wrote: > To me, this is in agreement with what I said before. I stand corrected! That's indeed what the spec says. Please witness as I go change to soft-wrapping in my gmi files! ;D
Ah thanks! I should have known that. To be honest, I wrote my pages with the intention that a monospace font would always be in use. It does seem a common behavior for Gemini clients. On 5/19/20 12:18 AM, colecmac at protonmail.com wrote: > In the second one, a client will not form a link, it will just show the raw text. > It should also show the text in a monospace font, whereas it might apply some > other font for the first example. -- gemini://kwiecien.us/
---