Added by Iñaqui Sandí Suárez over 7 years ago. Updated about 4 years ago.
0%
Description
I found this trying to join a room named Más_de_40
Doesn't show me the actual room, I know I joined but I can't see any conversation going or any users listed.
And I know I was in the room because a friend pvt'ed me and told me I was actually in.
What encoding are you using on that network? you can type /encoding in the Editbox to get current encoding.
Also what network is this on?
Per Amundsen wrote:
What encoding are you using on that network? you can type /encoding in the Editbox to get current encoding.
Also what network is this on?
Encoding is: Unicode (UTF-8) Which is the default I guess, haven't customized it
network is irc.irc-hispano.org
I joined a similar named channel with 3 different irc clients (all using UTF8), seems to work fine, I also joined a channel named #mas_de_40 with a regular a, also seems to work.
Per Amundsen wrote:
I joined a similar named channel with 3 different irc clients (all using UTF8), seems to work fine, I also joined a channel named #mas_de_40 with a regular a, also seems to work.
I was able to join by playing around with Encoding.. set it to Latin 9 (ISO) .. and as I said it looked like I joined (with utf/8) but it wasn't really the same room... I did the test logging to the same server same room with different nick and I saw myself "on" the room but on the AdiIRC I didn't saw any posts on the main channel... Anyway I found the workaround..
That makes sense, if the other users are sending data in ISO you might have problems seeing it, everyone should be using UTF8 though, it works for everyone, but glad you figure it out.
Keeping this open for now since I'm not sure if there is a bug or not, more testing with various clients needed.
Per Amundsen wrote:
That makes sense, if the other users are sending data in ISO you might have problems seeing it, everyone should be using UTF8 though, it works for everyone, but glad you figure it out.
Keeping this open for now since I'm not sure if there is a bug or not, more testing with various clients needed.
Maybe something to consider is to match the encoding from the server... as an option when defining serve connections ...