R. L. Dane :debian: :openbsd:🧉 on Nostr: npub1q5cq7…9tdyq npub1suam9…tszrk npub1wn3sl…sj4ad npub1j8v6w…94kxc Random ...
npub1q5cq7wef0kmwn4r26w4wvzqh4j92mwwt047jppn8fk7d4py0j78qc9tdyq (npub1q5c…tdyq) npub1suam9f3gwqeqxstd3rlccpekpfuxrgawc8est0jtkhpzm63zz5nqxtszrk (npub1sua…szrk) npub1wn3slql7qtxrrmx7f4k8tfs4y0v9ku559qm7ae88tkjurcjplxzs5sj4ad (npub1wn3…j4ad) npub1j8v6wt64gsdm8a3rycwgdq2jzwylk4ty4gztzcvun79ywxpnfcds794kxc (npub1j8v…4kxc)
Random aside, the modern mac .rtfd format reminds me a *LOT* of the classic mac "TeachText" format, which used a plain text file as the text itself, but used the #ResourceFork of the file to store images.
So the files *looked* like they were rich text because they had headers in a larger font than the rest of the body, but it was really just plain text with bitmap headers ;)
...
Random aside, the modern mac .rtfd format reminds me a *LOT* of the classic mac "TeachText" format, which used a plain text file as the text itself, but used the #ResourceFork of the file to store images.
So the files *looked* like they were rich text because they had headers in a larger font than the rest of the body, but it was really just plain text with bitmap headers ;)
...