Word 1.x-5.x?
in [Mac Applications]
|
From: Ed Kearns on 26 Feb 2010 12:37 in article tph-4FA9F7.09090426022010(a)localhost, Tom Harrington at tph(a)pcisys.no.spam.dammit.net wrote on 2/26/10 9:09 AM: > In article <C7AC5755.2AF77%kearnser(a)gmail.com>, > Ed Kearns <kearnser(a)gmail.com> wrote: > >> in article fmoore-51D4F3.10270625022010(a)feeder.eternal-september.org, Fred >> Moore at fmoore(a)gcfn.org wrote on 2/25/10 8:27 AM: >> >>> In article <C7AB4D4B.2A3B4%kearnser(a)gmail.com>, >>> Ed Kearns <kearnser(a)gmail.com> wrote: >>> >>>> in article 4b85c048$0$9208$c3e8da3(a)news.astraweb.com, Warren Oates at >>>> warren.oates(a)gmail.com wrote on 2/24/10 5:11 PM: >>>> >>>>> In article <C7AA900D.29DD4%kearnser(a)gmail.com>, >>>>> Ed Kearns <kearnser(a)gmail.com> wrote: >>>>> >>>>>> But does anyone know what Word 1.x-5.x means? >>>>> >>>>> Yes. >>>> I found that the files have no extension, expressed or otherwise. I also >>>> found an application, ManageNameExt, that will change these to .doc or .txt >>>> or whatever. >>> >>> If you mean just change the extension, that won't do it. There was a >>> file format change between 5 and later (i.e. .doc). And, yes the early >>> word files had no extension because the previous Mac OS didn't use them. >> I thought that because it loads into my new Mac it would be ok. I sent it to >> a friend who has Windows and he can't open it! What's the best way to do >> this? > > You mentioned earlier that you can open the files with Word 2008 and > save them in other formats. You've also had a couple of suggestions for > how to automate the conversion of all of the documents into other > formats. What problem are you trying to solve that you don't already > have an answer to? I didn't get, or didn't understand, any way to automate the conversion of a batch. Did you the think the Applescript approach would work on a batch? Ed
From: Tom Harrington on 26 Feb 2010 13:59 In article <C7AD54D0.2BD94%kearnser(a)gmail.com>, Ed Kearns <kearnser(a)gmail.com> wrote: > in article tph-4FA9F7.09090426022010(a)localhost, Tom Harrington at > tph(a)pcisys.no.spam.dammit.net wrote on 2/26/10 9:09 AM: > > > In article <C7AC5755.2AF77%kearnser(a)gmail.com>, > > Ed Kearns <kearnser(a)gmail.com> wrote: > > > >> in article fmoore-51D4F3.10270625022010(a)feeder.eternal-september.org, Fred > >> Moore at fmoore(a)gcfn.org wrote on 2/25/10 8:27 AM: > >> > >>> In article <C7AB4D4B.2A3B4%kearnser(a)gmail.com>, > >>> Ed Kearns <kearnser(a)gmail.com> wrote: > >>> > >>>> in article 4b85c048$0$9208$c3e8da3(a)news.astraweb.com, Warren Oates at > >>>> warren.oates(a)gmail.com wrote on 2/24/10 5:11 PM: > >>>> > >>>>> In article <C7AA900D.29DD4%kearnser(a)gmail.com>, > >>>>> Ed Kearns <kearnser(a)gmail.com> wrote: > >>>>> > >>>>>> But does anyone know what Word 1.x-5.x means? > >>>>> > >>>>> Yes. > >>>> I found that the files have no extension, expressed or otherwise. I also > >>>> found an application, ManageNameExt, that will change these to .doc or > >>>> .txt > >>>> or whatever. > >>> > >>> If you mean just change the extension, that won't do it. There was a > >>> file format change between 5 and later (i.e. .doc). And, yes the early > >>> word files had no extension because the previous Mac OS didn't use them. > >> I thought that because it loads into my new Mac it would be ok. I sent it > >> to > >> a friend who has Windows and he can't open it! What's the best way to do > >> this? > > > > You mentioned earlier that you can open the files with Word 2008 and > > save them in other formats. You've also had a couple of suggestions for > > how to automate the conversion of all of the documents into other > > formats. What problem are you trying to solve that you don't already > > have an answer to? > I didn't get, or didn't understand, any way to automate the conversion of a > batch. Did you the think the Applescript approach would work on a batch? Applescripts can work on collections of files dropped on the script. Word 2008's scripting capabilities include "save as" with file format. So yes, it's at least worth taking a serious look at, because all the capabilities appear to be present. -- Tom "Tom" Harrington Independent Mac OS X developer since 2002 http://www.atomicbird.com/
From: Ed Kearns on 26 Feb 2010 15:02 in article tph-81B2A2.11592326022010(a)localhost, Tom Harrington at tph(a)pcisys.no.spam.dammit.net wrote on 2/26/10 11:59 AM: > In article <C7AD54D0.2BD94%kearnser(a)gmail.com>, > Ed Kearns <kearnser(a)gmail.com> wrote: > >> in article tph-4FA9F7.09090426022010(a)localhost, Tom Harrington at >> tph(a)pcisys.no.spam.dammit.net wrote on 2/26/10 9:09 AM: >> >>> In article <C7AC5755.2AF77%kearnser(a)gmail.com>, >>> Ed Kearns <kearnser(a)gmail.com> wrote: >>> >>>> in article fmoore-51D4F3.10270625022010(a)feeder.eternal-september.org, Fred >>>> Moore at fmoore(a)gcfn.org wrote on 2/25/10 8:27 AM: >>>> >>>>> In article <C7AB4D4B.2A3B4%kearnser(a)gmail.com>, >>>>> Ed Kearns <kearnser(a)gmail.com> wrote: >>>>> >>>>>> in article 4b85c048$0$9208$c3e8da3(a)news.astraweb.com, Warren Oates at >>>>>> warren.oates(a)gmail.com wrote on 2/24/10 5:11 PM: >>>>>> >>>>>>> In article <C7AA900D.29DD4%kearnser(a)gmail.com>, >>>>>>> Ed Kearns <kearnser(a)gmail.com> wrote: >>>>>>> >>>>>>>> But does anyone know what Word 1.x-5.x means? >>>>>>> >>>>>>> Yes. >>>>>> I found that the files have no extension, expressed or otherwise. I also >>>>>> found an application, ManageNameExt, that will change these to .doc or >>>>>> .txt >>>>>> or whatever. >>>>> >>>>> If you mean just change the extension, that won't do it. There was a >>>>> file format change between 5 and later (i.e. .doc). And, yes the early >>>>> word files had no extension because the previous Mac OS didn't use them. >>>> I thought that because it loads into my new Mac it would be ok. I sent it >>>> to >>>> a friend who has Windows and he can't open it! What's the best way to do >>>> this? >>> >>> You mentioned earlier that you can open the files with Word 2008 and >>> save them in other formats. You've also had a couple of suggestions for >>> how to automate the conversion of all of the documents into other >>> formats. What problem are you trying to solve that you don't already >>> have an answer to? >> I didn't get, or didn't understand, any way to automate the conversion of a >> batch. Did you the think the Applescript approach would work on a batch? > > Applescripts can work on collections of files dropped on the script. > Word 2008's scripting capabilities include "save as" with file format. > So yes, it's at least worth taking a serious look at, because all the > capabilities appear to be present. Well, I've tried looking at tutorials and forums on Applescript, and I don't have a clue how to do this. I have a steep learning curve! Ed
From: J.J. O'Shea on 27 Feb 2010 12:26 On Wed, 24 Feb 2010 00:21:07 -0500, Ed Kearns wrote (in article <C7AA0553.29913%kearnser(a)gmail.com>): > I have some old word files (archiving old textual material). They open fine > in Word 2008 for the Mac. However, I'm trying to find a way that folks who > have both Macs and Windows in our church can search across files to find > searchstrings. BBEdit Lite works well for this. But the software my Windows > friends would like to use this (NoteTab Lite) only works with .txt or .rtf > files. I tried to convert them with various online DOC to TXT converters, > and they tell me they're not DOCs. A get-info says they're Word 1.x-5.x. They're old MS Word for Mac files, probably Word 5 or 5.1 format. > I > can't get any information on this, much less do I know how to convert them > to a TXT file. MacWrite Pro, if you can get it, and most versions of Claris/Apple Works, will read/write them at least as well as Word 2008. DataViz's MacLink Plus will do so as well, and is the best solution if you have a large number of these files as it will do the translation as a batch. if you don't have MacLink Plus, you can automate the translation with Word for Mac or Claris/Apple Works using AppleScript and/or Automator. > > Any Suggestions? I have a fairly elderly edition of MacLink Plus. (v 13, I think; the current version is 16.something) I haven't bothered to update it recently as I don't use it anywhere near as often as I used to back when I first got a much early version 20+ years ago. However, when I do use it, it's because nothing else I have handy will do the job as quickly and easily as it will. -- email to oshea dot j dot j at gmail dot com.
From: isw on 27 Feb 2010 13:10 In article <C7AA0553.29913%kearnser(a)gmail.com>, Ed Kearns <kearnser(a)gmail.com> wrote: > I have some old word files (archiving old textual material). They open fine > in Word 2008 for the Mac. However, I'm trying to find a way that folks who > have both Macs and Windows in our church can search across files to find > searchstrings. BBEdit Lite works well for this. But the software my Windows > friends would like to use this (NoteTab Lite) only works with .txt or .rtf > files. I tried to convert them with various online DOC to TXT converters, > and they tell me they're not DOCs. A get-info says they're Word 1.x-5.x. I > can't get any information on this, much less do I know how to convert them > to a TXT file. > > Any Suggestions? As you have found out, the text in the files is readable, because you can search it with BBEdit (the rest is formatting stuff). If all you want to do is search the text, maybe you don't need to convert them at all. What happens if you just add ".txt" to the end of the file names and then try to open them with NoteTab Lite? Isaac
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: Quicktime X Player Next: Entourage Contacts Date Stamping |