What happened to &XXquo; characters?

camdenmaine · 03-03-2013, 03:40 PM

I carefully replaced all opening quotes with “ and closing quotes with ” and similar changes for single quotes and dashes etc. Everything looks fine in book view. But when I look at the files in code view, I see that Sigil has replaced some of the &XXquo; characters with their typographic equivalents, “, ‘, ’, and ”. I'm not sure this is wrong, but it's a surprise. I'm also surprised that Sigil seems to have done this only in some files.

I guess I don't really understand the difference between keying in a typographic quote directly, say <Option><Left Bracket> for “ or entering “.

So . . . two questions: is my epub okay with some glyphs in one form and some in the other? and Is Sigil replacing “ with “ or am I going crazy? (Maybe that was three questions.)

t.

Keyword here is "curly quotes"

user_none · 03-03-2013, 05:05 PM

Book View (BV) converts entities to their unicode equivalent character. This isn't something we can control as the third party component we use for BV does this on it's own. We do convert some characters to the entity. But we only convert ones that either can't be seen or are hard to differentiate (shy and nbsp for example).

Using the unicode character instead of the entity is perfectly valid. The entity is just a representation for the character.

As to why it only happens on some files, most likely it's because you didn't make a change in BV in some files. Simply viewing a file in BV won't change it. The code is only modified if you make a change in BV.

Notjohn · 03-04-2013, 02:46 PM

Thanks for that information. I've wondered about similar replacements.

camdenmaine · 03-05-2013, 11:02 AM

Quote:

Originally Posted by user_none

Book View (BV) converts entities to their unicode equivalent character. This isn't something we can control as the third party component we use for BV does this on it's own. We do convert some characters to the entity. But we only convert ones that either can't be seen or are hard to differentiate (shy and nbsp for example).

Just to be clear: this is happening in Code View, not just Book View. I expected it to happen in BV, but not in CV.

Anyway, I guess you're saying I'm OK with some unicode quotes and some &XXquo; glyphs.

t.

Jellby · 03-06-2013, 05:25 AM

From the validity and rendering point of view, both &XXquo; and unicode characters are exactly equivalent, so nothing is lost. But I guess it's an undesired effect if Sigil changes the representation in the code, as there may be other reasons to have one or the other.

03-03-2013, 03:40 PM	#1
camdenmaine Member Posts: 13 Karma: 10 Join Date: May 2010 Device: iPad, Kidle	What happened to &XXquo; characters? I carefully replaced all opening quotes with “ and closing quotes with ” and similar changes for single quotes and dashes etc. Everything looks fine in book view. But when I look at the files in code view, I see that Sigil has replaced some of the &XXquo; characters with their typographic equivalents, “, ‘, ’, and ”. I'm not sure this is wrong, but it's a surprise. I'm also surprised that Sigil seems to have done this only in some files. I guess I don't really understand the difference between keying in a typographic quote directly, say <Option><Left Bracket> for “ or entering “. So . . . two questions: is my epub okay with some glyphs in one form and some in the other? and Is Sigil replacing “ with “ or am I going crazy? (Maybe that was three questions.) t. Keyword here is "curly quotes"

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
¿Convert unicode decomposed characters to unique/normal characters?	JohnQwerty	Calibre	3	04-05-2012 12:08 PM
Troubleshooting Wrong display of non-english characters in book title & author name.	smrtihlav	Amazon Kindle	0	04-28-2011 10:32 AM
Pocketbook 360 & romanian characters	Eddie	PocketBook	4	12-16-2010 04:32 PM
B&N and Smashwords--Has this happened to you?	Simon Wood	Writers' Corner	7	10-11-2010 09:23 PM
What happened to my extended characters?	ChrisI	Sigil	8	05-16-2010 07:31 AM

03-03-2013, 05:05 PM	#2
user_none Sigil & calibre developer Posts: 2,487 Karma: 1063785 Join Date: Jan 2009 Location: Florida, USA Device: Nook STR	Book View (BV) converts entities to their unicode equivalent character. This isn't something we can control as the third party component we use for BV does this on it's own. We do convert some characters to the entity. But we only convert ones that either can't be seen or are hard to differentiate (shy and nbsp for example). Using the unicode character instead of the entity is perfectly valid. The entity is just a representation for the character. As to why it only happens on some files, most likely it's because you didn't make a change in BV in some files. Simply viewing a file in BV won't change it. The code is only modified if you make a change in BV.

03-04-2013, 02:46 PM	#3
Notjohn mostly an observer Posts: 1,518 Karma: 987654 Join Date: Dec 2012 Device: Kindle	Thanks for that information. I've wondered about similar replacements.

03-06-2013, 05:25 AM	#5
Jellby frumious Bandersnatch Posts: 7,543 Karma: 19001583 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon, Kobo Aura	From the validity and rendering point of view, both &XXquo; and unicode characters are exactly equivalent, so nothing is lost. But I guess it's an undesired effect if Sigil changes the representation in the code, as there may be other reasons to have one or the other.

Advert

Advert