Dov Feldstern wrote:
1) First of all, the Arabic was coming out backwards at first. To fix
that, I applied the attached patch. I really just guessed that that's
what had to be fixed, and it did in fact work --- but I didn't try to
understand what it is, and I would feel better about it if
Georg Baum wrote:
Dov Feldstern wrote:
2) You can't see it in the screenshot, but the cursor is not positioned
correctly once the Arabic appears (I guess it's getting the wrong
metrics for the Arabic characters). So that'll have to be fixed. What's
strange to me is that it must be getting it
Abdelrazak Younes wrote:
Georg Baum wrote:
Dov Feldstern wrote:
2) You can't see it in the screenshot, but the cursor is not positioned
correctly once the Arabic appears (I guess it's getting the wrong
metrics for the Arabic characters). So that'll have to be fixed. What's
strange to me is
Georg Baum wrote:
Abdelrazak Younes wrote:
Georg Baum wrote:
Dov Feldstern wrote:
2) You can't see it in the screenshot, but the cursor is not positioned
correctly once the Arabic appears (I guess it's getting the wrong
metrics for the Arabic characters). So that'll have to be fixed. What's
Dov Feldstern wrote:
> 1) First of all, the Arabic was coming out backwards at first. To fix
> that, I applied the attached patch. I really just guessed that that's
> what had to be fixed, and it did in fact work --- but I didn't try to
> understand what it is, and I would feel better about it if
Georg Baum wrote:
Dov Feldstern wrote:
2) You can't see it in the screenshot, but the cursor is not positioned
correctly once the Arabic appears (I guess it's getting the wrong
metrics for the Arabic characters). So that'll have to be fixed. What's
strange to me is that it must be getting it
Abdelrazak Younes wrote:
> Georg Baum wrote:
>> Dov Feldstern wrote:
>>> 2) You can't see it in the screenshot, but the cursor is not positioned
>>> correctly once the Arabic appears (I guess it's getting the wrong
>>> metrics for the Arabic characters). So that'll have to be fixed. What's
>>>
Georg Baum wrote:
Abdelrazak Younes wrote:
Georg Baum wrote:
Dov Feldstern wrote:
2) You can't see it in the screenshot, but the cursor is not positioned
correctly once the Arabic appears (I guess it's getting the wrong
metrics for the Arabic characters). So that'll have to be fixed. What's
I forgot something in the instructions for typing Arabic:
While typing in the Arabic, you also have to switch the LyX-language to
Arabic. This can either be done with a key binding, as Dekel's
instructions show; or by just typing language arabic in the minibuffer
(although for some reason I
I forgot something in the instructions for typing Arabic:
While typing in the Arabic, you also have to switch the LyX-language to
Arabic. This can either be done with a key binding, as Dekel's
instructions show; or by just typing "language arabic" in the minibuffer
(although for some reason I
On Thursday 10 July 2003 2:59 pm, Jean-Marc Lasgouttes wrote:
Andre == Andre Poenitz [EMAIL PROTECTED] writes:
Andre Because the '%' will make TeX ignore the rest of the line
Andre _including_ the newline at the end. So, %\n is invisible to
Andre TeX's stomach. A \n alone, however, would be
On Thursday 10 July 2003 2:59 pm, Jean-Marc Lasgouttes wrote:
> > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
> Andre> Because the '%' will make TeX ignore the rest of the line
> Andre> _including_ the newline at the end. So, %\n is invisible to
> Andre> TeX's stomach. A \n alone,
First, I want to apologize for the long delay. Actually, I had a car accident
but praise be to God I am OK.
Second, as you guessed, if I changed the .tex file to look like this,
\begin{document}
hi
\begin{arabtext}
\begin{center}%
\end{center}
\end{arabtext}
\end{document}
I still get some
Andre == Andre Poenitz [EMAIL PROTECTED] writes:
However, I still wonder how come you can add a % and a newline
without breaking out something whereas adding a newline alone will
break out too much!!!
Andre Because the '%' will make TeX ignore the rest of the line
Andre _including_ the
First, I want to apologize for the long delay. Actually, I had a car accident
but praise be to God I am OK.
Second, as you guessed, if I changed the .tex file to look like this,
\begin{document}
hi
\begin{arabtext}
\begin{center}أهلا%
\end{center}
\end{arabtext}
\end{document}
I still get
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>> However, I still wonder how come you can add a % and a newline
>> without breaking out something whereas adding a newline alone will
>> break out too much!!!
Andre> Because the '%' will make TeX ignore the rest of the line
Andre>
On Thu, Jul 03, 2003 at 07:12:53AM +0300, Munzir Taha Obeid wrote:
really simple way out...
It works!
I am not sure why a percent sign not a space but it _almost_ work.
If I understand you properly, I made a small file in lyx and exported it to
TeX. I edited the file by adding the percent
On Thu, Jul 03, 2003 at 07:12:53AM +0300, Munzir Taha Obeid wrote:
> > really simple way out...
> It works!
> I am not sure why a percent sign not a space but it _almost_ work.
> If I understand you properly, I made a small file in lyx and exported it to
> TeX. I edited the file by adding the
On Monday 30 June 2003 7:42 pm, Jean-Marc Lasgouttes wrote:
The problem is that this package implements something which is not
really latex, but a subset of latex. For example, I may want to write
te\TeX (name of a famous distribution). I arabic context, this is
forbidden, and I shall write te
On Wed, Jul 02, 2003 at 01:14:11PM +0300, Munzir Taha Obeid wrote:
Yeah! I understand the problem now. But can I argue that if we exclude some
odd situations like te\TeX,..., it's considered good output to have
formatting tags like center,... to be in a newline.
It is _really_ hard to get
On Wed, Jul 02, 2003 at 05:39:23PM +0200, Jean-Marc Lasgouttes wrote:
Andre == Andre Poenitz [EMAIL PROTECTED] writes:
Andre What does arabtex do if it encounters
Andre asdasd some text%
Andre\end{...}
Andre Such a thing (the %) could be added without breaking too
Andre == Andre Poenitz [EMAIL PROTECTED] writes:
Andre What does arabtex do if it encounters
Andre asdasd some text%
Andre \end{...}
Andre Such a thing (the %) could be added without breaking too much.
arabtex will not see the break, since TeX eats it, I think.
JMarc
On Wednesday 02 July 2003 6:44 pm, Andre Poenitz wrote:
On Wed, Jul 02, 2003 at 05:39:23PM +0200, Jean-Marc Lasgouttes wrote:
Andre == Andre Poenitz [EMAIL PROTECTED] writes:
Andre What does arabtex do if it encounters
Andre asdasd some text%
Andre \end{...}
Andre
On Monday 30 June 2003 7:42 pm, Jean-Marc Lasgouttes wrote:
> The problem is that this package implements something which is not
> really latex, but a subset of latex. For example, I may want to write
> te\TeX (name of a famous distribution). I arabic context, this is
> forbidden, and I shall
On Wed, Jul 02, 2003 at 01:14:11PM +0300, Munzir Taha Obeid wrote:
> Yeah! I understand the problem now. But can I argue that if we exclude some
> odd situations like te\TeX,..., it's considered good output to have
> formatting tags like center,... to be in a newline.
It is _really_ hard to get
On Wed, Jul 02, 2003 at 05:39:23PM +0200, Jean-Marc Lasgouttes wrote:
> > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> Andre> What does arabtex do if it encounters
>
> Andre> asdasd some text%
> Andre>\end{...}
>
> Andre> Such a thing (the %) could be added
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> What does arabtex do if it encounters
Andre> asdasd some text%
Andre> \end{...}
Andre> Such a thing (the %) could be added without breaking too much.
arabtex will not see the break, since TeX eats it, I think.
JMarc
On Wednesday 02 July 2003 6:44 pm, Andre Poenitz wrote:
> On Wed, Jul 02, 2003 at 05:39:23PM +0200, Jean-Marc Lasgouttes wrote:
> > > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
> >
> > Andre> What does arabtex do if it encounters
> >
> > Andre> asdasd some text%
> > Andre>
Munzir == Munzir Taha Obeid [EMAIL PROTECTED] writes:
Munzir I don't know why the first patch to ChangeLog failed but I
Munzir think I can ignore it safely, right?
Right. The patch failed because there have been changes in the file
since the 1.3.2 release.
Munzir QError.lo make[5]: *** No rule
> "Munzir" == Munzir Taha Obeid <[EMAIL PROTECTED]> writes:
Munzir> I don't know why the first patch to ChangeLog failed but I
Munzir> think I can ignore it safely, right?
Right. The patch failed because there have been changes in the file
since the 1.3.2 release.
Munzir> QError.lo make[5]:
On Friday 27 June 2003 12:28 pm, Jean-Marc Lasgouttes wrote:
Munzir == Munzir Taha Obeid [EMAIL PROTECTED] writes:
OK, it would be easier to grab lyx-1.3.2.tar.gz from
ftp.lyx.org/pub/lyx/stable/ and apply the patch to that.
Ok, I downloaded the lyx-1.3.2.tar.bz2, extracted it, copied
On Friday 27 June 2003 12:28 pm, Jean-Marc Lasgouttes wrote:
> > "Munzir" == Munzir Taha Obeid <[EMAIL PROTECTED]> writes:
> OK, it would be easier to grab lyx-1.3.2.tar.gz from
> ftp.lyx.org/pub/lyx/stable/ and apply the patch to that.
Ok, I downloaded the lyx-1.3.2.tar.bz2, extracted it,
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:
Juergen Many thanks! Two questions (without testing): - os
Juergen subst(lyxrc.language_command_begin, + os '\n' +
Juergen subst(lyxrc.language_command_begin,
Juergen is this needed? I thought \begin{lang} was always set
Juergen
Munzir == Munzir Taha Obeid [EMAIL PROTECTED] writes:
Munzir I am sorry just now I knew the thread spreaded between the
Munzir devel and users mailing lists and this is why I receive part
Munzir of the messages only. I am going to forward it again to both
Munzir and try to keep an eye ;-)
OK,
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Many thanks! Two questions (without testing): - os <<
Juergen> subst(lyxrc.language_command_begin, + os << '\n' + <<
Juergen> subst(lyxrc.language_command_begin,
Juergen> is this needed? I thought \begin{lang} was
> "Munzir" == Munzir Taha Obeid <[EMAIL PROTECTED]> writes:
Munzir> I am sorry just now I knew the thread spreaded between the
Munzir> devel and users mailing lists and this is why I receive part
Munzir> of the messages only. I am going to forward it again to both
Munzir> and try to keep an
I am sorry just now I knew the thread spreaded between the devel and users
mailing lists and this is why I receive part of the messages only. I am going
to forward it again to both and try to keep an eye ;-)
On Tuesday 24 June 2003 12:56 pm, Jean-Marc Lasgouttes wrote:
Munzir, I do not know if
I am sorry just now I knew the thread spreaded between the devel and users
mailing lists and this is why I receive part of the messages only. I am going
to forward it again to both and try to keep an eye ;-)
On Tuesday 24 June 2003 12:56 pm, Jean-Marc Lasgouttes wrote:
> Munzir, I do not know
Munzir Taha Obeid wrote:
Does the problem go away if you place the \end{arabtex} on a line of its
own?
Yes, if I place the \end{arabtex} in a line of its known or if I place a
space before it, the problem goes away completely.
The attached patch adds a linebreak before \end{environment}
Munzir Taha Obeid wrote:
> > Does the problem go away if you place the \end{arabtex} on a line of its
> > own?
>
> Yes, if I place the \end{arabtex} in a line of its known or if I place a
> space before it, the problem goes away completely.
The attached patch adds a linebreak before
) without having to
use other fonts thatn latin1. Arabic and I guess also Hebrew suffers
under this.
Anyway ... _I_ am not going to do anything with the arabic support
since I cannot test it. It more information is probably needed to fix
the problem easily. When working with key-bugs always describe
The code is now setup to handle all latin (almost) without having to
use other fonts thatn latin1. Arabic and I guess also Hebrew suffers
under this.
Hey, Dekel, what say you?
Anyway ... _I_ am not going to do anything with the arabic support
since I cannot test it. It more information
I want to be able to run my English keyboard as is in most applications,
and simultaneously be able to do Arabic/Farsi/etc in LyX.
aol
me too
/aol
But I also understand it is not The Right Thing and creates a lot of
troubles for LyX...
I think the situaton is even a bit more complicated.
Kayvan A. Sylvan [EMAIL PROTECTED] writes:
| btw. I want to flag all keymaps for removal at a later date. It really
| isn't LyX's task to remap the keyboard, that is a task of the desktop.
| (And it complicates things a great deal in LyX)
|
| I don't agree with this.
|
| I want to be able
Andre Poenitz [EMAIL PROTECTED] writes:
| I want to be able to run my English keyboard as is in most applications,
| and simultaneously be able to do Arabic/Farsi/etc in LyX.
|
| aol
| me too
| /aol
|
| But I also understand it is not The Right Thing and creates a lot of
| troubles for
On Wed, May 23, 2001 at 10:20:04AM +0200, Lars Gullik Bjønnes wrote:
Kayvan A. Sylvan [EMAIL PROTECTED] writes:
| btw. I want to flag all keymaps for removal at a later date. It really
| isn't LyX's task to remap the keyboard, that is a task of the desktop.
| (And it complicates things a
Andre Poenitz wrote:
I want to be able to run my English keyboard as is in most applications,
and simultaneously be able to do Arabic/Farsi/etc in LyX.
aol
me too
/aol
But I also understand it is not The Right Thing and creates a lot of
troubles for LyX...
I think the situaton
Kayvan A. Sylvan [EMAIL PROTECTED] writes:
| Will I be able to do what I do now?
|
| Write a bit of English, write a translation in Farsi, write more
| English, etc.
| Just by pressing a key to toggle the keymap?
That is how it works in KDE at least.
--
Lgb
No, as I know, it isn't possible. The keyboard mapping
is X-Server global. Changes to it are possible with
the xmodmap client and all X-clients get an
UnmapNotify/MapNotify notify event if the keyboard
is changed.
But we could have some function within LyX to change this global X keymap
to
ll latin (almost) without having to
use other fonts thatn latin1. Arabic and I guess also Hebrew suffers
under this.
Anyway ... _I_ am not going to do anything with the arabic support
since I cannot test it. It more information is probably needed to fix
the problem easily. When working with key-bugs
>
> The code is now setup to handle all latin (almost) without having to
> use other fonts thatn latin1. Arabic and I guess also Hebrew suffers
> under this.
Hey, Dekel, what say you?
> Anyway ... _I_ am not going to do anything with the arabic support
> since I canno
> I want to be able to run my English keyboard as is in most applications,
> and simultaneously be able to do Arabic/Farsi/etc in LyX.
me too
But I also understand it is not The Right Thing and creates a lot of
troubles for LyX...
I think the situaton is even a bit more complicated.
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| > btw. I want to flag all keymaps for removal at a later date. It really
| > isn't LyX's task to remap the keyboard, that is a task of the desktop.
| > (And it complicates things a great deal in LyX)
|
| I don't agree with this.
|
| I want to be
Andre Poenitz <[EMAIL PROTECTED]> writes:
| > I want to be able to run my English keyboard as is in most applications,
| > and simultaneously be able to do Arabic/Farsi/etc in LyX.
|
|
| me too
|
|
| But I also understand it is not The Right Thing and creates a lot of
| troubles for LyX...
|
On Wed, May 23, 2001 at 10:20:04AM +0200, Lars Gullik Bjønnes wrote:
> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
>
> | > btw. I want to flag all keymaps for removal at a later date. It really
> | > isn't LyX's task to remap the keyboard, that is a task of the desktop.
> | > (And it
Andre Poenitz wrote:
>
> > I want to be able to run my English keyboard as is in most applications,
> > and simultaneously be able to do Arabic/Farsi/etc in LyX.
>
>
> me too
>
>
> But I also understand it is not The Right Thing and creates a lot of
> troubles for LyX...
>
> I think the
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| Will I be able to do what I do now?
|
| Write a bit of English, write a translation in Farsi, write more
| English, etc.
| Just by pressing a key to toggle the keymap?
That is how it works in KDE at least.
--
Lgb
> No, as I know, it isn't possible. The keyboard mapping
> is X-Server global. Changes to it are possible with
> the xmodmap client and all X-clients get an
> UnmapNotify/MapNotify notify event if the keyboard
> is changed.
But we could have some function within LyX to change this global X
Dekel Tsur [EMAIL PROTECTED] writes:
| This one I particulary do not like, this is not a LyX property but a
| language one. I think we should use Jean-Marcs suggestion and store
| rtl info in the babel struct.
|
| I don't like it either :-(
Should be now problem to remove this right away?
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars not sure about screen_font_encoding either. I think the problem
Lars is rather that we don't support several norms at the same time.
Yes, once we support this at buffer-level, we should describe the
default encoding in the language
On Mon, Feb 28, 2000 at 09:43:32AM +0100, Lars Gullik Bjnnes wrote:
| There is other language info which is currently stored in lyxrc (like
| screen_font_encoding and kbmap_primary) which shouldn't be stored
| there.
the kbmap should be there, this is not a buffer property. (I still do
On Sat, Feb 26, 2000 at 01:38:23AM +0200, Dekel Tsur wrote:
On Fri, Feb 25, 2000 at 07:59:22PM +0100, Lars Gullik Bjnnes wrote:
|The text rendering in the LyX screen doesn't use ligatures.
mmm, I have thought about this (ligatures that is) and have the
feeling that the cursor
Dekel Tsur <[EMAIL PROTECTED]> writes:
| > This one I particulary do not like, this is not a LyX property but a
| > language one. I think we should use Jean-Marcs suggestion and store
| > rtl info in the babel struct.
|
| I don't like it either :-(
Should be now problem to remove this right
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> not sure about screen_font_encoding either. I think the problem
Lars> is rather that we don't support several norms at the same time.
Yes, once we support this at buffer-level, we should describe the
default encoding in the
On Mon, Feb 28, 2000 at 09:43:32AM +0100, Lars Gullik Bjnnes wrote:
> | There is other language info which is currently stored in lyxrc (like
> | screen_font_encoding and kbmap_primary) which shouldn't be stored
> | there.
>
> the kbmap should be there, this is not a buffer property. (I still
On Sat, Feb 26, 2000 at 01:38:23AM +0200, Dekel Tsur wrote:
> On Fri, Feb 25, 2000 at 07:59:22PM +0100, Lars Gullik Bjnnes wrote:
> > |The text rendering in the LyX screen doesn't use ligatures.
> >
> > mmm, I have thought about this (ligatures that is) and have the
> > feeling that the
On Mon, Feb 21, 2000 at 08:24:24PM +0100, Lars Gullik Bjnnes wrote:
[EMAIL PROTECTED] writes:
| I have a new linux oprtingsystem software(SuSe ver. 6.3),
| this included a Lyx software. I would like to use the lyx
| editor for reading / writing arabic text
This
ebrew" being used. That does not look right to me.
Did I mention that the Arabic support is a hack?
| However, there are several limitations to this hack:
|
| 1. BIGGEST LIMITATION:
|The text rendering in the LyX screen doesn't use ligatures.
mmm, I have thought about this
On Mon, Feb 21, 2000 at 08:24:24PM +0100, Lars Gullik Bjnnes wrote:
> [EMAIL PROTECTED] writes:
>
> | I have a new linux oprtingsystem software(SuSe ver. 6.3),
> | this included a Lyx software. I would like to use the lyx
> | editor for reading / writing arabic text
>
ependant on the language
> "hebrew" being used. That does not look right to me.
Did I mention that the Arabic support is a hack?
> | However, there are several limitations to this hack:
> |
> | 1. BIGGEST LIMITATION:
> |The text rendering in the LyX screen does
70 matches
Mail list logo
