💾 Archived View for bbs.geminispace.org › u › mozz › 940 captured on 2023-09-28 at 19:20:39. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-09-08)
-=-=-=-=-=-=-
Re: "[gemini link] Visual Gemtext Primer I created a visual..."
Consecutive blank lines wonʼt be compacted into one.
I agree with you on this one. It's tempting to treat consecutive plain gemtext lines like a markdown paragraph, and normalize whitespace between "paragraphs" and other elements such as headings. But gemtext doesn't have semantic paragraphs, and grouping consecutive lines together that way feels like a misinterpretation of the spec to me.
For example, these two snippets should be rendered differently.
# Heading Hello
# Heading Hello world
The same argument applies to consecutive quote lines and bullet lines, which should not be grouped into a single semantic list or quote. But it's very familiar to want to treat them like <ul> and <blockquote> tags so that's what ends up happening.
2023-05-24 · 4 months ago
@lufte With Gemini repo, do you mean
— https://gitlab.com/gemini-specification
It is not linked from gemini.circumlunar.space and seems to be outdated. Spec is v0.15.0 vs. v0.16.1.
@mozz I'm not sure I understand what you mean. I'm pro context-free rendering. So compacting multiple lines would be bad.
What I meant was inline whitespace. What happens to a text line, where I have two spaces in a row? What happens with quotes regarding ">" vs. "> "? In this case, Geopard, the Gnome-native Gemini browser, used to indent a quote by a space, but the wrapped line beginning was not indented.
FYI, I updated the parts for headings and quote regarding whitespace.
@michaelnordmeyer Huh, I did mean that repo but I didn't know it was abandoned. It looks like work is happening in another repo or privately.
@mozz I'm not sure I understand what you mean. I'm pro context-free rendering. So compacting multiple lines would be bad.
Right, I think we're on the same wavelength here. I was just elaborating my thoughts behind it for the sake of discussion.
What I meant was inline whitespace. What happens to a text line, where I have two spaces in a row? What happens with quotes regarding ">" vs. "> "? In this case, Geopard, the Gnome-native Gemini browser, used to indent a quote by a space, but the wrapped line beginning was not indented.
My take on how it 'ought to be matches the implementation that you are describing for Geopard. That's how I did it on my proxy server. For example, the quote on this page preserves the leading whitespace, but does not indent wrapped lines.
https://portal.mozz.us/gemini/astrobotany.mozz.us/
2023-05-25 · 4 months ago
@lufte Found the current repo. It was a little hidden in the official FAQ: git://gemini.circumlunar.space/gemini-site
@michaelnordmeyer:
What happens to a text line, where I have two spaces in a row?
The specification says that spacing in text lines can be normalized, so it's up to the client what happens there. The spaces can be normalized to one space, or they can be kept as multiple.
@skyjake The exact wording is not excatly clear. From the spec:
For example, variable width fonts may be used, spacing may be normalised, with spaces between sentences being made wider than spacing between words, and other such typographical niceties may be applied.
It can also mean, that just the space between sentences can be varied with unicode spaces of different length.
Given that Gemini is a modernized Gopher, and Solderpunk uses tabs to align his links, normalization of inline whitespace could very well be the goal.
[gemini link] Visual Gemtext Primer I created a visual Gemtext primer some months ago to spot the difference in the rendering of Gemtext pages with different browsers. Today I added a section at the bottom, because some clients behave differently and the spec is not very clear about this. What's your take?
💬 michaelnordmeyer · 11 comments · 1 like · 2023-05-24 · 4 months ago