I tried opening a .CSV file on Windows 7 with Open Office and it opens it just fine.
However when I try the same file in openSUSE it comes in all scrambled.
Who do I talk to about this ?
Or I imagine that Open Office is available instead. Let me see.
On 2013-08-09 20:26, hextejas wrote:
>
> I tried opening a .CSV file on Windows 7 with Open Office and it opens
> it just fine.
> However when I try the same file in openSUSE it comes in all scrambled.
Can you post two lines of that csv for us to try?
> Or I imagine that Open Office is available instead. Let me see.
nope.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
OpenOffice normally shows you a preview and you can change the default separator and default text delimiter at this stage. If you open the .csv file in a text editor, you should see what these are.
Ever since year dot there have been different conventions for .csv separators and delimiters; it is easy in Windows to set the default to the Windows style but in Linux you may be importing files from several different sources; hence the preview.
Sorry that I wasn’t more clear on my description and I will post some lines when I get back to my desk sometime tomorrow.
When I say scrambled, the preview of the file has what looks like a bunch of @@@@@ ampersands only they look like they have been shaded in. Kinda like what you will see if a font is missing.
I will post more and better info tomorrow.
Other CSV seem to work fine.
If I can’t figure out how to show you, the file is pretty small so I could upload it somewhere or email it.
On Fri, 09 Aug 2013 23:56:03 +0000, hextejas wrote:
> Sorry that I wasn’t more clear on my description and I will post some
> lines when I get back to my desk sometime tomorrow.
>
> When I say scrambled, the preview of the file has what looks like a
> bunch of @@@@@ ampersands only they look like they have been shaded in.
> Kinda like what you will see if a font is missing.
>
> I will post more and better info tomorrow.
>
> Other CSV seem to work fine.
>
> If I can’t figure out how to show you, the file is pretty small so I
> could upload it somewhere or email it.
You should be able to just copy/paste a line or two from the file
(obscuring anything that’s sensitive) inside code tags here.
On 2013-08-10 02:13, Jim Henderson wrote:
> You should be able to just copy/paste a line or two from the file
> (obscuring anything that’s sensitive) inside code tags here.
That should be enough - unless there is a text coding difference, like 8
bit chars to utf, because the pasting (and mailing) does a conversion.
In that case the real file would be necessary, I think.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On Sat, 10 Aug 2013 00:28:06 +0000, Carlos E. R. wrote:
> On 2013-08-10 02:13, Jim Henderson wrote:
>> You should be able to just copy/paste a line or two from the file
>> (obscuring anything that’s sensitive) inside code tags here.
>
> That should be enough - unless there is a text coding difference, like 8
> bit chars to utf, because the pasting (and mailing) does a conversion.
> In that case the real file would be necessary, I think.
Yeah, I was thinking about that as well - the output from the ‘file’
command would probably be useful, too.
hextejas wrote:
>
> I tried opening a .CSV file on Windows 7 with Open Office and it opens
> it just fine.
> However when I try the same file in openSUSE it comes in all scrambled.
>
> Who do I talk to about this ?
>
> Or I imagine that Open Office is available instead. Let me see.
>
>
When you double click on csv a libreoffice window pops up where you need
to check/set the correct “character set” and “language”. I had a issue
similar to what you describe and i found that my character set was set
to Unicode,but when i changed it unicode (UTF-8) it makes massive
difference.
screenshots
wrong character set http://paste.opensuse.org/images/42758011.png
correct character set http://paste.opensuse.org/images/88091917.png
GNOME 3.6.2
openSUSE Release 12.3 (Dartmouth) 64-bit
Kernel Linux 3.7.10-1.16-desktop
On 2013-08-10 04:23, vazhavandan wrote:
> When you double click on csv a libreoffice window pops up where you need
> to check/set the correct “character set” and “language”. I had a issue
> similar to what you describe and i found that my character set was set
> to Unicode,but when i changed it unicode (UTF-8) it makes massive
> difference.
Yes, same here.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
That’s a great idea about the unicode and I thought for sure that you had it, but alas. no luck.
Here is a screenshot of the open and further to the discussion I tried opening it with Keditor and got a lot of more undecipherable gibberish. Mostly square boxes.
I also made another copy from the Win 7 box, thinking that somehow it had gotten scrambled during the transition, but that did no good.
I am thinking about installing Libre Office on Win 7 and see if it behaves the same.
What say you ? http://i44.tinypic.com/29bop5u.png
Well, I have no clue as to how to give you a “file sample”, I have the file over here and do you want me to email it to you ?
And "output of “file thatfile” is now making sense to me . I didn’t know that “file” was a command.
The output says:
VWEAXPrices.csv: OpenDocument Spreadsheet
hextejas wrote:
> Here is a screenshot of the open and further to the discussion I tried
> opening it with Keditor and got a lot of more undecipherable gibberish.
> Mostly square boxes.
A csv is a plain text file (comma separated values) .Any csv should be
readable by humans in lain text editors. Your “csv” may not be a csv at
all, but a file in binary format .
> Well, I have no clue as to how to give you a “file sample”, I have the
> file over here and do you want me to email it to you ?
Well, that’s a posibility. Or upload to some shared site. It does not
need to be your private file, I suppose you can create a sample file on
the other machine.
> And "output of “file thatfile” is now making sense to me . I didn’t
> know that “file” was a command.
Oh.
Didn’t occur to me to think of that - I’m so used to the command.
> The output says:
> VWEAXPrices.csv: OpenDocument Spreadsheet
Maybe it is not a csv file - try renaming it, or a copy, to “name.ods”,
and then open it.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
> A csv is a plain text file (comma separated values) .Any csv should be
> readable by humans in lain text editors. Your “csv” may not be a csv at
> all, but a file in binary format .
Two banks I work with provide account data in what they say is .csv, or
xls, but is in fact html.
One is:
HTML document, ISO-8859 text, with very long lines, with CRLF line
terminators.
another:
Composite Document File V2 Document, Little Endian, Os: Windows, Version
6.0, Code page: 1252
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
VAz, that is what I always thought .CSV were, but this is what’s happening.
The file is really an .ODS file, Open Office Spreadsheet, but saved with the wrong ext.
It was just my bad luck to pick it for a test.
I renamed it to a .ODS and Libre Office treated it well.
Apparently Open Office was able to recognize it in spite of the extension whereas Libre Office could not. So I guess I was accurate in that they do work differently. :shame:
An well, consider this issue closed, it’s just something I need to be aware of.
hextejas wrote:
>
> vazhavandan;2578245 Wrote:
>> hextejas wrote:
>>> Here is a screenshot of the open and further to the discussion I
>> tried
>>> opening it with Keditor and got a lot of more undecipherable
>> gibberish.
>>> Mostly square boxes.
>>
>> A csv is a plain text file (comma separated values) .Any csv should be
>> readable by humans in lain text editors. Your “csv” may not be a csv at
>> all, but a file in binary format .
>>
>> –
>> GNOME 3.6.2
>> openSUSE Release 12.3 (Dartmouth) 64-bit
>> Kernel Linux 3.7.10-1.16-desktop
>
> VAz, that is what I always thought .CSV were, but this is what’s
> happening.
> The file is really an .ODS file, Open Office Spreadsheet, but saved
> with the wrong ext.
> It was just my bad luck to pick it for a test.
> I renamed it to a .ODS and Libre Office treated it well.
> Apparently Open Office was able to recognize it in spite of the
> extension whereas Libre Office could not. So I guess I was accurate in
> that they do work differently. :shame:
>
> An well, consider this issue closed, it’s just something I need to be
> aware of.
>
> Thanks for the false alarm.
>
>
Even ODS is a simple plain text/xml file archive.
Try extracting ods using arch/file-roller and you will find some plain
text xml files with data and other meta-data files.