develooper Front page | perl.perl5.porters | Postings from March 2023

Re: perlbug UX

Thread Previous | Thread Next
From:
Zefram via perl5-porters
Date:
March 2, 2023 07:43
Subject:
Re: perlbug UX
Message ID:
ZABTe6f3flHLr/Gu@fysh.org
Dan Book wrote:
>I don't know what you propose to fix it.

I did make recommendations, but to be fair they were buried in a lngthy
message.  I propose that the perlbug template should state, in the
to-be-user-edited portion, what relationship the user input is expected
to bear to the markup language, and should point at a specification for
that markup language.  I also propose that, if the body of the perlbug
output is expected to be a marked-up document, then the headers of the
perlbug output should include the appropriate MIME bits saying so.

>user does not need to know that the user-edited portion will be interpreted
>as markdown, because they are the one who has chosen to paste it into a
>markdown input and will understand that as a GitHub user,

That is true of GitHub users, and is also a point that I made in the
message to which you replied.  My concern is really about the experience
of non GitHub users, who are not themselves putting the perlbug output
into a Markdown context.  They're sending an email message.  (MIME headers
would be a good clue to an email user that the body of the message is
a Markdown context, albeit not which version of Markdown is intended,
but perlbug doesn't show the headers at the editing stage.)

-zefram

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About