The raku compiler allows for what you want. It is the Pod render module that has to do this work. SO....

I've just re-written Pod::To::HTML. It's in Raku::Pod::Render (Note the Raku at the beginning, I also wrote another module with almost the same name that doesn't do this).

The legacy Pod::To::HTML (which is Pod::To::HTML:auth<github:Raku> ) does all of the HTML rendering hardcoded. Essentially, I took out all the output-specific and put it into templates.

So, now you can put something like '=Figure' (or '=MyWonderfulBlock') into your pod6 file, and define a template as 'figure' (or 'mywonderfulblock') with custom output formating, eg. '<img src="mylogo" width="100px">') and it will work.

Also, you can create your own Format Codes, so F<fa-business-card> could be made to embed font-awesome icons into pod6 files.

Also, the Raku::Pod::Render distribution has a GUI tool called Extractor.raku that will take any pm6 file and extract the Pod6 and format it into README.md or .html files.

Sorry for shameless ad

On 02/09/2020 03:02, Vadim Belman wrote:
Unfortunately, neither rendered constraints nor image insertions are 
implemented yet. Or it is so up to my knowledge, at least. I miss these 
features too sometimes.

Best regards,
Vadim Belman

On Aug 31, 2020, at 6:56 AM, Fernando Santagata <nando.santag...@gmail.com> 
wrote:

Hello *,

I was wondering whether there's a way to tell that a section of pod6 should be 
rendered only by a specific renderer.

My problem is that I want to show a figure in a README.md and I'm using 
App::MI6, which builds the README.md file from the pod6 documentation in the 
module file.

As far as I can tell, there's no specific pod6 formatter for a figure; so far I 've 
beeninserting raw markdown lines in the pod6 documentation, such as 
"![description](file.svg)", but it's ugly and it would show when other 
renderers will be used on the same pod6 file.

Is there a way to restrict some text to just one renderer, or to insert a 
figure or picture in a pod6 file?

--
Fernando Santagata

Reply via email to