[tex4ht] [bug #449] \ is not a nobreak space

2020-06-29 Thread Karl Berry
Update of bug #449 (project tex4ht): Open/Closed:Open => Closed ___ Follow-up Comment #11: guess we have to give up on this idea of breakable spaces, unfortunately. closing.

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-28 Thread Michal Hoftich
Follow-up Comment #10, bug #449 (project tex4ht): Ah, that is bad. I think we should revert for now. I will put \:nbsp back. ___ Reply to this item at:

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-27 Thread Karl Berry
Update of bug #449 (project tex4ht): Open/Closed: Closed => Open ___ Follow-up Comment #9: Hi Michal - as you warned, but I didn't fully take in, this change affects verbatim also. That

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-26 Thread Karl Berry
Update of bug #449 (project tex4ht): Open/Closed:Open => Closed ___ Follow-up Comment #8: thanks. we'll see. ___ Reply to this

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-26 Thread Michal Hoftich
Follow-up Comment #7, bug #449 (project tex4ht): OK, I've introduced a new command \:ensp. It is used for \Configure{ }. ___ Reply to this item at: ___

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-25 Thread Karl Berry
Follow-up Comment #6, bug #449 (project tex4ht): well, \ being an unbreakable space is just plain wrong. And multiple \ being preserved at line breaks (which I think happens now with nbsp?) is also wrong. So I'd like to try the enspace thing. Agreed it is a big change that might cause problems,

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-21 Thread Michal Hoftich
Follow-up Comment #5, bug #449 (project tex4ht): It seems that multiple enspaces after line break are discarded. So should I add them? I am bit worried that it may break things. ___ Reply to this item at:

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-19 Thread Karl Berry
Follow-up Comment #4, bug #449 (project tex4ht): how about some kind of css? is the normal interword space for the current font somehow accessible, the way it should be? allowing line breaks would be an improvement, at least. an en space would generally be a little too wide, but the line breaks

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-19 Thread Michal Hoftich
Follow-up Comment #3, bug #449 (project tex4ht): I' am afraid it isn't possible to use , it collapses. It is possible to use en space (), but I don't think it has any advantages over nbsp, except that it allows line breaks. ___ Reply to

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-18 Thread Karl Berry
Follow-up Comment #2, bug #449 (project tex4ht): oh yeah, collapsing multiple. Hmm. Is there really no way to output a normal, breakable, interword space other than a literal " " character in html/css? It seems so basic. How about outputting , so that it does not collapse if there is more than

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-18 Thread Michal Hoftich
Follow-up Comment #1, bug #449 (project tex4ht): Hi Karl, I see. But the space generated by '\ ' is non-collapsible, so it is not an ordinary space. It is possible to configure it to produce normal space using: \Configure{ }{ }, but it causes issues in verbatim, for example. You will lose line

[tex4ht] [bug #449] \ is not a nobreak space

2020-02-17 Thread Karl Berry
URL: Summary: \ is not a nobreak space Project: tex4ht Submitted by: karl Submitted on: Tue 18 Feb 2020 01:44:31 AM EET Category: None Priority: 5 - Normal