I *think* we discuss the space separator business purely related to display. So when exporting to excel, or any other case where the number is expected to be consumed as a number (including storage in the database), exported via api in json/xml datavalueset etc there should be no spaces, commas etc. Confusion on this would be a recipe for disaster.
Everyone seems to agree that how numbers display should be configurable. Though I thought the question was more what would be the default appearance in the absence of any configuration. In which case there are only two approaches: (i) pick something, in which case space seems to be the most standard default, or (ii) infer something based on the locale. On 4 May 2016 at 09:56, Lars Helge Øverland <l...@dhis2.org> wrote: > Hi all, > > many thanks for all the feedback. Will make this configurable per system > then given the all the various opinions. > > > Another point of clarification: It seems that space is a preferred separator > in the Web based pivot table. However, when downloading to Excel, it seems > space is useless as it makes Excel interpret the cell as text, not numbers. > > So as a short term solution (which could be back-ported) could be that when > downloading to Excel, the system could fall back to no separator when space > is selected as separator. This because space never seems useful for Excel > spreadsheets. > > Would that work? > > > regards, > > Lars > > > > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : dhis2-d...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : dhis2-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp