numberformat - is optional no longer optional?

[miki]

Hey all, we just switched to mx. mx 7 is on our horizon, but not close enough
for me. I have a problem with numberformat that i did not have on cf5. When i
apply the optional (9 or _) formatting after a decimal place it is forcing 0.
Now, it used to truly be optional. However now it's apparently only optional
if it's to the left of the decimal place. Is there a work-around? EXAMPLES
#numberFormat(999.99, '999,999.9999')#<br /> #numberFormat(9999.99,
'999,999.0999')#<br /> return the following 999.9900 9,999.9900 other options
i tried include: #numberFormat(999.99, '999,999.____')#<br /> and
#numberFormat(99.9900)#<br /> every single one of them has the trailing 0. my
final goal is to have a) a database value of 9999.900 appear as 9,999.9 as
well as b) NOT to have 99.997 appear as 99.9970. If i can reach the second
goal (b) i will not worry about the first so much. Is there a workaround for
these so-called optional digit place holders when they are refusing to be
optional? Thanks

[OldCFer]

As I remember, Numberformat() has always acted like this. Whether you use "9"
or "0"
on the right side of the decimal, it will always display the number of
formatting characters.
The reason for this is the decimal portion of numbers are not padding, but a
part of the
number. Take 1.120045 , for example. If you numberformat() it with "00.999"
it will display
01.120 because the left side 0 is padding, the right side 0 is not..