Quote:
Originally Posted by JSWolf
I've had another go at this and I've managed to keep the italics and cleaned up the code very much.
It was a lot easier the second time now that I knew what to look for. And it even took less time.
|
And? Would you be able to list a few steps on how you did it?
Quote:
Originally Posted by Hitch
I seem to remember this at least...hell, 7-8 years back? I think it existed with the old Typekit subscriptions, too. And Pages (the Mac word processor) has had this same exact issue for dog's years. We used to get a lotta lotta work from Pages users, between that white background cruft and the MIA italics. It's gotten better, but the Case of the Missing Italics still plagues them.
|
Thanks for the info.
And I haven't had the "pleasure" of working with anything from Pages yet.
I usually noticed missing italics further along in the process after too aggressive initial cleanup steps. Nowadays, it's one of the first things I look for.
Quote:
Originally Posted by Hitch
I know, right? Google is a damned internet company. You'd think that they could focus on the underlying HTML, right? But noooooooooooooo, they're thinking about how they can be like Apple and make everything drag-drop and easy-peasy. Ugh.
|
A while back, I came up with a "markdown" -> LibreOffice -> Google Docs workflow, so I could mass convert my changelogs.
(See the ~steps in my Reddit answers from 7 months ago:
/r/LibreOffice: "How do I replace formatting tags surrounding text with that text formated?".)
But the annoying step then became Styles within Google Docs.
If I made any sort of adjustments, the super clean Styles I applied in the LibreOffice step became botched.
Side Note: And has everyone seen, LibreOffice 7.1 introduced a new "Style Inspector":
https://wiki.documentfoundation.org/...tyle_inspector
It allows you to easily spot direct formatting + what's being applied where (similar to Inspect Code in your browser).