I'd start by looking at how other clients handle it those three cases. This isn't the world's first MUD client so you have the luxury of being able to look at how the competition is handling these cases.
"1. Neither game nor client know where the other party defines the tab positions." So? That's between the game and the user. The client just needs to let the user config the behavior and the user can then configure it based on the expected behavior of the game he's connecting to. "2. What happens if the user sets word wrap to 20 and we use the most common 8-Tab-Stop-Position. Your game sends "this/tis/tgetting/tdifficult" How do you wrapt the lines? How about tab pos #3?" When it wraps, the tab stops start over: "this____is getting_difficult" (Underscores indicate where client should pad spaces) Position 0 of the second line would be the "next" tab stop since we wrapped around. So "is" and "difficult" should line up. "3. What happens if the user has triggers on this line that do larger text replacements in-line, insert newlines etc.?" Why would this be an issue? This behavior wouldn't need to change. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1099688 Title: does not resolve the \t character Status in Mudlet the MUD client: New Bug description: Mudlet does not seem to support the \t character (tab). On muds where this is used, Mudlet prints nothing. It does not indent at all. What is expected is either showing the tab character or 8 spaces, but neither happens, and things that are aligned using tabs make things look all wonky, like maps, etc. Mudlet: 2.1 OS: OSX 10.8.2 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1099688/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mudlet-makers Post to : [email protected] Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
