On 2011-07-25, Uwe Stöhr wrote:
Am 23.07.2011 23:23, schrieb Guenter Milde:
What is the replacement character used by Windows?
a square
An open square or a filled black one? IMV, an open square is not worse than
\leer in ERT: both need explanation.
It is an open square. This would be
On 2011-07-25, Uwe Stöhr wrote:
> Am 23.07.2011 23:23, schrieb Guenter Milde:
What is the replacement character used by Windows?
>>> a square
>> An open square or a filled black one? IMV, an open square is not worse than
>> "\leer" in ERT: both need explanation.
> It is an open square.
Am 23.07.2011 23:23, schrieb Guenter Milde:
What is the replacement character used by Windows?
a square
An open square or a filled black one? IMV, an open square is not worse than
\leer in ERT: both need explanation.
It is an open square. This would be worse because this character is
Am 23.07.2011 23:23, schrieb Guenter Milde:
What is the replacement character used by Windows?
a square
An open square or a filled black one? IMV, an open square is not worse than
"\leer" in ERT: both need explanation.
It is an open square. This would be worse because this character is
On 2011-07-22, Uwe Stöhr wrote:
Am 22.07.2011 23:52, schrieb Guenter Milde:
What is the replacement character used by Windows?
a square
An open square or a filled black one? IMV, an open square is not worse than
\leer in ERT: both need explanation.
If we use it in our manuals, then many
On 2011-07-22, Uwe Stöhr wrote:
> Am 22.07.2011 23:52, schrieb Guenter Milde:
>> What is the replacement character used by Windows?
> a square
An open square or a filled black one? IMV, an open square is not worse than
"\leer" in ERT: both need explanation.
If we use it in our manuals,
On 2011-07-15, Uwe Stöhr wrote:
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.
No, under my OS (Debian
Am 22.07.2011 23:52, schrieb Guenter Milde:
What is the replacement character used by Windows?
a square
If we use it in our manuals, then many people will be just unable to
view the manual!
What does unable to view the manual precisely mean?
I meant view it within LyX. As the Windows
Am 21.07.2011 08:30, schrieb Jürgen Spitzmüller:
The implementation in InsetSpace is indeed better for the on-screen
representation. So I'm convinced now, but we should do something about the
menu logic. Perhaps we can use the menu Insert-Special character-Visible
space that inserts an
On 2011-07-15, Uwe Stöhr wrote:
>> 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.
No, under my OS
Am 22.07.2011 23:52, schrieb Guenter Milde:
What is the replacement character used by Windows?
a square
If we use it in our manuals, then many people will be just unable to
view the manual!
What does "unable to view the manual" precisely mean?
I meant view it within LyX. As the Windows
Am 21.07.2011 08:30, schrieb Jürgen Spitzmüller:
The implementation in InsetSpace is indeed better for the on-screen
representation. So I'm convinced now, but we should do something about the
menu logic. Perhaps we can use the menu Insert->Special character->Visible
space that inserts an
Uwe Stöhr wrote:
Am 20.07.2011 08:10, schrieb Jürgen Spitzmüller:
It is totally confusing that we have the menu Insert-Special
character
that already provides the char.
I don't understand.
We have the menu
Insert-Special character
for characters but the space inset is in
Uwe Stöhr wrote:
> Am 20.07.2011 08:10, schrieb Jürgen Spitzmüller:
> >>It is totally confusing that we have the menu Insert->Special
> >>character
> >>
> >> that already provides the char.
> >
> > I don't understand.
>
> We have the menu
> Insert->Special character
> for characters but
Uwe Stöhr wrote:
It is totally confusing that we have the menu Insert-Special character
that already provides the char.
I don't understand.
OK, this doesn't work on windows because
the Windows standard fonts don't support to display this character and one
therefore cannot even see it in
Am 20.07.2011 08:10, schrieb Jürgen Spitzmüller:
It is totally confusing that we have the menu Insert-Special character
that already provides the char.
I don't understand.
We have the menu
Insert-Special character
for characters but the space inset is in the menu
Insert-Formatting
So the
Uwe Stöhr wrote:
> It is totally confusing that we have the menu Insert->Special character
> that already provides the char.
I don't understand.
> OK, this doesn't work on windows because
> the Windows standard fonts don't support to display this character and one
> therefore cannot even see
Am 20.07.2011 08:10, schrieb Jürgen Spitzmüller:
It is totally confusing that we have the menu Insert->Special character
that already provides the char.
I don't understand.
We have the menu
Insert->Special character
for characters but the space inset is in the menu
Insert->Formatting
So
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
Uwe Stöhr wrote:
I still think it is wrong, but I am not going to fight forever on that
(what is there a space in foo bar and not foo_bar???).
The internal behaviour of a space and a character is different. LaTeX can
change the width of spaces to e.g. fit a line into the column margins.
Jean-Marc Lasgouttes wrote:
Attached is a patch that does this.
The advantage is that we avoid confusions. If we would implement it as
InsetSpace, it is hard for the user to distinguish it within LyX from
the other spaces.
Just output it in black instead of blue.
this is already
Jürgen Spitzmüller wrote:
And this is exactly why it makes sense. It's a possibility to represent a
space. Why shouldn't InsetSpace allow for that possibility?
The discussion about glyph classification (technical symbol vs. space) is
completely irrelevant for most users. They might just
Pavel Sanda wrote:
the border of technical symbol vs. space is fuzzy to me and i don't
have hard opinion to dicuss it.
but to sum up as the time passed we have 3 patches:
1. special symbol - simple unicode char
2. part of insetspace
3. special symbol - specific drawing
if my counting is
Le 19/07/2011 08:41, Jürgen Spitzmüller a écrit :
That's not true for all spaces. Non-break spaces are of fixed width as well.
And so is \thinspace.
[...]
And this is exactly why it makes sense. It's a possibility to represent a
space. Why shouldn't InsetSpace allow for that possibility?
The
Am 19.07.2011 08:14, schrieb Stephan Witt:
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
Am 19.07.2011 08:41, schrieb Jürgen Spitzmüller:
And this is exactly why it makes sense. It's a possibility to represent a
space. Why shouldn't InsetSpace allow for that possibility?
It is totally confusing that we have the menu Insert-Special character that already provides the
char. OK,
Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
the border of technical symbol vs. space is fuzzy to me and i don't
have hard opinion to dicuss it.
but to sum up as the time passed we have 3 patches:
1. special symbol - simple unicode char
2. part of insetspace
3. special symbol -
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
>>>
Uwe Stöhr wrote:
> > I still think it is wrong, but I am not going to fight forever on that
> > (what is there a space in "foo bar" and not "foo_bar"???).
>
> The internal behaviour of a space and a character is different. LaTeX can
> change the width of spaces to e.g. fit a line into the column
Jean-Marc Lasgouttes wrote:
>> Attached is a patch that does this.
>>
>> The advantage is that we avoid confusions. If we would implement it as
>> InsetSpace, it is hard for the user to distinguish it within LyX from
>> the other spaces.
>
> Just output it in black instead of blue.
this is
Jürgen Spitzmüller wrote:
> And this is exactly why it makes sense. It's a possibility to represent a
> space. Why shouldn't InsetSpace allow for that possibility?
>
> The discussion about glyph classification ("technical symbol" vs. "space") is
> completely irrelevant for most users. They
Pavel Sanda wrote:
> the border of "technical symbol" vs. "space" is fuzzy to me and i don't
> have hard opinion to dicuss it.
>
> but to sum up as the time passed we have 3 patches:
> 1. special symbol - simple unicode char
> 2. part of insetspace
> 3. special symbol - specific drawing
>
> if
Le 19/07/2011 08:41, Jürgen Spitzmüller a écrit :
That's not true for all spaces. Non-break spaces are of fixed width as well.
And so is \thinspace.
[...]
And this is exactly why it makes sense. It's a possibility to represent a
space. Why shouldn't InsetSpace allow for that possibility?
The
Am 19.07.2011 08:14, schrieb Stephan Witt:
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
Am 19.07.2011 08:41, schrieb Jürgen Spitzmüller:
And this is exactly why it makes sense. It's a possibility to represent a
space. Why shouldn't InsetSpace allow for that possibility?
It is totally confusing that we have the menu Insert->Special character that already provides the
char. OK,
Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
> > the border of "technical symbol" vs. "space" is fuzzy to me and i don't
> > have hard opinion to dicuss it.
> >
> > but to sum up as the time passed we have 3 patches:
> > 1. special symbol - simple unicode char
> > 2. part of insetspace
> > 3.
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
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
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
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
40 matches
Mail list logo
