MobileRead Forums - View Single Post - Adding a limited Automate Feature To Sigil

KevinH · 09-22-2021, 09:16 AM

IMHO, adding all those unneeded classes to the code is really a shame. It creates quite the mess.

And it converts all selectors into class selectors with *non* mnemonic class names destroying the structure of the original css completely.

Perhaps something that simply identifies and removes identical classes would be better / safer / cleaner.

As for a properties filter, that should be easy to now do with a SavedSearch Group and run with the target set to all css stylesheets, all in one command.

That could be run first with then something that identifies and removes extra identical selectors might be enough.

But I have never seen anything with 206 stylesheets, I must admit.

If In-Design can handle style mapping from .docx styles, why isn't this handled by In-Design when inputting the .docx files?

09-22-2021, 09:16 AM	#101
KevinH Sigil Developer Posts: 8,914 Karma: 6120478 Join Date: Nov 2009 Device: many	IMHO, adding all those unneeded classes to the code is really a shame. It creates quite the mess. And it converts all selectors into class selectors with non mnemonic class names destroying the structure of the original css completely. Perhaps something that simply identifies and removes identical classes would be better / safer / cleaner. As for a properties filter, that should be easy to now do with a SavedSearch Group and run with the target set to all css stylesheets, all in one command. That could be run first with then something that identifies and removes extra identical selectors might be enough. But I have never seen anything with 206 stylesheets, I must admit. If In-Design can handle style mapping from .docx styles, why isn't this handled by In-Design when inputting the .docx files? Last edited by KevinH; 09-22-2021 at 09:42 AM.