Sigil-0.9.15 Beta Released

[DiapDealer]

Originally Posted by Tex2002ans

Looks like it only shows #160 .

I'll toss   in there now and test.

Make sure it's one or the other: not both.

Originally Posted by Tex2002ans

(But I never looked at/messed with that menu in my life—only when I fixed the Sigil manual—and Sigil definitely didn't replace   in previous versions.)

Sure it did (if   was in the list). That's what it's intended to do.

Originally Posted by Tex2002ans

Note: Just tested with   in the Preserved Entities, still replaces it.

Again ... make sure it's one or the other (and not both) and that's what all no-break spaces will be converted to. If you work with EPUB3 at all, numeric (or neither starting with 0.9.14) is recommended.

And "Never in my life (except for) "... really?

[Tex2002ans]

Originally Posted by DiapDealer

Again ... make sure it's one or the other (and not both) and that's what all no-break spaces will be converted to.

There we go. Back as it should be (forgot that one-or-the-other nuance).

Originally Posted by DiapDealer

If you work with EPUB3 at all, numeric (or neither starting with 0.9.14) is recommended.

Perhaps that's another potential enhancement, splitting Preserved Entities into EPUB2 + EPUB3. Or having checkboxes that applies a given entity to one/both.

Originally Posted by DiapDealer

And "Never in my life (except for) "... really?

I'm serious.

I only noticed because I have Saved Searches that adjust ellipses (using  ), and I haven't touched those things in years and years since they're proven across hundreds of books.

Just went to fix an older one of my ebooks right now, and the ellipsis fix wasn't working. Surprised to see &160; in my code, and I would never use that. (Plus it would make code comparing Before/After an enormous pain.)

[DiapDealer]

Originally Posted by Tex2002ans

Perhaps that's another thing, splitting Preserved Entities into EPUB2 + EPUB3. Or having checkboxes that applies a given entity to one/both.

Or just get used to using numeric entities if you commonly work with both EPUB3/2 (since they're valid in both). Or better yet... empty the Preserve Entities list and go totally entity free.

We thought briefly about separate entities lists, but ultimately couldn't justify the extra prefs clutter when using numeric entities solves the problem for both formats.

Just went to fix an older one of my ebooks right now, and the ellipsis fix wasn't working. Surprised to see &160; in my code, and I would never use that.

Then you never had the numeric no-break space entity in your list back then, or you'd have definitely seen them.

[Tex2002ans]

Originally Posted by DiapDealer

Then you never had the numeric no-break space entity in your list back then, or you'd have definitely seen them.

I have a Sigil 0.9.13 EPUB I just created from 2019.07.03 with nbsp.

I updated to Sigil 0.9.14 a few days ago... magically, nbsp's are now changed to #160...

I never visited the Preserved Entities menu. Only variable that changed in the past few days was the update. :P

I'm blaming YOU Diap, you you you! You're the reason why my EPUBs are all broken.

[BeckyEbook]

This commit was change default preserve entity from & nbsp; to & #160;

This should not be a problem, but of course for saved searches can cause minor inconvenience.

Use for both:

&(nbsp|#160);

[DiapDealer]

If you didn't place   in your Preserve Entities list yourself. Then the only answer is that you deleted your Sigil Preferences at some point and allowed them to be re-created with the default values. The default entry in the Preserve Entities list was changed to   recently. We did it precisely because it ensures being able to open all EPUB2s and EPUB3s without generating errors. If you try to open an EPUB3 containing no-break spaces with   in the Preserve Entities list, there will immediately be errors. We thought it best not to subject new users to that possibility.

Anyway ... now you now. Put your   back in your list and live happy (it would still be there had your prefs not been wiped/reset at some point). Just don't come crying when an unknown epub you open starts giving you pink errors!

[Tex2002ans]

Originally Posted by DiapDealer

Anyway ... now you now. Put your   back in your list and live happy (it would still be there had your prefs not been wiped/reset at some point).

You know what else could have happened?

I did open an EPUB3 within the past few days too (rarely do that). Perhaps that's what changed my Preserved Entities list (and not the update itself)? And when I went back to my usual EPUB2 ways, it never changed back?

(I usually have multiple Sigil's open as well... and we all remember those strange shenanigans with the Clips blanking themselves out between Sigil instances.)

So perhaps it was a case of EPUB3 and EPUB2 being opened at the same time... overwriting some sort of preferences.

Originally Posted by DiapDealer

Just don't come crying when an unknown epub you open starts giving you pink errors!

You'll pry those human-understandable named entities from my cold, dead hands!

(Enough rambling, time for bed, too sleepy!)

[Notjohn]

Originally Posted by Tex2002ans

You'll pry those human-understandable named entities from my cold, dead hands!

Mine too!

[DiapDealer]

I like human understandable characters myself. So I typically rock a completely empty Preserve Entities list. Which means I don't have to see a single entity (named, numeric or hex)* in Code View, but hey!... whatever floats your boat.

* Yes, I know characters like & and < and > would still require the use of entities in Code View, but those entities are always preserved without listing them. So please -- in the name of all that's holy -- never ever enter any of those 3 particular entities in the Preserve Entities list!! In fact, I need to remember to modify Sigil to ignore those entities if someone mistakenly adds them to the Preserve Entities list.

[Tex2002ans]

Originally Posted by DiapDealer

So please -- in the name of all that's holy -- never ever enter any of those 3 particular entities in the Preserve Entities list!! In fact, I need to remember to modify Sigil to ignore those entities if someone mistakenly adds them to the Preserve Entities list.

Now that sounds like a good addition.