Font size changing

[ever-fresh]

Can some one please tell me where these fonts are defined ?
Which file and where located ?
i just imported board from phpBB3 and all fonts was large fonts on phpBB.
Now its showing number 7 Fonts in VB. Extra Large.
i want to change it via CSS or any other file where its defined ???

Screen shot Image is attached.

Thank You.

[Lynne]

It's in the file /clientscript/vbulletin_textedit.js Do a search in the file for "12pt" and you'll find the area. (At least, I think that is it. Try it and see.)

[ever-fresh]

hi. i did it. changed the 36pt to 18pt and also changed the 24pt to 18pt to get same size for both 36pt and 24pt .
i refreshed the Style information also from admincp . but its still showing all posts large.
Which file exactly i need to rebuild / refresh ?

Thank you.

[ever-fresh]

Hi. plesae someone tell me how to fix the maximum font size for signaturs and Post contents ? so all large and extra large font will be displayed in maximum 18pt only ?

i just imported my phpBB3 board to Vb. and all fonts are extra large as they are BBcoded in phpBB3.
Just like this one: http://urdustar.com/home/showthread.php?t=54110

[Lynne]

Do you have post caching on? Maybe that is why it isn't changing. I would ceck a post in the post table and then the corresponding post in the post cache table to see what it is doing.

[ever-fresh]

i am new to VB. can you please tell me how to turn on post caching ?

[Lynne]

It's in vboptions > Server Settings > Cached Posts Lifespan

Cached Posts Lifespan
Posts are normally stored with bbcode tags etc. in the same form as the user posted them with so that it may be edited later, and then parsed at display time. By caching them, they are parsed at post time (instead of display time) into the HTML they will be displayed in and stored separately from the pre-parsed posts. This results in a faster display on threads, since the posts do not have to be parsed at display time.

This option determines how long posts are stored. While a post is cached, it will take approximately twice as much storage space since it is essentially being stored twice. If you have a busy site, and threads typically don't last very long, you can probably set this to a lower value such as 10 days. If you have a slower site, and threads typically last longer, 20 to 30 days might be a better choice. If you have the disc space, you can set this to a higher value for better performance.