Dov Feldstern wrote:
Abdelrazak Younes wrote:
This is not only about the bidi algorithm but also about unicode.
Right now, everything about RTL is based on the assumption that
encodings matters for the display. It does not.
I don't understand what you mean --- can you be more specific? What
Abdelrazak Younes wrote:
This is not only about the bidi algorithm but also about unicode. Right
now, everything about RTL is based on the assumption that encodings
matters for the display. It does not.
I don't understand what you mean --- can you be more specific? What in
RTL is based on th
Guy Rutenberg wrote:
Hi,
Dov mentioned that LyX bidi algorithm did a good job at previous versions,
and I agree with it. If Lyx bidi algroithm is indeed spread all over the
place, I think we will be better off disabling Qt bidi algorithm (if it's
possible). I think it won't require much additiona
Hi,
Dov mentioned that LyX bidi algorithm did a good job at previous versions,
and I agree with it. If Lyx bidi algroithm is indeed spread all over the
place, I think we will be better off disabling Qt bidi algorithm (if it's
possible). I think it won't require much additional code as disabling th
Dov Feldstern wrote:
Abdel, I know that you agree with Guy on this one, so maybe you guys are
right... And it's true that for Arabic, letting Qt deal with everything
will probably simplify things a lot... However, it sounds like a really
big job to me, and I think that the alternative would wo
Am Mittwoch, 10. Januar 2007 22:08 schrieb Dov Feldstern:
> *) Apparently Qt still isn't working perfectly, either --- why is it so
> dependent on the locale settings? It seems to me that the locale setting
> should not affect whether or not bidi is applied.
I believe that _we_ are causing qt to
Guy Rutenberg wrote:
Hi,
Further more when typing hebrew when LC_CTYPE is configured to a valid
value, and not setting the text as "language hebrew" in LyX (that causes
lyx
to treat the Hebrew as English or the default language) the hebrew text is
displayed right,
Totally correct? Or just t
Hi,
I did further testing on the issue and found out that the problem occurs
only when the locale that is set in LC_CTYPE (directly or via LANG) is a
valid locale.
For example the display of Hebrew will be wrong if LC_CTYPE is set to en_US
but it will be correct when set to he, en, he_US or any o
Hi,
The faulty environment variable is LC_CTYPE. when setting this
variable (either directly or by setting the LANG) LyX doesn't handle
hebrew text correctly.
Do someone now when lyx looks at the LC_CTYPE and what effect it has
when it's set in LyX?
Regards,
Guy
On 1/4/07, Guy Rutenberg <[EM
Hi,
I can confirm that the bug is related to the environment variable, and
especially the ones that relate to the locale settings.
I couldn't solve the problem with only unsetting the LANG but I solved it
when I unset all the locale related variables. As this is not a nice
solution I will try to f
On Saturday 30 December 2006 21:34, Dov Feldstern wrote:
> See my reply from yesterday to Abdel, where I point to a test file, as
> well as screenshots of correct and incorrect display --- do you see it
> correctly or incorrectly?
I have currently no working LyX to test with, so this will have to
Georg Baum wrote:
On Friday 29 December 2006 00:39, Dov Feldstern wrote:
Is there anyone else out there testing 1.5.0svn with any BiDi language?
I can not input anything (because I don't know how to set that up), but I can
load existing files and compare with the generated DVI output. I do
Dov Feldstern wrote:
Does anyone else have any ideas as to what might be causing these
weird problems?
Is there anyone else out there testing 1.5.0svn with any BiDi language?
I'd like to test it but I don't know if I can install any RTL language
keyboard support on my WinXP laptop :-(
A
On Friday 29 December 2006 00:39, Dov Feldstern wrote:
> Hi!
>
> I don't know what to say, it's working for me even after setting the
> locales that you sent.
>
> Could it have to do with the screen-fonts? Perhaps True-type fonts (I
> don't know if that's what you're using) have a built-in BiDi alg
Does anyone else have any ideas as to what might be causing these
weird problems?
Is there anyone else out there testing 1.5.0svn with any BiDi language?
I'd like to test it but I don't know if I can install any RTL language
keyboard support on my WinXP laptop :-(
Abdel.
Hi Abdel!
I
Dov Feldstern wrote:
Hi!
I don't know what to say, it's working for me even after setting the
locales that you sent.
Could it have to do with the screen-fonts? Perhaps True-type fonts (I
don't know if that's what you're using) have a built-in BiDi algorithm
or something? I'm using the culmu
Hi!
I don't know what to say, it's working for me even after setting the
locales that you sent.
Could it have to do with the screen-fonts? Perhaps True-type fonts (I
don't know if that's what you're using) have a built-in BiDi algorithm
or something? I'm using the culmus fonts, maybe you sho
On Friday 22 December 2006 13:59, Georg Baum wrote:
> Anyway, here is a patch that gets rid of the encoding list in the
> preferences dialog. It also adds some other encodings I found in my tetex
> installation. Do we still miss some (I know, arabic is missing)?
I installed texlive and added all e
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> On Sunday 24 December 2006 01:02, Dov Feldstern wrote:
>> Okay, this is the issue: if a paragraph's language is Hebrew, then
>> the encoding is identified correctly using "use language's default
>> encoding". However, if the paragraph'
On Sunday 24 December 2006 01:02, Dov Feldstern wrote:
> Okay, this is the issue: if a paragraph's language is Hebrew, then the
> encoding is identified correctly using "use language's default
> encoding". However, if the paragraph's language is English, but you have
> some Hebrew words in it, the
Well, first of all I wasn't able to open the file, because its lyxformat
version is 255, and I'm currently using lyxformat version 256. This is
due to Georg's patch (in this thread, from Dec. 22 at 14:59) which
solves the problem of the hardcoded list of encodings. I don't know if
that patch ma
Hi,
1) I'm using Gentoo Linux
2) yes, I do svn update every time I begin testing lyx. I also did svn
update couple of minutes before creating the example file.
3) tried that, didn't effect anything. I'm starting lyx with the -userdir
flag set to ~/.lyx-1.5 so it won't mess with the older lyx insta
Hi!
This is strange, because I don't see the problems you're describing (in
bug #3040).
1) What OS are you working in? (I'm in Linux)
2) Have you recompiled the latest version from svn?
3) You might want to try removing the .lyx directory (or whatever the
equivalent on Windows is) --- I've fo
Hi,
I tried Dov's fix for the problem, but unfortunately it doesn't work for me.
The output is still correct (as it used to) but the display in the UI is
still wrong. I opened yesterday a bug report with detailed explanation with
what is wrong in the hebrew display in the UI.
I Hope it will get f
Dov Feldstern wrote:
Georg Baum wrote:
Am Freitag, 22. Dezember 2006 12:14 schrieb Dov Feldstern:
3) There's probably a better way than having to manually change the
encoding to cp1255. There's probably some way to automatically
associate the language with the encoding (I thought that's wha
Georg Baum wrote:
Am Freitag, 22. Dezember 2006 12:14 schrieb Dov Feldstern:
Anyway, here is a patch that gets rid of the encoding list in the
preferences dialog. It also adds some other encodings I found in my tetex
installation. Do we still miss some (I know, arabic is missing)?
If nobody
Dov Feldstern wrote:
(although with the latest build I'm having trouble with the
keyboard focus, so doing this from the minibuffer only takes effect if I
first type something, then select it and then call the command; using
the binding it still works as normal, however...).
The focus problem
Georg Baum wrote:
Am Freitag, 22. Dezember 2006 12:14 schrieb Dov Feldstern:
3) There's probably a better way than having to manually change the
encoding to cp1255. There's probably some way to automatically associate
the language with the encoding (I thought that's what "use language's
defa
Abdelrazak Younes wrote:
Dov Feldstern wrote:
2) In order to type in Hebrew, you need to do *two* things:
a) change the language (F12, if you're using Dekel's bindings for
Hebrew)
How do I change the language if I don't use Dekel's bindings? Where are
those binding by the way and coul
Dov Feldstern wrote:
Hi!
I've been following this issue and playing around with it for a while
now, and I think the problem may not be as bad as we think --- I don't
think any major rewriting is necessary.
Here's how I'm able to get bidi (Hebrew) at least basically working (I
just tried it
Georg Baum wrote:
Am Freitag, 22. Dezember 2006 13:49 schrieb Abdelrazak Younes:
Here is it attached together with cp1255 and cp1257, just in case.
You misunderstood me, I wanted to know where one can get these files. Which
TeX distributions include them?
Miktex 2.5 has them (if you instal
Am Freitag, 22. Dezember 2006 13:49 schrieb Abdelrazak Younes:
> Here is it attached together with cp1255 and cp1257, just in case.
You misunderstood me, I wanted to know where one can get these files. Which
TeX distributions include them? Are there places where one can download
them?
Georg
Am Freitag, 22. Dezember 2006 12:14 schrieb Dov Feldstern:
> 3) There's probably a better way than having to manually change the
> encoding to cp1255. There's probably some way to automatically associate
> the language with the encoding (I thought that's what "use language's
> default encoding"
Georg Baum wrote:
Am Freitag, 22. Dezember 2006 13:34 schrieb Abdelrazak Younes:
Georg, I see in http://bugzilla.lyx.org/show_bug.cgi?id=2927 that you
recommend to add cp1256 encoding for Arabic. Is it OK if I put this
patch in with the following change or is there more to it?
+ "koi8-
Am Freitag, 22. Dezember 2006 13:34 schrieb Abdelrazak Younes:
> Georg, I see in http://bugzilla.lyx.org/show_bug.cgi?id=2927 that you
> recommend to add cp1256 encoding for Arabic. Is it OK if I put this
> patch in with the following change or is there more to it?
>
> + "koi8-r", "koi8-u",
Dov Feldstern wrote:
Index: src/frontends/qt4/QDocumentDialog.C
===
--- src/frontends/qt4/QDocumentDialog.C (revision 16375)
+++ src/frontends/qt4/QDocumentDialog.C (working copy)
@@ -62,7 +62,7 @@
// the available encodings in src/
Hi!
I've been following this issue and playing around with it for a while
now, and I think the problem may not be as bad as we think --- I don't
think any major rewriting is necessary.
Here's how I'm able to get bidi (Hebrew) at least basically working (I
just tried it now on r16375):
(Not
Guy Rutenberg wrote:
It doesn't work well with unicode, my guess is that it will have to be
rewritten.
Hello Guy,
Some time ago, one other developer (Hossein Noorikhah, interested in
Farsi IIRC) was also interested in fixing RTL support. We end-up with
the exact same conclusion as for the re
It doesn't work well with unicode, my guess is that it will have to be
rewritten.
Guy
On 12/21/06, Martin Vermeer <[EMAIL PROTECTED]> wrote:
On Thu, 2006-12-21 at 11:45 +0200, Guy Rutenberg wrote:
> Hi,
>
> I'm testing Lyx 1.5 svn, and specifically interested in the bidi
support.
> Lyx 1.5 has
On Thu, 2006-12-21 at 11:45 +0200, Guy Rutenberg wrote:
> Hi,
>
> I'm testing Lyx 1.5 svn, and specifically interested in the bidi support.
> Lyx 1.5 has a regression in the bidi support compared to lyx 1.4. I would
> like to help fix this problem, but I can't understand how Lyx determines
> when
Hi,
I'm testing Lyx 1.5 svn, and specifically interested in the bidi support.
Lyx 1.5 has a regression in the bidi support compared to lyx 1.4. I would
like to help fix this problem, but I can't understand how Lyx determines
when a paragraph should be RTL and when it should be LTR. If someone wou
41 matches
Mail list logo
