Skip to content

Commit b6dc916

Browse files
committed
2 parents fb531dd + 9a3b3bf commit b6dc916

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

README.rst

+4-5
Original file line numberDiff line numberDiff line change
@@ -171,21 +171,20 @@ contents of the output file will look like:
171171
---------------------------
172172

173173
In order to correctly handle all possible characters in the tweets
174-
(think of chinese or arabic characters), the output is saved as utf-8
174+
(think of Japanese or Arabic characters), the output is saved as utf-8
175175
encoded bytes. That is why you could see text like
176-
"":raw-latex:`\u3`0b1:raw-latex:`\u3`0f3:raw-latex:`\u3`055:raw-latex:`\u3`07e:raw-latex:`\u3`0fe
177-
..." in the output file.
176+
"\u30b1 \u30f3 \u3055 \u307e \u30fe ..." in the output file.
178177

179178
What you should do is open the file with the proper encoding:
180179

181180
.. figure:: https://user-images.githubusercontent.com/4409108/30702318-f05bc196-9eec-11e7-8234-a07aabec294f.PNG
182-
:alt: Example of output with chinese characters
183181

184-
Example of output with chinese characters
182+
Example of output with Japanese characters
185183

186184
TO DO
187185
=====
188186

187+
- Twitterscraper can not retrieve retweets.
189188
- Add caching potentially? Would be nice to be able to resume scraping
190189
if something goes wrong and have half of the data of a request cached
191190
or so.

0 commit comments

Comments
 (0)