💾 Archived View for gemini.bunburya.eu › newsgroups › gemini › messages › slrnt0b8lh.2ofh.vlad@happy… captured on 2024-07-08 at 23:51:11. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2022-04-28)

-=-=-=-=-=-=-

Re: Gemini markup extensions [Was: Re: a solution for emphasis]

Message headers

From: Vlad Markov <vlad@happy.dwarf7.net>

Subject: Re: Gemini markup extensions [Was: Re: a solution for emphasis]

Date: Thu, 10 Feb 2022 23:41:37 -0000 (UTC)

Message-ID: <slrnt0b8lh.2ofh.vlad@happy.dwarf7.net>

Message content

On 2022-02-07, Winston <wbe@UBEBLOCK.psr.com.invalid> wrote:

Winston <wbe@UBEBLOCK.psr.com.invalid> writes:
> "*SURPRISE*!!" would match (assuming word separation),
> "Please be _very_ careful." would contain <u>very</u>.
As I used Gnus to view the article I just posted, I see that Emacs shows
the "*SURPRISE*" in bold with the asterisks, and shows the _very_ as
underlined without its leading and trailing underscores. It did
not, however, show the *a*b*c*d* in bold, so that differs from what I
suggested.
So another alternative would be to adopt what Emacs does.
-WBE

I do not think any more rendering directives should be added to gemini.

If more advanced rendering is required then use a pdf document A gemini

URL can point to a pdf document. There is little value in recreating

HTML in gemini.

Related

Parent:

Re: Gemini markup extensions [Was: Re: a solution for emphasis] (by Winston <wbe@UBEBLOCK.psr.com.invalid> on Mon, 07 Feb 2022 10:02:45 -0500)

Start of thread:

a solution for emphasis (by Gustaf Erikson <gerikson@gmial.com> on Sat, 05 Feb 2022 00:13:15 +0100)

Children:

Re: Gemini markup extensions [Was: Re: a solution for emphasis] (by Jason McBrayer <jmcbray@carcosa.net> on Fri, 11 Feb 2022 09:17:17 -0500)