Andre Poenitz wrote:
Pretty trivial patch attached.
Ok?
can you add a comment?
On Fri, Jun 22, 2007 at 08:00:04AM +0200, Edwin Leuven wrote:
Andre Poenitz wrote:
Pretty trivial patch attached.
Ok?
can you add a comment?
The feature (inserting a space via lfun) was asked for twice during the
last few weeks. Now that is possible using M-x unicode-insert 0x20.
Alfredo Braunstein wrote:
Bo Peng wrote:
I don't know Bo, I think that latex_code() is a reasonably efficient way
of having a signature of the math inset (to check if it has changed). I
would be surprised if this had a real performance impact (typically O(1)
operations per user interaction, we
Edwin Leuven wrote:
Richard Heck wrote:
This patch addresses the usability bugs discussed in this thread:
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg121160.html
and largely implements Helge's suggestions. (Helge often seems to have
good ideas on these things.) The main change
On Wed, Jun 20, 2007 at 10:00:54PM +0200, Enrico Forestieri wrote:
On Wed, Jun 20, 2007 at 09:44:12AM +0100, José Matos wrote:
On Wednesday 20 June 2007 00:00:06 Enrico Forestieri wrote:
The attached patch fixes it. José, OK to commit?
The patch seems right. If you someone to test
Am 22.06.2007 um 00:42 schrieb Uwe Stöhr:
Attached is a patch from Georg that fixes the regression bug 1942:
Inconsistent look of integral symbols.
I tested it thoroughly will all combinations of the packages esint,
wasysym, and amsmath.
A Mac user has reported a perhaps related
Andre Poenitz wrote:
On Fri, Jun 22, 2007 at 08:00:04AM +0200, Edwin Leuven wrote:
Andre Poenitz wrote:
Pretty trivial patch attached.
Ok?
can you add a comment?
The feature (inserting a space via lfun) was asked for twice during the
last few weeks. Now that is possible using M-x
Alfredo Braunstein wrote:
Specially with new document classes I normally don't know what the layouts
really are so I switch back and forth several times...
i agree that the only situation where this might reasonably occur is when
switching document classes.
so given that:
- people don't
Leuven, E. wrote:
- case 1 2 are rare
No, they're not.
Jürgen
- case 1 2 are rare
No, they're not.
where do you get your stats from?
Abdelrazak Younes wrote:
I agree with Edwin personally. I would also agree with
o Justified (Default)
o Left
o Center
o Right
But we can change that later if we reach consensus.
I think default should be an additional option. There may be good
reasons to set the alignment to the setting
Leuven, E. wrote:
No, they're not.
where do you get your stats from?
Where do you get your stats from?
I just think it's wrong to assume that justified is the de facto standard
alignment. This might be true for standard paragraphs in most book and
article classes, for others it is not.
I
Mostafa Vahedi wrote:
Currently (only) Unicode is used for Farsi as the input
encoding. Moreover in Unicode the openning parenthesis
is always the left one (independent of the language)
I have modified the code to reverse the direction of
the character-pairs when it wants to display the
Alfredo Braunstein wrote:
Let me give you another case: I often write my titles first in Standard
Layout and *then* switch the layout to Title. With your approach I would
have to manually center it. Awful.
no.
reread what i wrote:
i would be fine with having the default take precedence in
Juergen Spitzmueller wrote:
Where do you get your stats from?
from a very reliable source
I just think it's wrong to assume that justified is the de facto standard
alignment.
?
you are misunderstanding me. the inset/layout should tell us what the default
is (and i think it does at the
Edwin Leuven wrote:
if i creat a selection that spans more than one line and then type
something (so that the selection gets replace with my new text), the
selection before the line where cursor is isn't crossed out. there is a
missing screen update here.
Confirmed.
second thing is when i
Leuven, E. wrote:
so given that:
- people don't switch document classes often (i for example never do)
- switching document layouts often involve information loss because they
do not define similar environments - case 1 2 are rare
Let me give you another case: I often write my titles
Jürgen Spitzmüller wrote:
http://bugzilla.lyx.org/show_bug.cgi?id=2520
The attached patch does this (I think it's the last remaining
non-translatable ui part).
Any opinions on this?
Jürgen
Leuven, E. wrote:
Alfredo Braunstein wrote:
Let me give you another case: I often write my titles first in Standard
Layout and *then* switch the layout to Title. With your approach I would
have to manually center it. Awful.
no.
reread what i wrote:
That implies I've read it in the
Stefan Schimanski schrieb:
Before you apply the patch: Check if bug 3902 is not already there.
With the double integral the math preview does not appear. What should I
do now?
When this is the case without the patch is applied,
- confirm the bug report 3902
- aplly the patch for bug 1942
Dov Feldstern wrote:
Hi!
First of all, I just want to apologize to you, Uwe: I feel that we were
getting very argumentative last night, and I'm not sure why... I'll
blame it on the hour and on the fact that I was getting very frustrated
with the fact that not all my messages were making it
Dear Dov and Uwe,
ARABI is a good package for Farsi that supports BABEL. But it has some (even
many) limitations. About Arabic I believe that I am not the person who should
decides at this moment. I need more time for that one.
I would like to keep the possibility of using ArabTeX (NOT
Hi!
First of all, I just want to apologize to you, Uwe: I feel that we were
getting very argumentative last night, and I'm not sure why... I'll
blame it on the hour and on the fact that I was getting very frustrated
with the fact that not all my messages were making it through for some
Leuven, E. wrote:
you are misunderstanding me. the inset/layout should tell us what the
default is (and i think it does at the moment). so sometimes this will be
justified, in other cases center, etc.
I obviously did. Sorry. I'm still not entirely convinced.
Jürgen
On Friday 22 June 2007 09:48:02 Juergen Spitzmueller wrote:
Jürgen Spitzmüller wrote:
http://bugzilla.lyx.org/show_bug.cgi?id=2520
The attached patch does this (I think it's the last remaining
non-translatable ui part).
Any opinions on this?
I like it, I was expecting for other
Dov Feldstern schrieb:
First of all, I just want to apologize to you, Uwe: I feel that we were
getting very argumentative last night, and I'm not sure why...
No problem. I think such discussions are needed to get a decision.
So what about the following:
- I commit the Farsi related stuff
On Friday 22 June 2007 06:55:01 Andre Poenitz wrote:
Pretty trivial patch attached.
Ok?
Andre'
OK.
--
José Abílio
Uwe Stöhr wrote:
Dov Feldstern schrieb:
First of all, I just want to apologize to you, Uwe: I feel that we
were getting very argumentative last night, and I'm not sure why...
No problem. I think such discussions are needed to get a decision.
So what about the following:
- I commit the
Alfredo Braunstein wrote:
Dov Feldstern wrote:
Hi!
First of all, I just want to apologize to you, Uwe: I feel that we were
getting very argumentative last night, and I'm not sure why... I'll
blame it on the hour and on the fact that I was getting very frustrated
with the fact that not all my
If we are going to support both ARABI and ArabTeX for Arabic then we should
also see how we can combine them in LaTeX terms. I will do that and I will let
you know the result. Therefore as I prepared an skeleton (how-to) for writing
Farsi based on ARABI, I will prepare one for Arabic based on
Attached is a better patch where
everything is implemented:
- correct encoding for the fontenc
package. Mostafa tested this and
gave his OK for this issue.
This is exteremly OK.
- special quotation mark definitions
for Farsi. Mostafa tested this and
gave his OK for this issue.
This
I have attached the Farsi keyboard based
on Linux Farsi keymap which can be added to
directory LYX_DEVEL/lib/kbd/. The only
problem I have is the last line in which
I tried to assign a letter to the double
quote, i.e. \, and it did not work.
couldn't be mapped because it's reserved
I obviously did. Sorry. I'm still not entirely convinced.
i was thinking like the attached...
Index: src/frontends/qt4/QParagraph.cpp
===
--- src/frontends/qt4/QParagraph.cpp (revision 18850)
+++ src/frontends/qt4/QParagraph.cpp
Mostafa Vahedi schrieb:
- use the document language also for
the TOC. This is a special arabi-package
thing. Please test.
It needs more investigation. We should
find the correct point in the source
at which we could place the command
\TOCLanguage{farsi}.
I think I have found it out: It
Mostafa Vahedi wrote:
If we are going to support both ARABI and ArabTeX for Arabic then we should
also see
how we can combine them in LaTeX terms. I will do that and I will let you know the
result. Therefore as I prepared an skeleton (how-to) for writing Farsi based on ARABI,
I will prepare
Alfredo Braunstein wrote:
What happends if the user moves the cursor when the dialog is open, does it
get updated?
The dialog is presently modal, precisely because there's no reliable
trigger right now to do the update. Making this work involves re-working
the controller fairly extensively,
José Matos wrote:
Any opinions on this?
I like it, I was expecting for other opinions.
Som nanyone? Can I commit?
Jürgen
http://bugzilla.lyx.org/show_bug.cgi?id=3346
The fix is simply to clear the dirty flag of the tabular clipboard on normal
text copy.
Seeking 2 OKs.
A/
Index: CutAndPaste.cpp
===
--- CutAndPaste.cpp (revision 18850)
+++
The attached onliner fixes the issue for me (and Uwe).
Explanation: if current_layout is updated here, the test in LyXView.cpp:462
returns false and the combo is not updated. Furthermore, current_layout will
be reset in LyXView.cpp (after the combo update).
OK?
Jürgen
Index: src/Text3.cpp
Alfredo Braunstein wrote:
Leuven, E. wrote:
Alfredo Braunstein wrote:
since default takes precedence things go fine in your example.
I see.
WRT the current situation, your approach tends to make things default (on
layout switching) against user will, which is sort of lyx philosophy:
On Friday 22 June 2007 14:54:58 Alfredo Braunstein wrote:
http://bugzilla.lyx.org/show_bug.cgi?id=3346
The fix is simply to clear the dirty flag of the tabular clipboard on
normal text copy.
Seeking 2 OKs.
A/
OK.
--
José Abílio
On Friday 22 June 2007 16:37:53 Jürgen Spitzmüller wrote:
The attached onliner fixes the issue for me (and Uwe).
Explanation: if current_layout is updated here, the test in LyXView.cpp:462
returns false and the combo is not updated. Furthermore, current_layout
will be reset in LyXView.cpp
Mostafa Vahedi wrote:
Mostafa Vahedi wrote:
Currently (only) Unicode is used for Farsi as the input
encoding. Moreover in Unicode the openning parenthesis
is always the left one (independent of the language)
I have modified the code to reverse the direction of
the character-pairs when it
(Again, resending because it didn't arrive the first time; sorry if you
got it twice)
Uwe Stöhr wrote:
Dov Feldstern schrieb:
The question is, should we really go to all this trouble? (Well, not
so much, but (a) should we separate between ArabTeX and Arabi, and (b)
should we update lyx2lyx
José Matos wrote:
OK. I think that the subject is important and I liked the discussion
there, now let us move to other (critical) bugs. :-)
Since I have to decide I opt for Richard's argument without any
demerit for Edwin patch/solution.
let me guess, you tossed a coin...?
Jürgen == Jürgen Spitzmüller [EMAIL PROTECTED] writes:
Jürgen http://bugzilla.lyx.org/show_bug.cgi?id=2520
Jürgen The attached patch does this (I think it's the last remaining
Jürgen non-translatable ui part).
I have no idea about the python part, but the rest looks sane.
JMarc
On Friday 22 June 2007 17:59:21 Richard Heck wrote:
José Matos wrote:
On Friday 22 June 2007 17:42:34 Edwin Leuven wrote:
did you have a look at this one?
I had both under my radar. :-)
What are the (minor) differences between both patches?
Edwin's patch attempts to treat the
Jürgen Spitzmüller wrote:
The attached onliner fixes the issue for me (and Uwe).
Explanation: if current_layout is updated here, the test in
LyXView.cpp:462 returns false and the combo is not updated. Furthermore,
current_layout will be reset in LyXView.cpp (after the combo update).
OK?
Explanation: if current_layout is updated here, the test in LyXView.cpp:462
returns false and the combo is not updated. Furthermore, current_layout
will be reset in LyXView.cpp (after the combo update).
Does this fix the issue of layout change with shortcut?
Bo
This patch addresses the usability bugs discussed in this thread:
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg121160.html
and largely implements Helge's suggestions. (Helge often seems to have
good ideas on these things.) The main change is that the Default
button is now a radio
On Friday 22 June 2007 17:28:06 Richard Heck wrote:
OK to apply?
OK.
Richard
--
José Abílio
José Matos wrote:
On Friday 22 June 2007 17:28:06 Richard Heck wrote:
OK to apply?
did you have a look at this one?
Index: src/frontends/qt4/QParagraph.cpp
===
--- src/frontends/qt4/QParagraph.cpp (revision 18850)
+++
José Matos wrote:
On Friday 22 June 2007 17:42:34 Edwin Leuven wrote:
did you have a look at this one?
I had both under my radar. :-)
What are the (minor) differences between both patches?
Edwin's patch attempts to treat the alignment that happens to be the
default (say,
On Friday 22 June 2007 17:04:25 Dov Feldstern wrote:
I don't think that a format change is needed, because we're using new
languages, not changing the interpretation of existing ones. If there
are users out there who have existing documents in ArabTeX, they'll have
to replace all \lang arabic
On Friday 22 June 2007 17:42:34 Edwin Leuven wrote:
did you have a look at this one?
I had both under my radar. :-)
What are the (minor) differences between both patches?
--
José Abílio
Richard Heck wrote:
What are the (minor) differences between both patches?
there is a long thread on this but to summarize:
the question is whether we want a separate default button for the rare
situations in which we (1) change document layouts and (2) run into:
1 x is set and we change
The List of algorithms label cannot be customized (translated) into
the output.
1. Create a new document
2. Choose a non english language
3. Insert a list of algorithms (Insert List / TOC List of
Algorithms)
4. View the source (View View Source)
The code corresponding to the List of
The List of algorithms label cannot be customized (translated) into
the output.
1. Create a new document
2. Choose a non english language
3. Insert a list of algorithms (Insert List / TOC List of
Algorithms)
4. View the source (View View Source)
The code corresponding to the List of
The List of algorithms label cannot be customized (translated) into the
output.
1. Create a new document
2. Choose a non english language
3. Insert a list of algorithms (Insert List / TOC List of Algorithms)
4. View the source (View View Source)
The code corresponding to the List of
On Friday 22 June 2007 18:21:52 Edwin Leuven wrote:
let me guess, you tossed a coin...?
Not on Fridays. :-)
In case it matters both solutions are better than what we have now, and I am
closer from Richard's reasoning in this case. Also after some time if no
consensus is reached it is better
On Friday 22 June 2007 16:33:41 Jürgen Spitzmüller wrote:
Som nanyone? Can I commit?
Jürgen
OK.
--
José Abílio
José Matos wrote:
On Friday 22 June 2007 18:21:52 Edwin Leuven wrote:
let me guess, you tossed a coin...?
Not on Fridays. :-)
observational equivalent though...
In case it matters both solutions are better than what we have now,
sure
and I am closer from Richard's reasoning in this
I apologize, I sent this mail twice. I had some problems with my SMTP
server...
Le 22 juin 07 à 20:48, Mael Hilléreau a écrit :
The List of algorithms label cannot be customized (translated)
into the
output.
1. Create a new document
2. Choose a non english language
3. Insert a list of
On Fri, Jun 22, 2007 at 07:21:52PM +0200, Edwin Leuven wrote:
José Matos wrote:
OK. I think that the subject is important and I liked the discussion
there, now let us move to other (critical) bugs. :-)
Since I have to decide I opt for Richard's argument without any
demerit for Edwin
I don't think that bug 3902 should stop you committing your valuable solution
to bug 1942 as, in
the Mac case, it provides a considerable improvement.
OK then I misunderstood you. I thought you meant that the patch introduces a
new problem.
I applied the patch.
regards Uwe
Mael Hilléreau wrote:
I apologize, I sent this mail twice. I had some problems with my SMTP
server...
No need to apologize. The list is terribly slow today, some messages had a
delay of more than an hour.
A/
I applied the following patch:
http://www.lyx.org/trac/changeset/18858
Mostafa Vahedi schrieb:
Attached is a better patch where
everything is implemented:
- correct encoding for the fontenc
package. Mostafa tested this and
gave his OK for this issue.
This is exteremly OK.
This is
Uwe Stöhr schrieb:
I applied the following patch:
http://www.lyx.org/trac/changeset/18858
I corrected it:
http://www.lyx.org/trac/changeset/18859
Uwe
I've committed this now, with a reference to this discussion.
Richard
Richard Heck wrote:
José Matos wrote:
On Friday 22 June 2007 17:42:34 Edwin Leuven wrote:
did you have a look at this one?
I had both under my radar. :-)
What are the (minor) differences between both patches?
Mostafa Vahedi schrieb:
Ok. Here you are!
Done, I committed the keymap file.
regards Uwe
Does this fix the issue of layout change with shortcut?
Yes.
Uwe
Le 22 juin 07 à 22:44, Alfredo Braunstein a écrit :
Mael Hilléreau wrote:
I apologize, I sent this mail twice. I had some problems with my SMTP
server...
No need to apologize. The list is terribly slow today, some
messages had a
delay of more than an hour.
Ok, happy to know that it's
I had a bit of trouble with Step 7. of http://www.lyx.org/trac/
browser/lyx-devel/trunk/INSTALL.Win32 by following the instruction
too literally.
Preceding instructions excellent.
I suggest the following would be an improvement:
7 Compile
From MS Visual Studio command prompt (not
I suggest the following would be an improvement:
7 Compile
From MS Visual Studio command prompt (not the regular cmd.exe),
cd lyx root directory\development\Win32\packaging\
build_msvc.bat
This worked for me.
Thank you very much. The instruction has been updated.
Attached is Dov's latest patch. I added the font encoding stuff and the fileformat change. It is
furthermore needed to load arabtex in the preamble when the language is arabic_arabtex, I added this
to the patch. Please test.
---
Dov wrote:
+arabic_arabtex arabic Arabic (ArabTeX) true
Can anybody help me with this issue?:
Special lines should to be added to the preamble whenever e.g. Arabic is used
in the document.
I know how to do this in Bufferparams.cp when Arabic is the document language:
if (language-lang() == arabic_arabtex) {
os \\usepackage{arabtex}\n;
cd lyx root directory\development\Win32\packaging\
build_msvc.bat
The best way is to add the following line at the begining
of build_msvc.bat:
cd /D %~dp0
and also for bebug build. In this way, you can drag the .bat
and drop in any MSVC command console, then hit return to compile.
Uwe Stöhr wrote:
Can anybody help me with this issue?:
Special lines should to be added to the preamble whenever e.g. Arabic
is used in the document.
I know how to do this in Bufferparams.cp when Arabic is the document
language:
if (language-lang() == arabic_arabtex) {
os
Contrary to what I said in a previous message, completing the reworking
of the Paragraph Settings dialog isn't terribly difficult. Here's the
issue: In this dialog---both before the most recent patch and since it,
though there was some disagreement about this---we distinguish between
the
In ParagraphParameters.cpp and elsewhere, there are references to a
leftindent property. At present, however, I see no way to set this
property. In particular, it isn't in the Paragraph Settings dialog, and
isn't in 1.4.4, either. Anyone know the history of this?
Richard
Slight update...
Contrary to what I said in a previous message, completing the reworking
of the Paragraph Settings dialog isn't terribly difficult. Here's the
issue: In this dialog---both before the most recent patch and since it,
though there was some disagreement about this---we distinguish
Andre Poenitz wrote:
Pretty trivial patch attached.
Ok?
can you add a comment?
On Fri, Jun 22, 2007 at 08:00:04AM +0200, Edwin Leuven wrote:
> Andre Poenitz wrote:
> >Pretty trivial patch attached.
> >
> >Ok?
>
> can you add a comment?
The feature (inserting a space via lfun) was asked for twice during the
last few weeks. Now that is possible using M-x unicode-insert
Alfredo Braunstein wrote:
Bo Peng wrote:
I don't know Bo, I think that latex_code() is a reasonably efficient way
of having a signature of the math inset (to check if it has changed). I
would be surprised if this had a real performance impact (typically O(1)
operations per user interaction, we
Edwin Leuven wrote:
Richard Heck wrote:
This patch addresses the usability bugs discussed in this thread:
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg121160.html
and largely implements Helge's suggestions. (Helge often seems to have
good ideas on these things.) The main change
On Wed, Jun 20, 2007 at 10:00:54PM +0200, Enrico Forestieri wrote:
> On Wed, Jun 20, 2007 at 09:44:12AM +0100, José Matos wrote:
> > On Wednesday 20 June 2007 00:00:06 Enrico Forestieri wrote:
> > > The attached patch fixes it. José, OK to commit?
> >
> > The patch seems right. If you someone
Am 22.06.2007 um 00:42 schrieb Uwe Stöhr:
Attached is a patch from Georg that fixes the regression bug 1942:
Inconsistent look of integral symbols.
I tested it thoroughly will all combinations of the packages esint,
wasysym, and amsmath.
A Mac user has reported a perhaps related
Andre Poenitz wrote:
> On Fri, Jun 22, 2007 at 08:00:04AM +0200, Edwin Leuven wrote:
>> Andre Poenitz wrote:
>>> Pretty trivial patch attached.
>>>
>>> Ok?
>> can you add a comment?
>
> The feature (inserting a space via lfun) was asked for twice during the
> last few weeks. Now that is possible
Alfredo Braunstein wrote:
> Specially with new document classes I normally don't know what the layouts
> really are so I switch back and forth several times...
i agree that the only situation where this might reasonably occur is when
switching document classes.
so given that:
- people don't
Leuven, E. wrote:
> - case 1 & 2 are rare
No, they're not.
Jürgen
>> - case 1 & 2 are rare
>
> No, they're not.
where do you get your stats from?
Abdelrazak Younes wrote:
I agree with Edwin personally. I would also agree with
o Justified (Default)
o Left
o Center
o Right
But we can change that later if we reach consensus.
I think default should be an additional option. There may be good
reasons to set the alignment to the setting
Leuven, E. wrote:
>> No, they're not.
>
> where do you get your stats from?
Where do you get your stats from?
I just think it's wrong to assume that justified is the de facto "standard"
alignment. This might be true for standard paragraphs in most book and
article classes, for others it is
Mostafa Vahedi wrote:
>> Currently (only) Unicode is used for Farsi as the input
>> encoding. Moreover in Unicode the openning parenthesis
>> is always the left one (independent of the language)
>> I have modified the code to reverse the direction of
>> the character-pairs when it wants to
Alfredo Braunstein wrote:
> Let me give you another case: I often write my titles first in Standard
> Layout and *then* switch the layout to Title. With your approach I would
> have to manually center it. Awful.
no.
reread what i wrote:
"i would be fine with having the default take precedence
Juergen Spitzmueller wrote:
> Where do you get your stats from?
from a very reliable source
> I just think it's wrong to assume that justified is the de facto "standard"
> alignment.
?
you are misunderstanding me. the inset/layout should tell us what the default
is (and i think it does at
Edwin Leuven wrote:
> if i creat a selection that spans more than one line and then type
> something (so that the selection gets replace with my new text), the
> selection before the line where cursor is isn't crossed out. there is a
> missing screen update here.
Confirmed.
> second thing is
Leuven, E. wrote:
> so given that:
>
> - people don't switch document classes often (i for example never do)
> - switching document layouts often involve information loss because they
> do not define similar environments - case 1 & 2 are rare
Let me give you another case: I often write my
Jürgen Spitzmüller wrote:
> http://bugzilla.lyx.org/show_bug.cgi?id=2520
>
> The attached patch does this (I think it's the last remaining
> non-translatable ui part).
Any opinions on this?
Jürgen
Leuven, E. wrote:
> Alfredo Braunstein wrote:
>> Let me give you another case: I often write my titles first in Standard
>> Layout and *then* switch the layout to Title. With your approach I would
>> have to manually center it. Awful.
>
> no.
>
> reread what i wrote:
That implies I've read it
1 - 100 of 162 matches
Mail list logo
