I had to install iWork on my MacOS 12 machine, but those 'charming people' at Apple Central, in a merry attempt to make me go out and spend major spondulicks on their 'latest and greatest' have now made iWork unavailable for any machine running a lower version of MacOS than 14.
This is particularly 'fudgy-poos' as I own an iMac that runs MacOS 12 that HAD iWorks pre-installed, but in a fit of bonkersness deleted it previously.
I downloaded the required version of iWorks from the internet archive and then . . .
Or regress to a previous version of MacOS.
Or (heaven forbid), install a different OS altogether. ::said with a slight hint of sarcasm::
Although don't do what a teacher at my work did: go get themselves one of the last macs that would natively boot into Windows, then go install windows 7 on it.
All of the pose value, with all of the vulnerabilities. And with all the questions as to "why not just get an old windows 7 PC if that's what you really wanted all along? - and pay a 6th of the cost for essentially the same parts, just not wrapped up in an Apple case."
tperry2x wrote: ↑Fri Feb 28, 2025 8:19 pm
Or regress to a previous version of MacOS.
Or (heaven forbid), install a different OS altogether. ::said with a slight hint of sarcasm::
Although don't do what a teacher at my work did: go get themselves one of the last macs that would natively boot into Windows, then go install windows 7 on it.
All of the pose value, with all of the vulnerabilities. And with all the questions as to "why not just get an old windows 7 PC if that's what you really wanted all along? - and pay a 6th of the cost for essentially the same parts, just not wrapped up in an Apple case."
Or depending on what one needs Windows 7 for, why not just run Windows in a VM within the macOS host?
That's ignoring the fact the very latest (AppleSilicon CPU) Macs would need to run the ARM builds of Windows 10/11 in order to run Windows 'native' without CPU emulation.
richmond62 wrote: ↑Tue Mar 11, 2025 6:09 am
iWorks is supposedly better at compressing PDF documents than LibreOffice, and does NOT corrupt them.
I've never had any PDFs being corrupted by LibreOffice, and I use it daily for sending out PDFs.
Compression-wise, it's all to do with the settings you choose:
My younger son sent me the first half of his doctoral thesis as a PDF to go through in case there were any minor grammar mistakes, or logical cock-ups.
There were neither, and as he is a clever laddie he has been accepted to do the second part of the Doctorate (Kings College, London).
HOWEVER there were several words that ended in "ion" in his footnotes which LibreOffice rendered as "N".
Oh, and having been working with several PDF documents containing embedded Old Church Slavonic and Glagolitic fonts recently; while those rendered perfectly in the Macintosh Preview program, LibreOffice produced an utter Pig's Breakfast.
richmond62 wrote: ↑Tue Mar 11, 2025 9:03 am
Oh, and having been working with several PDF documents containing embedded Old Church Slavonic and Glagolitic fonts recently; while those rendered perfectly in the Macintosh Preview program, LibreOffice produced an utter Pig's Breakfast.
Do you mean you opened the PDF in Libreoffice, as that would cause any embedded fonts to not necessarily be interpreted correctly. (Libreoffice is opening the PDF in edit mode, so needs the fonts). Preview is only viewing it, so doesn't need the user to have the embedded fonts installed on their system - hence the "corruption".
richmond62 wrote: ↑Tue Mar 11, 2025 8:44 pm
But that does not explain the corruption of the footnotes in my son's work.
Maybe, maybe not. I mean, do they use Arial? What version of Arial? - Arial was different on a Mac, on Windows and there were different releases. Arial on MacOS 9 is not the same Arial on MacOS X for example. (Kerning is different and other things like contains unicode stuff on MacOS X which OS9 didn't have).
Not saying that Libreoffice is never the cause of document corruption, but there are normally other underlying reasons - it's a conversion process after all, not a standard open that's happening. With conversion, it's normally a trade-off between how it looks and how it's technically structured. Depends on how the conversion is interpreted. That's true in any program. Plus, if the PDF has had it's fonts outlined when it was created, this will play merry-hell with any program when it's read back in to be edited. Also depends on what version of Libreoffice too.
