Ross,
Because there is no need for it. When the vectors (bold) i, j, k are
defined to be the standard basis vectors, then they are already unit
vectors. Putting a hat over them is quite superfluous. That there is no
easy way to do this in Unicode is surely indicative that standard usage
does
I have received a private mail from François Charette saying that he
no longer has time to maintain polyglossia and he offered the package
to others to become maintainers. I myself will not have any time tilll
the end of this year and moreover do not know git and have no time to
learn it. If
El 25/09/2011 12:08, Zdenek Wagner escribió:
I could use babel with XeLaTeX without any modification. The problem
is that in non-unicode babel a lot of things is implemented via active
characters. Thus if you use czech or slovak option, \cline ceases to
work. If you use slovak or latin option,
Hi all,
Babel gets back on track and it is again actively maintained. The
goals are mainly to fix bugs, to make it compatible with XeTeX and
LuaTeX (as far as possible), and perhaps to add some minor new
features (provided they are backward compatible).
No attempt will be done to take full
Arthur,
Javier, that's great news! I suppose you're part of the team
developing it?
Yes, I am.
Javier
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
, send bug
reports or explain the problems and the expected behaviour.
Javier
On Wed, May 2, 2012 at 4:54 PM, Javier Bezos lis...@tex-tipografia.com
mailto:lis...@tex-tipografia.com wrote:
Hi all,
Babel gets back on track and it is again actively maintained. The
goals are mainly
El 02/05/2012 18:29, Vafa Khalighi escribió:
I can send you lots more, if you want to fix these.
Thanks. You may send them to me directly, if you want.
Javier
--
Subscriptions, Archive, and List information, etc.:
El 04/05/2012 9:24, Vafa Khalighi escribió:
Is there a mailing list/development repository for babel?
Sure. The repository is on:
http://www.latex-project.org/svnroot/latex2e-public/required/babel/
Until now, there are only changes in the test files.
As to the mailing list, I'm not sure.
François,
Some times ago, I read that babel will be compatible with xelatex.
I would like to use babel with french and sanskrit languages, do I have
any chance to succeed?
Not yet -- I'm still working on it. For further info, see:
http://www.tex-tipografia.com/babel_news.html
An advance of
Maintainig babel is important for (pdf)latex which is still in use but
for XeLaTeX I would suggest polyglossia which already works.
I would add the new version of babel won't make things to
work automagically. Rather it will provide some tools to
ease making language files compatible with
Hi all,
A beta version is babel 3.9 is now available. For further info see:
http://www.tex-tipografia.com/babel_news.html
Javier
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
This is in fact a question about fontspec, but since it is
used mainly with xetex (and luatex) I think I'll get better
answers here.
The question is: Does fontspec provide a way to set the
language so that it's always active even if other default
features are changed.
Javier
El 11/09/2013 11:24, Ulrike Fischer escribió:
The question is: Does fontspec provide a way to set the
language so that it's always active even if other default
features are changed.
Not that I know (and the code doesn't look as if it does).
Thanks. That was my impression after reading the
Last time I heard from him on this, it was something in the lines of “I
wish I didn’t implement \addfontfeatures”, say I maintain my position
that people should avoid it whenever possible, it is just a hack.
And the alternative is...?
Javier
Ulrike,
Did you try to contact Will?
I intend to do it, but I'd like a bit of discussión before,
to have a clearer idea of how fontspec works and what I
should request.
Javier
--
Subscriptions, Archive, and List information, etc.:
El 09/01/2014 17:27, Ulrike Fischer escribió:
And I checked with miktex + babel 3.8m and texlive + babel 3.9h. In
both cases I can see the difference between lualatex and xelatex. So
it can't be something new in babel.
In fact, in my system (TL) I can see the differences selecting the
Ulrike,
\lccode`\^^[=`\^^[ % oe in OT1
\lccode`\- =`\- % default hyphen char
\lccode 127=127 % alternate hyphen char
\lccode 23 =23% textcompwordmark in T1
\InputIfFileExists{hyphen.cfg}
There is no sensible hook for xelatex.ini.
Then clearly it must be fixed in hyphen.cfg. Right
El 25/03/2016 10:40, Zdenek Wagner escribió:
The old IL2 encoding was creased for the CS fonts and supported in
cslatex. [...] Thus the result is that
the only encoding for Czech and Slovak that has ever been officially
supported in babel is T1. It makes no sense to introduce IL2 (and XL2
that
Apostolos,
preface = \textPi \textrho\acctonos \textomicron\textlambda
\textomicron\textgamma
XeLaTeX is Unicode aware and can handle Unicode strings. Therefore, I fail to
see
why you are doing things this way. The LGR font encoding is an ancient hack that
has no usage anymore.
Of course,
Hi all,
I'm working on a new version of babel, with a new way to define
languages in a descriptive way, more than in a programmatic one (of
course, the latter won't be excluded because it's still necessary).
The idea is to create a set of ini file like those you can find on
Mojca,
Thank you. See me reply to Zdeněk.
What is the difference between months.format.wide and
months.stand-alone.wide?
In most languages, none. This distinction is made by the CLDR,
but I wonder if it's useful here, so very likely the format
branch should be removed.
In Slovenian one
Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz
2016-03-23 19:31 GMT+01:00 Javier Bezos <lis...@tex-tipografia.com
<mailto:lis...@tex-tipografia.com>>:
Hi all,
I'm working on a new version of babel, with a new way to define
languages in a des
Apostolos,
> preface = \textPi \textrho\acctonos \textomicron\textlambda
\textomicron\textgamma
>
> XeLaTeX is Unicode aware and can handle Unicode strings. Therefore, I
fail to see
> why you are doing things this way. The LGR font encoding is an ancient
hack that
> has no usage anymore.
\fontspec[Language=Hindi,Script=Devanagari]{FontName}
\fontspec[Language=Sanskrit,Script=Devanagari]{FontName}
\fontspec[Language=Sanskrit,Script=LatinScript]{FontName}
\fontspec[Language=Sanskrit,Script=Sarada]{FontName}
\fontspec[Language=Sanskrit,Script=Grantha]{FontName}
So why does Polyglossia make \devanagarifont and \sanskritfont equivalent?
There should be no such entity as \sanskritfont. Sanskrit isn't a font or
a script, it's a language.
Your point makes sense. Next version of babel will include a new
command which will allow to select a font depending
Hi all,
A new list on localization is now hosted at tug.org. Its name
is Kadingira (the Sumerian name of Babylon) and it was created
by Mojca and Arthur:
https://www.tug.org/mailman/listinfo/kadingira
There is currently just one message, which I posted a few days
ago:
Again, if you have an explicit list of issues with tex--xet that are
not shared with tex-xet it would be good if you could post them here.
And issues with the omega/luatex model, too. I resumed my work on
the basic bidi support for babel and they would be very useful.
Javier
Apostolos,
I would recommend against following this dangerous path. Once I asked I
asked the luaTeX list how to load hyphenation patterns and practically
no one knew the answer! So I think your decision is wise.
Interesting, because my experience when developing babel is
quite the opposite --
David,
(If you wish to try this for yourself, you will need a font that
includes both the Old Italic block of Unicode and the appropriate OT
features. I will share the one I’m making if anybody is reall
interested.)
I'm currently working on the bidi support for babel, so having
your font
> According to documentation it seems to me that ucharclasses work only
> with XeLaTeX.
But with babel and lualatex you can switch the font depending
on the script, even with RTL ones, which, if things haven’t
changed, isn’t possible with ucharclasses. See the examples
in p. 44 of the babel
According to documentation it seems to me that ucharclasses work only
with XeLaTeX.
But with babel and lualatex you can switch the font depending
on the script, even with RTL ones, which, if things haven’t
changed, isn’t possible with ucharclasses. See the examples
in p. 44 of the babel
I can do the same with polyglossia both with xelatex and lualatex but
imagine that I am writing a document in Hindi and from time to time it
contains a single word in English, Russian, Urdu, Gujarati and it may
be loaded from another file. I just do not want to write \textenglish,
32 matches
Mail list logo
