develooper Front page | perl.perl5.porters | Postings from January 2022

Re: Pre-RFC: images in Pod

Thread Previous | Thread Next
From:
Yuki Kimoto
Date:
January 7, 2022 04:43
Subject:
Re: Pre-RFC: images in Pod
Message ID:
CAExogxOxn2CJ55M2esKPU=WCk2XXjZWSJjwWqFG-Lf-MR4Pmmg@mail.gmail.com
2022-1-7 11:20 Dan Book <grinnz@gmail.com> wrote:

> On Thu, Jan 6, 2022 at 9:01 PM Yuki Kimoto <kimoto.yuki@gmail.com> wrote:
>
>>
>> 2021-11-16 19:18 Paul "LeoNerd" Evans <leonerd@leonerd.org.uk> wrote:
>>
>>>
>>>   P<A little logo|http://url-to-my/logo.png|64x48>
>>>
>>>
>> I have an idea to customize the width and height of the image.
>>
>> In the current idea the first thing is the "alt" attribute, and the
>> second is URL.
>>
>> P<A little logo|http://url-to-my/logo.png|64x48>
>>
>> If it is changed to the following.
>>
>> P<alt:"A little logo",width:64,height:48|http://url-to-my/logo.png
>> <http://url-to-my/logo.png%7C64x48>>
>>
>
> This seems more complex (does order matter? parsers need to ignore unknown
> keys, additional escape mechanisms and delimiting rules are needed for the
> alt text which don't have any precedent currently). I think the idea of
> three sections in the style of existing directives is fine.
>
> -Dan
>

Dan

OK.

My concern is, to be honest, that P <> is actually implemented.

It is desirable to be flexible even if it is a little complicated because
there is actual demand.

- width
- height
- max-width
- alt
- display(block)

For example,

  =begin html

  <img alt="Foo" style="max-width:100%; width:640px; display:block;">

  =end html

Is there an implementation proposal we can agree on to proceed to pre-RFC?

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