• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: driving LibreOffice.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: driving LibreOffice.


  • Subject: Re: driving LibreOffice.
  • From: Iurista GmbH <email@hidden>
  • Date: Sun, 21 Aug 2016 19:26:03 +0200

I just made a check: I still own 4361 Applework files.
I use two methods for converting them (if I find the time):

1. Files of which I still would like to access their content will be converted to Pages, which opens Applework files directly.
2. I still run 10.6.8 on a Mac Mini, and therefore Appleworks 6. Files which are kept only for memory will be printed to PDF, also by means of a script

If you have no access to AppleWorks, there's also the possibility to convert to Pages and then print to PDF. No big scripting effort.

Rudolf


Am 20.08.2016 um 17.56 schrieb Yvan KOENIG:

> Hello has
>
>
>
>> Le 20 août 2016 à 17:51, has <email@hidden> a écrit :
>>
>> Yvan KOENIG wrote:
>>> An user asked me for a script exporting more than 10,000 AppleWorks documents as PDF files. ... As LibreOffice is able to open the AppleWorks file, I'm working upon a code doing the job with this free app running on modern machines.
>> LibreOffice is directly scriptable with Python. I expect they'll have forums where you can get help.
>>
>>> set theDoc to choose file of type {"public.rtf"}
>>
>
> I sent a script treating rtf files because I guess that few helpers have AppleWorks files available on their machine.
>
>> If they're RTF files, it shouldn't be that hard to convert them to other formats using other apps, Cocoa APIs, etc. The main thing with opening old file formats in other apps is to check the translation process isn't losing any formatting or content you care about.
>>
>> However, if scripting AppleWorks on an old Mac works already works then why not just leave that to spin through the jobs over a few days? If it's taking more than a minute per-file, there's probably something wrong with the script/machine, else it'll be done in under a week. As long as your error handling is robust and knows to skip and log any problem files, it shouldn't matter if it's a bit slow to get through it. Why waste days trying to devise and debug a 'cleverer' implementation for a one-off throwaway script anyway?
>


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users

This email sent to email@hidden


  • Follow-Ups:
    • Re: driving LibreOffice.
      • From: Yvan KOENIG <email@hidden>
References: 
 >Re: driving LibreOffice. (From: has <email@hidden>)
 >Re: driving LibreOffice. (From: Yvan KOENIG <email@hidden>)

  • Prev by Date: Re: A bug to crash AppleScript Applets
  • Next by Date: Re: driving LibreOffice.
  • Previous by thread: Re: driving LibreOffice.
  • Next by thread: Re: driving LibreOffice.
  • Index(es):
    • Date
    • Thread