On Mon, Feb 20, 2012 at 07:24:04AM -0800, julien2412 wrote:
I think there are 2 different points :
1) to list files in a directory with extension filter
2) to open a file with or without extension
About 2), I agree with the fact we should look at the content and,
considering your comment
https://bugs.freedesktop.org/show_bug.cgi?id=46180#c5, it should be ok with
DBF problem I suppose
but what about 1) ?
When you're on the dialog box, must we list only ods files or ods + ODS
files when we select "ods" filter ?
Ah right, I hadn't thought of the "open file" dialog. In this dialog,
I don't see much/any harm in being inclusive and listing files
case-insensitively. If there are three files:
FoO.oDs
FoO.ODs
fOo.ODs
the user will select one of those and we'll open the one he/she
selected.
For the case of CSV-like database files, it remains more tricky,
because the user selects a *directory*, and we have to *automatically*
consider files from that directory. Each file we consider is a
table. So, if there are two files:
foo.CSv
and
foo.cSV
I don't see how to meaningfully decide which one should be table
"foo". So I'd be inclined to be more strict there and (on a
case-sensitive filesystem) take only files named "*.csv"
case-sensitively. On a case-insensitive filesystem, we should not get
stuck up on the name and match case-insensitively.
As explained in the bug log, our check for case-sensitiveness of the
filesystem is buggy...
--
Lionel
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.