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 should try those?

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?

Dov

Guy Rutenberg wrote:
Hi,

I rechecked out the source and applied the patch. I noticed few things:
1) when I set the language of the document to english but type hebrew (without changing the language in lyx) the hebrew text is aligned left but otherwise it's displayed correct. 2)when in the last example I mark the hebrew text and in the command buffer do "language hebrew" the hebrew text is aligned correctly but displayed in reverse order (like I described in bug #3040. 3) When I set the document language to hebrew then the hebrew text is always aligned correctly but it's displayed wrong.

I attached a screenshot of the file that I attached to the bug report (after changing the 255 to 256 in the file)

Maybe it is concerend with the locales?
here is my locales
LANG=en_US.UTF-8
LC_CTYPE=he_IL.UTF-8
LC_NUMERIC=he_IL.UTF-8
LC_TIME=he_IL.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=he_IL.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=he_IL.UTF-8
LC_NAME=he_IL.UTF-8
LC_ADDRESS=he_IL.UTF-8
LC_TELEPHONE=he_IL.UTF-8
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION=he_IL.UTF-8

maybe the fault is with my locales. I will change them and tell you if it helped

Best Regards,
Guy


Dov Feldstern <[EMAIL PROTECTED]> writes:

 >
 > 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 makes a difference in terms of the result, but you should try
 > to apply it and see if that helps. Anyhow, in order to test the file I
 > just changed the 255 to 256 in the file, and then it opened correctly,
 > and the Hebrew was fine (see attached screenshot). So as a first stage I
 > would definitely try applying Georg's patch, and see if that helps.
 > Also, is it possible that you have any of your own code in the tree ---
 > perhaps from trying to fix this yourself at some point -- which may be
 > affecting the outcome? Maybe even a Qt flag somewhere which is RTL/LTR?
 >
 > BTW, I'm using debian unstable.
 >
 > Guy Rutenberg wrote:
 > > 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 installation.
 > >
> > I have attached a small LyX file the shows the bug that I'm talking about. > > By the way, I noticed when creating the example that the punctuation marks > > are in the right place. So the ony problem is with the letters themselves.
 > >
 > > Thanks for your help,
 > > Guy
 > >
 > > Dov Feldstern wrote:
 > >
 > > 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 found in the past that sometimes the
 > >> old configuration made all kinds of weird things happened which turned
 > >> out to work just fine when I started with a clean configuration.
 > >>
> >> Perhaps if none of this helps, you could either send to the list or else > >> attach to the bug report a small LyX file with some Hebrew, and I'll try
 > >> opening it at my end and see if it looks okay here?
 > >>
 > >> Good luck!
 > >> Dov
 > >>
 > >
 >
 >
 >




------------------------------------------------------------------------


Reply via email to