Am 19.07.2011 um 01:05 schrieb Uwe Stöhr:
> Am 19.07.2011 00:05, schrieb Jean-Marc Lasgouttes:
>
>> Le 15/07/11 22:30, Uwe Stöhr a écrit :
>>> I don't agree that implementing it as part of the space inset is a good
>>> idea. \textvisiblespace is not a space in the sense of the meaning but a
>>> special character. It does not create a space, but a character. I would
>>> therefore like to implement this as special character like an ellipsis.
...
>> + case VISIBLE_SPACE:
>> + os << "\\textvisiblespace{}";
>> + break;
>>
>> For LaTeX output, can't we just output the unicode character and let our
>> stream sort out the right
>> output? We may want unicode to output natively (maybe also for other special
>> characters, actually).
>
> I can do this, but what is the benefit? I know users looking at the LyX file
> directly with a text editor, and on Windows they would only see a square.
>
>> + case VISIBLE_SPACE:
>> + os << "|_|";
>> + return 3;
>>
>> I do not think it makes much sense to use this ascii-art output here. I
>> would use a plain space or
>> an underscore. Or even the unicode character, since we output to utf8 (Hmmm,
>> do we?)
>
> The problem is that when you use the Unicode character and the user open the
> result e.g. in Windows standard editor "Notepad" he sees a black square
> instead because the Windows standard fonts (Arial, times new Roman, etc.)
> don't have a representation for this character (at least here on my XP).
Sorry, I cannot resist... Notepad is not an editor. It's an excuse for not
having one.
Every time I have to view a file on stock windows I get an attack of windows
hate.
It's the same with the never ending newline story.
One should at least use Wordpad instead.
Stephan
