Font Tidbits!

The basic neoHTML font code is made of [font]neoHTML[/font]. If you were to use this exact code your font would be the default black font. In order to change the color of your font from black, you add c= in your code. If you only want to change the color of your font and you wanted say, a red font, then your neoHTML code would look like:

[fontc=red]neoHTML[/font]

Replace red with the color you want your neoHTML to be. There is a list of colors here.

You might notice on this page, a bunch of letters and numbers under a column called "hexadecimal" next to the color name. You can use this hex code, as it's called, just like a color name. In other words, instead of using red in the code above, you could use #ff0000. I would recommend using the hex code equivalent if the color name you want is over 7 letters in order to conserve space in your code. I also would advise you to keep the # sign in your code; that means, don't use ff0000 instead of #ff0000. The new board layouts appear to have made it so that the # sign is now necessary before a hex code.

If you wish to change the size of your neoHTML, you add s= within the basic [font]neoHTML[/font] code. If you only want to change your font size and you wanted say, a tiny font, then your neoHTML code would look like:

[fonts=1]neoHTML[/font]

Replace 1 with a number between 1-4. The smaller the number, the smaller the font is.

If you wish to change the type of font, also called the face, then you add f= within your basic [font]neoHTML[/font] code. If you only want to change your font face to say, tahoma, then your neoHTML code would look like:

[fontf=tahoma]neoHTML[/font]

Replace tahoma with whatever font you want AS LONG AS the font is one word. Fonts longer than one word will not work. This means that font names like verdana, impact, and georgia are okay but font names like times new roman and courier new are not! Also keep in mind that if the font you choose is uncommon and someone does not have that font installed on their computer, that font will appear to be arial to them!

If you wish to combine these things and make, like, a size 3 green verdana font then your neoHTML code would look like:

[fontc=greenf=verdanas=3]neoHTML[/font]

Feel free to change the color, font face, size, whatever you want! Also please note that the order in which you put the c= and the f= and the s= does not matter; it will still work the same.

The codes for your neoHTML go in your neoHTML box in Chat Preferences.

Here are some other codes you can add to your neoHTML:
[b]neoHTML[/b] will make your neoHTML bold
[i]neoHTML[/i] will make your neoHTML italicized
[u]neoHTML[/u] will make your neoHTML underlined

To combine any or all of these codes with your pretty neoHTML from above, you wrap these codes around what you already have. For example, say I have that size 3 green verdana neoHTML and I want it to be bold. My neoHTML code will look like this:

[b][fontc=greenf=verdanas=3]neoHTML[/font][/b]

If I want it to be bold and underlined, my code will look like this:

[u][b][fontc=greenf=verdanas=3]neoHTML[/font][/b][/u]

Please note that the order of the codes does not matter. I could make my code look like

[fontc=greenf=verdanas=3][u][b]neoHTML[/b][/u][/font]

or even

[u][fontc=greenf=verdanas=3][b]neoHTML[/u][/font][/b]

if I wanted to! HOWEVER, all the beginning codes must be before the "neoHTML" and all the ending codes must be after the "neoHTML". The ending codes, which have a slash after the first bracket, are [/u], [/font], and [/b] in this example.

You use the [center] and [/center] tags. I will use the size 3 green verdana font as an example. My code for this would look something like this:

[center][fontc=greenf=verdanas=3]neoHTML[/font][/center]

You can't anymore. :( These effects were disabled August 16, 2004.

Invisible fonts, which are technically really pale-colored or white fonts, are considered to be against the rules. More info on this can be found here.

You put your text before the "neoHTML" in your code. Using the size 3 green verdana font as my example, I will explain. Say I wanted to say "icebabe1113 says," before my post and ", so listen!" after my post. I would use this code in my neoHTML box:

icebabe1113 says, [fontc=greenf=verdanas=3]neoHTML[/font], so listen!

If I wanted all of my text to the same color as my neoHTML, I would use the following code:

[fontc=greenf=verdanas=3]icebabe1113 says, neoHTML, so listen![/font]

If I wanted to use just "icebabe1113 says," before my post and I wanted it to be purple and bold but have my neoHTML be the size 3 green verdana font, I would use the following code:

[fontc=purple][b]icebabe1113 says,[/b][/font] [fontc=greenf=verdanas=3]neoHTML[/font]

You can mix and match codes however you want here!

Insert a [br] into your code wherever you want the text to go onto a new line. This is the equivalent of hitting the "Enter" button once on your keyboard. Using the last code from the previous FAQ, I will demonstrate. Say I want a line break after "icebabe1113 says,". Then my code should look like:

[fontc=purple][b]icebabe1113 says,[/b][/font][br][fontc=greenf=verdanas=3]neoHTML[/font]

