Jean-Marc Lasgouttes <lasgouttes <at> lyx.org>
2011-07-01 14:48:01 GMT
Le 01/07/2011 12:45, Pavel Sanda a écrit :
> Jean-Marc Lasgouttes wrote:
>> No, because LyX will output \textvisiblespace when needed. The only problem
>> is with screen rendering and also discoverability. Using the space inset
>> solves all these problems.
> with discoverability i'm not sure. when i was looking whether lyx knows
> visible space i was going to insert->special character, not formatting.
Frankly, inserting special characters is a nightmare to me. You look at
an endless list of unicode characters, and you only know whether they
render in the GUI main font. Then you insert it in the document, it
shows or not on your screen (depending on your screen font), it works or
not in LaTeX (depending on utf8 encoding support) and then when you send
it to somebody else who uses another screen font he may or may not be
able to see it.
It is only useful for desperate cases IMO.
> screen rendering is worse. Uwe, does this patch still produce invisible screen space on windows?
The problem is the same under any OS. Our user are free to pick the font
they want (with or without accents if they are English speakers, limited
to latin1++ for western countries...) and nobody knows whether visible
space is in there. If we use it in our manuals, then many people will be
just unable to view the manual!
Finally, if it is an InsetSpace, we may give it properties related to
our line breaking algorithm (I am not sure which though).