Talk:Xterm 256 colors

MUD client support

Wasn't sure where else to put this section, but as Mudpedia is focused on muds I thought it should be okay to include a section within the XTerm 256 colors article. The problem I'm having right now is that there's no way to autodetect support, and you can't just base it on the client name because many players use older clients (for example 2 of the 3 CMUD users on GW2 currently use CMUD 2.37, which displays XTerm orange as flashing text, the same as zMUD). So I'm having to dig up this information for each client, to make sure I don't screw up the output for people who don't support it. Of course in theory I could just make people turn it on manually, but autodetection is much cuter.

However it also makes me wonder whether it would be worth doing the same for other features that can't be easily, accurately or consistently detected, such as client name, client version, Go Ahead, VT100, etc - perhaps even create an article giving a rundown of how you can safely identify a client that you know will support a specific option. I did add some notes in the GMud and Portal client sections, but it'd be nice to have an overall summary. KaVir 14:58, 21 January 2011 (UTC)

It's tricky, I proposed a mud TTYPE standard a while ago, which in itself would contain all the protocols that are difficult to detect. If this was to be worked out it'd provide a centralized article to work with, killing two birds with one stone. --Scandum 21:36, 22 January 2011 (UTC)

Client identification

Proactive negotiations in PuTTY can be disabled, so it's not a guaranteed way to identify PuTTY. I think it's almost universal that a client reporting itself as xterm has 256 color capabilities, unless it reports itself as xterm-color. --Scandum 00:57, 13 April 2011 (UTC)