Re: Pod::Simple output as POD
[email protected] (John SJ Anderson) Tue, 8 May 2018 15:48:35 -0700
| Newsgroups | perl.pod-people |
|---|---|
| Message-ID | <[email protected]> |
> On May 7, 2018, at 21:52, Karl Williamson <[email protected]> = wrote: >=20 > And I'm running into something that I know I had not previously gotten = as far as (which is encouraging), and I'm writing now for counsel. >=20 > What to do about input files that are encoded in some alien encoding, = like Japanese 2202? The Pod::Simple docs say it translates the pod into = perl's internal representation. But should the extracted pod also be in = perl's representation, or should it be translated back to the original = encoding? The second way would be a way to really extract the pod = portions of the original. >=20 > But I'm thinking it should be perl's, so that downstream modules can = use it as-is. But I'm open to other reasoned opinions I suspect the plea for counsel was more intended for David, but I=E2=80=99= ll pipe up from the peanut gallery and say, =E2=80=9Cwhy not both?=E2=80=9D= It seems like the ideal thing to put under a feature flag.=20 Of course, that just changes this decision into =E2=80=9Cwhich one = should be the default and which one should need to be enabled?=E2=80=9D, = but perhaps thinking about it in those terms will make it more clear = which has the higher utility value?=20 j.=