blue
/
4Chan-Web-Scraper-v2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update html_text vs html_text2.md

This commit is contained in:
Lucky 2023-08-24 18:20:37 -03:00 committed by GitHub
parent 4a2e9165fd
commit bc279e01f1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
html_text vs html_text2.md
View File

@ -1,16 +1,2 @@
# html_text vs html_text2 from rvest
I did an experiment comparing the `tidy_pol_fixed2` output of text.
html_text = 21776 observations
html_text2 = 20004 observations
I will continue using html_text because it contains more observations, which I can later filter out the noise as needed.
There were no substantial differences that I noticed in the graphs, so retaining a greater number of observations seems better than less.
From the rvest::html_text website:
There are two ways to retrieve text from a element: html_text() and html_text2(). html_text() is a thin wrapper around xml2::xml_text() which returns just the raw underlying text. html_text2() simulates how text looks in a browser, using an approach inspired by JavaScript's innerText(). Roughly speaking, it converts <br /> to "\n", adds blank lines around <p> tags, and lightly formats tabular data.
html_text2() is usually what you want, but it is much slower than html_text() so for simple applications where performance is important you may want to use html_text() instead.