José Matos wrote:
On Sunday 15 July 2007 10:47:46 Martin Vermeer wrote:
If the LaTeX output is different, I would say it is a format
change... the problem is then to produce a lyx2lyx entry
that would modify an old .lyx file upon conversion to the
new format so, that it nevertheless produces
Hi!
I haven't gotten any responses to this. I think this patch
(http://permalink.gmane.org/gmane.editors.lyx.devel/89975) should go in,
I would be happy for people to test it. Can I commit?
Dov
Hi!
Attached find a cleaned up version of the patch for 1820, based on the
explanations I provided last night
(http://permalink.gmane.org/gmane.editors.lyx.devel/89979).
I now feel quite confident that this patch is good. I tried it on all
the sample files I have and that I created, I tried
Hi!
Attached find a patch which I believe is necessary for correctly
displaying numbers in the output of arabic documents using Arabi
(ArabTeX takes care of this internally).
Uwe, Mostafa --- could you please test this? (I'm still having trouble
with setting up Arabi correctly --- though
Hi!
Is there any way for me to only apply one of the stages if the original
format number of the file being converted was under 249?
The problem with my current patch for bug 3613 is this:
Files from pre-249 are wrong, but post-249 don't have the problem. So my
new stage (277) should only
Dov Feldstern wrote:
Hi!
Attached find a patch for the last remaining problem with bug 3613. It's
a format change. The problem it solves is due to some missed cases way
back in format change 249.
I'm attaching example files which demonstrate the problem (and which
this patch fixes
Dov Feldstern wrote:
Dov Feldstern wrote:
Hi!
Attached find a patch for the last remaining problem with bug 3613.
It's a format change. The problem it solves is due to some missed
cases way back in format change 249.
I'm attaching example files which demonstrate the problem (and which
Hi!
Here I will try to explain my understanding of the issues leading to
bugs 1820 and 3613. This is partly because I feel that it's important
that as many people as possible be aware of these, for future
development; partly in order to explain the patches I'm proposing for
these two bugs,
Hi!
Is there any way for me to only apply one of the stages if the original
format number of the file being converted was under 249?
The problem with my current patch for bug 3613 is this:
Files from pre-249 are wrong, but post-249 don't have the problem. So my
new stage (277) should only
Dov Feldstern wrote:
Hi!
Attached find a patch for the last remaining problem with bug 3613. It's
a format change. The problem it solves is due to some missed cases way
back in format change 249.
I'm attaching example files which demonstrate the problem (and which
this patch fixes
Dov Feldstern wrote:
Dov Feldstern wrote:
Hi!
Attached find a patch for the last remaining problem with bug 3613.
It's a format change. The problem it solves is due to some missed
cases way back in format change 249.
I'm attaching example files which demonstrate the problem (and which
Hi!
Here I will try to explain my understanding of the issues leading to
bugs 1820 and 3613. This is partly because I feel that it's important
that as many people as possible be aware of these, for future
development; partly in order to explain the patches I'm proposing for
these two bugs,
Hi!
I have a few patches (for bugs 1820, 3613) which have to go in before
the final release, because they involve format changes, but which
require more work and testing. I realize, however, that this is holding
up continued development, and generally developers (much more than the
users, I
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 07:10:10PM +0300, Dov Feldstern wrote:
Attached find the latest additions to the patch. Enrico, I think these
will solve the samples you sent me, and it seems to still work for the
RTL stuff. But I haven't had time to clean up the patch yet
Joost Verburg wrote:
Abdelrazak Younes wrote:
Quite frankly, as there is no format change and that this needs some
more testing, I'd prefer that you wait for 1.5.1 which will hopefully
happen very soon. Just look at my recent brown paper bag which was
supposed to be very very safe.
===
--- lyx-devel.orig/development/FORMAT 2007-07-15 02:25:40.0 +0300
+++ lyx-devel/development/FORMAT2007-07-15 02:31:28.0 +0300
@@ -1,6 +1,10 @@
LyX file-format changes
---
+2007-07-15 Dov Feldstern [EMAIL PROTECTED
Hi!
I have a few patches (for bugs 1820, 3613) which have to go in before
the final release, because they involve format changes, but which
require more work and testing. I realize, however, that this is holding
up continued development, and generally developers (much more than the
users, I
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 07:10:10PM +0300, Dov Feldstern wrote:
Attached find the latest additions to the patch. Enrico, I think these
will solve the samples you sent me, and it seems to still work for the
RTL stuff. But I haven't had time to clean up the patch yet
Joost Verburg wrote:
Abdelrazak Younes wrote:
Quite frankly, as there is no format change and that this needs some
more testing, I'd prefer that you wait for 1.5.1 which will hopefully
happen very soon. Just look at my recent brown paper bag which was
supposed to be very very safe.
==
--- lyx-devel.orig/development/FORMAT 2007-07-15 02:25:40.0 +0300
+++ lyx-devel/development/FORMAT2007-07-15 02:31:28.0 +0300
@@ -1,6 +1,10 @@
LyX file-format changes
---
+2007-07-15 Dov Feldstern <[EMAIL PROTECTED]>
+
+ * format
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 03:21:42AM +0300, Dov Feldstern wrote:
Dov Feldstern wrote:
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:31:05AM +0300, Dov Feldstern wrote:
Enrico Forestieri wrote:
With your patch applied, when I mark as english the footnote
content
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 03:05:39AM +0300, Dov Feldstern wrote:
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:31:05AM +0300, Dov Feldstern wrote:
Enrico Forestieri wrote:
With your patch applied, when I mark as english the footnote content
I correctly see
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:48:49AM +0300, Dov Feldstern wrote:
I realized that with the partial solution, which fixed some cases, other
cases which used to work stopped working. So the only way to go is to
provide a complete solution for all cases (well, maybe
Hi
w.r.t. bug 1820, I'm getting very confused about what constitutes a
format change and what does not.
Generally, I think, a format change is when given an existing file F, I
used to get latex output X, and due to a change in LyX I now get latex
output Y. In such a case, we normally have
Dov Feldstern wrote:
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:48:49AM +0300, Dov Feldstern wrote:
I realized that with the partial solution, which fixed some cases,
other cases which used to work stopped working. So the only way to go
is to provide a complete solution for all
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 03:21:42AM +0300, Dov Feldstern wrote:
Dov Feldstern wrote:
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:31:05AM +0300, Dov Feldstern wrote:
Enrico Forestieri wrote:
With your patch applied, when I mark as english the footnote
content
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 03:05:39AM +0300, Dov Feldstern wrote:
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:31:05AM +0300, Dov Feldstern wrote:
Enrico Forestieri wrote:
With your patch applied, when I mark as english the footnote content
I correctly see
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:48:49AM +0300, Dov Feldstern wrote:
I realized that with the partial solution, which fixed some cases, other
cases which used to work stopped working. So the only way to go is to
provide a complete solution for all cases (well, maybe
Hi
w.r.t. bug 1820, I'm getting very confused about what constitutes a
format change and what does not.
Generally, I think, a format change is when given an existing file F, I
used to get latex output X, and due to a change in LyX I now get latex
output Y. In such a case, we normally have
Dov Feldstern wrote:
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:48:49AM +0300, Dov Feldstern wrote:
I realized that with the partial solution, which fixed some cases,
other cases which used to work stopped working. So the only way to go
is to provide a complete solution for all
OK, here's my original patch for bug 1820 (without the second part,
identical to what I originally sent in). It solves most cases, as far as
I can determine is safe (I tried it on my documents with complex bidi /
encoding / language transitions), and it does not constitute a format
change,
Dov Feldstern wrote:
encoding / language transitions), and it does not constitute a format
change, IMO.
I'm not sure this is true, I think even just this patch is a format
change... anyone care to take a look?
Peter Kümmel wrote:
Dov Feldstern wrote:
OK, here's my original patch for bug 1820 (without the second part,
identical to what I originally sent in). It solves most cases, as far as
I can determine is safe (I tried it on my documents with complex bidi /
encoding / language transitions
Enrico Forestieri wrote:
Dov,
Hi Enrico! Thanks for taking a look at this... :)
this is what I did. Without your patch applied, I started a new
document, so the language is english, and then activated View Source.
I wrote bla bla bla , then switched the language to italian and wrote
BLA
Enrico Forestieri wrote:
With your patch applied, when I mark as english the footnote content
I correctly see a \selectlanguage{english} inserted before bla bla bla.
But I also see that the whole footnote inset is marked as foreign, so I
select the whole of it and mark it as english. Now it is
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:31:05AM +0300, Dov Feldstern wrote:
Enrico Forestieri wrote:
With your patch applied, when I mark as english the footnote content
I correctly see a \selectlanguage{english} inserted before bla bla bla.
But I also see that the whole footnote
Dov Feldstern wrote:
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:31:05AM +0300, Dov Feldstern wrote:
Enrico Forestieri wrote:
With your patch applied, when I mark as english the footnote
content I correctly see a \selectlanguage{english} inserted before
bla bla bla.
But I also see
OK, here's my original patch for bug 1820 (without the second part,
identical to what I originally sent in). It solves most cases, as far as
I can determine is safe (I tried it on my documents with complex bidi /
encoding / language transitions), and it does not constitute a format
change,
Dov Feldstern wrote:
encoding / language transitions), and it does not constitute a format
change, IMO.
I'm not sure this is true, I think even just this patch is a format
change... anyone care to take a look?
Peter Kümmel wrote:
Dov Feldstern wrote:
OK, here's my original patch for bug 1820 (without the second part,
identical to what I originally sent in). It solves most cases, as far as
I can determine is safe (I tried it on my documents with complex bidi /
encoding / language transitions
Enrico Forestieri wrote:
Dov,
Hi Enrico! Thanks for taking a look at this... :)
this is what I did. Without your patch applied, I started a new
document, so the language is english, and then activated "View Source".
I wrote "bla bla bla ", then switched the language to italian and wrote
Enrico Forestieri wrote:
With your patch applied, when I mark as english the footnote content
I correctly see a \selectlanguage{english} inserted before "bla bla bla".
But I also see that the whole footnote inset is marked as foreign, so I
select the whole of it and mark it as english. Now it
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:31:05AM +0300, Dov Feldstern wrote:
Enrico Forestieri wrote:
With your patch applied, when I mark as english the footnote content
I correctly see a \selectlanguage{english} inserted before "bla bla bla".
But I also see that
Dov Feldstern wrote:
Enrico Forestieri wrote:
On Fri, Jul 13, 2007 at 02:31:05AM +0300, Dov Feldstern wrote:
Enrico Forestieri wrote:
With your patch applied, when I mark as english the footnote
content I correctly see a \selectlanguage{english} inserted before
"bla bla bla".
But
Jean-Marc Lasgouttes wrote:
Dov == Dov Feldstern dfeldstern-rhxOsnTko2JWk0Htik3J/[EMAIL PROTECTED]
writes:
Dov Do you know why this whole font-change mechanism was originally
Dov added?
Consider a footnote with several paragraphs and assume it is typeset
in \emph like this:
\emph{Some
Jürgen Spitzmüller wrote:
Michael Gerz wrote:
there are three more patches which may be subject to discussion:
[patch] bug 1820 --- footnotes in different language (by Dov)
As I just posted in a separate message, it turns out that (I'm pretty
sure) this will require a format change in
Jean-Marc Lasgouttes wrote:
"Dov" == Dov Feldstern
writes:
Dov> Do you know why this whole font-change mechanism was originally
Dov> added?
Consider a footnote with several paragraphs and assume it is typeset
in \emph like this:
\emph{Some text\footnote{and and explana
Jürgen Spitzmüller wrote:
Michael Gerz wrote:
there are three more patches which may be subject to discussion:
[patch] bug 1820 --- footnotes in different language (by Dov)
As I just posted in a separate message, it turns out that (I'm pretty
sure) this will require a format change in
Dov Feldstern wrote:
Dov Feldstern wrote:
So, to sum up: the patch attached at
http://permalink.gmane.org/gmane.editors.lyx.devel/89376 together with
the patch attached here solve bug 1820 completely.
Index: src/insets
Dov Feldstern wrote:
Dov Feldstern wrote:
So, to sum up: the patch attached at
http://permalink.gmane.org/gmane.editors.lyx.devel/89376 together with
the patch attached here solve bug 1820 completely.
Index: src/insets
José Matos wrote:
On Monday 09 July 2007 09:50:27 Abdelrazak Younes wrote:
I guess the problem is that nobody understands this bidi stuff like
you do. I would tend to say go ahead!, but I am not sure what are my
credentials to do so :)
Same position for me. The patch looks not so complicate so
Dov Feldstern wrote:
Dov Feldstern wrote:
are attached in bugzilla (though I'm having trouble downloading
attachments from bugzilla, at the moment, anyone know anything about
this?)
Dov
I was able to download the attachments from bugzilla now, and I see
there's one case which still isn't
José Matos wrote:
On Monday 09 July 2007 09:50:27 Abdelrazak Younes wrote:
I guess the problem is that nobody understands this bidi stuff like
you do. I would tend to say "go ahead!", but I am not sure what are my
credentials to do so :)
Same position for me. The patch looks not so complicate
Dov Feldstern wrote:
Dov Feldstern wrote:
are attached in bugzilla (though I'm having trouble downloading
attachments from bugzilla, at the moment, anyone know anything about
this?)
Dov
I was able to download the attachments from bugzilla now, and I see
there's one case which still isn't
Dov Feldstern wrote:
José Matos wrote:
On Thursday 28 June 2007 21:00:28 Dov Feldstern wrote:
I haven't gotten any further comments regarding this patch. Is it OK to
go in?
Are you sure it is safe?
Could have the opinion of other RTL users?
Would anyone like the patch attached at
http
Hi!
Attached find a patch for bug 1820, which has resisted solution for a
long time. After a lot of work done by others to tidy up the
output_latex code in the past few months, the infrastructure was now in
place so that finally we can provide a solution. It would be good if
this could still
Dov Feldstern wrote:
are attached in bugzilla (though I'm having trouble downloading
attachments from bugzilla, at the moment, anyone know anything about this?)
Dov
I was able to download the attachments from bugzilla now, and I see
there's one case which still isn't solved. I'll try
Dov Feldstern wrote:
José Matos wrote:
On Thursday 28 June 2007 21:00:28 Dov Feldstern wrote:
I haven't gotten any further comments regarding this patch. Is it OK to
go in?
Are you sure it is safe?
Could have the opinion of other RTL users?
Would anyone like the patch attached at
http
Hi!
Attached find a patch for bug 1820, which has resisted solution for a
long time. After a lot of work done by others to tidy up the
output_latex code in the past few months, the infrastructure was now in
place so that finally we can provide a solution. It would be good if
this could still
Dov Feldstern wrote:
are attached in bugzilla (though I'm having trouble downloading
attachments from bugzilla, at the moment, anyone know anything about this?)
Dov
I was able to download the attachments from bugzilla now, and I see
there's one case which still isn't solved. I'll try
Abdelrazak Younes wrote:
Jean-Marc Lasgouttes wrote:
Dov Therefore, attached is the original patch, with a comment
Dov explaining the situation. OK to commit?
OK with me.
me too.
Abdel.
Thanks, guys. Committed as r18993.
I still need another OK for the default encoding patch (attached
Abdelrazak Younes wrote:
Dov Feldstern wrote:
I still need another OK for the default encoding patch (attached in
http://permalink.gmane.org/gmane.editors.lyx.devel/89143), which I
think is important for 1.5.0. Could anyone please take a look?
If Georg has given his OK I think you can go
Abdelrazak Younes wrote:
Jean-Marc Lasgouttes wrote:
Dov> Therefore, attached is the original patch, with a comment
Dov> explaining the situation. OK to commit?
OK with me.
me too.
Abdel.
Thanks, guys. Committed as r18993.
I still need another OK for the "default" encoding patch
Abdelrazak Younes wrote:
Dov Feldstern wrote:
I still need another OK for the "default" encoding patch (attached in
http://permalink.gmane.org/gmane.editors.lyx.devel/89143), which I
think is important for 1.5.0. Could anyone please take a look?
If Georg has given his OK I think
Hi!
Attached find the (I hope) final version of this patch. I addressed all
of the issues which Georg pointed out (Georg, please make sure), and
tested this again.
I think that this should go in for 1.5.0 if possible, so if I get
another OK (I'm assuming Georg's unless I hear otherwise)
Jean-Marc Lasgouttes wrote:
Dov == Dov Feldstern dfeldstern-rhxOsnTko2JWk0Htik3J/[EMAIL PROTECTED]
writes:
Dov I think that I'll try to create a constructor which accepts a
Dov font to be used as the initial font. Does this sound all right?
That may turn out to be complicated. Do you really
Hi!
Attached find the (I hope) final version of this patch. I addressed all
of the issues which Georg pointed out (Georg, please make sure), and
tested this again.
I think that this should go in for 1.5.0 if possible, so if I get
another OK (I'm assuming Georg's unless I hear otherwise)
Jean-Marc Lasgouttes wrote:
"Dov" == Dov Feldstern
writes:
Dov> I think that I'll try to create a constructor which accepts a
Dov> font to be used as the initial font. Does this sound all right?
That may turn out to be complicated. Do you really need to set the
font in
Georg Baum wrote:
Dov Feldstern wrote:
Index: lyx-devel/src/output_latex.cpp
===
--- lyx-devel.orig/src/output_latex.cpp2007-06-29
16:02:45.0 +0300
+++ lyx-devel/src/output_latex.cpp2007-07-01 20:52
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Or you could just replace the two attached files in your tree.
Sorry, those won't compile, try these instead.
Abdel.
Abdel, the attached files seem to be working just fine for me, I don't
see anything wrong with the RTL. Is there anything
Uwe Stöhr wrote:
Dov Feldstern schrieb:
Concerning the page: I would not mention the bind file because this
is unnecessary. New users will be scared about every preferences
fiddling. We don't use special bind files for the other languages,
and when the user is experianced enough, he can
Uwe Stöhr wrote:
First, sorry for the delay. This mail never reached me, I found it by
chance in the mail-archive.
All of the problems you're describing are because you haven't
performed the one-time setup
required for Arabtex, see
http://permalink.gmane.org/gmane.editors.lyx.devel/88100
Hi!
[Don't worry, this is for post-1.5.0]
A few times in the past month or two, the issue of whether or not
keymaps should be used has come up. I would like to defend the position
which says: yes, keymaps are good! and suggest an improvement in how
they're used.
Let me just start out by
Hi!
We would like to add some keybindings for switching languages for Hebrew
and Arabic, but I'm not sure where in the tree they belong, so that they
will be automatically used (based on the locale?). Also, will the
inclusion of cua.bind work correctly (I know it works when I do it in my
lyx
Jean-Marc Lasgouttes wrote:
Dov == Dov Feldstern dfeldstern-rhxOsnTko2JWk0Htik3J/[EMAIL PROTECTED]
writes:
Dov Hi! Attached find a patch fixing
Dov http://bugzilla.lyx.org/show_bug.cgi?id=3959 (which I just opened
Dov tonight).
Dov Please note that there appears to have been an attempt
Georg Baum wrote:
Dov Feldstern wrote:
Index: lyx-devel/src/output_latex.cpp
===
--- lyx-devel.orig/src/output_latex.cpp2007-06-29
16:02:45.0 +0300
+++ lyx-devel/src/output_latex.cpp2007-07-01 20:52
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Or you could just replace the two attached files in your tree.
Sorry, those won't compile, try these instead.
Abdel.
Abdel, the attached files seem to be working just fine for me, I don't
see anything wrong with the RTL. Is there anything
Uwe Stöhr wrote:
Dov Feldstern schrieb:
Concerning the page: I would not mention the bind file because this
is unnecessary. New users will be scared about every preferences
fiddling. We don't use special bind files for the other languages,
and when the user is experianced enough, he can
Uwe Stöhr wrote:
First, sorry for the delay. This mail never reached me, I found it by
chance in the mail-archive.
> All of the problems you're describing are because you haven't
performed the one-time setup
> required for Arabtex, see
Hi!
[Don't worry, this is for post-1.5.0]
A few times in the past month or two, the issue of whether or not
keymaps should be used has come up. I would like to defend the position
which says: yes, keymaps are good! and suggest an improvement in how
they're used.
Let me just start out by
Hi!
We would like to add some keybindings for switching languages for Hebrew
and Arabic, but I'm not sure where in the tree they belong, so that they
will be automatically used (based on the locale?). Also, will the
inclusion of cua.bind work correctly (I know it works when I do it in my
lyx
Jean-Marc Lasgouttes wrote:
"Dov" == Dov Feldstern
writes:
Dov> Hi! Attached find a patch fixing
Dov> http://bugzilla.lyx.org/show_bug.cgi?id=3959 (which I just opened
Dov> tonight).
Dov> Please note that there appears to have been an attempt to
Dov> explicitly do
Georg Baum wrote:
Am Samstag, 30. Juni 2007 22:10 schrieb Dov Feldstern:
That would put knowledge about the switchEncoding internals into the
caller. That is dangerous, because the internals might change. I would
prefer to be explicit: Let switchEncoding return a std::pairbool, int.
The bool
Hi!
Attached find a patch fixing
http://bugzilla.lyx.org/show_bug.cgi?id=3959 (which I just opened tonight).
Please note that there appears to have been an attempt to explicitly do
the opposite of what I'm trying to do here, though for different
reasons, I think: r10808, which fixed bug
Georg Baum wrote:
Am Samstag, 30. Juni 2007 22:10 schrieb Dov Feldstern:
That would put knowledge about the switchEncoding internals into the
caller. That is dangerous, because the internals might change. I would
prefer to be explicit: Let switchEncoding return a std::pair<bool,
Hi!
Attached find a patch fixing
http://bugzilla.lyx.org/show_bug.cgi?id=3959 (which I just opened tonight).
Please note that there appears to have been an attempt to explicitly do
the opposite of what I'm trying to do here, though for different
reasons, I think: r10808, which fixed bug
GoogleGuy wrote:
On Fri, 29 Jun 2007 17:54:40 +0300
Dov Feldstern dfeldstern-rhxOsnTko2JWk0Htik3J/[EMAIL PROTECTED] wrote:
Sorry, I didn't explain myself clearly. I already committed a fix for
a *different* keymap bug a few weeks ago, and I thought that that fix
was causing your problem
Andre Poenitz wrote:
On Fri, Jun 29, 2007 at 11:17:51AM +0300, Dov Feldstern wrote:
Right now it's being called on every cursor blink, I think (I put in a
debug printout, and it prints on every blink); and what it's doing every
time is to loop over all the characters from the beginning
Georg Baum wrote:
Am Freitag, 29. Juni 2007 15:11 schrieb Dov Feldstern:
Just a reminder: default is supposed to be exactly like auto (i.e.,
the encoding is determined based on the language), except that it
shouldn't output any inputencoding commands, because LaTeX will
determine
Richard Heck wrote:
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) {
GoogleGuy wrote:
On Fri, 29 Jun 2007 17:54:40 +0300
Dov Feldstern wrote:
Sorry, I didn't explain myself clearly. I already committed a fix for
a *different* keymap bug a few weeks ago, and I thought that that fix
was causing your problem. But now I don't think that it's my fix
that's causing
Andre Poenitz wrote:
On Fri, Jun 29, 2007 at 11:17:51AM +0300, Dov Feldstern wrote:
Right now it's being called on every cursor blink, I think (I put in a
debug printout, and it prints on every blink); and what it's doing every
time is to loop over all the characters from the beginning
Georg Baum wrote:
Am Freitag, 29. Juni 2007 15:11 schrieb Dov Feldstern:
Just a reminder: "default" is supposed to be exactly like "auto" (i.e.,
the encoding is determined based on the language), except that it
shouldn't output any "inputencoding" commands,
Richard Heck wrote:
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")
Uwe Stöhr wrote:
Concerning the page: I would not mention the bind file because this is
unnecessary. New users will be scared about every preferences fiddling.
We don't use special bind files for the other languages, and when the
user is experianced enough, he can create any time later its own
Abdelrazak Younes wrote:
Dov Feldstern wrote:
We would also have to decide where the correct place for this cache is
(TextMetrics?);
Cursor seems like the ideal place for that.
should caching occur for the entire paragraph (or even
document), or just for the line which the cursor
Jean-Marc Lasgouttes wrote:
Dov == Dov Feldstern dfeldstern-rhxOsnTko2JWk0Htik3J/[EMAIL PROTECTED]
writes:
Dov Right now it's being called on every cursor blink, I think (I put
Dov in a debug printout, and it prints on every blink); and what it's
Dov doing every time is to loop over all
Jean-Marc Lasgouttes wrote:
Dov == Dov Feldstern [EMAIL PROTECTED] writes:
Dov Perhaps, I don't know. But note that the main incentive here is
Dov not the optimization, but the cleaning up of the code. Right now
Dov we have almost identical code in two different places. That's why
Dov
Hi!
Attached find a patch which fixes some problems that existed with the
default encoding. Georg and I discussed some of these a few months
back, but nothing ever came of it then. Now this patch seems to fix all
of the problems that I have with default encoding.
The attached files are two
GoogleGuy wrote:
Hi All,
I just compiled LyX 1.5.0rc2 from source, and ran into a keyboard map
problem.
(I'm using primary and secondary keyboard maps extensively, rather than
XKB, because this way LyX shortcuts work no matter the layout, and
this, I think, is one of LyX's biggest strengths.)
601 - 700 of 1478 matches
Mail list logo
