https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19910 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@bugs.koha-c | |ommunity.org, | |oleonard@myacpl.org --- Comment #15 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to Victor Grousset/tuxayo from comment #14)
@Nick: Does the last discussion in bug 19928 affects this one?
See from https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19928#c29
I suppose it does if the buttons here seem too long too. Let me describe the issue here though: 1 - Staff member without access to system preferences uses a report to get some data to load back into koha (or another system) 2 - The click 'Download as CSV' and get a *.csv file 3 - They assume the file is actually comma separated 4 - They try to load the file into Koha (or another system) which wants actual commas in a csv 5 - Things don't work 6 - They don't know why 7 - :-( Now, if you open the file in libreoffice/excel/etc. you can fix the delimiters, but sometimes you lose leading zeros etc. And it is an extra step. I just want to make sure someone who can't see the pref understands what they are getting. It could be a tooltip and not on the button It could be a note under the button We could provide selection of delimiter at export and use the pref only to determine default. What would folks prefer? -- You are receiving this mail because: You are watching all bug changes.