Red lines THROUGH mispellings and bottoms of words cut off

Gregg Bell · 11-19-2016, 11:02 AM

I have Sigil 0.9.5 on two computers. On one it works fine. On the other the red line under mispellings is through, not under, the words. (screenshot) Also when I first open an individual text file in it, on some of the lines (I'd say about 20%) the bottom halves of the letters are not visible (including the p tags). However, when I click something (like even when I went to take a screenshot) the bottoms reappear.

I'm figuring (hoping) none of this is problematic for the finished .epub, but still it would be nice to correct this. Thanks.

DiapDealer · 11-19-2016, 11:18 AM

It has absolutely no bearing on the finished epub. That much is easy.

I would suspect the difference between machines is a Qt5 version issue. You were using Linux if I recall correctly? Are both of the machines running Linux? The same flavor of Linux? The same Desktop Environment? The same fonts chosen for the text in Code View? Both fully updated, and with the same versions of Qt5?

If the answer to any of the above questions is no. Then there's probably very little to be done. Sorry. Qt do what it do.

There's also the issue of various font-config tweaks to improve font rendering on Linux that may play a role on one or the other machine.

KevinH · 11-19-2016, 01:38 PM

My guess is the font metrics are messed up on one of your fonts. Probably the fint height metric. Alternatively, if a font is missing, the layout will have to guess the font metrics and sometimes does a bad job.

Please try changing fonts in the Sigil Preferences on the problem machine to see what if any impact it has.

KevinH

Gregg Bell · 11-19-2016, 01:40 PM

Quote:

Originally Posted by DiapDealer

It has absolutely no bearing on the finished epub. That much is easy.

Thanks Diap. That was my chief concern. The other stuff is fluff, especially since the missing bottom halves of characters return when I click on anything.

Quote:

Originally Posted by DiapDealer

I would suspect the difference between machines is a Qt5 version issue. You were using Linux if I recall correctly? Are both of the machines running Linux? The same flavor of Linux? The same Desktop Environment? The same fonts chosen for the text in Code View? Both fully updated, and with the same versions of Qt5?

If the answer to any of the above questions is no. Then there's probably very little to be done. Sorry. Qt do what it do.

There's also the issue of various font-config tweaks to improve font rendering on Linux that may play a role on one or the other machine.

Yes, Linux on both machines. Both same flavor. Same desktop. I will check on the fonts issue. And I'm not sure what you mean by fully updated. I do all the software updates that come along if that's what you mean. I'll also check the other machines QT version. I have done nothing with font-config tweaks.

Anyway, it's functional, and as long as I know the epub will come out all right I'm a happy camper.

Thanks very much for the response and have a good weekend!

DiapDealer · 11-19-2016, 01:48 PM

Do try changing the Code View font in Sigil's Appearance preferences, as Kevin suggested, too.

Gregg Bell · 11-29-2016, 06:36 PM

Sorry. I somehow missed Kevin's post. I'm not on that computer but will try it when I get home tonight. And I looked at the Sigil fonts on this computer and it made me think. I am composing on really old laptops (using LibreOffice) and using Deja Vu on them. Then I transfer them to a newer computer and save them as .html there (in LO). I wonder if the Deja Vu has anything to do with it. And I just need to change the fonts in CSS/Codeview, right? And changing the fonts isn't going to change the finished epub, is it? I mean, that's just how I see it in Sigil, right? Thanks.

DiapDealer · 11-29-2016, 08:14 PM

Quote:

Originally Posted by Gregg Bell

And I just need to change the fonts in CSS/Codeview, right?

Yep. That's the only place the red wavy underline occurs. You typically want a mono-spaced (fixed-width) font for Code View.

Quote:

Originally Posted by Gregg Bell

And changing the fonts isn't going to change the finished epub, is it? I mean, that's just how I see it in Sigil, right? Thanks.

Exactly right. None of Sigil's Appearance preferences can affect an epub's internal code. It's just how you want things to look when displayed in Sigil.

Gregg Bell · 11-30-2016, 12:48 AM

Quote:

Originally Posted by DiapDealer

Yep. That's the only place the red wavy underline occurs. You typically want a mono-spaced (fixed-width) font for Code View.

Exactly right. None of Sigil's Appearance preferences can affect an epub's internal code. It's just how you want things to look when displayed in Sigil.

Thanks Diap. Changing the font type or size in the Code view in Preferences made no difference whatsoever in the red line or the font type or size.

DiapDealer · 11-30-2016, 08:27 AM

Quote:

Originally Posted by Gregg Bell

Changing the font type or size in the Code view in Preferences made no difference whatsoever in the red line or the font type or size.

Wait, what!? Forget the wavy, red underline for now. You're saying that changing the Code View font-type and/or font-size preferences had NO effect on how Code View text was displayed? That doesn't make sense. Your system fonts must be hosed in some way.

BetterRed · 11-30-2016, 03:46 PM

DiapDealer - On Windows, if I change the CV font or size, the change is not reflected in the current CV tab, even if I switch to another tab and back again. I have to close the tab I had open when I changed the CV font or size and reopen the file. I am pretty sure my system fonts are OK, and I use the same font (Consolas) elsewhere - Notepad++, ConEmu, Calibre editor, Bowpad, etc.

I change the font size if my eyes are getting scratchy. I've tried going into Book View before changing font size and back to CV after, and doing a Mend and Prettify after the change, but they don't repaint the current CV tab. And I can't see a Refresh option in the menus.

When I close the tab and reopen the file, it doesn't open it where it was before I closed the tab. So I work around the issue by deferring the font size change until I reach a point where I am happy to stop and start Sigil after changing the CV font size.

I can't be 100% sure, but I think Sigil has been like this since at least 0.8.?.

BR

DiapDealer · 11-30-2016, 06:09 PM

Sorry. Yes. I knew that. My mistake for not telling Gregg to open a new tab to see the appearance changes. I take for granted that people aren't mind-readers sometimes.

Hopefully Gregg will see this and try the test again.

Gregg Bell · 12-02-2016, 12:40 AM

Thanks Red. Thanks Diap. Yeah, switching the tab made the font changes in Code stick. And I switched to Mononspace (it had been 'Courier New') and it put the red lines back where they should be (under the words). The crops are saved! Thanks guys!

KevinH · 12-02-2016, 07:54 AM

That means that the Courier New font found on that system has corrupted font metrics. You should probably replace all variants of that font with a known good copy.

DiapDealer · 12-02-2016, 08:09 AM

It's fairly unusual for the Courier New font to be available on a Linux system in the first place -- what with it being a Microsoft font, and all.

Gregg Bell · 12-02-2016, 11:18 AM

I have no idea how it got there. And do I really need to do anything about it? (I have no plans to use it.)

11-19-2016, 11:02 AM	#1
Gregg Bell Gregg Bell Posts: 2,266 Karma: 3917598 Join Date: Jan 2013 Location: Itasca, Illinois Device: Kindle Touch 7, Sony PRS300, Fire HD8 Tablet	Red lines THROUGH mispellings and bottoms of words cut off I have Sigil 0.9.5 on two computers. On one it works fine. On the other the red line under mispellings is through, not under, the words. (screenshot) Also when I first open an individual text file in it, on some of the lines (I'd say about 20%) the bottom halves of the letters are not visible (including the p tags). However, when I click something (like even when I went to take a screenshot) the bottoms reappear. I'm figuring (hoping) none of this is problematic for the finished .epub, but still it would be nice to correct this. Thanks. Attached Thumbnails

11-19-2016, 11:18 AM	#2
DiapDealer Grand Sorcerer Posts: 28,394 Karma: 203720150 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	It has absolutely no bearing on the finished epub. That much is easy. I would suspect the difference between machines is a Qt5 version issue. You were using Linux if I recall correctly? Are both of the machines running Linux? The same flavor of Linux? The same Desktop Environment? The same fonts chosen for the text in Code View? Both fully updated, and with the same versions of Qt5? If the answer to any of the above questions is no. Then there's probably very little to be done. Sorry. Qt do what it do. There's also the issue of various font-config tweaks to improve font rendering on Linux that may play a role on one or the other machine. Last edited by DiapDealer; 11-19-2016 at 11:24 AM.

11-30-2016, 03:46 PM	#10
BetterRed null operator (he/him) Posts: 21,642 Karma: 29710510 Join Date: Mar 2012 Location: Sydney Australia Device: none	DiapDealer - On Windows, if I change the CV font or size, the change is not reflected in the current CV tab, even if I switch to another tab and back again. I have to close the tab I had open when I changed the CV font or size and reopen the file. I am pretty sure my system fonts are OK, and I use the same font (Consolas) elsewhere - Notepad++, ConEmu, Calibre editor, Bowpad, etc. I change the font size if my eyes are getting scratchy. I've tried going into Book View before changing font size and back to CV after, and doing a Mend and Prettify after the change, but they don't repaint the current CV tab. And I can't see a Refresh option in the menus. When I close the tab and reopen the file, it doesn't open it where it was before I closed the tab. So I work around the issue by deferring the font size change until I reach a point where I am happy to stop and start Sigil after changing the CV font size. I can't be 100% sure, but I think Sigil has been like this since at least 0.8.?. BR Last edited by BetterRed; 11-30-2016 at 04:03 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Keep words from splitting between lines	CGidari	ePub	4	03-12-2013 09:01 AM
Calibre cut lines in a converted CHM to MOBI	jomaweb	Calibre	12	07-21-2010 03:07 PM
fbreader: Words get cut off at right edge	doremifaso	PocketBook	24	07-10-2010 08:57 AM

11-19-2016, 01:38 PM	#3
KevinH Sigil Developer Posts: 8,506 Karma: 5703586 Join Date: Nov 2009 Device: many	My guess is the font metrics are messed up on one of your fonts. Probably the fint height metric. Alternatively, if a font is missing, the layout will have to guess the font metrics and sometimes does a bad job. Please try changing fonts in the Sigil Preferences on the problem machine to see what if any impact it has. KevinH

11-19-2016, 01:48 PM	#5
DiapDealer Grand Sorcerer Posts: 28,394 Karma: 203720150 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Do try changing the Code View font in Sigil's Appearance preferences, as Kevin suggested, too.

11-29-2016, 06:36 PM	#6
Gregg Bell Gregg Bell Posts: 2,266 Karma: 3917598 Join Date: Jan 2013 Location: Itasca, Illinois Device: Kindle Touch 7, Sony PRS300, Fire HD8 Tablet	Sorry. I somehow missed Kevin's post. I'm not on that computer but will try it when I get home tonight. And I looked at the Sigil fonts on this computer and it made me think. I am composing on really old laptops (using LibreOffice) and using Deja Vu on them. Then I transfer them to a newer computer and save them as .html there (in LO). I wonder if the Deja Vu has anything to do with it. And I just need to change the fonts in CSS/Codeview, right? And changing the fonts isn't going to change the finished epub, is it? I mean, that's just how I see it in Sigil, right? Thanks.

11-30-2016, 06:09 PM	#11
DiapDealer Grand Sorcerer Posts: 28,394 Karma: 203720150 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Sorry. Yes. I knew that. My mistake for not telling Gregg to open a new tab to see the appearance changes. I take for granted that people aren't mind-readers sometimes. Hopefully Gregg will see this and try the test again.

12-02-2016, 12:40 AM	#12
Gregg Bell Gregg Bell Posts: 2,266 Karma: 3917598 Join Date: Jan 2013 Location: Itasca, Illinois Device: Kindle Touch 7, Sony PRS300, Fire HD8 Tablet	Thanks Red. Thanks Diap. Yeah, switching the tab made the font changes in Code stick. And I switched to Mononspace (it had been 'Courier New') and it put the red lines back where they should be (under the words). The crops are saved! Thanks guys!

12-02-2016, 07:54 AM	#13
KevinH Sigil Developer Posts: 8,506 Karma: 5703586 Join Date: Nov 2009 Device: many	That means that the Courier New font found on that system has corrupted font metrics. You should probably replace all variants of that font with a known good copy.

12-02-2016, 08:09 AM	#14
DiapDealer Grand Sorcerer Posts: 28,394 Karma: 203720150 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	It's fairly unusual for the Courier New font to be available on a Linux system in the first place -- what with it being a Microsoft font, and all.

12-02-2016, 11:18 AM	#15
Gregg Bell Gregg Bell Posts: 2,266 Karma: 3917598 Join Date: Jan 2013 Location: Itasca, Illinois Device: Kindle Touch 7, Sony PRS300, Fire HD8 Tablet	I have no idea how it got there. And do I really need to do anything about it? (I have no plans to use it.)

Advert

Advert