Testing to see if the code tags work. I’m putting this into the tags:
FILE FILEA V(1000) SEQUENTIAL +
SYSNAME ‘H:\EZ_Text_Files\999999_Input.txt’
AR-NUM 6 12 A
NAME 18 40 A
*NAME2 58 40 A
ADDR1 58 30 A
ADDR2 88 30 A
CITY 118 20 A
STATE 138 2 A
ZIP 158 5 A
ZIP-4 163 4 A
PHONE-AREA 252 3 A
PHONE-PRE 255 3 A
PHONE-REST 258 4 A
*START-YEAR 189 2 N
DOLS-MM 268 2 N
DOLS-YY 274 2 N
*TERMS 203 7 A
COMMENTS 276 2 A
RHC 168 12 A
RHC-BYTE-IN1 RHC 1 A INDEX SUB1
RHC-DOLLARS 168 10 N
RHC-CENTS 178 2 N
BALANCE 180 12 A
BALANCE-NUM 180 12 N 0
BALANCE-BYTE-IN1 BALANCE 1 A INDEX SUB1
BALANCE-DOLLARS 180 10 N
BALANCE-CENTS 190 2 N
CURRENT 192 12 A
CURRENT-NUM 192 12 N 0
CURRENT-BYTE-IN1 CURRENT 1 A INDEX SUB1
CURRENT-DOLLARS 192 10 N
CURRENT-CENTS 202 2 N
01-30 204 12 A
01-30-BYTE-IN1 01-30 1 A INDEX SUB1
01-30-DOLLARS 204 10 N
01-30-CENTS 214 2 N
31-60 216 12 A
31-60-BYTE-IN1 31-60 1 A INDEX SUB1
31-60-DOLLARS 216 10 N
31-60-CENTS 226 2 N
61-90 228 12 A
61-90-BYTE-IN1 61-90 1 A INDEX SUB1
61-90-DOLLARS 228 10 N
61-90-CENTS 238 2 N
OVER-90 240 12 A
OVER-90-BYTE-IN1 OVER-90 1 A INDEX SUB1
OVER-90-DOLLARS 240 10 N
OVER-90-CENTS 250 2 N
FILE FILEA V(1000) SEQUENTIAL +
SYSNAME 'H:\EZ_Text_Files\999999_Input.txt'
AR-NUM 6 12 A
NAME 18 40 A
*NAME2 58 40 A
ADDR1 58 30 A
ADDR2 88 30 A
CITY 118 20 A
STATE 138 2 A
ZIP 158 5 A
ZIP-4 163 4 A
PHONE-AREA 252 3 A
PHONE-PRE 255 3 A
PHONE-REST 258 4 A
*START-YEAR 189 2 N
DOLS-MM 268 2 N
DOLS-YY 274 2 N
*TERMS 203 7 A
COMMENTS 276 2 A
RHC 168 12 A
RHC-BYTE-IN1 RHC 1 A INDEX SUB1
RHC-DOLLARS 168 10 N
RHC-CENTS 178 2 N
BALANCE 180 12 A
BALANCE-NUM 180 12 N 0
BALANCE-BYTE-IN1 BALANCE 1 A INDEX SUB1
BALANCE-DOLLARS 180 10 N
BALANCE-CENTS 190 2 N
CURRENT 192 12 A
CURRENT-NUM 192 12 N 0
CURRENT-BYTE-IN1 CURRENT 1 A INDEX SUB1
CURRENT-DOLLARS 192 10 N
CURRENT-CENTS 202 2 N
01-30 204 12 A
01-30-BYTE-IN1 01-30 1 A INDEX SUB1
01-30-DOLLARS 204 10 N
01-30-CENTS 214 2 N
31-60 216 12 A
31-60-BYTE-IN1 31-60 1 A INDEX SUB1
31-60-DOLLARS 216 10 N
31-60-CENTS 226 2 N
61-90 228 12 A
61-90-BYTE-IN1 61-90 1 A INDEX SUB1
61-90-DOLLARS 228 10 N
61-90-CENTS 238 2 N
OVER-90 240 12 A
OVER-90-BYTE-IN1 OVER-90 1 A INDEX SUB1
OVER-90-DOLLARS 240 10 N
OVER-90-CENTS 250 2 N
In my display, the text inside the code box is aligned with columns, and looks OK, at least at first glance. However, I am using the old vB template (3.7.3). I’ll try the new one and get back to you.
Getting back: No good. The new skin destroys the column alignment and renders your sample code box as a linear string. Baaaad.
So now we have a workaround. Set your display to the old vB template, and enjoy.
How to change the default display for your account: Scroll down to the untitled dropdown box near the left bottom and select “Straight Dope v3.7.3”. This will return your display to the version used previous to the upgrade until changed again.
Further/alternate instructions are available on the ATMB sub-forum.
This might not be desirable for mobile displays; it’s up to you to choose the best compromise.
OK, that worked. For me. But anyone reading this thread who wants to see the code-formatted post will need to make the change. I think that the code tags should work in the new version so that people don’t have to do that.
tag isn't fully, or properly, implemented in the latest vB skin/version. Unless you can provide a good reason why not, wouldn't the best solution be to implement it properly?
One of the admins could go to Styles & Templates in the admincp, go to this style and play with the variables until right, as in this instruction for changing the width of the code box. http://www.digitalfaq.com/forum/web-tech/3317-widen-code-box.html
Tedious, but not that difficult.
When Johnny L.A. started this thread, it wasn’t known why his sample text didn’t display properly, or if the vB version made a difference. Now we know it does and why. That’s called fighting ignorance.
It was known. It seems that it just wasn’t known to you.
The reskin screwed up the ‘code’ tag functionality. That’s been a known issue from day one. Johnny L.A. posted this thread to check if that issue had been resolved and found that it had been not.
I posted to this thread because while I’m not that prolific a poster I use ‘code’ tags in many of my posts and I this seemed like a way to bring a little extra attention to this issue.
So now not only is there no way to post a formatted table or formatted code, the reskin also screwed up all past posts that used ‘code’ tags. Changing my VB template only changes what I see so is not really a fix since other posters may be using the new template (not to mention lurkers and people who read without logging in).
I obviously would like this issue to be fixed and if I could do it myself I would.
That doesn’t seem to be the right issue. That affects the size of the code box. The issue is the lack of retaining spacing and returns in the formatting within the box.
However, I posted the issue to the developer’s site, and he has added a fix.
Indeed — which is why I said ‘play with the variables until right, as in this instruction’.
You can do a lot with Styles.
I added an SSL seal recently, no help from Comodo how to add the html to a vBulletin forum. Just referred me to the same document I was complaining about.
In the end I just shoved it in the footer of each Style. Worked.
And I’ve posted the screenshots Ed asked for, after I started feeling better. So he has the fix and the screenshots to make sure it works. (I have a feeling that his contractor requires screenshots so they know they got it right.)