Re: [patch] fix bug 2928: make Arabic and Farsi correctly usable
Dov Feldstern schrieb: I haven't read this entire thread thoroughly yet, but you might want to see if this specific issue is related to http://bugzilla.lyx.org/show_bug.cgi?id=3555 (only relevant in mixed language documents, I think, but I'm not sure...) We don't have this problem here because the arabi-package requires the explicit setting of the language for the TOC. So the \TOCLanguage command assures that the correct encoding is used inside the TOC. regards Uwe
Re: [patch] fix bug 2928: make Arabic and Farsi correctly usable
Mostafa Vahedi schrieb:
But if you put the command "\TOCLanguage{farsi}" then
if you do not put "\selectlanguage{farsi}" as the first
command after the "\begin{document}" or in other words
as an ERT at the first line of the document then you
will receive several complains from LyX about some
undefined characters.
Wit my latest patch I just sent I can really see no difference with or without a first ERT
\selectlanguage command. Could you please check this again with my latest patch. If you still see a
difference, please tell me exactly what it is.
regards Uwe
Re: [patch] fix bug 2928: make Arabic and Farsi correctly usable
Uwe Stöhr wrote:
Mostafa Vahedi schrieb:
> See the attached patch. I implemented this but disabled it because
> \TOCLanguage gives me the error
> "unknown command". Therefore your example-lyxified doesn't compile.
The command "\TOCLanguage{}" is defined after the call to BABEL in
Latex Preamble.
This was the first I tested, but it doesn't work for me, no matter where
I call \TOCLanguage.
I haven't read this entire thread thoroughly yet, but you might want to
see if this specific issue is related to
http://bugzilla.lyx.org/show_bug.cgi?id=3555 (only relevant in mixed
language documents, I think, but I'm not sure...)
Dov
Re: [patch] fix bug 2928: make Arabic and Farsi correctly usable
Mostafa Vahedi schrieb:
OK. So which way are we going to follow? The manual one or
the other one?
The automatic one if possible.
I tested, but it doesn't work for me,
no matter where I call \TOCLanguage.
We should load the babel package this way:
"\usepackage[farsi,arabic,english]{babel}",
before using the command "\TOCLanguage{farsi}".
This command is defined in the arabic-babel files.
I did this and it doesn't work. I'll check this again later today.
I am using the windows version packaged for MiKTeX 2.5
on the date 2nd Jan 2007.
I use the same one but with MiKTeX 2.6.
regards Uwe
Re: [patch] fix bug 2928: make Arabic and Farsi correctly usable
6)(One other bug!). We should add the command
"\selectlanguage{farsi}" as an ERT as the first
line of the
document.
>>> I can see no difference. With and without the
>>> ERT command, the result is identical.
>> I checked this issue after applying the patches.
>> Still I have problem if I don't put the mentioned
>> ERT. Something is wrong!!
> What is wrong?
> What is the version number of the arabi-package
> you are using? Mine is version 1.1, December 16, 2006
I found out the problem.
First note that when you don't put the command
"\TOCLanguage{farsi}" everything is OK except
that you will see the page numbers in English.
Don't you? Moreover in this case putting the
ERT does not make any difference!
But if you put the command "\TOCLanguage{farsi}" then
if you do not put "\selectlanguage{farsi}" as the first
command after the "\begin{document}" or in other words
as an ERT at the first line of the document then you
will receive several complains from LyX about some
undefined characters.
-
Bored stiff? Loosen up...
Download and play hundreds of games for free on Yahoo! Games.
Re: [patch] fix bug 2928: make Arabic and Farsi correctly usable
>> Mostafa Vahedi schrieb:
>> I can not give any guarantee about the fix. The author
>> is extermely busy sometimes. I prefer the manual one for
>> the time being. Then if it stays more we can do something
>> about it. I have submitted many bug fixes to the author
>> and I am waiting for his reply.
> OK, but this requires a bit more work. I suggest you
> open a new bug report in bugzilla so that we can keep
> the overview.
OK. So which way are we going to follow? The manual one or
the other one?
>>> See the attached patch. I implemented this but disabled
>>> it because \TOCLanguage gives me the error "unknown
>>> command". Therefore your example-lyxified doesn't
>>> compile.
>> The command "\TOCLanguage{}" is defined after the
>> call to BABEL in Latex Preamble.
> This was the first I tested, but it doesn't work for me,
> no matter where I call \TOCLanguage.
We should load the babel package this way:
"\usepackage[farsi,arabic,english]{babel}",
before using the command "\TOCLanguage{farsi}".
This command is defined in the arabic-babel files.
>> The Arabic peopel may use other quotation marks.
>> I will check it!
> Please inform me when you found it out.
Sure.
> 6) (One other bug!). We should add the command
> "\selectlanguage{farsi}" as an ERT as the first
> line of the
> document.
>>> I can see no difference. With and without the ERT
>>> command, the result is identical.
>> I checked this issue after applying the patches.
>> Still I have problem if I don't put the mentioned
>> ERT. Something is wrong!!
> What is wrong?
> What is the version number of the arabi-package you are using? Mine is
> version
> Version 1.1, December 16, 2006
I am using the windows version packaged for MiKTeX 2.5
on the date 2nd Jan 2007.
> Does the fontenc part of my patch work for you?
Yes. Thanks.
Mostafa
-
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink Q&A.
Re: [patch] fix bug 2928: make Arabic and Farsi correctly usable
Mostafa Vahedi schrieb:
I can not give any guarantee about the fix. The author is extermely busy
sometimes. I prefer the manual one for the time being. Then if it stays
more we can do something about it. I have submitted many bug fixes to
the author and I am waiting for his reply.
OK, but this requires a bit more work. I suggest you open a new bug report in bugzilla so that we
can keep the overview.
> See the attached patch. I implemented this but disabled it because
> \TOCLanguage gives me the error
> "unknown command". Therefore your example-lyxified doesn't compile.
The command "\TOCLanguage{}" is defined after the call to BABEL in Latex
Preamble.
This was the first I tested, but it doesn't work for me, no matter where I call
\TOCLanguage.
The Arabic peopel may use other quoatation marks. I will check it!
Please inform me when you found it out.
6) (One other bug!). We should add the command
"\selectlanguage{farsi}" as an ERT as the first line of the
document.
> I can see no difference. With and without the ERT command, the result
> is identical.
I checked this issue after applying the patches. Still I
have problem if I don't put the mentioned ERT. Something is wrong!!
What is wrong?
What is the version number of the arabi-package you are using? Mine is version
Version 1.1, December 16, 2006
---
Does the fontenc part of my patch work for you?
regards Uwe
Re: [patch] fix bug 2928: make Arabic and Farsi correctly usable
6) (One other bug!). We should add the command
"\selectlanguage{farsi}" as an ERT as the first line of the
document.
>>> No need for this. When the document language is Farsi, no switch is
>>> needed. For later switches, this
>>> is currently correctly done by LyX.
>> Again as I said this bug is due to ARABI package. In the previous
>> email I have attached the example_lyxified.lyx. Try to compile it as it
>> is and then try to compile it without the first line containing the
>> ERT. You will see that LyX will complain about some undefined characters.
>> Again since this is a bug of LyX we should not change the source again
>> as I said before!
> I can see no difference. With and without the ERT command, the result
> is identical.
I checked this issue after applying the patches. Still I
have problem if I don't put the mentioned ERT. Something
is wrong!!
-
Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on,
when.
Re: [patch] fix bug 2928: make Arabic and Farsi correctly usable
2) Due to the current bugs or limitations of the ARABI package
whenever we want to use Farsi we should use Arabic too (because
some of the
shared definitions are defined in Arabic definitions files only).
Moreover Farsi should be called before Arabic. Again there are two
ways:
2-a) It is possible to adjust the input field "Options" in
"Document->Setteings:Document Class" (though I am not sure!).
>>> This is the way we do know: When a language is used in a document,
>>> its
>>> name is automatically added
>>> to the document class option. To in case the user uses Farsi, we
>>> should
>>> also add arabic.
>> You are right! But since this is a bug of ARABI package hopefully
>> it will be OK later and then we should/may remove this part from the
>> source. However Please let me know the point that I should look into the
>> source or
> I haven't touched this in the patch. Do you reported the bug to the
> arabi maintainers? If yes and
> they have it fixed in their development resources, please ask them to
> release this fixed version,
> because this is a mayor bug.
> I don't want to build this in as I expect that they will fix this
> quickly. This would only be a
> nasty hack nobody remembers to remove later. The user can for a quick
> workaround add "arabic"
> manually to the documentclass options. Or do you think this status will
> stay in arabi for longer time?
I can not give any guarantee about the fix. The author is extermely busy
sometimes. I prefer the manual one for the time being. Then if it stays more we
can do something about it. I have submitted many bug fixes to the author and I
am waiting for his reply.
3) ARABI has a seperate command to specify the Main language of the
document. This main language
is used to specify the language and orientation of the "Table of
Contents" and "Page numbers" and so
on. It is necessary to put the command "\TOCLanguage{farsi}" in the
"Document->Setteings:LaTeX Preamble".
>>> Yes, but not to the user visible preamble but to the one that LyX
>>> sets.
>> You are right! How can we understand what the main language of the
>> document is?
> See the attached patch. I implemented this but disabled it because
> \TOCLanguage gives me the error
> "unknown command". Therefore your example-lyxified doesn't compile.
The command "\TOCLanguage{}" is defined after the call to BABEL in Latex
Preamble.
5) (One other bug!) We should add the following two commands
"\DeclareTextSymbol{\guillemotright}{LFE}{62}" and
"\DeclareTextSymbol{\guillemotleft}{LFE}{60}" to
"Document->Setteings:LaTeX
Preamble".
>>> Why?
>> The bug is again due to ARABI package. These two lines define the
>> quote symboles in defined font-encoding LFE used for Farsi which are
>> "«" and "»". Again we should not change the source of LyX. This is a bug
>> of ARABI.
> Implemented in the patch too, but please report this to the arabi
> people.
The Arabic peopel may use other quoatation marks. I will check it!
6) (One other bug!). We should add the command
"\selectlanguage{farsi}" as an ERT as the first line of the
document.
>>> No need for this. When the document language is Farsi, no switch is
>>> needed. For later switches, this
>>> is currently correctly done by LyX.
>> Again as I said this bug is due to ARABI package. In the previous
>> email I have attached the example_lyxified.lyx. Try to compile it as it
>> is and then try to compile it without the first line containing the
>> ERT. You will see that LyX will complain about some undefined characters.
>> Again since this is a bug of LyX we should not change the source again
>> as I said before!
> I can see no difference. With and without the ERT command, the result
> is identical.
I will check it.
thank you Uwe for your attention,
Mostafa
-
Building a website is a piece of cake.
Yahoo! Small Business gives you all the tools to get online.
