Hello all,
There seems to be no more contributions to the discussion, so I'd like to ask
for the next step. If I'm to make a patch/pull reuest, what does it take now to
have a green light to have it reviewer and merged?
I understand that there's never a single person authority that does that,
Example of images in pod documents:
Spreadsheet::WriteExcel::Examples
https://metacpan.org/pod/Spreadsheet::WriteExcel::Examples
=begin html
http://homepage.eircom.net/~jmcnamara/perl/images/a_simple.jpg;
width="640" height="420" alt="Output from a_simple.pl" />
=end html
I’m not sure that I understand your argument and it feel a bit of a straw man -
I’m targeting specifically html, latex, and pdf as the graphic backends, and
have in mind markdown and xml as easily supported too. The proposal is that
title and image are always shown together, or always ignored
>
> Hm, using =begin/=end as an extension mechanism is an interesting idea.
> It's unfortunate that limitations in the existing mechanism mean that a
> formatter still has to understand the extension to show the fallback text,
> but that may not be a significant problem.
Agree
> I think there
On Sun, Oct 04, 2020 at 04:15:23PM -0400, Shawn H Corey wrote:
> On 2020-10-04 4:01 p.m., Dmitry Karasik wrote:
> > Indeed, either don't use ":" in "something", or use the full syntax, or we
> > may
> > extend the syntax so that "\:" and "\\" expand to the unquoted symbols.
>
> Use the POD
On 2020-10-04 4:01 p.m., Dmitry Karasik wrote:
Indeed, either don't use ":" in "something", or use the full syntax, or we may
extend the syntax so that "\:" and "\\" expand to the unquoted symbols.
Use the POD escape sequence instead: E<0x3A> and E<0x20>
Also think about this:
=for image
Dmitry Karasik writes:
> 1) Full syntax (somewhat YAML-inspired)
> =begin image
> src: file.png
> title: Figure.1
> comment:
> This is a multi-line
> comment. Must start end end with newline.
> Prefix spaces are skipped.
> resolution: 120
> whatever: value
> text:
>
On Sun, Oct 04, 2020 at 03:29:04PM -0400, Shawn H Corey wrote:
> On 2020-10-04 3:23 p.m., Patrice Dumas wrote:
> > Are spaces ignored between :? Should there be a separator to simplify
> > parsing, like
Spaces are ignored, yes.
> > =for image src:file.png, text:something
> Yes, there will be
On 2020-10-04 3:23 p.m., Patrice Dumas wrote:
Are spaces ignored between :? Should there be a separator to simplify
parsing, like
=for image src:file.png, text:something
Yes, there will be problems with separators since the separator can
appear in the "something".
=for image src:file.png
On Sun, Oct 04, 2020 at 05:11:35PM +0200, Dmitry Karasik wrote:
> Hello
>
> Thank you all for review, it is clear that some things I wasn't focused at
> don't fall in as gracefully as I wanted. So it seems that P<> neither serves
> any good as an inline image anchor, nor versatile enough to
On Sun, Oct 04, 2020 at 11:23:18AM -0400, Shawn H Corey wrote:
> On 2020-10-04 11:11 a.m., Dmitry Karasik wrote:
> > =for image src:file.png
>
> =for image src:file.png [fallback text]
>
> There should be an option for fallback text.
There is, "text:". Or in this case,
=for image src:file.png
On 2020-10-04 11:11 a.m., Dmitry Karasik wrote:
=for image src:file.png
=for image src:file.png [fallback text]
There should be an option for fallback text.
Hello
Thank you all for review, it is clear that some things I wasn't focused at
don't fall in as gracefully as I wanted. So it seems that P<> neither serves
any good as an inline image anchor, nor versatile enough to specity
accompanying text, and will require further additions to pod that would
> I proposed an alternative with title that could be used in text output
> or in any output that cannot render the image. The advantage of my
> proposal is that this would truly be independent of the format. Whereas
> what you propose is actually format specific as one has to handle
> text/man
> Using a formatting code for this seems a bit more complicated than might
> be necessary, since now the formatter needs to know whether the image
> truly should be inline (an emoji), whether it should float, whether it
> should be set off as a figure, etc. Formatting codes imply that this is
>
Dmitry Karasik writes:
> I've proposed addition of images to pod, as discussed at [1], and would
> like to ask for some more discussion here as well The idea is rather
> simple, to introduce a P<> tag in two forms, P and
> P, that would get converted to image in graphic formats,
> and ignored
On Thu, Oct 01, 2020 at 01:44:38PM +0200, Dmitry Karasik wrote:
> The proposal is that title and image are always shown together, or always
> ignored together. For html and others, P<> doesn’t need to be wrapped in
> =begin, that’s the whole point of it to not care about specific format, and
>
On Thu, Oct 01, 2020 at 11:35:45AM +0200, Dmitry Karasik wrote:
> Hello,
>
> I've proposed addition of images to pod, as discussed at [1], and would like
> to
> ask for some more discussion here as well The idea is rather simple, to
> introduce a P<> tag in two forms, P and P, that would
> get
Hello,
I've proposed addition of images to pod, as discussed at [1], and would like to
ask for some more discussion here as well The idea is rather simple, to
introduce a P<> tag in two forms, P and P, that would
get converted to image in graphic formats, and ignored otherwise.
The image URI
19 matches
Mail list logo
