Python Forum
'utf-8' codec can't decode byte 0xda in position 184: invalid continuation byte
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
'utf-8' codec can't decode byte 0xda in position 184: invalid continuation byte
#9
(Sep-12-2019, 11:19 PM)newbieAuggie2019 Wrote:
(Sep-02-2019, 09:45 PM)karkas Wrote: 9
00:00:15,377 --> 00:00:18,570
ESTAMOS HACIENDO
UN FASCINANTE EXPERIMENTO.

10
00:00:19,150 --> 00:00:20,280
AÚN LO ESCUCHO.

(Sep-06-2019, 02:02 PM)karkas Wrote: 1
00:00:00,066 --> 00:00:01,888
HOLA, SOY <i>JACK RICO,</i>

2
00:00:01,888 --> 00:00:04,444
<i>Y ESTO ES </i>"TALLER
DEL CONSUMIDOR".

3
00:00:04,444 --> 00:00:05,530
<i>[MÚSICA]</i>

Hi!

I think you are dealing with subtitles, and although it's a personal option, I would like to comment on something off your question. It's about formatting (by the way, you asked also about 'f'. It's also related to formatting strings).

I personally (so you can completely avoid my suggestions) find UPPERCASE LETTERS in subtitles (like in a chat), as if somebody is shouting, instead of speaking (actually, when lowercase letters are used, sometimes UPPERCASE LETTERS are then used to mean that somebody is shouting or emphasizing something).

Therefore, I would personally use something like the following, instead of what you provide as an example (of course, you can completely ignore my advice):
Quote:9
00:00:15,377 --> 00:00:18,570
Estamos haciendo
un experimento fascinante.

10
00:00:19,150 --> 00:00:20,280
Todavía lo escucho.

Quote:1
00:00:00,066 --> 00:00:01,888
¡Hola! Soy <i>Jack Rico</i>,

2
00:00:01,888 --> 00:00:04,444
<i>y esto es </i>"Taller
del Consumidor".

3
00:00:04,444 --> 00:00:05,530
<i>[Música]</i>

All the best,

Hello, newbieAuggie2019.

Thanks for your reply. I have been away and for some reason didn't get a notification for this message. I understand what you mean by this, it's very common among forums and other interaction environments to avoid uppercase writing. However, this is part of the style of the TV channel and their request, so this is how it has to be done for them. When working with subtitles and captions, it all depends on what the client needs and prefers. In fact, sometimes a client will make a request that doesn't help with the readability—which I don't think is the case here.

When dealing with subtitles, I personally don't consider this as shouting; when you want to convey that, you use a sound effects tag. Probably the client wants to make sure the captions are read by everyone irrespective of how far they are from the TV. I'm not sure, though.
Reply


Messages In This Thread
RE: 'utf-8' codec can't decode byte 0xda in position 184: invalid continuation byte - by karkas - Feb-08-2020, 06:58 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Search for multiple unknown 3 (2) Byte combinations in a file. lastyle 7 1,322 Aug-14-2023, 02:28 AM
Last Post: deanhystad
Question UnicodeEncodeError: 'ascii' codec can't encode character u'\xe8' in position 562: ord ctrldan 23 4,808 Apr-24-2023, 03:40 PM
Last Post: ctrldan
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd2 in position 16: invalid cont Melcu54 3 4,930 Mar-26-2023, 12:12 PM
Last Post: Gribouillis
  Decode string ? JohnnyCoffee 1 813 Jan-11-2023, 12:29 AM
Last Post: bowlofred
  extract only text strip byte array Pir8Radio 7 2,924 Nov-29-2022, 10:24 PM
Last Post: Pir8Radio
  [SOLVED] [Debian] UnicodeEncodeError: 'ascii' codec Winfried 1 1,023 Nov-16-2022, 11:41 AM
Last Post: Winfried
  sending byte in code? korenron 2 1,115 Oct-30-2022, 01:14 PM
Last Post: korenron
  UnicodeDecodeError: 'charmap' codec can't decode byte 0x81 in position 34: character Melcu54 7 18,866 Sep-26-2022, 10:09 AM
Last Post: Melcu54
  Byte Error when working with APIs Oshadha 2 1,010 Jul-05-2022, 05:23 AM
Last Post: deanhystad
  UnicodeEncodeError: 'ascii' codec can't encode character '\xfd' in position 14: ordin Armandito 6 2,721 Apr-29-2022, 12:36 PM
Last Post: Armandito

Forum Jump:

User Panel Messages

Announcements
Announcement #1 8/1/2020
Announcement #2 8/2/2020
Announcement #3 8/6/2020