&()nbsp , &()#160 , inconsistencies??

[theducks]

Originally Posted by MickiTee

Will you be updating the Insert Character functionality to replace the existing entities with HEX unicode values in V0.9?

Can we leave IT AS Entities and simply provide a clean-on-exit (convert entities) OPTION

Only a few need this and many find entities so much easier to work with while editing.

[Turtle91]

Quick question... why would anyone use entities in the first place? Why not just insert the actual unicode character??? Much easier to understand what the entity is if you just read it. And most readers/apps support unicode, don't they?

[theducks]

Originally Posted by Turtle91

Quick question... why would anyone use entities in the first place? Why not just insert the actual unicode character??? Much easier to understand what the entity is if you just read it. And most readers/apps support unicode, don't they?

Simple I remember the NAMES of the ones I frequently use. No Charts, Pick lists needed.
Quick (without a chart) Where is NGU

[Turtle91]

ßàáíìëêéÞÔÓÒÝèçæÛÜÑÐÏÚåäÙÎÍŠãïú§©®™•±

No need for codes at all.

[KevinH]

And by just looking you can tell the difference between a nbsp and normal space for editing purposes, right?

;-)

KevinH

Originally Posted by Turtle91

ßàáíìëêéÞÔÓÒÝèçæÛÜÑÐÏÚåäÙÎÍŠãïú§©®™•±

No need for codes at all.

[Turtle91]

THAT makes sense.... how many unicode characters are invisible?

[KevinH]

a bunch, here is a link I found

https://www.cs.tut.fi/~jkorpela/chars/spaces.html

[Notjohn]

Originally Posted by KevinH

Hi,
You (and even new users) will be able to use both named and numeric entities by changing the Preserve Entities preferences.

Thank you, thank you! I knew that Sigil would never let me down!

[Notjohn]

Originally Posted by Turtle91

ßàáíìëêéÞÔÓÒÝèçæÛÜÑÐÏÚåäÙÎÍŠãïú§©®™•±

No need for codes at all.

I don't think that works for writing a web page! (At least not if you're writing in WordStar, tee hee.)

Besides, nailing a character in a chart is more difficult for me than writing for example — which I have off by heart. The only things I have to look up are the more obscure diacrits.

[DiapDealer]

Originally Posted by Turtle91

THAT makes sense.... how many unicode characters are invisible?

Originally Posted by KevinH

a bunch, here is a link I found

https://www.cs.tut.fi/~jkorpela/chars/spaces.html

And remember ... there's a handy plugin that will turn those sneaky invisible characters into entities (or whatever you want to turn them into).

[Turtle91]

Nice Diap!

Added to that, it would be really nice to have a button/function that automatically converts entities (named or numbered) to their actual character. One of those last step after editing and before saving things.

[Jellby]

Originally Posted by Turtle91

Quick question... why would anyone use entities in the first place? Why not just insert the actual unicode character??? Much easier to understand what the entity is if you just read it. And most readers/apps support unicode, don't they?

You can always type an entity, but the Unicode character may not be easily accessible in your keyboard layout (you could use ALT+code, but then you need to know the code, which is harder, and it doesn't work in all platforms).

Some characters are not visually distinguishable, like &nbps; and space, or m- and n-dash in a monospace font. Some characters are actually the same, like curly apostrophe and curly right single quote (I sometimes use entities for one of them, so I can know which is which if I want to bulk-replace quotes, for example). You may want to explicitly save some accented characters as precomposed and others as accent + base character, with entities you can see the difference, without... the editor may convert one to the other.

But entities are a pain in the arse for regex and searching in general.

[eschwartz]

I just thought I'd point out, calibre editor does what I personally like to think of as The Right Way.

As you type an entity -- named/numeric -- calibre converts it into a unicode character.

Troublesomely confusing unicode characters, e.g. U+00A0 (   ) get highlighted in yellow, indicating you should take a look at what it actually is.

[Notjohn]

>curly apostrophe and curly right single quote

They're different? OMG. I thought they were the same (so does Bill Gates, I think, to judge by how Word replaces my straight quotes with curlies).

[DiapDealer]

Originally Posted by eschwartz

I just thought I'd point out, calibre editor does what I personally like to think of as The Right Way.

As you type an entity -- named/numeric -- calibre converts it into a unicode character.

Troublesomely confusing unicode characters, e.g. U+00A0 (   ) get highlighted in yellow, indicating you should take a look at what it actually is.

The calibre-editor doesn't have the headache of dealing with allowing WYSIWYG editing (by choice). If Sigil dropped WYSIWYG editing, it could do it The Right Way, too. But alas ... different things are different.

Do you never tire of pointing out what calibre's editor does differently than Sigil? Are they not keeping you busy enough over there in calibre-land or something?