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. Thi
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 us
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, the
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 InsetSp
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 s
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
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
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 t
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 i
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. sp
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, t
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 Wordpa
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
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
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
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
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
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
>>> s
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 charact
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 speci
Am 01.07.2011 16:48, schrieb Jean-Marc Lasgouttes:
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, limite
On 2011-07-04, Jean-Marc Lasgouttes wrote:
> Le 02/07/2011 22:24, Guenter Milde a écrit :
>>> 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
Le 02/07/2011 22:24, Guenter Milde a écrit :
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
On 2011-07-01, Jean-Marc Lasgouttes wrote:
> Le 01/07/2011 12:45, Pavel Sanda a écrit :
>> Jean-Marc Lasgouttes wrote:
...
>> 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 spe
Jean-Marc Lasgouttes wrote:
> Frankly, inserting special characters is a nightmare to me.
ooonly for yuuur
bjutifuuul ees
sun never seeets
through coooding nghts :)
pavel
diff --git a/development/FORMAT b/development/FORMAT
index afcd41c..3d5b603 100644
--- a/development/FORMAT
+++ b/
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 l
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
Jean-Marc Lasgouttes wrote:
> The simplest solution is to add it to InsetSpace.
i have no strong opinion on unicode char vs insetspace.
however why you think insetspace is simpler than
adding one menu item with unicode-insert XXX?
pavel
On 2011-06-29, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> why should it get special treatment?
> Because it's a "space" variant.
No, \textvisiblespace is an ordinary symbol (that stands for an ASCII
space character or for the action "Press the Space key"). In the second
sense, it is sim
Guenter Milde wrote:
> why should it get special treatment?
Because it's a "space" variant. If it's covered by InsetSpace, it can be
easily toggled from/to other space types.
This doesn't mean that the unicode glyph couldn't be supported anyway, via
unicodesymbols (and the symbols dialog). We a
On 2011-06-28, Jürgen Spitzmüller wrote:
> Jean-Marc Lasgouttes wrote:
>> The simplest solution is to add it to InsetSpace.
> This also seems conceptually most sane.
I disagree:
* it is a visible character, like other punctuation or "miscellaneous
technical" symbol⌫,
* there is a Unicode code
Jean-Marc Lasgouttes wrote:
> The simplest solution is to add it to InsetSpace.
This also seems conceptually most sane.
Jürgen
Le 28/06/2011 12:40, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Also, I have a patch for the math guide to replace the ERT with the
Unicode character.
Uwe tried this at my demand earlier but gave up because of missing
character in windows.
we can either paint is as InsetSpace derivate
Le 28/06/2011 12:37, Pavel Sanda a écrit :
Guenter Milde wrote:
is there some reason/obstacle why we dont directly support \textvisiblespace
in menu and rendering? i may add it if there are no objections.
You can already paste the corresponding Unicode character:
??? 2423 OPEN BOX * gr
Jean-Marc Lasgouttes wrote:
>> Also, I have a patch for the math guide to replace the ERT with the
>> Unicode character.
>
> Uwe tried this at my demand earlier but gave up because of missing
> character in windows.
we can either paint is as InsetSpace derivate or i can device bitmap
font file wi
Guenter Milde wrote:
> > is there some reason/obstacle why we dont directly support \textvisiblespace
> > in menu and rendering? i may add it if there are no objections.
>
> You can already paste the corresponding Unicode character:
>
> ??? 2423OPEN BOX * graphic for space
but then i need
Le 28/06/2011 10:28, Guenter Milde a écrit :
On 2011-06-27, Pavel Sanda wrote:
is there some reason/obstacle why we dont directly support \textvisiblespace
in menu and rendering? i may add it if there are no objections.
This is something I wanted to do before 2.0, but I did not find the
time.
On 2011-06-27, Pavel Sanda wrote:
> hi,
> is there some reason/obstacle why we dont directly support \textvisiblespace
> in menu and rendering? i may add it if there are no objections.
You can already paste the corresponding Unicode character:
␣ 2423OPEN BOX * graphic for space
and it
38 matches
Mail list logo
