[Editor Plugin] Otter's Editing Toolbag

[Lukusaukko]

This started out as a personal fork of Diaps Editing Toolbag, and is now in a state where I feel others might benefit from it as well - so after checking in with DiapDealer and asking his opinion, this is now released to the public.

Disclosure: AI was used in the making of this plugin. The design decisions, iteration and testing is by humans.

The plugin has four tools: expanded Span/Div tool; expanded Smarten Punctuation that has customizable apostrophe mapping and some tweaks to the underlying Smartypants engine; Cleanup tool that can clean up bad apostrophes, normalize ellipses with the ellipse character with several style options and optional wrapping of plain text inside <p> tags (useful for PG ebooks); and CSS Cleanup that cleans up some of my pet peeves in CSS, like stripping named font families, Adobe/vendor-prefixed properties, or explicit colors (for my grayscale e-ink device, most color choices are bad or mess up the night mode).

Apostrophe mapping is something that has been on my mental wishlist for a long time, since smartening tools usually cannot do this properly - like render omitted letter contractions such as 'em with a closing single quote/apostrophe. They practically always render it with starting single quote. So this plugin has a feature where you can make specific rules about how to handle it: for example "@em -> ’em" converts all cases of em preceded by apostrophe-like character to closing single quote type apostrophe. You can also have different custom exception files so if you are working with something like Engiish Romantic poems you can define exceptions just for that and avoid accidentally changing words that could appear in normal text.

It also has tweaks for things like class of '79, '68 Mustang, and '90s (Smartypants has a special rule for decades, but it's broken). It can also handle DOM-boundary cases like <i>John</i>'s where most smartening engines fail because they cannot connect the apostrope after the closing tag to the preceding word.

So what else is different from Diaps Editing Toolbag:

- Modernized codebase with QT layouts to draw the GUI (this makes it possible to hide and show elements from the UI, so that even relatively complex possibilities don't clutter up the UI unnecessarily)

- Improved XHTML parsing and serialization with lxml, so even really messy documents with nasty case of deeply nested tag soup can be parsed reliably. Unless it's broken enough not to render in the first place, this should be able to deal with it.

Many of the concepts, user workflows, and portions of the codebase originated in DiapDealer's plugin, so special thanks to DiapDealer for the original project and for giving me permission for releasing my fork to the public.

More details can be found in the README included in the archive, and each tool has a comprehensive help button.

Current stable version: 0.4.2

[Lukusaukko]

Testing versions:

0.4.3

• adds multicolumn span/div customization interface
• import tag settings from Diaps Editing Toolbag

[JSWolf]

You should (IMHO) change the UI so goes width instead of height like the original. Most screens are wider then they are high.

One other suggestion is to read the configuration from the original plugin and transfer the customizations to the new plugin.

[Lukusaukko]

Originally Posted by JSWolf

You should (IMHO) change the UI so goes width instead of height like the original. Most screens are wider then they are high.
One other suggestion is to read the configuration from the original plugin and transfer the customizations to the new plugin.

This is mostly an issue with the customization UI, right? Since the other dialogs are quite small and never get that all that big, but the customization UI can get long since it adds a new UI row for each tag. With the custom tag/attribute dropdown options, I ended up not using the customization interface all that much - unlike with Diap's original where you needed to add custom tags to edit them, here the role of the dialog is more like "these are the tags I use most often, and want to include them as shortcuts" and you'd use the custom options to modify rarely touched tags/attributes.

[JSWolf]

I did customize Diap's and I had to copy over the customization from there. However, I found the UI to be clunky because it's vertical instead of horizontal.

Since those that would be using your plugin are most likey already using Diap's. So being able to read Diap's settings and apply them would make it a lot easier to setup your plugin.

[Lukusaukko]

Originally Posted by JSWolf

I did customize Diap's and I had to copy over the customization from there. However, I found the UI to be clunky because it's vertical instead of horizontal.

Since those that would be using your plugin are most likey already using Diap's. So being able to read Diap's settings and apply them would make it a lot easier to setup your plugin.

Please check the second post in this thread, where I've uploaded a new testing version.

I have now added a button to import the settings from Diaps, but you have to browse to diaps_editing_toolbag_SpanDivEdit_settings.json file manually.

The customization interface is now based on 10 rows, and once it goes past that, it will add another column, so it will expand width-wise (may add a setting for number of rows later).

If you are willing to test it, please do - as I hardly use it, my test case was quite small, but it should work with larger files as well.

[JSWolf]

Since you are keeping the vertical look, will it full fit on a screen that's only 768 lines?

I will test it when I get a chance. Thanks.

[Lukusaukko]

Originally Posted by JSWolf

Since you are keeping the vertical look, will it full fit on a screen that's only 768 lines?

I will test it when I get a chance. Thanks.

If changing my monitor to 1024x768 is a suitable test, then just about. The bottom border may end up under the task bar, but the buttons are all visible.

[JSWolf]

Originally Posted by Lukusaukko

If changing my monitor to 1024x768 is a suitable test, then just about. The bottom border may end up under the task bar, but the buttons are all visible.

This is why I suggested going horizontal instead of vertical. To me, I prefer the horizontal UI.

[Lukusaukko]

Originally Posted by JSWolf

This is why I suggested going horizontal instead of vertical. To me, I prefer the horizontal UI.

Could be ok for the customize dialog without leaving too much white space in the layout. I'll see what I can do if it's not working for you.

[JSWolf]

Originally Posted by Lukusaukko

Could be ok for the customize dialog without leaving too much white space in the layout. I'll see what I can do if it's not working for you.

It works. It's just that for those with a smaller screen, they may need to it be horizontal.

On my main laptop, my screen is 2560x1440 and my second laptop is 1920x1200. My Mini-PC can be 4K if I use my TV as a monitor. If I use the computer monitor, it would be 2560x1440,