You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When formatNumbers is TRUE in a call to latexTable(), leading zeroes are eliminated. For example, "0.67" becomes ".67". But some people don't like this behavior. So add a noLeadingZeroes argument to the function. When TRUE, the default, it will function as it does now. When FALSE, leading zeroes won't be touched.
And: if we implement noLeadingZeroes, do we still need the formatNumbers argument at all? Or would the combination of noLeadingZeroes and decimalPlaces cover everything? (formatNumbers may induce some rounding, but that should probably be a default; the user needn't have control over that in latexTable().)
The text was updated successfully, but these errors were encountered:
We shouldn't eliminate the formatNumbers argument. See ?latexTable on this argument: formatNumbers rounds numbers, pads out numbers with trailing zeroes, and removes leading zeroes. It's not obvious that the padding function should be covered by a decimalPlaces argument. Better to leave formatNumbers as is.
When
formatNumbers
isTRUE
in a call tolatexTable()
, leading zeroes are eliminated. For example, "0.67" becomes ".67". But some people don't like this behavior. So add anoLeadingZeroes
argument to the function. WhenTRUE
, the default, it will function as it does now. WhenFALSE
, leading zeroes won't be touched.And: if we implement
noLeadingZeroes
, do we still need theformatNumbers
argument at all? Or would the combination ofnoLeadingZeroes
anddecimalPlaces
cover everything? (formatNumbers
may induce some rounding, but that should probably be a default; the user needn't have control over that inlatexTable()
.)The text was updated successfully, but these errors were encountered: