Ticket #1835 (closed Enhancement: fixed)

Opened 2 years ago

Last modified 20 months ago

Colloquy should fallback to connection encoding if unable to decode channel message as UTF-8 (when setting as so)

Reported by: naises@… Owned by: kiji.roshi
Priority: Low Milestone:
Component: Colloquy (Mobile) Version: 1.1 (Mobile)
Severity: Minor Keywords:
Cc:

Description

When channel encoding is UTF-8 and Colloquy can't decode the message sent, Colloquy should fallback that message to connection's message instead of defaults the fallback to ISO-8859-1. This will make Colloquy works better with non-Western IRC network.

For example, irc.thai.com uses TIS-620 as connection encoding but some channel uses UTF-8, in order to read both of them correctly with current Colloquy's implemention, user have to set both connection and channel to TIS-620, which in return, will not able to write in UTF-8.

With the suggested change, user can set connection encoding to TIS-620 with channel encoding to UTF-8 and Colloquy will be able to fallback both of them correctly.

Change History

Changed 2 years ago by kiji.roshi

  • status changed from new to accepted

Good idea.

Changed 20 months ago by kiji.roshi

  • status changed from accepted to closed
  • resolution set to fixed

Fixed in [5028].

Note: See TracTickets for help on using tickets.