From: Eric B. <er...@go...> - 2008-01-07 14:20:05
|
Colin Adams wrote: > On 07/01/2008, *Eric Bezault* <er...@go... > <mailto:er...@go...>> wrote: > > Colin Adams wrote: > > > But the code is shared by xsl:number (as the formatting rules are > > defined to be the same), which might format any number. > > And is it that much code duplication to implement the formatting > rules both for an INTEGER and for a MA_DECIMAL as input? > > > Unfortunately, yes, it is (I did have a look into this). > What is more, it will get worse in the future - so far there is only an > English language version. There will be more. What impact would it have on the integers held in a date? Would they use other unicode characters for the digits? > It sounds to me as if because when written to a file an integer > and a decimal look the same we should first convert INTEGERs to > MA_DECIMALs when passing them to class FILE. > > > Now you've lost me. In other words, for anything I want to do in an INTEGER, why would I need to convert it to a MA_DECIMAL first? If I dpn't do this conversion for anything I do with an INTEGER, why should it be different in this particular case? -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |