mudlet-makers team mailing list archive

[Jeremy Akers <1099688@xxxxxxxxxxxxxxxxxx>]

The behavior of tabs are well known and defined since the age of
typewriters.  Saying a tab character is technically undefined is
absolutely incorrect.  See:  http://en.wikipedia.org/wiki/Tab_key  and
http://en.wikipedia.org/wiki/Tab_stop

Yes most systems allow users to change the "tab stop" setting, but it
generally defaults to 8 unless the user changes it.

Just replacing tabs with "x" number of spaces is also wrong.  Tabs are
meant to create "tabular" data.  They are generally set up to create 8
column "tab stops"

So:

"Text\tMore text"

would display as:

"Text    More Text"

and:

"Someone\tMore Text"

Would be:

"Someone More text"

Basically the word "More" should always start at the 9th column due to
the use of the tab character here.  Even the crappy Windows telnet.exe
handles tabs properly.

-- 
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