Skip Menu |

This queue is for tickets about the Text-Extract-MaketextCallPhrases CPAN distribution.

Report information
The Basics
Id: 98322
Status: new
Priority: 0/
Queue: Text-Extract-MaketextCallPhrases

People
Owner: Nobody in particular
Requestors: dmuey [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: document how to do '## no extract maketext' in POD
Based on: http://perldoc.perl.org/perlpod.html http://perldoc.perl.org/perlpodspec.html http://docstore.mik.ua/orelly/perl3/prog/ch26_01.htm I think we should go with the “null (zero-effect) formatting code”, Z<>, (i.e. Z<## no extract maketext>) because: 1. It is “A zero-width character” (i.e. it is not displayed) that “is nice for putting in front of sequences that might confuse something”. I’d call “## no extract maketext (for POD)” a sequence that might be confusing :) 2. The only caveat is that “it should have no content” so “a processor may complain” but regardless the “text should ignored” (i.e. it is not displayed). 3. But being able to hide the notation in rendered docs far outweighs a possible warning during rendering and its much less of a stretch than misusing the indexing code (X<>) to achieve the same results. 4. If POD ever has a proper inline-comment format we can change to that w/ a quick perl pie ;)
FWIW, we can’t address by just removing POD first because: a. it is syntax agonistic (it is currently used to parse perl, TT, JS, a few custom formats, and python that I know of). b. that would throw off the line/offset data. (although we could skip lines that are POD but that would make the parser that much more complex. c. what if you wanted to extract the phrases that are in the POD? doof keep it simple and let the programmer do what they mean instead of having a stupid computer guess badly same principle as not stripping comments first …
Show quoted text
> 2. The only caveat is that “it should have no content” so “a processor > may complain” but regardless the “text should ignored” (i.e. it is not > displayed).
It is considered an error by POD::Checker, seeing what we can do via https://rt.cpan.org/Ticket/Display.html?id=98326
Also: =head1 token can be done w/ =head1 toZ<>ken and: 1. T::E::M will skip it 2. display correctly 3. POD::Coverage sees it as documentation for 'token' still and not 'toZ<>ken' the only downside is its a little terse but a comment at the top explaining it (link to T::E::M section about it) would solve that …