Add option to specify encoding #50

Closed
opened 2018-03-23 22:48:23 +01:00 by coderkun · 6 comments
coderkun commented 2018-03-23 22:48:23 +01:00 (Migrated from gitlab.com)

Created by: coderkun

The current code assums UTF-8 as encoding for the MPD responses. This might not be correct for all libraries. The application therefore needs an option to specify the encoding as connection parameter on the Server panel. When left blank, fall back to UTF-8.

*Created by: coderkun* The current code assums UTF-8 as encoding for the MPD responses. This might not be correct for all libraries. The application therefore needs an option to specify the encoding as connection parameter on the Server panel. When left blank, fall back to UTF-8.
coderkun commented 2018-08-04 10:54:18 +02:00 (Migrated from gitlab.com)

assigned to @coderkun

assigned to @coderkun
coderkun commented 2018-11-04 19:16:32 +01:00 (Migrated from gitlab.com)

The Request section of the protocol spec says that

All data between the client and the server is encoded in UTF-8.

I am not sure if this applies only to requests or also to responses. Additionally I am not sure if this is new since version 0.21 or has been the case for earlier versions, too.

The [Request section](https://www.musicpd.org/doc/html/protocol.html#requests) of the protocol spec says that > All data between the client and the server is encoded in UTF-8. I am not sure if this applies only to requests or also to responses. Additionally I am not sure if this is new since version 0.21 or has been the case for earlier versions, too.
coderkun commented 2018-12-09 11:31:50 +01:00 (Migrated from gitlab.com)

changed milestone to %10

changed milestone to %10
coderkun commented 2019-05-11 18:34:06 +02:00 (Migrated from gitlab.com)

changed milestone to %11

changed milestone to %11
coderkun commented 2019-09-22 18:37:47 +02:00 (Migrated from gitlab.com)

changed milestone to %9

changed milestone to %9
coderkun commented 2020-08-09 11:19:41 +02:00 (Migrated from gitlab.com)

As I have no way to test any other encoding than UTF-8, I am going to assume that MPD servers use UTF-8 for all strings as the protocol documentation states.

As I have no way to test any other encoding than UTF-8, I am going to assume that MPD servers use UTF-8 for all strings as the protocol documentation states.
Sign in to join this conversation.
No description provided.