Insert a [p] into your code for the equivalent of hitting the "Enter" button twice. If I wanted two line breaks in the code I just used instead of one after "icebabe1113 says," my code would look like:

[fontc=purple][b]icebabe1113 says,[/b][/font][p][fontc=greenf=verdanas=3]neoHTML[/font]

[br] and [p] can also be used in your signature in the same way!

If I wanted 'icebabe1113 says' and 'so listen!' each to be on a new line, my code might look like:
[fontc=greenf=verdanas=3]icebabe1113 says[br]neoHTML[br]so listen![/font]
With this code, everything would be size 3 green verdana font.

When you've posted on the boards, you probably have noticed these buttons: , , and .
Here is what they do and the code for each:

[quote]YOUR TEXT HERE[/quote] will put your text in a quote box.
[sup]YOUR TEXT HERE[/sup] will put your text into superscript. (^{This is superscript.} neoHTML)
[sub]YOUR TEXT HERE[/sub] will put your text into subscript. (_{This is subscript.} neoHTML)

You simply put [ at the very end of your neoHTML box and ] at the very beginning of your signature box. You may want to add a [p] or [br] before the [ (in the neoHTML box) or after the ] (in the signature box) in order to keep the neoHTML and signatures seperated.

DUE TO THE BOARD LAYOUT CHANGES, IT APPEARS THAT WINGDINGS AND WEBDINGS FONT DO NOT WORK PROPERLY - AT LEAST WHEN IT COMES TO FIREFOX.
Why yes, you can. (Can you tell I made this question up?) However, you cannot change the color of the siggy line. These may not be the only fonts that will change a siggy line; try replacing the codes here with a one-word font inserted in it if you wish. (Thanks to the person who gave me the idea to test more fonts out. xD) Please be aware that the examples here will not necessarily be the same size as your new siggy line.

If you want to make your siggy line smaller, put [fonts=1] at the end of your neoHTML box and [/font] at the beginning of your Signature box in Chat Prefs. If you want to make your siggy line bigger, put [fonts=3] or [fonts=4] (depending on how big you want the line to be) at the end of your neoHTML box and [/font] at the beginning of your Signature box.

Then place [fontf=charlesworth] at the very end of your neoHTML box in Chat Prefs and place [/font] at the very beginning of your Signature box. Feel free to play around with sizes.

Then place [fontf=lithograph] at the very end of your neoHTML box in Chat Prefs and place [/font] at the very beginning of your Signature box. Feel free to play around with sizes.

Then place [fontf=impact] at the very end of your neoHTML box in Chat Prefs and place [/font] at the very beginning of your Signature box. Feel free to play around with sizes; I just prefer size 2 personally, but it doesn't mean you will.

Then place [fontf=webdingss=1] at the very end of your neoHTML box in Chat Prefs and place [/font] at the very beginning of your Signature box. Feel free to play around with sizes; I just prefer size 1 personally, because the siggy line starts to get really big otherwise.

Then place [fontf=wingdingss=1] at the very end of your neoHTML box in Chat Prefs and place [/font] at the very beginning of your Signature box. Feel free to play around with sizes; I just prefer size 1 personally, because the siggy line starts to get really big otherwise.

Inverting your siggy and neoHTML means having your siggy on top of the siggy line and having your neoHTML below the siggy line. However, this is merely an illusion; try putting "neoHTML" in your siggy and you will make the evil fuzzles cry. The bulk of your code must be placed in your neoHTML box, including your siggy and most of your neoHTML.

Say I wanted to have a simple, size 3 red ♥ as my siggy. (Your siggy will probably need to be small in order to do this; although, it does not necessarily need to be this small.) Say I wanted my neoHTML to be size 2 pinkish tahoma font. Say I also wanted it all to be centered.

My neoHTML might look like:
[center][fontc=reds=4]♥[/font][br][fontc=#818181s=3]-------------------------[/font][br][fontc=FF0066f=tahoma]neoHTML[

My signature box would then look like:
][br][/font][/center]

Notice that I DO have stuff in my signature box. If you are attempting to invert your neoHTML and signatures, be VERY careful about what you place in your signature box. If you place anything in your signature box, the dotted siggy line will show up, making the font look sort of odd because you'll have two siggy lines. If you are going to place ANYTHING in your signature box, you probably will want to use the code to remove the siggy line.

If the way I broke up the codes among the neoHTML and signature boxes is confusing, see the last section of the tidbit about needing more room for coding.

I would also like to mention with this tip, you run the risk of confusing fellow Neopians because they may confuse your siggy with your neoHTML and wonder why you keep posting the "same thing" all the time. If you would like to prevent this, as might be courteous, put something like, "Text below" so as to direct their eyes to the right spot.

