No break space and alignment - Page 3

RbnJrg · 11-21-2019, 08:44 AM

Quote:

Originally Posted by jhowell

I did some testing with the Kindle Previewer and had good results there by replacing the non-breaking space with a figure space (   ). KFX treats that as having a fixed width.

Great discovery!

And your investigation leaded me to try another special spaces to see how they worked in KP. According to my tests, all the following spaces work everywhere:

Code:

&#x2002;	&ensp;		Half an EM SPACE.
&#x2003;	&emsp;		Usually a space equal to the type size in points.
&#x2004;	&emsp13;	One-third of an EM SPACE, called a thick space.
&#x2005;	&emsp14;	One-fourth of an EM SPACE, called a mid space.
&#x2007;	&numsp;		Width of a digit in some fonts.

I used   and looks perfect everywhere (ADE, Sigil, Calibre, KP 3.35). Of course, the user has the choice of employing the space whose width is according to his/her wishes.

So, with your contribution, I can say that the following code:

Code:

  <p>—<span class="ps">&#x2005;</span>Lorem ipsum dolor sit amet, consectetur adipiscing elit.</p>

  <p>Etiam lobortis, massa ac aliquam auctor. —<span class="ps">&#x2005;</span>Nulla ac tellus nunc. Phasellus imperdiet leo metus, et gravida lacus.</p>

with

Code:

p {
  text-align: justify;
}

.ps {
  white-space: pre;
}

works everywhere. Of course, the user can change   for any of the others special spaces cited above.

jbacelar · 11-21-2019, 12:10 PM

Thank you very much Rubén.
(Eres un artista)

RbnJrg · 11-21-2019, 12:44 PM

Quote:

Originally Posted by jbacelar

Thank you very much Rubén.
(Eres un artista)

Thanks! (very probably a failed artist, but thanks

)

Hitch · 11-21-2019, 01:41 PM

Quote:

Originally Posted by RbnJrg

Thanks! (very probably a failed artist, but thanks

)

No, no, Ruben--no false modesty here. You do lovely work.

Spoiler:

Hitch

RbnJrg · 11-21-2019, 06:42 PM

Quote:

Originally Posted by Hitch

No, no, Ruben--no false modesty here. You do lovely work.

Spoiler:

Hitch

Thank you very much Hitch, I appreciate a lot your words. And yes, you are right; KF7 is there so that we can tear the hair from our heads

With each solution for .kf8 and .KFX, we have more new code to write for KF7. But it is what it is and we cannot change it. But I have the solution for that issue: Amazon has to propose to all users of K1/K2/KDX to switch their devices for the latest version of Kindle, completely free of charge.

And announcing that those who do not accept the proposal, they must accept that Amazon does not provide e-books for their old devices in the future. Of course, Amazon never will do that madness, but it would be a solution.

Hitch · 11-21-2019, 07:32 PM

Quote:

Originally Posted by RbnJrg

Thank you very much Hitch, I appreciate a lot your words. And yes, you are right; KF7 is there so that we can tear the hair from our heads

With each solution for .kf8 and .KFX, we have more new code to write for KF7. But it is what it is and we cannot change it. But I have the solution for that issue: Amazon has to propose to all users of K1/K2/KDX to switch their devices for the latest version of Kindle, completely free of charge.

And announcing that those who do not accept the proposal, they must accept that Amazon does not provide e-books for their old devices in the future. Of course, Amazon never will do that madness, but it would be a solution.

:-)

Hitch

JSWolf · 11-21-2019, 09:51 PM

Quote:

Originally Posted by RbnJrg

Thank you very much Hitch, I appreciate a lot your words. And yes, you are right; KF7 is there so that we can tear the hair from our heads

With each solution for .kf8 and .KFX, we have more new code to write for KF7. But it is what it is and we cannot change it. But I have the solution for that issue: Amazon has to propose to all users of K1/K2/KDX to switch their devices for the latest version of Kindle, completely free of charge.

And announcing that those who do not accept the proposal, they must accept that Amazon does not provide e-books for their old devices in the future. Of course, Amazon never will do that madness, but it would be a solution.

Giving users of these old Kindles a free upgrade to a new Kindle for free is going to piss off everyone who paid to upgrade. It would piss off me.

I agree that Amazon should say that some eBooks may not be available in Mobi going forward and if they want to make sure all Kindle eBooks are available, that they need to upgrade their devices. I don't mind if Amazon gives them $25 for an old 6" Kindle and $50 for a DX in trade for a working device. But a free trade? No way.

DNSB · 11-22-2019, 12:52 AM

Quote:

Originally Posted by JSWolf

Giving users of these old Kindles a free upgrade to a new Kindle for free is going to piss off everyone who paid to upgrade. It would piss off me.

I agree that Amazon should say that some eBooks may not be available in Mobi going forward and if they want to make sure all Kindle eBooks are available, that they need to upgrade their devices. I don't mind if Amazon gives them $25 for an old 6" Kindle and $50 for a DX in trade for a working device. But a free trade? No way.

"If you are going to dream, ... dream big."—Chris Robinson

roger64 · 11-23-2019, 09:02 PM

I am a little late at the party, but, as the tests have been made, I congratulate Ruben too for his inventive proposal. The "pre" property should be recognized by any user agent.

As far as I am being concerned, I'll be sticking with the nbsp first solution because this no-break space is quite commonly used for French books.

Users of KFX format may make other choices. Each one its own...

P.S. Mobi, someone said "Mobi"? What's that?

Turtle91 · 11-24-2019, 09:45 AM

Quote:

Originally Posted by roger64

P.S. Mobi, someone said "Mobi"? What's that?

DNSB · 11-24-2019, 11:29 PM

Quote:

Originally Posted by roger64

P.S. Mobi, someone said "Mobi"? What's that?

Mobi is why people who produce ebooks for a living have what's left of their hair turning grey.

11-23-2019, 09:02 PM	#39
roger64 Wizard Posts: 2,608 Karma: 3000161 Join Date: Jan 2009 Device: Kindle PW3 (wifi)	I am a little late at the party, but, as the tests have been made, I congratulate Ruben too for his inventive proposal. The "pre" property should be recognized by any user agent. As far as I am being concerned, I'll be sticking with the nbsp first solution because this no-break space is quite commonly used for French books. Users of KFX format may make other choices. Each one its own... P.S. Mobi, someone said "Mobi"? What's that? Last edited by roger64; 11-23-2019 at 09:13 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Display of narrow no-break space (Linux build)	roger64	Sigil	16	02-17-2018 10:35 AM
Representing the no-break space	roger64	Sigil	11	08-09-2017 02:09 AM
Narrow No-Break Space display	roger64	Sigil	6	12-20-2012 02:43 PM
Narrow No-Break Space and commercial support.	roger64	ePub	8	09-04-2012 01:08 PM
Is it possible to define rules for non break space?	habanr	Conversion	4	02-22-2011 07:36 AM

11-21-2019, 12:10 PM	#32
jbacelar Interested in the matter Posts: 421 Karma: 426094 Join Date: Dec 2011 Location: Spain, south coast Device: Pocketbook InkPad 3	Thank you very much Rubén. (Eres un artista)