First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 63394
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Perl Devs @ Gentoo <perl@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Moshe Kamensky <samvimes@fastmail.fm>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
HTML-Parser-3.36-r1.ebuild HTML::Parser ebuild with optional unicode entities support text/plain Moshe Kamensky 2004-09-09 01:41 0000 887 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 63394 depends on: Show dependency tree
Bug 63394 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-09-09 01:39 0000 
The perl module HTML::Parser includes support for decoding unicode entities in
html (such as &#8222;) into the corresponding characters. This should be
enabled during the installation. However, the current ebuild automatically
answers 'no' to this question.

Attached is a modified ebuild that gives 'yes' if the use flags include
unicode.

Reproducible: Always
Steps to Reproduce:
1. Install HTML::Parser
2. Use it to parse a web page that contains unicode entities (for example,
http://www.witkacy.hg.pl/witkosmos/kosmopis.html)
3.

Actual Results:  
The text contains the original entities.

Expected Results:  
(Optionally) translate them to unicode characters.

------- Comment #1 From Moshe Kamensky 2004-09-09 01:41:17 0000 ------- 
Created an attachment (id=39241) [edit]
HTML::Parser ebuild with optional unicode entities support

------- Comment #2 From Michael Cummings (RETIRED) 2004-09-21 06:17:13 0000 ------- 
That is an unfortunate oversight on my part (I could lay blame on the legacy of
the ebuild, but that wouldn't be fair). Corrected and noted in 3.36-r1.

------- Comment #3 From Moshe Kamensky 2004-09-22 02:45:49 0000 ------- 
The $answer should not be (at least single) quoted in the echo statement.
It appears you like curly braces around variables so it should probably be

echo ${answer} ...

or

echo "${answer}" ...

(Note that there are two of those)

------- Comment #4 From Michael Cummings (RETIRED) 2004-09-22 03:40:04 0000 ------- 
Thanks for the catch; corrected and re-closing.
First Last Prev Next    No search results available      Search page      Enter new bug