& hearts; (without a space after the &) = ♥
& spades; (without a space after the &) = ♠
& clubs; (without a space after the &) = ♣

DUE TO THE BOARD LAYOUT CHANGES, IT APPEARS THAT WINGDINGS AND WEBDINGS FONT DO NOT WORK PROPERLY - AT LEAST WHEN IT COMES TO FIREFOX.
Usually, people with symbols in their neoHTML or siggies are using certain letters in webdings or wingdings font. Play around with a Word document and test it out to see what sort of symbols you like. Also, there are some special characters you can use as well, such as ▒; again, play around with Word.

Depending how long you've been a Neopets user, you might remember a pretty big neoboards layout change that occurred, altering the boards forever. (No, not the one that stimulated the need for bumping.) Anyways, it appears that now all hex codes need the # sign before them. In other words if your color code is ff0000, you should change it to #ff0000.

If this isn't your problem, check to make sure your color name or hex code is valid. Bubbles Colour Charts, I believe, has all the possible color names listed so check to see if you are using the right spelling or whatever. If you are using an inaccurately spelled color name, it will just translate into a different color than you are probably looking for. The page does not contain all possible hex codes (that would be very difficult to do) but does contain hex codes for many different colors, so check it out.

Place a [center] at the very beginning of your neoHTML box and a [/center] at the very end of your Signature box.

I am assuming you have a [br] or [p] somewhere between the end of your neoHTML code and the beginning of your siggy. If you have a [p], replace it with a [br]. If you have a [br], try removing it completely.

Assuming you don't want to completely change your font, this is a problem that can be solved in several ways. I have listed all the ones I know of (currently five). They will be listed accordingly; the simplest is first and the most complicated is last. I routinely use number five, but it's not a miracle worker; if you still don't have enough room after reading these tips, you might have to change your font. Of course, I could still be wrong and there may be other ways to fix this problem...

Ah, but of course you can also choose to use color names. Color names will vary in length from the 3 character red to much longer ones such as royalblue. If the color you want has a name longer than 7 characters choose the hex code equivalent of the color. You can try this page; it has a color converter.

If you want to use a color with a name less than 7 characters than use the color name. Don't use the hex code equivalents of red, blue, pink, etc; use their actual names. Yes it only saves you, at best, a few characters but everything helps!

If you wanted to make ALL of your post (including siggy) bold you can do the same thing; you put [b] at the very beginning of your neoHTML box and [/b] at the very end of your Signature box without having to put in a [/b] at the end of your neoHTML box and a [b] at the beginning of your signature box.

Similarly, you can do this with more complicated codes. If you wanted to make all of your post (including siggy) be red verdana size 2 font, you can put [fontc=redf=verdana] at the beginning of your neoHTML box and [/font] at the end of your Signature box without having to put [/font] at the end of your neoHTML box and [fontc=redf=verdana] at the beginning of your Signature box. Please note that for this step, you will NOT be able to view your font correctly in Chat Preferences BUT it will show up correctly when you post.

[center][fontc=#FF3300f=tahoma]▒░Icey░▒[br][/font][fontf=verdanac=#666699]neoHTML[p][

Look at it carefully. Notice how I have not ended my code for [fontf=verdanac=#666699]! So, where is the [/font] at the end of my code for this? Well, I put it in my Signature box. My complementary Signature looked like this:

][/font][fontc=#339900s=1f=tahoma][b]-green with greed-[/b][/font][/center]

You see, I have placed the [/font] towards the beginning of my Signature box BEFORE the code for my siggy. I do not place it at the very beginning of my Signature box because then it would upset the code I have used for removing the "siggy line". If you also are using this code to remove your siggy line, remember that the two brackets must ALWAYS be at the very end of your neoHTML box and the very beginning of your Signature box.

Also, you MUST end your font code somewhere before the code for your siggy if you want to have your signature a different color/font than your neoHTML.

THIS IS VERY IMPORTANT: You MUST end your codes somewhere, even if you do it in the same manner I do. If you don't, your font will not work. It may save you space not to end your codes at all, but your font won't work at all!

Conversely, I could be running out of room in my Signature box but have extra room in my neoHTML box. You would, thus, approach this in the same manner as I did above with a large amount of neoHTML and a smaller siggy. A sample code for the neoHTML might look like:

[center][fontc=redf=verdana]neoHTML[/font][fontc=purples=1][b][p][

Notice how I put [fontc=purples=1][b] in my neoHTML box towards the end. Guess where the ending codes are? Well, they are in my Signature box. They have to be somewhere, after all, or else my coding won't work! So, this is what my Signature box would look like:

]Somereallylongsiggyhere[/b][/font][/center]

Yep, you see how I put my ending tags after my siggy text?