Non-ascii chars in "-e", and a project that uses youtube-dl

[edrx]

Hello youtube-dl people,

I've been using youtube-dl heavily in this project:

http://angg.twu.net/youtube-db/README.html
http://angg.twu.net/linkdasruas2.html

It uses very few features of youtube-dl, but calls it on thousands of videos.

Right now the only bug that I have to report - that has been around for months without disappearing with "youtube-dl -U" - is that I see no way to get the full titles of videos when they have latin-1 chars in
them. Doing this, for example,

youtube-dl -e "http://www.youtube.com/watch?v=n72B3zCOLU0"

outputs the first line below, instead of the second:

Tribunais secretos, prises, agresses, ameaas, crcere privado: Um Brasil sem direitos
Tribunais secretos, prisões, agressões, ameaças, cárcere privado: Um Brasil sem direitos

The non-ascii chars are dropped, in a way that seems to be somehow similar to what this does:

youtube-dl -t -f 18 --restrict-filenames 'http://www.youtube.com/watch?v=n72B3zCOLU0'

I do have some wishlist items for youtube-dl, though... Most of them would be easier to tell by chat, because I know very little Python and very little about Windows, so I would have to try to translate my
knowledge of other languages and *NIX into something viable, and that would be easier to do in real-time dialog than by bug reports and e-mails... Do any of the developers drop by the #youtube-dl channel at Freenode? When? That would be a great place to chat - but if not I can try to post my ideas here or elsewhere, too. What do you recommend?

Cheers and thanks =),
Eduardo Ochs
eduardoochs@gmail.com
http://angg.twu.net/

[juancri]

I think it could a problem with your terminal. Does it support special characters? You could try to redirect the output to a file or reading the output with hexdump or other similar tool.

Here's the output I get:
$ youtube-dl -e https://www.youtube.com/watch?v=n72B3zCOLU0
Tribunais secretos, prisões, agressões, ameaças, cárcere privado: Um Brasil sem direitos

Regards,

[tanmauwu]

@edrx has not responded regarding whether the problem was associated with his terminal, as @juancri suggested. Plus, it's been more than four years. So, this issue seems like it can be closed.