Improvements? New Features? post sigil 2.7.6

[un_pogaz]

Oh, quick, a little bug:
If you delete all the entrys in the ToC editor, you can no longuer add a new entry (since their require a entry as reference)

[User_Z]

Hello.

Where in the interface are the following lines found:
AdjustImage
PrettyPrinting...
Mending...

If possible, with pictures.

[KevinH]

Originally Posted by un_pogaz

Oh, quick, a little bug:
If you delete all the entrys in the ToC editor, you can no longuer add a new entry (since their require a entry as reference)

Yes you then need to rebuild the ToC first to get restarted. It has always worked like that. So this is not something new, I am not sure if it is a bug. The TOC editor has always needed a reference to an underlying heading tag in order to allow the editing to work. It just adds title attribute or a special class to tell Sigil to ignore it. But without a pointer to an underlying h1-h6 tag nothing can be done. It is not a TOC creator (there is a different tool that does that), it is meant to edit existing entries.

After studying the code, I probably could add a check in the delete code itself to check if after the delete the invisible root item has no rows left and if so inject an empty row.
I will look into that.

Update: I have pushed to master a change to inject an empty placeholder entry if when editing the TOC, the user deletes the last entry. So there is always an entry so "Add above" and "Add below" can still both work with no issues as does simply editing the placeholder itself.

[KevinH]

Originally Posted by User_Z

Hello.

Where in the interface are the following lines found:
AdjustImage
PrettyPrinting...
Mending...

If possible, with pictures.

Huh? Is this a request for a new feature? Or a bug report about a translation? I am confused. Most strings to translate are found in either the C++ (cpp files) or in the qt ui files. Simply grepping Sigil source should tell you which file.

Note all ui strings in ui files are automatically included in to the list of strings to be translated.

For example: Here is one place that the string AdjustImage is set for translation for a WindowTitle.

In Sigil/src/Form_Files/AdjustImage.ui

<?xml version="1.0" encoding="UTF-8"?>
<ui version="4.0">
 <class>AdjustImage</class>
 <widget class="QWidget" name="AdjustImage">
  <property name="windowTitle">
   <string>AdjustImage</string>
  </property>

Some translatable strings are set on menu actions many of which can be found in the main.ui located in that same folder.

If you are looking for screenshots of new features then please download the latest DNSB test build.

[User_Z]

This question asks where I can see new strings from the new features implemented on my computer screen while working with the program (test build 2.8.0).

Judging by the provided code fragment, the string "AdjustImage" doesn't require translation, even though it's in Transifex.
Conversely, I see the string "coordinates" on the screen, but not in Transifex.

[DiapDealer]

Prettify and Mend Are not new features. Prettify has been tweaked.

Mend is on by default, but you can turn it off in Sigil's Preferences.

Both can be run manually from the context menu by right clicking on CodeView when Xhtml is open.

The ways to trigger Prettify and Mend have not changed. They are both covered in the user manual.

The change to Prettify is the ability to tweak how it works by means of an .xml file in Sigil's preferences. There is no current documentation for this (aside from posts in this thread) because this new feature has not been released yet.

The other new features are found when you open an image from the bookbrowser. New buttons are available for editing images directly from Sigil.

[KevinH]

Originally Posted by User_Z

This question asks where I can see new strings from the new features implemented on my computer screen while working with the program (test build 2.8.0).

Judging by the provided code fragment, the string "AdjustImage" doesn't require translation, even though it's in Transifex.
Conversely, I see the string "coordinates" on the screen, but not in Transifex.

AdjustImage is a window title just like BookBrowser or any other window in Sigil and can and probably should be translated.

I will add a tr() around the word "coordinates" to mark it as translatable. What about "Zoom" should that be translatable too?

This will require rebuilding the base for translations one more time. But we are in no rush so.

[User_Z]

>What about "Zoom" should that be translatable too?

Yes.

[KevinH]

Okay, I have pushed this to master. The new base for translations should be automagically updated sometime overnight by Transifex so any time after that the strings will be available for translators.

And I have pulled in all translations so far into Sigil but with the recent base.ts update more pulls will be made over the next 2 weeks, so no rush.

[KarlG]

Originally Posted by KevinH

And any new Sigil Preferences are not a good idea. We have too many Preferences as it is now.

So at best this would be an environment variable setting only.

I don't think Sigil has THAT many preferences, but if you feel differently then an environment variable would be fine.

[KarlG]

Originally Posted by KevinH

The last one used is adaptive. It is used everyplace in Sigil, Very few people will have organized all desired files to sit beside their epub. But even if they did, after the first input, it will adapt. How does forcing it to one location to start help most users?

Maybe I am missing something here. Please justify it would be better for most people?

If very few people will have organised all desired files, then each time they are working on a new epub and want to add new files they're probably going to have to select a different folder anyway.

So with this option, it just means they're starting from the epub folder and not the last one used.

Either way, they're going to have to select a new folder (and maybe if they notice they're always starting in the actual epub folder they might start organising their files better).

[KevinH]

Originally Posted by KarlG

If very few people will have organised all desired files, then each time they are working on a new epub and want to add new files they're probably going to have to select a different folder anyway.

So with this option, it just means they're starting from the epub folder and not the last one used.

Either way, they're going to have to select a new folder (and maybe if they notice they're always starting in the actual epub folder they might start organising their files better).

Still not convinced. Many epubs people edit will not have extra image files, extra xhtml files, and css files to add to that epub sitting right beside it. Many have separate image folders, css folders, or boilerplate xhtml folders that can be in various places. Not necessarily next to an epub. This is especially true for those that edit epubs via calibre's open with.

So again, some better justification for this feature or maybe a few other users requesting this feature are really needed. Change just to save one or two users a single click or two are really not the kinds of feature requests I will accept. You can of course set a folder as a commonly used location to remember in the file dialog.

[KevinH]

Deleted a duplicate response generated somehow

[DNSB]

Link removed

[jugaor]

Hi.

Originally Posted by KevinH

1. add some way (especially for tables) for users to control what Prettify does
(accepted and in master)

Thanks, a fantastic improvement!
One question/suggestion (aka suquestion): is there any way to configure prettyprint.xml to wrap lines at <br / > tags? (like it used to do in pre-Gumbo Sigil).
Often, especially with third-party epubs/imports from word processors/copy-pasted content from websites, these tags appear, and it would be visually easier if they were clearly marked in code view.
(Fingers crossed)

Originally Posted by KevinH

7. fix issues related to dark mode and Sigil's native dark mode theme on windows
when trying to identify the active tab (without needing qss styling)
(this is still open and waiting to see how it resolves with Windows users)

Since this was initially my request, with my limited qss skills (enhanced by BeckyEbook’s suggestions), I've already solved it.
If it's still open because of me, please feel free to close it.