Juergen Spitzmueller wrote:
I wonder if this is the culprit:
http://www.lyx.org/trac/changeset/20567
And it is. I just reverted this and verified.
Too bad, this optimization is quite necessary. I think that this should
be resolved by forcing a full repaint when editing within a table.
On Thu, Oct 04, 2007 at 12:39:05AM +0200, [EMAIL PROTECTED] wrote:
On Wed, 3 Oct 2007, Andre Poenitz wrote:
On Wed, Oct 03, 2007 at 01:20:42PM +0100, John Levon wrote:
On Wed, Oct 03, 2007 at 08:25:12AM +0200, Abdelrazak Younes wrote:
However, insets imply all sorts of things about cursor
On Wed, Oct 03, 2007 at 10:22:41PM -, [EMAIL PROTECTED] wrote:
Author: uwestoehr
Date: Thu Oct 4 00:22:40 2007
New Revision: 20721
URL: http://www.lyx.org/trac/changeset/20721
Log:
Buffer.cpp: compile fix
scons_manifest.py: dito
André, please check if you can compile before you
Abdelrazak Younes wrote:
Too bad, this optimization is quite necessary. I think that this should
be resolved by forcing a full repaint when editing within a table.
But if we don't have a quick and straightforward fix, we will have to revert
for the time being (and are you sure there are no
Abdelrazak Younes wrote:
No, hence my idea of one word per inset. The fact that there is more
than one inset will only be visible if the cursor is in or if you hover
the mouse over it.
What are your criteria for something being a word? I.e., does your
approach handle cases like:
Juergen Spitzmueller wrote:
Abdelrazak Younes wrote:
No, hence my idea of one word per inset. The fact that there is more
than one inset will only be visible if the cursor is in or if you hover
the mouse over it.
What are your criteria for something being a word? I.e., does your
approach
Juergen Spitzmueller wrote:
Abdelrazak Younes wrote:
Too bad, this optimization is quite necessary. I think that this should
be resolved by forcing a full repaint when editing within a table.
But if we don't have a quick and straightforward fix, we will have to revert
for the time being
I do no know much about hyperref, but these hanges look strange to me.
Can someone comment?
+ // since LyX uses unicode, also set the PDF strings to unicode strings
with the
+ // hyperref option unicode
+ opt += unicode=true,\n ;
What happens when the output is _not_ unicode?
Juergen Spitzmueller wrote:
Abdelrazak Younes wrote:
No, hence my idea of one word per inset. The fact that there is more
than one inset will only be visible if the cursor is in or if you hover
the mouse over it.
What are your criteria for something being a word? I.e., does your
approach
[EMAIL PROTECTED] writes:
What is the TAB-key mapped to by the way? Could TAB and S-TAB be used
for M-P Right/Left?
This is something I want to do. I think it is next-cell right now.
JMarc
I do no know much about hyperref, but these hanges look strange to me.
Can someone comment?
look on the yeasterday's thread Changeset 20707. i had exactly the same
concerns.
+ // since LyX uses unicode, also set the PDF strings to unicode strings
with the
+ // hyperref option
Juergen Spitzmueller [EMAIL PROTECTED] writes:
Abdelrazak Younes wrote:
No, hence my idea of one word per inset. The fact that there is more
than one inset will only be visible if the cursor is in or if you hover
the mouse over it.
What are your criteria for something being a word?
I
Abdelrazak Younes [EMAIL PROTECTED] writes:
To satisfy everybody maybe we should implement charstyle as font
attribute (and thus please Dov and John) and rename our current
charstyle to textstyle. I know for sure that I won't use charstyle
where the atom is a character.
Yesss ! Three
Abdelrazak Younes wrote:
No, anything that is character level should be done by hand by the user.
So, as a user, you will have to exit the inset after the 'r' of Peter.
Otherwise the 's would be in the noun inset together with Peter. We
just cannot read the mind of users :-)
Sure. However,
Andre Poenitz [EMAIL PROTECTED] writes:
Insets are straightforward to implement. Font ranges are not.
I recently had a look at our coding rules. KISS was and still is
the first item...
Yes, but it should not dictqte the UI (am I repeating myself?)
JMarc
I was not succesfull even wihtout changes with pdflatex :
on console many thinhs like:
Warning--I didn't find a database entry for fancyhdr
That means that you cannot compile the LyX UserGuide?
Yes.
Then there is something wrong with your LaTeX installation.
I dont think so. But there
Abdelrazak Younes wrote:
Are you sure you don't want my wide() removal patch? As 1.5.2 has been
delayed, I reckon there is enough time to test it.
I want to prepare the tarball tomorrow and release on monday. 1.5.2 is
overdue. I think the wide change would require some more time.
Jürgen
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
To satisfy everybody maybe we should implement charstyle as font
attribute (and thus please Dov and John) and rename our current
charstyle to textstyle. I know for sure that I won't use charstyle
where the atom is a
Juergen Spitzmueller [EMAIL PROTECTED] writes:
BTW Word's side panel is not too bad as a model.
The office 2007 UI blog posts I referred to earlier explain how the
proliferation of side panels in word meant that they just scrapped
everything and built a new UI.
JMarc
Jean-Marc Lasgouttes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
Insets are straightforward to implement. Font ranges are not.
I recently had a look at our coding rules. KISS was and still is
the first item...
Yes, but it should not dictqte the UI (am I repeating myself?)
But _I_
Uwe Stöhr [EMAIL PROTECTED] writes:
The only difference to other languages is that you have to load
babel direcly with the language options:
\usepackage[bla,vietnam,blub]{babel}
and not
\documentclass[bla,vietnam,blub]{article}
\usepackage{babel}
This is very weird. The two uses should
Juergen Spitzmueller wrote:
Abdelrazak Younes wrote:
No, anything that is character level should be done by hand by the user.
So, as a user, you will have to exit the inset after the 'r' of Peter.
Otherwise the 's would be in the noun inset together with Peter. We
just cannot read the mind of
Andre Poenitz wrote:
On Wed, Oct 03, 2007 at 12:15:43PM +0200, Helge Hafting wrote:
Richard Heck wrote:
Andre Poenitz wrote:
Is there a particular reason we keep the dialogs around instead of
re-build them each time they are shown?
Do they keep important state?
I
Pavel Sanda [EMAIL PROTECTED] writes:
I do no know much about hyperref, but these hanges look strange to me.
Can someone comment?
look on the yeasterday's thread Changeset 20707. i had exactly the same
concerns.
Yes, I saw it too late.
JMarc
On Thursday 04 October 2007 08:14:22 Jean-Marc Lasgouttes wrote:
Why do this even if the author did not ask for it? Shouldn't it be an
additional option?
I agree with Jean-Marc here, and I also think that we should set this option
to be enabled by default.
In general, adding options behind
Abdelrazak Younes [EMAIL PROTECTED] writes:
Right. This was to say: we will obviously never reach an agreement as
our views are fundamentally different.
What we could to try try to resolve this argument is look at what
proper html editors (nvu?) do. They have to deal with the same
problems,
José Matos wrote:
In general, adding options behind the user's back looks bad to me.
+2
Abdelrazak Younes [EMAIL PROTECTED] writes:
But _I_ happen to like clear threshold between different things, the
kind of threshold is naturally achieved by insets. So why, as a user,
do I have to suffer your way of typing? This goes the other way around
obviously. With insets at least we can
Michael Gerz wrote:
Question: Is it really desirable to change dialogs which each major
release?
your question suggests that changing them is a goal in itself.
but yes, it is desirable to improve lyx's dialogs and make them more
uniform...
Why can't we get them right at the very first
Abdelrazak Younes wrote:
Sure and this will be very easy to achieve with the inset
implementation. We are not in contracdiction here
Fine then. I just wanted to make sure.
Jürgen
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
Right. This was to say: we will obviously never reach an agreement as
our views are fundamentally different.
What we could to try try to resolve this argument is look at what
proper html editors (nvu?) do. They have to
Juergen Spitzmueller wrote:
Abdelrazak Younes wrote:
Too bad, this optimization is quite necessary. I think that this should
be resolved by forcing a full repaint when editing within a table.
But if we don't have a quick and straightforward fix,
Could you please try this?
Abdel.
Index:
On Thursday 04 October 2007 08:14:22 Jean-Marc Lasgouttes wrote:
Why do this even if the author did not ask for it? Shouldn't it be an
additional option?
I agree with Jean-Marc here, and I also think that we should set this
option
to be enabled by default.
it was my original
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
More seriously, this whole discussion comes a bit late IMHO. I know
that you emitted some objections when Martin started the
implementation but they were not too strong. We have something _now_
and I'd be a pity to revert
Abdelrazak Younes [EMAIL PROTECTED] writes:
Within text the space syndrome won't be as evident because you
generally only have one depth and not multiple level like in mathed.
Why do we need to nest insets then ? :-P
JMarc
Jean-Marc Lasgouttes wrote:
Dov Feldstern [EMAIL PROTECTED] writes:
Abdelrazak Younes wrote:
We will face challenge for sure but Cursor movement is already
working well for entering and leaving insets. We will have to decide
what to do with selection though. I am in the opinion that
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
But _I_ happen to like clear threshold between different things, the
kind of threshold is naturally achieved by insets. So why, as a user,
do I have to suffer your way of typing? This goes the other way around
obviously.
Abdelrazak Younes wrote:
More seriously, this whole discussion comes a bit late IMHO.
But nevertheless, it's a good thing that we have the discussion finally.
Even if I did not find enough time to jump in, I appreciate it very much.
Jürgen
Abdelrazak Younes [EMAIL PROTECTED] writes:
More seriously, this whole discussion comes a bit late IMHO. I know
that you emitted some objections when Martin started the
implementation but they were not too strong. We have something _now_
and I'd be a pity to revert it because you and others
Abdelrazak Younes wrote:
But why would you want to have two different charstyles in the _same_
word? If you need that then I would say that this is a use case where
you really want to use font attributes and not charstyle.
This happens natureally when you really start to add markup.
A word
Andre Poenitz wrote:
On Wed, Oct 03, 2007 at 01:05:38PM +0200, Helge Hafting wrote:
I, for instance, actually prefer having two separate positions at a font
boundary.
For the sole purpose of supporting dissolving?
No, for the prupose of being able to work with it. Right now I
Helge Hafting wrote:
Abdelrazak Younes wrote:
But why would you want to have two different charstyles in the _same_
word? If you need that then I would say that this is a use case where
you really want to use font attributes and not charstyle.
This happens natureally when you really start
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
Within text the space syndrome won't be as evident because you
generally only have one depth and not multiple level like in mathed.
Why do we need to nest insets then ? :-P
You know what I meant... :-)
Abdel.
Martin Vermeer wrote:
On Thu, Oct 04, 2007 at 12:46:45AM +0200, [EMAIL PROTECTED] wrote:
On Wed, 3 Oct 2007, Martin Vermeer wrote:
Here's another example (metaphor):
|line of text
press spacespacespace
|line of text, indented
Why doesn't this work? Ought to work, right, in an
Juergen Spitzmueller wrote:
Abdelrazak Younes wrote:
More seriously, this whole discussion comes a bit late IMHO.
But nevertheless, it's a good thing that we have the discussion finally.
Even if I did not find enough time to jump in, I appreciate it very much.
Yes sorry, I think I wrote
Richard Heck wrote:
Without meaning to prejudge the question whether CharStyles should be
insets, here's my list of things that ought to be done if they are
going to stay that way. They are addressed specifically to what Abdel
was calling the look and feel aspect of charstyles, which are in
It seems that there's a bogus character between 'h' and 'C'. At least
Thunderbird does not understand it:
ĤĴĥȷ̂ĈĜŜĉĝŝ
Abdel.
Martin Vermeer wrote:
On Wed, Oct 03, 2007 at 06:39:14PM +0200, Juergen Spitzmueller wrote:
Richard Heck wrote:
The difficulty is that, if you're already in the inset, you might be
wanting to apply another one. How do you distinguish that from changing
the inset type (which is the
Dear All,
I would like to ask you about document comparison.
How can I compare two .lyx document to see the changes between them?
It would be quite nice for updating translations.(since thange tracking
is disabled for this.)
A few month ago I've set-up a local svn on my linux box to store both
Abdelrazak Younes wrote:
Could you please try this?
Doesn't work, unfortunately.
Jürgen
Juergen Spitzmueller wrote:
Abdelrazak Younes wrote:
Could you please try this?
Doesn't work, unfortunately.
OK then revert the optimization as I don't want to spend too much time
on it.
Abdel.
Abdelrazak Younes wrote:
OK then revert the optimization as I don't want to spend too much time
on it.
done.
Jürgen
Jean-Marc Lasgouttes schrieb:
\usepackage[bla,vietnam,blub]{babel}
and not
\documentclass[bla,vietnam,blub]{article}
\usepackage{babel}
This is very weird. The two uses should be equivqlent. Where is this
documented?
Why is this weird? Every language package manual I know states to load
It seems that there's a bogus character between 'h' and 'C'. At least
Thunderbird does not
understand it:
ĤĴĥȷ̂ĈĜŜĉĝŝ
Because Qt? don't understand it and I copied it from there. The character is the ĵ and appears
correctly in the output. We discussed this short before the LyX 1.5.0 release
Uwe Stöhr wrote:
It seems that there's a bogus character between 'h' and 'C'. At least
Thunderbird does not
understand it:
ĤĴĥȷ̂ĈĜŜĉĝŝ
Because Qt?
Maybe but I don't think so, otherwise it would have appeared correctly
in thunderbird and on the wiki page in mozilla.
don't
http://www.lyx.org/trac/changeset/20727
Eh, what are you doing? You destroyed the complete dialog.
We discussed this before I committed this. Please revert! (Or I'll do.)
Uwe
Abdelrazak Younes wrote:
Uwe Stöhr wrote:
It seems that there's a bogus character between 'h' and 'C'. At
least Thunderbird does not
understand it:
ĤĴĥȷ̂ĈĜŜĉĝŝ
Because Qt?
Maybe but I don't think so, otherwise it would have appeared correctly
in thunderbird and on the wiki page in
Abdelrazak Younes wrote:
OK but note that I think this mean that a single math inset in a
paragraph, no matter where will trigger a full redraw in any case.
I know. That's certainly not ideal, but we're going to get back to the issue
for 1.5.3 (and 1.5.2 still has enough improvements).
Jürgen
Juergen Spitzmueller wrote:
Abdelrazak Younes wrote:
OK then revert the optimization as I don't want to spend too much time
on it.
done.
OK but note that I think this mean that a single math inset in a
paragraph, no matter where will trigger a full redraw in any case.
Abdel.
+ // since LyX uses unicode, also set the PDF strings to unicode strings
with the
+ // hyperref option unicode
+ opt += unicode=true,\n ;
What happens when the output is _not_ unicode?
How that?
What does this option do exactly?
Option pdfencoding
The PDF format allows two
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Uwe Stöhr wrote:
It seems that there's a bogus character between 'h' and 'C'. At
least Thunderbird does not
understand it:
ĤĴĥȷ̂ĈĜŜĉĝŝ
Because Qt?
Maybe but I don't think so, otherwise it would have appeared correctly
in
Uwe Stöhr wrote:
Eh, what are you doing? You destroyed the complete dialog.
We discussed this before I committed this.
what is destroyed?
Please revert! (Or I'll do.)
the dialog layout was very messy, so please tell me what is wrong atm so that i
can address it...
Abdelrazak Younes [EMAIL PROTECTED] writes:
To be frank, I am tired of people introducing features by promosing
things and the do something else (martin, if you are reading this, it
is not for you :).
So, is it for me?
Not only :)
JMarc
PS: you probably know of a couple of cases where I
Helge Hafting [EMAIL PROTECTED] writes:
In mathed, repeated spaces cycle though whitespaces of different width.
It's fun when you get used to it, but intuitive? Hardly. These are
gimmicks.
I think that is simple enough - press space again to get bigger space.
Whether bigger space is done
Alex [EMAIL PROTECTED] writes:
I would like to ask you about document comparison.
How can I compare two .lyx document to see the changes between them?
It would be quite nice for updating translations.(since thange tracking
is disabled for this.)
One solution is using wdiff:
Abdelrazak Younes wrote:
It seems that there's a bogus character between 'h' and 'C'. At least
Thunderbird does not understand it:
ĤĴĥȷ̂ĈĜŜĉĝŝ
There is no problem with the userguide at all. It contains the ĵ in
denormalized form:
0x0237 dotless j
0x0302 combining circumflex
If you'd use a
iT IS SAVE TO USE UNICODE IN ALL CASES. I tested this carefully I think.
I hope, because if some trouble bubbles up user has no reasonable way how to
get rid of it then.
Pavel
On Thu, Oct 04, 2007 at 01:55:54PM +0200, Jean-Marc Lasgouttes wrote:
Alex [EMAIL PROTECTED] writes:
I would like to ask you about document comparison.
How can I compare two .lyx document to see the changes between them?
It would be quite nice for updating translations.(since thange
make[6]: Entering directory `/local/lasgoutt/devbuild/src/frontends/qt4'
echo !DOCTYPE RCCRCC version='1.0'qresource Resources.qrc
find ../../../../lyx-devel/lib/images -name '*.png' \
| sed -e 's:../../../../lyx-devel/lib/\(.*\):file alias=\1/file:' \
Resources.qrc
echo /qresource/RCC
Uwe Stöhr [EMAIL PROTECTED] writes:
+ // since LyX uses unicode, also set the PDF strings to unicode
strings
with the
+ // hyperref option unicode
+ opt += unicode=true,\n ;
What happens when the output is _not_ unicode?
How that?
So when a document is in, say, latin2,
I find equation entry on lyx rather nice (being a long-time latex user), but
editing leaves something to be desired. I find it almost impossible to
mark, cut and paste parts of equations. Almost every time I try, I wind up
selecting the whole equation and starting over.
I hope this can be
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
To be frank, I am tired of people introducing features by promosing
things and the do something else (martin, if you are reading this, it
is not for you :).
So, is it for me?
Not only :)
Well, I'd be interested to
On Thu, Oct 04, 2007 at 12:31:32PM +0200, Uwe Stöhr wrote:
http://www.lyx.org/trac/changeset/20727
Eh, what are you doing? You destroyed the complete dialog.
We discussed this before I committed this. Please revert! (Or I'll do.)
Uwe, you have to understand that when something works on
Georg Baum wrote:
Abdelrazak Younes wrote:
It seems that there's a bogus character between 'h' and 'C'. At
least Thunderbird does not understand it: ĤĴĥȷ̂ĈĜŜĉĝŝ
There is no problem with the userguide at all. It contains the ĵ in
denormalized form:
0x0237 dotless j 0x0302 combining
On Wed, Oct 03, 2007 at 03:57:56AM +0200, Dov Feldstern wrote:
Hi!
This is an email I started writing a couple of months ago, regarding the
ignore-spellcheck discussion; but it is even more relevant now with
reference to the questions being raised about character styles as insets.
I
Neal Becker wrote:
I find equation entry on lyx rather nice (being a long-time latex user), but
editing leaves something to be desired. I find it almost impossible to
mark, cut and paste parts of equations. Almost every time I try, I wind up
selecting the whole equation and starting over.
If
Abdelrazak Younes wrote:
Georg Baum wrote:
Abdelrazak Younes wrote:
It seems that there's a bogus character between 'h' and 'C'. At
least Thunderbird does not understand it: ĤĴĥȷ̂ĈĜŜĉĝŝ
There is no problem with the userguide at all. It contains the ĵ in
denormalized form:
0x0237 dotless
Abdelrazak Younes wrote:
Neal Becker wrote:
I find equation entry on lyx rather nice (being a long-time latex user),
but
editing leaves something to be desired. I find it almost impossible to
mark, cut and paste parts of equations. Almost every time I try, I wind
up selecting the whole
Jean-Marc Lasgouttes schrieb:
So when a document is in, say, latin2, the pdf strings will be in
correct unicode?
As far as I tested, yes.
iT IS SAVE TO USE UNICODE IN ALL CASES. I tested this carefully I
think. And nevertheless, whenever the user uses not latin1 as
encoding, unicode must
On Wednesday 03 October 2007 02:57:56 Dov Feldstern wrote:
Hi!
This is an email I started writing a couple of months ago, regarding the
ignore-spellcheck discussion; but it is even more relevant now with
reference to the questions being raised about character styles as insets.
In the last
Leuven, E. schrieb:
what is destroyed?
Please revert! (Or I'll do.)
the dialog layout was very messy, so please tell me what is wrong atm so
that i can address it...
No, this is not the way it works! I implemented that we now use the wrapfig-package for wrap floats.
We can therefore
José Matos wrote:
On Wednesday 03 October 2007 02:57:56 Dov Feldstern wrote:
Hi!
This is an email I started writing a couple of months ago, regarding the
ignore-spellcheck discussion; but it is even more relevant now with
reference to the questions being raised about character styles as
On Thu, 4 Oct 2007, Jean-Marc Lasgouttes wrote:
Helge Hafting [EMAIL PROTECTED] writes:
In mathed, repeated spaces cycle though whitespaces of different width.
It's fun when you get used to it, but intuitive? Hardly. These are
gimmicks.
I think that is simple enough - press space again to
Before people start to add their +1, please read my statement in
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg129100.html
I read it, but I still prefer a checkbox, even if it defaults to on.
As for the previous option, if it was so great, it would default to
true in hyperref.
Fine
On Thu, Oct 04, 2007 at 10:20:43AM +0200, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
Within text the space syndrome won't be as evident because you
generally only have one depth and not multiple level like in mathed.
Why do we need to nest insets then ? :-P
On Thu, Oct 04, 2007 at 10:13:59AM +0200, Jean-Marc Lasgouttes wrote:
More seriously, this whole discussion comes a bit late IMHO. I know
that you emitted some objections when Martin started the
implementation but they were not too strong. We have something _now_
and I'd be a pity to
On Thu, Oct 04, 2007 at 10:09:22AM +0200, Helge Hafting wrote:
Jean-Marc Lasgouttes wrote:
Dov Feldstern [EMAIL PROTECTED] writes:
Abdelrazak Younes wrote:
We will face challenge for sure but Cursor movement is already
working well for entering and leaving insets. We will have to
On Thu, Oct 04, 2007 at 09:47:28AM +0200, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
Right. This was to say: we will obviously never reach an agreement as
our views are fundamentally different.
What we could to try try to resolve this argument is look at
On Thu, Oct 04, 2007 at 09:52:44AM +0200, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
But _I_ happen to like clear threshold between different things, the
kind of threshold is naturally achieved by insets. So why, as a user,
do I have to suffer your way of
On Thu, Oct 04, 2007 at 09:22:15AM +0200, Jean-Marc Lasgouttes wrote:
Juergen Spitzmueller [EMAIL PROTECTED] writes:
Abdelrazak Younes wrote:
No, hence my idea of one word per inset. The fact that there is more
than one inset will only be visible if the cursor is in or if you hover
On Thu, Oct 04, 2007 at 09:24:13AM +0200, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
To satisfy everybody maybe we should implement charstyle as font
attribute (and thus please Dov and John) and rename our current
charstyle to textstyle. I know for sure that I
On Thu, 4 Oct 2007, Abdelrazak Younes wrote:
What are your criteria for something being a word? I.e., does your
approach handle cases like:
\noun[Peter}'s patch \command{\define}s some new \program{LyX}-friendly
\command{environtment}s in a \noun{Knuth}ian way?
No, anything that is
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
I suspected something like that but we had 770 not 237 in addition to
302 so I think there was a problem nevertheless.
There is no problem in 1.5. 1.5 has 0x0237 and then 0x0302, and this is
correct. If 1.6 is different then there might be a
On Thu, 4 Oct 2007, Martin Vermeer wrote:
Perhaps Andre doesn't suffer fools gladly, in which case I sympathise.
Not implying that you're one of those fools, but the refusal by so many
on this list to accept a UI paradigm for LyX that matches hand-in-glove
the natural structure of the feature
Uwe, you have to understand that when something works on windows
(or for you) it doesn't mean that it works everywhere (or for others).
The layout was broken on solaris (wrap-bad.png) and Edwin corrected
that (wrap-ok.png).
This is not what I meant. Edwin reverted the checkboxes and their
On Thu, Oct 04, 2007 at 06:46:45PM +0300, Martin Vermeer wrote:
Not very convincing, is it? Most people learn from experience. What
would happen here is that they would quickly pick up that -- no, this
stuff does not behave like italicize; it behaves like insets instead.
Familiar paradigm
On Thu, 4 Oct 2007, Abdelrazak Younes wrote:
No, hence my idea of one word per inset. The fact that there is more
than one inset will only be visible if the cursor is in or if you
hover the mouse over it.
What are your criteria for something being a word? I.e., does your
approach
On Thu, Oct 04, 2007 at 06:52:48PM +0300, Martin Vermeer wrote:
Why do we need to nest insets then ? :-P
Actually I don't think we should (usually). In text, cases where we
want to nest (charstyle) insets ought to be rare, if we have defined
them as sensible semantic units. Over-use of
The unicode character is #309 but the one in the wiki and also in the
UserGuide is #770. So a
simple correction should solve the problem. I don't get a crash here anyway
when selecting the
small black square used to represent #770.
When you found a solution, could you please fix this in the
-- Forwarded message --
Date: Thu, 4 Oct 2007 12:31:57 -0400
From: Steve Litt [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Use cases for charstyles (Was: *not* everything is an inset!)
On Wednesday 03 October 2007 18:20, you wrote:
Hi Steve,
There's a discussion going
1 - 100 of 360 matches
Mail list logo
