>>* pod2text should split in front of `-' in /\s-\S/, not after it, as it
>> does with -F*regexp* in perltoc (item Switches).
>
> That's not really my fault, you know. :-) I'm just using perl's ^<<<
> thingie.
Now I know why I couldn't figure out where the splitting happened...
I've almost never used formats!
Suggestion:
It seems like a more complex $: would be useful. Maybe it could
optionally contain a reference to ["line-break-chars", matching-regexp]
or something like that. I.e.
$: = [" \n-.", '\s|\b.\S|\B.\B'];
would
* always break at space and newline,
* break at "-" and "." chars that are either preceded by a word
and followed by non-whitespace, or surrounded by non-words.
Or maybe the regexp should look at the preceding char, so we can check
both preceding and following char properly. Though a lot of such
regexps would probably have to start with a construct like [\s\S], to
ignore the 1st char.
Regards,
Hallvard
>> does with -F*regexp* in perltoc (item Switches).
>
> That's not really my fault, you know. :-) I'm just using perl's ^<<<
> thingie.
Now I know why I couldn't figure out where the splitting happened...
I've almost never used formats!
Suggestion:
It seems like a more complex $: would be useful. Maybe it could
optionally contain a reference to ["line-break-chars", matching-regexp]
or something like that. I.e.
$: = [" \n-.", '\s|\b.\S|\B.\B'];
would
* always break at space and newline,
* break at "-" and "." chars that are either preceded by a word
and followed by non-whitespace, or surrounded by non-words.
Or maybe the regexp should look at the preceding char, so we can check
both preceding and following char properly. Though a lot of such
regexps would probably have to start with a construct like [\s\S], to
ignore the 1st char.
Regards,
Hallvard