Code tag wonkiness

[Staffan]

As I was typing up my class conversion for Dark Sun (thread here), I noticed a certain wonkiness in the Code tag - it converts groups of four spaces into tabs (which are a lot longer than the four spaces). This is seriously annoying when writing class tables - any way of either changing that, or getting another tag that allows pre-formatted text without said wonkiness (the latter would probably be better for compatibility with posts written using the old Code tag).

I note that the PHP tag does not change spaces into tabs, but on the other hand it does wonky stuff with coloring instead.

 

[Mark]

Can you use $nbsp; (replacing "$" with a "&") to make a space?

 

[Fanog]

Isn't there already a CODE tag?

 1  2   3    test

Fanog

 

[LightPhoenix]

Isn't there already a CODE tag?

 1 2 3 test

I award thee the missing the point award!

 

[Fanog]

I award thee the missing the point award!

Wow, I normally never win anything.

... now excuse me as I silently crawl back into my corner. That'll teach me to post in a hurry.

Fanog

 

[LightPhoenix]

Wow, I normally never win anything.

... now excuse me as I silently crawl back into my corner. That'll teach me to post in a hurry.

Bah, that's the best way to post!

 

[Staffan]

Bumping this in hope of an official reply.

 

[Michael Morris]

As I was typing up my class conversion for Dark Sun (thread here), I noticed a certain wonkiness in the Code tag - it converts groups of four spaces into tabs (which are a lot longer than the four spaces). This is seriously annoying when writing class tables - any way of either changing that, or getting another tag that allows pre-formatted text without said wonkiness (the latter would probably be better for compatibility with posts written using the old Code tag).

It isn't converting spaces to tabs per se, instead it's granting you a way to do indents. Remember that the tab key can't be used in this interface - the browser has reserved it for moving between fields.

The best way to construct tables is to use Notepad (Win) or Textpad (Mac, I think that's it's name) to build the tables since neither of those programs supports proportional fonts. Once you get them the way you like, cut and paste.

I note that the PHP tag does not change spaces into tabs, but on the other hand it does wonky stuff with coloring instead.

The PHP tag is for those occasions and boards where code monkeys like myself are discussing large blocks of code. The colorization is based on the commands in PHP and allow the code to be read more quickly. It's also a cheap way to catch typos. Most PHP editors (like Dreamweaver) colorize code in the same way.

 

[Staffan]

It isn't converting spaces to tabs per se, instead it's granting you a way to do indents. Remember that the tab key can't be used in this interface - the browser has reserved it for moving between fields.

But it does that through converting groups of four spaces to tabs.

The best way to construct tables is to use Notepad (Win) or Textpad (Mac, I think that's it's name) to build the tables since neither of those programs supports proportional fonts. Once you get them the way you like, cut and paste.

That's what I did, and it ended up looking all wrong because of the conversion. The problem appears when making class progression tables because (a) you need to have +1 and +15/10/5 (or even +20/+15/+10/+5) in the same column, and that requires more than four spaces until the next column; and (b) because of the "special abilities" column sometimes having lots of text and other times being blank, but spell progression being after it so you need to fill the blanks with spaces.

If the purpose is to make indents, that would be better done if it only transformed spaces to tabs at the beginnings of lines.

Edit: fixed a typo.

 

[Staffan]

Giving this one another bump.