Question for those who edit .CSS files

[Jaws]

Originally Posted by JSWolf

You don't need that file Apple requires for embedded fonts. There's a way to do it in the OPF. I cannot tell you what it is. Thorium doesn't need any of the code Apple Books needs to handle embedded fonts.

I've not heard of any program other then Books that need extra code to allow embedded fonts.

That extra file in the "Miscellaneous" segment -- next to the OPF -- is what I was referring to. I've found that trying to deal with Apple's arrogance just in the OPF can have some unexpected results in tables.

This not at all about Calibre, either the reader or any other component. It's about Apple's refusal to work with existing standards (if you're old enough, you may remember the hard-formatting of 3.5" floppy disks that was incompatible with existing formatting standards and actually reduced capacity, and the less said about choosing the 6809 processor instead of the 6805...).

[DNSB]

Originally Posted by Jaws

It's about Apple's refusal to work with existing standards (if you're old enough, you may remember the hard-formatting of 3.5" floppy disks that was incompatible with existing formatting standards and actually reduced capacity, and the less said about choosing the 6809 processor instead of the 6805...).

I was around in those good old days. Virtually every manufacturer had their own variant of formatting floppy disks and there were no standards as such. Sure, you could argue that for 3.5" floppy disks, IBM with their SD, DD and ED disks were somewhat of a standard. Though then I have to remember Microsoft's software distribution using DMF format to squeeze a bit more data on a 3.5" floppy disk, Amiga's format, one oddity that varied the rotational speed to allow squeezing more data on a disk (much like Apple's 400K/800K floppies) which was based on the Victor 9000 design though it didn't use the Victor's GCR encoding.

[Jaws]

Originally Posted by DNSB

I was around in those good old days. Virtually every manufacturer had their own variant of formatting floppy disks and there were no standards as such. Sure, you could argue that for 3.5" floppy disks, IBM with their SD, DD and ED disks were somewhat of a standard. Though then I have to remember Microsoft's software distribution using DMF format to squeeze a bit more data on a 3.5" floppy disk, Amiga's format, one oddity that varied the rotational speed to allow squeezing more data on a disk (much like Apple's 400K/800K floppies) which was based on the Victor 9000 design though it didn't use the Victor's GCR encoding.

The existing standard in 1982 (and used by pre-Mac Apple machines) was "soft formatting by machine establishing the disk format, with concentric rings" — sure, lots of variations, but the method was similar AND there was no manufacturer lockin, not even by IBM! — but Apple insisted on hardcoding its spiralized formatting onto the 3.5" disks while simultaneously abandoning the 5.25" disk (admittedly, the hardware change was going to happen...). No non-Apple machine would read those disks; an Apple machine would not read non-Apple disks. That garden wall has spikes and barbed wire on top. (Rusty barbed wire.)

It also extends to things like "what's the order of segments in a MIME-encoded e-mail message that includes binary attachments?" issue, in which Apple has refused to comply with a formal standard (don't have the RFC reference chain handy, this has been a problem for over a decade), the "forked" file-storage system, etc. To say that this makes data recovery a nightmare is an understatement... especially when dealing with an estate's data, so the originator isn't around any more...

[JSWolf]

The worst thing is when someone dies and didn't leave the password and the system is encrypted.

[Sirtel]

Originally Posted by JSWolf

The worst thing is when someone dies and didn't leave the password and the system is encrypted.

That's assuming the heirs are interested in your stuff. No one in my family would be interested in what I have on my computer.