New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pod::HTML should use a proper Unicode-aware definition of "word character" #12026
Comments
From horton-p@aist.go.jpBackground: Tom Christiansen asked me to report the following as Symptom: When running pod2html on files with non-ascii characters in link anchor names, Workaround: In Pod/Html.pm, comment out line containing "$anchor =~ s/\W/_/g;" Perl Info
|
From @rjbsThere's a Google Summer of Code proposal to fix this, along with many |
@rjbs - Status changed from 'new' to 'open' |
From @cpansproutOn Sat Mar 26 02:56:26 2011, horton-p@aist.go.jp wrote:
On Sun Mar 27 06:22:13 2011, rjbs wrote:
This problem still exists in blead, though I’m unsure whether it is -- Father Chrysostomos |
From @nwc10Pod::Html has this: use locale; # make \w work right in non-ASCII lands It was added in 1998 by this commit: commit 3ec0728 Pod::Html and Pod::Text were not locale-savvy: The code referenced is this: # At first glance it would seem better to replace that \W with a POSIX character However, with the refactor to use Pod::Simple::XHTML &anchorify is no longer Nicholas Clark * There are several copies and derivatives of Pod::HTML on CPAN - I couldn't |
From tchrist@perl.comActually, I think \W is the correct thing. Things have changed. This should only be an issue now if both these held true: (1) if they were using byte strings whose high-bit bytes were and (2) There were no =encoding directive. With everyone moving to UTF-8, or else giving an explicit encoding, Also, the unicode_strings feature would also take care of the matter.
There wre other pod2html issue involving Unicode in v5.14, but I think I don't think we should support "guessed" encodings. --tom |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Fri Mar 30 09:03:57 2012, tom christiansen wrote:
If you want to follow HTML 5, it’s actually [^ \t\n\f\r], which I There is nothing preventing anyone from having an anchor named #@>$^,
I think it was a mistake for such ever to have been supported by anything. Father Chrysostomos |
It became a project, but only a subset of it was ever delivered, as I recall. It's been nine years… |
If I read the discussion in this ticket correctly -- particularly Tom's remark, there's nothing to be done in this ticket and the ticket should be closed. Is my reading correct? Thank you very much. |
No one has argued that there is something remaining to be done in this ticket. Accordingly, closing. Thank you very much. |
Migrated from rt.perl.org#112140 (status was 'open')
Searchable as RT112140$
The text was updated successfully, but these errors were encountered: