Hello: I have an old, some kind of text file I would like to open in openSUSE. According to the file's date it was created in 1997 and the lack of an extension suggests that it was created on an Apple Mac OS. It probably was made by MS Word for Mac. If I open the file with kwrite or hex viewer it contains lots of gibberish and recognizable valid text parts. The first 8 characters in kwrite with iso8859-1 encoding are: ± EXPW In the hex viewer: 0000:0000 | 01 00 B1 00 | ..±.EXPW How could I find an application that opens the file correctly? I can send the file itself in private mail. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 30 mei 2019 16:59:07 CEST schreef Istvan Gabor:
Hello:
I have an old, some kind of text file I would like to open in openSUSE.
According to the file's date it was created in 1997 and the lack of an extension suggests that it was created on an Apple Mac OS.
It probably was made by MS Word for Mac.
If I open the file with kwrite or hex viewer it contains lots of gibberish and recognizable valid text parts.
The first 8 characters in kwrite with iso8859-1 encoding are: ± EXPW
In the hex viewer: 0000:0000 | 01 00 B1 00 | ..±.EXPW
How could I find an application that opens the file correctly?
I can send the file itself in private mail.
Thanks,
Istvan Try LibreOffice ....
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
And maybe a old version of openofficeorg because libreoffice they have removed some old converters (especially the staroffice .sd? converters. what will show the command: file yourfile simoN Am 30.05.19 um 17:02 schrieb Knurpht-openSUSE:
Op donderdag 30 mei 2019 16:59:07 CEST schreef Istvan Gabor:
Hello:
I have an old, some kind of text file I would like to open in openSUSE.
According to the file's date it was created in 1997 and the lack of an extension suggests that it was created on an Apple Mac OS.
It probably was made by MS Word for Mac.
If I open the file with kwrite or hex viewer it contains lots of gibberish and recognizable valid text parts.
The first 8 characters in kwrite with iso8859-1 encoding are: ± EXPW
In the hex viewer: 0000:0000 | 01 00 B1 00 | ..±.EXPW
How could I find an application that opens the file correctly?
I can send the file itself in private mail.
Thanks,
Istvan Try LibreOffice ....
-- B e c h e r e r GmbH Sondermaschinenbau Mauermatten Strasse 22 79183 Waldkirch Germany Tel.: (+49) (0)7681 3134 Fax: (+49) (0)7681 4378 Mail: info@becherer.de Web: www.becherer.de USt-ID-Nr.: DE 814912198 Registergericht: Freiburg HRB 701860 Geschäftsführer: Dipl.-Ing. (FH), EWE Simon H. Becherer Gerichtsstand / Sitz: Waldkirch Es gelten ausschließlich unsere allgemeinen Liefer- und Zahlungsbedingungen / Einkaufsbedingungen: www.becherer.de/AGB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/05/2019 16.59, Istvan Gabor wrote:
The first 8 characters in kwrite with iso8859-1 encoding are: ± EXPW
In the hex viewer: 0000:0000 | 01 00 B1 00 | ..±.EXPW
How could I find an application that opens the file correctly?
The first thing is to try the command "file" on it. I fdon't know if there is anything better at identifying files. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 5/30/19 5:59 PM, Istvan Gabor wrote:
Hello:
I have an old, some kind of text file I would like to open in openSUSE.
According to the file's date it was created in 1997 and the lack of an extension suggests that it was created on an Apple Mac OS.
It probably was made by MS Word for Mac.
If I open the file with kwrite or hex viewer it contains lots of gibberish and recognizable valid text parts.
The first 8 characters in kwrite with iso8859-1 encoding are: ± EXPW
In the hex viewer: 0000:0000 | 01 00 B1 00 | ..±.EXPW
How could I find an application that opens the file correctly?
I can send the file itself in private mail.
Thanks,
Istvan
- sometimes Abiword opens things that others cannot ..... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/30/2019 09:59 AM, Istvan Gabor wrote:
According to the file's date it was created in 1997 and the lack of an extension suggests that it was created on an Apple Mac OS.
It probably was made by MS Word for Mac.
Also recall, Mac OS, prior to OSX used '\r' for end of line for text files. If it was created in MS Word, then it should be in Word format unless you explicitly saved to text. I'm betting it is text. The first 8-bytes of a word-97 file I show as: d0 cf 11 e0 a1 b1 1a e1 (that is consistent from a number of files dated 1997-1998) For word files from the 1994 timeframe you have: db a5 2d 00 2f 40 09 04 (which may be as old as from Word 1.0f in the Win 3.1 timeframe) Also, what you show as the first 4-bytes (01 00 B1 00) isn't any type of byte-order-mark, but I am curious about: EXPW which could loosely translate to Word-XP, but I don't have a reference for that. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/05/2019 07.07, David C. Rankin wrote:
On 05/30/2019 09:59 AM, Istvan Gabor wrote:
...
Also, what you show as the first 4-bytes (01 00 B1 00) isn't any type of byte-order-mark, but I am curious about:
EXPW
which could loosely translate to Word-XP, but I don't have a reference for that.
It is not enough for an identification: cer@Telcontar:~/Download/Firefox_downloads> hexdump -C p 00000000 01 00 b1 00 45 58 50 57 |....EXPW| 00000008 cer@Telcontar:~/Download/Firefox_downloads> file p p: data cer@Telcontar:~/Download/Firefox_downloads> -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Fri, 31 May 2019 08:43:41 +0200, Carlos E. R. wrote:
On 31/05/2019 07.07, David C. Rankin wrote:
On 05/30/2019 09:59 AM, Istvan Gabor wrote:
...
Also, what you show as the first 4-bytes (01 00 B1 00) isn't any type of byte-order-mark, but I am curious about:
EXPW
which could loosely translate to Word-XP, but I don't have a reference for that.
It is not enough for an identification:
cer@Telcontar:~/Download/Firefox_downloads> hexdump -C p 00000000 01 00 b1 00 45 58 50 57 |....EXPW| 00000008 cer@Telcontar:~/Download/Firefox_downloads> file p p: data cer@Telcontar:~/Download/Firefox_downloads>
Thank you all for answering. I forgot to mention in my original post that I tried to open the file with Libreoffice (4.1) and Apache OpenOffice (4 something). Both asked for choosing encoding then opened the file with many of special encodign characters like ##### etc. file command says it is data (as Carlos showed). If the file was made on Mac (90 %) the it must have been legacy Mac with its specific file hierarchy system. Legacy (prior OSX) used so called file type identifiers and creator identifiers for files. These identifiers were used to determine which program should open the file. If I remember correctly these identifiers were accompanied with each file in the filesystem but separated. That is if the file itself were copied to another system, the identifiers did not go with the file, and it is not possible or difficult to find out what program created the file. The problem with my file is that I cannot determine the progarm that created. Maybe it was not MS Word for Mac. Thanks again, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/05/2019 14.19, Istvan Gabor wrote:
On Fri, 31 May 2019 08:43:41 +0200, Carlos E. R. wrote:
On 31/05/2019 07.07, David C. Rankin wrote:
On 05/30/2019 09:59 AM, Istvan Gabor wrote:
Thank you all for answering.
I forgot to mention in my original post that I tried to open the file with Libreoffice (4.1) and Apache OpenOffice (4 something).
Both asked for choosing encoding then opened the file with many of special encodign characters like ##### etc.
file command says it is data (as Carlos showed).
If the file was made on Mac (90 %) the it must have been legacy Mac with its specific file hierarchy system.
Legacy (prior OSX) used so called file type identifiers and creator identifiers for files. These identifiers were used to determine which program should open the file. If I remember correctly these identifiers were accompanied with each file in the filesystem but separated. That is if the file itself were copied to another system, the identifiers did not go with the file, and it is not possible or difficult to find out what program created the file.
That metadata is not stored on copy as another file, same name different extension perhaps? (guessing) The original disk is not available?
The problem with my file is that I cannot determine the progarm that created. Maybe it was not MS Word for Mac.
Too bad :-(
Thanks again,
Istvan
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 5/31/19 8:19 AM, Istvan Gabor wrote:
On Fri, 31 May 2019 08:43:41 +0200, Carlos E. R. wrote:
On 31/05/2019 07.07, David C. Rankin wrote:
On 05/30/2019 09:59 AM, Istvan Gabor wrote:
...
Also, what you show as the first 4-bytes (01 00 B1 00) isn't any type of byte-order-mark, but I am curious about:
EXPW
which could loosely translate to Word-XP, but I don't have a reference for that.
It is not enough for an identification:
cer@Telcontar:~/Download/Firefox_downloads> hexdump -C p 00000000 01 00 b1 00 45 58 50 57 |....EXPW| 00000008 cer@Telcontar:~/Download/Firefox_downloads> file p p: data cer@Telcontar:~/Download/Firefox_downloads>
Thank you all for answering.
I forgot to mention in my original post that I tried to open the file with Libreoffice (4.1) and Apache OpenOffice (4 something).
Both asked for choosing encoding then opened the file with many of special encodign characters like ##### etc.
file command says it is data (as Carlos showed).
If the file was made on Mac (90 %) the it must have been legacy Mac with its specific file hierarchy system.
Legacy (prior OSX) used so called file type identifiers and creator identifiers for files. These identifiers were used to determine which program should open the file. If I remember correctly these identifiers were accompanied with each file in the filesystem but separated. That is if the file itself were copied to another system, the identifiers did not go with the file, and it is not possible or difficult to find out what program created the file.
The problem with my file is that I cannot determine the progarm that created. Maybe it was not MS Word for Mac.
Thanks again,
Istvan
Let's not forget the "strings" command as a diagnostic tool. strings <filename> | less -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/05/2019 14.19, Istvan Gabor wrote:
On Fri, 31 May 2019 08:43:41 +0200, Carlos E. R. wrote:
The problem with my file is that I cannot determine the progarm that created. Maybe it was not MS Word for Mac.
Google "online tools to identify files", there are some. Or google "linux tools to identify files". Caveat: google thinks I asked "5 Command Line Tools to Find Files Quickly in Linux", which is not it. These two are promissing, though: <http://checkfiletype.com/> <https://www.forensicswiki.org/wiki/File_Format_Identification> -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Le 31/05/2019 à 14:19, Istvan Gabor a écrit :
The problem with my file is that I cannot determine the progarm that created. Maybe it was not MS Word for Mac.
two hints: * if the file is mostly text, try to remove the firts bits (with vi, for example) and see if it opens * try to open with a browser (Firefox?), and try other text encoding :-( jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Carlos E. R. -
Carlos E.R. -
David C. Rankin -
ellanios82 -
Istvan Gabor -
jdd＠dodin.org -
Ken Schneider - openSUSE -
Knurpht-openSUSE -
Simon Becherer