-- Leo's gemini proxy

-- Connecting to git.thebackupbox.net:1965...

-- Connected

-- Sending request

-- Meta line: 20 text/gemini

repo: gemini-site
action: commit
revision:
path_from:
revision_from: 4893b3ffc332181f56512da2a935d583973bdb61:
path_to:
revision_to:

commit 4893b3ffc332181f56512da2a935d583973bdb61
Author: Solderpunk <solderpunk@sdf.org>
Date:   Mon Feb 3 20:08:57 2020 +0000

    Change text-wrapping section of spec-spec.

diff --git a/docs/spec-spec.txt b/docs/spec-spec.txt

--- a/docs/spec-spec.txt
+++ b/docs/spec-spec.txt
@@ -1,7 +1,7 @@
 -----------------------------
 Project Gemini
 "Speculative specification"
-v0.9.2, October 6th 2019
+v0.10.0, February 3rd 2020
 -----------------------------

 This is an increasingly less rough sketch of an actual spec for
@@ -277,29 +277,42 @@ non-gopher content via a non-standard adaptation of the `h` item-type.

 1.3.5.3 Text display

-While simple Gemini clients are likely to print non-link lines of
-documents verbatim without any regard for the length of the lines
-relative to the length of the client's display, clients MAY optionally
-apply "reflowing" of text so that long lines are shown cleanly on
-narrow displays.  Reflowing should be performed as per the definition
-of the text/enriched media type in RFC 1896: isolated CRLF pairs are
-translated into a single SPACE character, while sequences of N
-consecutive CRLF pairs are translated into N-1 actual line breaks.
-However, care should be taken that link lines are not flowed into
-text: links should always be displayed on lines of their own.  After
-reflowing has been applied, lines of text too long to be displayed on
-a single line on the client's display may be wrapped at the
-appropriate point.
-
-As a result of this optional reflowing, authors of Gemini content
-MUST NOT assume that they have any control over the fine details of
-how their text is displayed.  Authors should avoid producing content
-which critically depends upon assumptions of a particular line width
-or the use of monospaced fonts.
-
-In order to facilitate a comfortable user experience with simple
-clients which do not implement reflowing, authors SHOULD limit the
-width of lines to 78 characters, excluding CRLF pairs.
+Textual content for Gopher is typically "hard-wrapped", i.e. composed
+of lines no longer than (typically) 80 characters.  Each line of text
+is printed to the screen as-is.  In contrast, in HTML content on the
+web, browsers ignore the length of lines of text and instead "reflow"
+text to a width appropriate for the display device - lines of text in
+a HTML file which are "too long" get split up, while consecutive
+lines which are "too short" get joined together.  Gemini adopts a
+strategy between these two approaches, designed to strike a balance
+between implementation complexity, flexibility of display width, and
+support for common text formatting patterns.
+
+Lines of text in a text/gemini document which are not link lines (i.e.
+do not begin with "=>") 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.  Recall that text/gemini
+processing is strictly line-based: the above 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.
+
+Blank lines receive no special treatment: they are ordinary text
+lines, with a display length of zero.  Thus, they fit on any
+client's display device and never need to be wrapped.  Each
+individual blank line in a text/gemini document MUST be rendered by
+the client as an individual blank line.
+
+In order to take full advantage of this method of text formatting,
+uthors of text/gemini content SHOULD avoid hard-wrapping to a
+pecific fixed width.  Most text editors can be configured to
+"soft-wrap", i.e. to write this kind of file while displaying the long
+lines wrapped to fit the author's display device.
+
+Authors who insist on hard-wrapping their content MUST be aware that
+the content will display neatly on clients whose display device is as
+wide as the hard-wrapped lenth or wider, but will appear with
+irregular line widths on narrower clients.

 1.4 TLS

-- Response ended

-- Page fetched on Sun Jun 2 14:28:18 2024