On Thu, Oct 14, 2010 at 12:58:15PM -0400, Kamal Abdali wrote:
> Dear Gareth,
>
> Thanks for pointing out the better polyglossia style (\setmainfont).
I think defining an \urdufont is better than setting it globally using
\setmainfont (neither is a polyglossia command) in case your Urdu font
has n
Dear Gareth,
Thanks for pointing out the better polyglossia style (\setmainfont).
As to the main problem, Vafa Khalighi has kindly explained that for the
footnoterule to be aligned correctly, the RTLdocument or rldocument option
of bidi has to be activated. Apparently, this has not been done by
p
Am Fri, 15 Oct 2010 15:51:02 +0300 schrieb Alexandros Gotsis:
> My point was rather simple: I think it will be easier to persuade
> Electra, my nine year old daughter, to use XeLaTeX rather than
> MSWord to type her school reports if she can understand what she
> types (including the typesetting
Alexandros Gotsis wrote:
A suggestion : suppose that, for some future version of XeTeX,
the first line of the file was treated specially if it started
(say) %! (or some analogous but currently unused sequence of
characters that can be found in most keyboards without
requiring language switchi
>My point was rather simple: I think it will be easier to persuade Electra, my
>nine year old
>
>daughter, to use XeLaTeX rather than MSWord to type her school reports if she
>can
>
>understand what she types (including the typesetting commands).
Then you need to create a simple format fi
Keith J. Schultz wrote:
I am aware that it is not a trivial task.
I have stated before that the "english" is to be the default and
what is far more important the actually use language!!
This would keep backward compatibility, in other words
inorder to use "legacy" files is a trivial task.
IF
Dear friends,
1.
It was not my intention to generate all this discussion on the subject, a
discussion that reached out even to religious arguments and polemics on
linguistic imperialism. My point was rather simple: I think it will be easier
to persuade Electra, my nine year old daughter, to us
I am aware that it is not a trivial task.
I have stated before that the "english" is to be the default and
what is far more important the actually use language!!
This would keep backward compatibility, in other words
inorder to use "legacy" files is a trivial task.
IF one wanted to use a localize
Keith J. Schultz wrote:
Like I saiud the best point to confront the problem is in the parser at
a low level directly in the xetex engine. so that the "normal" is
distinguished
from the markup.
There seems to be a consensus that it would be a good idea to have
Hi Again,
Like I saiud the best point to confront the problem is in the parser at
a low level directly in the xetex engine. so that the "normal" is
distinguished
from the markup.
There seems to be a consensus that it would be a good idea to have the
marku
Am 14.10.2010 um 12:59 schrieb Peter Dyballa:
>
> Am 14.10.2010 um 12:39 schrieb Keith J. Schultz:
>
>> This would be a good idea, but the original thought was also
>> for using localized units and such.
>
> I don't think there are so many "localised" units at this size (presumingly
On 14 Oct, 2010, at 05:59, Peter Dyballa wrote:
> I don't think there are so many "localised" units at this size (presumingly
> they start around 25 mm and reach a few km [Russian verst])
I think you mean league, not verst (which is just a little bit more than 1 km).
Best
Axel
--
On 15 Oct, 2010, at 02:38, Ulrike Fischer wrote:
> Am Thu, 14 Oct 2010 20:44:19 +0200 schrieb Pablo RodrÃguez:
>
>> for some strange reason using both XeTeX and LuaTeX the \emph{} command
>> contained in the sample document below exceeds TeX capacity:
>>
>> \documentclass[12pt]{slides}
>> \use
Am Thu, 14 Oct 2010 20:44:19 +0200 schrieb Pablo RodrÃguez:
> Hi there,
>
> for some strange reason using both XeTeX and LuaTeX the \emph{} command
> contained in the sample document below exceeds TeX capacity:
>
> \documentclass[12pt]{slides}
> \usepackage{fontspec}
> \setsansfont{FreeSans}
>
14 matches
Mail list logo
