Re: [XeTeX] Polyglossia broken?
You may not get an answer from Francois. Try writing to Philipp Stephani p.stepha...@googlemail.com, who is the current maintainer. Best, Dominik On 3 October 2011 09:56, Vafa Khalighi vafa...@gmail.com wrote: I wrote an email to François Charette http://ctan.org/author/id/charettesaying that I am happy to maintain both arabxetex and polyglossia. On Mon, Oct 3, 2011 at 3:17 PM, Dominik Wujastyk wujas...@gmail.comwrote: I'm very pleased to be able to say that Philipp Stephani has added the required \RequirePackage statement to polyglossia.dtx and sent an update to CTAN. It should come down the pike soon. Thanks Philipp! He notes, however, that this is just an emergency fix, and that a new maintainer for polyglossia is needed. Volunteers? Dominik -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
there seem to be two git versions of polyglossia, i.e., it's been forked. Or am I wrong? Philipp's and Francois' On 1 October 2011 23:52, Alan Munn am...@gmx.com wrote: On Oct 1, 2011, at 2:13 PM, Alan Munn wrote: On Oct 1, 2011, at 1:23 PM, Dominik Wujastyk wrote: If anyone knows how to work git (I use it so rarely that I always have to start from scratch) then feel free to add this to the git hub. If anyone wishes to package this for CTAN, please do so. I've added the change to the git version. The question is whether Françcois (or the other person with commit permissions has the time to merge the change and upload the new version.) Actually, Philipp has already proposed the same change to the git version. Alan -- Alan Munn am...@gmx.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Oct 2, 2011, at 7:36 AM, Dominik Wujastyk wrote: there seem to be two git versions of polyglossia, i.e., it's been forked. Or am I wrong? Philipp's and Francois' Yes and no. The way github works is that when someone proposes a change, they fork it to their own account and then notify the owner of the code, who is able to incorporate the changes in that fork into the main branch of the code if the change is accepted. So Philipp's fork is the result of his having proposed the xkeyval fix. Alan On 1 October 2011 23:52, Alan Munn am...@gmx.com wrote: On Oct 1, 2011, at 2:13 PM, Alan Munn wrote: On Oct 1, 2011, at 1:23 PM, Dominik Wujastyk wrote: If anyone knows how to work git (I use it so rarely that I always have to start from scratch) then feel free to add this to the git hub. If anyone wishes to package this for CTAN, please do so. I've added the change to the git version. The question is whether Françcois (or the other person with commit permissions has the time to merge the change and upload the new version.) Actually, Philipp has already proposed the same change to the git version. Alan -- Alan Munn am...@gmx.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Alan Munn am...@gmx.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
All well and good, but useless if neither Philipp or Francois do anything, and the update never gets to CTAN. Humph. Dominik On 2 October 2011 18:21, Alan Munn am...@gmx.com wrote: On Oct 2, 2011, at 7:36 AM, Dominik Wujastyk wrote: there seem to be two git versions of polyglossia, i.e., it's been forked. Or am I wrong? Philipp's and Francois' Yes and no. The way github works is that when someone proposes a change, they fork it to their own account and then notify the owner of the code, who is able to incorporate the changes in that fork into the main branch of the code if the change is accepted. So Philipp's fork is the result of his having proposed the xkeyval fix. Alan On 1 October 2011 23:52, Alan Munn am...@gmx.com wrote: On Oct 1, 2011, at 2:13 PM, Alan Munn wrote: On Oct 1, 2011, at 1:23 PM, Dominik Wujastyk wrote: If anyone knows how to work git (I use it so rarely that I always have to start from scratch) then feel free to add this to the git hub. If anyone wishes to package this for CTAN, please do so. I've added the change to the git version. The question is whether Françcois (or the other person with commit permissions has the time to merge the change and upload the new version.) Actually, Philipp has already proposed the same change to the git version. Alan -- Alan Munn am...@gmx.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Alan Munn am...@gmx.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Oct 2, 2011, at 3:28 PM, Dominik Wujastyk wrote: All well and good, but useless if neither Philipp or Francois do anything, and the update never gets to CTAN. Humph. Well I don't think Philipp has commit privileges, and CTAN isn't happy about random (even highly trusted) people uploading new versions of packages that are still officially maintained. So we're back to the same problem as before, it's true. However, by posting the code to the github repository, we (i) save François some work and (ii) notify him directly. Of course we can't control whether he is too busy to upload the fixed version. Alan Dominik On 2 October 2011 18:21, Alan Munn am...@gmx.com wrote: On Oct 2, 2011, at 7:36 AM, Dominik Wujastyk wrote: there seem to be two git versions of polyglossia, i.e., it's been forked. Or am I wrong? Philipp's and Francois' Yes and no. The way github works is that when someone proposes a change, they fork it to their own account and then notify the owner of the code, who is able to incorporate the changes in that fork into the main branch of the code if the change is accepted. So Philipp's fork is the result of his having proposed the xkeyval fix. Alan On 1 October 2011 23:52, Alan Munn am...@gmx.com wrote: On Oct 1, 2011, at 2:13 PM, Alan Munn wrote: On Oct 1, 2011, at 1:23 PM, Dominik Wujastyk wrote: If anyone knows how to work git (I use it so rarely that I always have to start from scratch) then feel free to add this to the git hub. If anyone wishes to package this for CTAN, please do so. I've added the change to the git version. The question is whether Françcois (or the other person with commit permissions has the time to merge the change and upload the new version.) Actually, Philipp has already proposed the same change to the git version. Alan -- Alan Munn am...@gmx.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Alan Munn am...@gmx.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Alan Munn am...@gmx.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
2011/10/2 Alan Munn am...@gmx.com: Well I don't think Philipp has commit privileges, and CTAN isn't happy about random (even highly trusted) people uploading new versions of packages that are still officially maintained. Which seems to boil down to the original problem: polyglossia seems to need a new maintainer. Best Martin -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
2011/10/2 Martin Schröder mar...@oneiros.de: 2011/10/2 Alan Munn am...@gmx.com: Well I don't think Philipp has commit privileges, and CTAN isn't happy about random (even highly trusted) people uploading new versions of packages that are still officially maintained. Which seems to boil down to the original problem: polyglossia seems to need a new maintainer. I wrote it some time ago, so I literally copy the relevant part of François' letter: fc The fundamental problem is that polyglossia is no longer actively maintained (since over a year now). I have offered the package to various able people (notably the guys working on the LuaLaTeX stuff) but at the end nobody took it over. The source code is available at github and everybody can clone it and make further changes. There is no reason why a moderately simple LaTeX macro package distributed under the LPPL should stay static for over a year... Unfortunately I really have NO time at my disposal, and sadly enough, since I have left academia I no longer have any use for anything TeX-related :( I think time is ripe for another message on the XeTeX mailing list to look for a new maintainer... In the meanwhile if you know someone who might be interested, please tell me! /fc Since I do not know git and have no time to learn it, my suggestion was to move it to subversion. Although I am busy, adding \RequirePackage would be easy to me and the bug could be quickly fixed. There are other things that could (should) be fixed. I can deal with it since January next year when I am not so bus as now. Best Martin -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
I'm very pleased to be able to say that Philipp Stephani has added the required \RequirePackage statement to polyglossia.dtx and sent an update to CTAN. It should come down the pike soon. Thanks Philipp! He notes, however, that this is just an emergency fix, and that a new maintainer for polyglossia is needed. Volunteers? Dominik -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
Zdeněk, your offer to look after polyglossia from January 2012 is extremely welcome, and the best offer on the table at present. I'm sure nobody would mind in the least if you moved the code to subversion. I certainly wouldn't. Best, Dominik -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
I wrote an email to François Charette http://ctan.org/author/id/charettesaying that I am happy to maintain both arabxetex and polyglossia. On Mon, Oct 3, 2011 at 3:17 PM, Dominik Wujastyk wujas...@gmail.com wrote: I'm very pleased to be able to say that Philipp Stephani has added the required \RequirePackage statement to polyglossia.dtx and sent an update to CTAN. It should come down the pike soon. Thanks Philipp! He notes, however, that this is just an emergency fix, and that a new maintainer for polyglossia is needed. Volunteers? Dominik -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On 21 September 2011 17:52, Heiko Oberdiek heiko.oberd...@googlemail.comwrote:
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Okay, now that everything has been discussed, is someone actually going to
add this \RequirePackage{xkeyval} to polyglossia? If nobody else will do
it, I shall.
As things stand,
\documentclass{article}
\usepackage{polyglossia}
\begin{document}
Hello world!
\end{document}
fails to compile cleanly. That state of affairs can't be left to stand.
Best,
Dominik
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Oct 1, 2011, at 3:25 AM, Dominik Wujastyk wrote:
On 21 September 2011 17:52, Heiko Oberdiek
heiko.oberd...@googlemail.comwrote:
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Okay, now that everything has been discussed, is someone actually going to
add this \RequirePackage{xkeyval} to polyglossia? If nobody else will do
it, I shall.
As things stand,
\documentclass{article}
\usepackage{polyglossia}
\begin{document}
Hello world!
\end{document}
fails to compile cleanly. That state of affairs can't be left to stand.
Best,
Dominik
Howdy,
Best thing to do is to ask François Charette, the listed maintainer, if he will
do it or if he's willing to make you, or someone else who is willing to do the
job, the maintainer of the package.
Good Luck,
Herb Schulz
(herbs at wideopenwest dot com)
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
2011/10/1 Herbert Schulz he...@wideopenwest.com:
On Oct 1, 2011, at 3:25 AM, Dominik Wujastyk wrote:
On 21 September 2011 17:52, Heiko Oberdiek
heiko.oberd...@googlemail.comwrote:
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Okay, now that everything has been discussed, is someone actually going to
add this \RequirePackage{xkeyval} to polyglossia? If nobody else will do
it, I shall.
As things stand,
\documentclass{article}
\usepackage{polyglossia}
\begin{document}
Hello world!
\end{document}
fails to compile cleanly. That state of affairs can't be left to stand.
Best,
Dominik
Howdy,
Best thing to do is to ask François Charette, the listed maintainer, if he
will do it or if he's willing to make you, or someone else who is willing to
do the job, the maintainer of the package.
François wrote me that he is no longer able to maintain it and
searches someone who will continue his work. I do not know git and
have no time to learn it. If someone oves it to subversion (or at
least cvs) and adds me as a developer, I can do it. Adding
\RequirePackage is siple and I can do it quickly (or if somebody else
does it...). There are other possible improvements but I can deal more
with the package probably only since January next year.
Good Luck,
Herb Schulz
(herbs at wideopenwest dot com)
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
2011/10/1 Dominik Wujastyk wujas...@gmail.com:
On 21 September 2011 17:52, Heiko Oberdiek heiko.oberd...@googlemail.com
wrote:
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Okay, now that everything has been discussed, is someone actually going to
add this \RequirePackage{xkeyval} to polyglossia? If nobody else will do
it, I shall.
As things stand,
\documentclass{article}
\usepackage{polyglossia}
\begin{document}
Hello world!
\end{document}
fails to compile cleanly. That state of affairs can't be left to stand.
Best,
Dominik
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
I do not know where and when but I think François Charettehttp://ctan.org/author/id/charettemade *Philipp Stephani*, the maintainer of polyglossia. Also see https://github.com/phst It also seems that eg9 also has commit access to polyglossia on github. see https://github.com/eg9 -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Oct 1, 2011, at 1:23 PM, Dominik Wujastyk wrote:
I know this isn't the Right Procedure, but I've knocked up a polyglossia.dtx
with the \RequirePackage{xkeyval} statement in it, and with updated date and
version (1.2.0b).
Running
xelatex polyglossia.ins
generates all the right bits and pieces. I'm not providing an updated
polyglossia.pdf because I don't have all the necessary fonts on my system.
If anyone knows how to work git (I use it so rarely that I always have to
start from scratch) then feel free to add this to the git hub. If anyone
wishes to package this for CTAN, please do so.
I've added the change to the git version. The question is whether Françcois
(or the other person with commit permissions has the time to merge the change
and upload the new version.)
Alan
--
Alan Munn
am...@gmx.com
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Oct 1, 2011, at 2:13 PM, Alan Munn wrote: On Oct 1, 2011, at 1:23 PM, Dominik Wujastyk wrote: If anyone knows how to work git (I use it so rarely that I always have to start from scratch) then feel free to add this to the git hub. If anyone wishes to package this for CTAN, please do so. I've added the change to the git version. The question is whether Françcois (or the other person with commit permissions has the time to merge the change and upload the new version.) Actually, Philipp has already proposed the same change to the git version. Alan -- Alan Munn am...@gmx.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
load xkeyval before polyglossia.
On Wed, Sep 21, 2011 at 8:30 PM, Arash Zeini arash.ze...@gmail.com wrote:
Hello,
I updated my vanilla TexLive 2011 installation two days ago and have since
been unable to compile my document correctly. Nothing has changed in my
document but I now receive 181 error messages, most of which relate to
polyglossia. Here are some examples:
Package polyglossia Warning: \english@font@rm is not defined on input line
27.
! Extra \fi.
\inlineextras@german ...ds \german@shorthands \fi
l.183 ...e (`\textgerman{individuelle Lebensdauer}
').\footnote{For an
altern...
My editor opens up this section of polyglossia.sty:
%% ensure localization of \markright and \markboth commands
%%% THIS IS NOW DISABLED BY DEFAULT
\define@boolkey{polyglossia}[xpg@]{localmarks}[false]{%
\ifbool{xpg@localmarks}{%
\xpg@info{Option:~ localmarks}%
...
And this minimal example successfully reproduces the errors:
\documentclass[a4paper,12pt,oneside]{memoir}
\usepackage{fontspec}
\setmainfont[Mapping=tex-text]{Linux Libertine O}
\usepackage{polyglossia}
\setdefaultlanguage[variant=british]{english}
\setotherlanguages{german, french}
\begin{document}
\begin{quote}
\textgerman{Die Wahrheit wird, auch hier, in der Mitte der
Gegensätze
liegen \dots}
\end{quote}
\end{document}
Does anyone happen to know what might cause these errors?
Best wishes,
Arash
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
2011/9/21 Arash Zeini arash.ze...@gmail.com:
Hello,
See the previous thread open by Alex Hamann
I updated my vanilla TexLive 2011 installation two days ago and have since
been unable to compile my document correctly. Nothing has changed in my
document but I now receive 181 error messages, most of which relate to
polyglossia. Here are some examples:
Package polyglossia Warning: \english@font@rm is not defined on input line 27.
! Extra \fi.
\inlineextras@german ...ds \german@shorthands \fi
l.183 ...e (`\textgerman{individuelle Lebensdauer}
').\footnote{For an
altern...
My editor opens up this section of polyglossia.sty:
%% ensure localization of \markright and \markboth commands
%%% THIS IS NOW DISABLED BY DEFAULT
\define@boolkey{polyglossia}[xpg@]{localmarks}[false]{%
\ifbool{xpg@localmarks}{%
\xpg@info{Option:~ localmarks}%
...
And this minimal example successfully reproduces the errors:
\documentclass[a4paper,12pt,oneside]{memoir}
\usepackage{fontspec}
\setmainfont[Mapping=tex-text]{Linux Libertine O}
\usepackage{polyglossia}
\setdefaultlanguage[variant=british]{english}
\setotherlanguages{german, french}
\begin{document}
\begin{quote}
\textgerman{Die Wahrheit wird, auch hier, in der Mitte der Gegensätze
liegen \dots}
\end{quote}
\end{document}
Does anyone happen to know what might cause these errors?
Best wishes,
Arash
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Wednesday 21 September 2011, Zdenek Wagner wrote:
2011/9/21 Arash Zeini arash.ze...@gmail.com:
Hello,
See the previous thread open by Alex Hamann
Thanks for your prompt response. I am unable to locate a recent and relevant
thread started by Alex Hamann.
Vafa's suggestion of loading xkeyval before polyglossia reduces the number of
errors drastically but brings up new ones related to exaccent, which I load
after xkeyval and polyglossia.
My apologies if I am missing the obvious. I am wondering what could have
changed in the past week or so.
Thanks and best wishes,
Arash
I updated my vanilla TexLive 2011 installation two days ago and have
since been unable to compile my document correctly. Nothing has changed
in my document but I now receive 181 error messages, most of which
relate to polyglossia. Here are some examples:
Package polyglossia Warning: \english@font@rm is not defined on input
line 27.
! Extra \fi.
\inlineextras@german ...ds \german@shorthands \fi
l.183 ...e (`\textgerman{individuelle Lebensdauer}
').\footnote{For an
altern...
My editor opens up this section of polyglossia.sty:
%% ensure localization of \markright and \markboth commands
%%% THIS IS NOW DISABLED BY DEFAULT
\define@boolkey{polyglossia}[xpg@]{localmarks}[false]{%
\ifbool{xpg@localmarks}{%
\xpg@info{Option:~ localmarks}%
...
And this minimal example successfully reproduces the errors:
\documentclass[a4paper,12pt,oneside]{memoir}
\usepackage{fontspec}
\setmainfont[Mapping=tex-text]{Linux Libertine O}
\usepackage{polyglossia}
\setdefaultlanguage[variant=british]{english}
\setotherlanguages{german, french}
\begin{document}
\begin{quote}
\textgerman{Die Wahrheit wird, auch hier, in der Mitte der
Gegensätze liegen \dots}
\end{quote}
\end{document}
Does anyone happen to know what might cause these errors?
Best wishes,
Arash
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
I do not know about your other error messages but I guess they all should be
related to fontspec. A similar questions was asked on the TeXLive mailing
list and Wagner perhaps thought that your question was on the TeXLive mailng
list; that is why...
fontspec does not load xkeyval anymore (but used to load xkeyval),
polyglossia uses xkeyval but does not load it since it loads fontspec and
fontspec used to load xkeyval anymore.
2011/9/21 Arash Zeini arash.ze...@gmail.com
On Wednesday 21 September 2011, Zdenek Wagner wrote:
2011/9/21 Arash Zeini arash.ze...@gmail.com:
Hello,
See the previous thread open by Alex Hamann
Thanks for your prompt response. I am unable to locate a recent and
relevant
thread started by Alex Hamann.
Vafa's suggestion of loading xkeyval before polyglossia reduces the number
of
errors drastically but brings up new ones related to exaccent, which I load
after xkeyval and polyglossia.
My apologies if I am missing the obvious. I am wondering what could have
changed in the past week or so.
Thanks and best wishes,
Arash
I updated my vanilla TexLive 2011 installation two days ago and have
since been unable to compile my document correctly. Nothing has changed
in my document but I now receive 181 error messages, most of which
relate to polyglossia. Here are some examples:
Package polyglossia Warning: \english@font@rm is not defined on input
line 27.
! Extra \fi.
\inlineextras@german ...ds \german@shorthands \fi
l.183 ...e (`\textgerman{individuelle Lebensdauer}
').\footnote{For an
altern...
My editor opens up this section of polyglossia.sty:
%% ensure localization of \markright and \markboth commands
%%% THIS IS NOW DISABLED BY DEFAULT
\define@boolkey{polyglossia}[xpg@]{localmarks}[false]{%
\ifbool{xpg@localmarks}{%
\xpg@info{Option:~ localmarks}%
...
And this minimal example successfully reproduces the errors:
\documentclass[a4paper,12pt,oneside]{memoir}
\usepackage{fontspec}
\setmainfont[Mapping=tex-text]{Linux Libertine O}
\usepackage{polyglossia}
\setdefaultlanguage[variant=british]{english}
\setotherlanguages{german, french}
\begin{document}
\begin{quote}
\textgerman{Die Wahrheit wird, auch hier, in der Mitte der
Gegensätze liegen \dots}
\end{quote}
\end{document}
Does anyone happen to know what might cause these errors?
Best wishes,
Arash
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Wed, Sep 21, 2011 at 02:04:51PM +0200, Pander wrote:
On 2011-09-21 13:58, Arash Zeini wrote:
On Wednesday 21 September 2011, Zdenek Wagner wrote:
2011/9/21 Arash Zeini arash.ze...@gmail.com:
Hello,
See the previous thread open by Alex Hamann
Thanks for your prompt response. I am unable to locate a recent and
relevant
thread started by Alex Hamann.
Vafa's suggestion of loading xkeyval before polyglossia reduces the number
of
errors drastically but brings up new ones related to exaccent, which I load
after xkeyval and polyglossia.
Perhaps both packages should generate a warning if they detect a
usepackage order which is dangerous?
You are quoting *three* packages (xkeyval, polyglossia, exaccent),
which of them do you mean with *both*?
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Not really. fontspec used to load xkeyval and polyglossia loaded fontspec so
there was no need for polyglossia to load xkeyval again.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Sep 21, 2011, at 7:21 AM, VAFA KHALIGHI wrote:
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Not really. fontspec used to load xkeyval and polyglossia loaded fontspec so
there was no need for polyglossia to load xkeyval again.
Howdy,
It should have been there anyway since I believe \RequirePackage won't load
xkeyval again if it's already loaded.
Good Luck,
Herb Schulz
(herbs at wideopenwest dot com)
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
2011/9/21 Herbert Schulz he...@wideopenwest.com:
On Sep 21, 2011, at 7:21 AM, VAFA KHALIGHI wrote:
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Not really. fontspec used to load xkeyval and polyglossia loaded fontspec so
there was no need for polyglossia to load xkeyval again.
Howdy,
It should have been there anyway since I believe \RequirePackage won't load
xkeyval again if it's already loaded.
That's right. \RequirePackage and \usepackage maintain internally a
list of already loaded packages. There is one potential problem, you
are not specified a different list of options. Thus if you use
\RequirePackage{something} without any options, it is harmless. If a
user needs something with some options, he or she must load it
explicitely with these options in advance.
Good Luck,
Herb Schulz
(herbs at wideopenwest dot com)
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Wed, Sep 21, 2011 at 02:34:41PM +0200, Zdenek Wagner wrote:
That's right. \RequirePackage and \usepackage maintain internally a
list of already loaded packages. There is one potential problem, you
are not specified a different list of options. Thus if you use
\RequirePackage{something} without any options, it is harmless. If a
user needs something with some options, he or she must load it
explicitely with these options in advance.
The option lists may differ. But the requirement of LaTeX is that
the option list of the first load request is the superset of
the options in all load requests.
(load request: \RequirePackage, \usepackage, (\PassOptionsToPackage))
\usepackage[foo,bar,xyz]{something}
\usepackage[bar,foo,xyz]{something}
\usepackage[bar]{something}
\usepackage{something}
is ok, but any new option given later
\usepackage[foo,bar,xyz]{something}
\usepackage[new]{something}% throws an error
If there is an option clash, the user can press h to get
the exented help text of the error and LaTeX shows the options.
Then the user can resolve it by calling the package earlier with
the option superset as option list. And the package documentation
needs to be checked, if options of this package might overwrite
each other.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Wed, Sep 21, 2011 at 10:21:46PM +1000, VAFA KHALIGHI wrote:
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Not really. fontspec used to load xkeyval and polyglossia loaded fontspec so
there was no need for polyglossia to load xkeyval again.
No, packages *MUST* add packages for *all* required packages.
The use of xkeyval for fontspec was an *implementation* detail
that can change *any* time, like it has now happened.
AFAIK, the use of xkeyval was never part of the official interface
for fontspec. This would not make any sense, because fontspec deals
with fonts and is not a package for providing key value parsers.
Therefore it is a very clear bug of polyglossia, not to load
xkeyval. A package can be loaded many times using \usepackage
or \RequirePackage. LaTeX only loads the package at the first
request. At the later requests it only checks the date and options
of the request.
It is also good style to add a date, if a package must not be too old:
\RequirePackage{foo}[2010/04/20]
Then LaTeX will complain, if the loaded packages is too old.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
2011/9/21 Heiko Oberdiek heiko.oberd...@googlemail.com:
On Wed, Sep 21, 2011 at 02:34:41PM +0200, Zdenek Wagner wrote:
That's right. \RequirePackage and \usepackage maintain internally a
list of already loaded packages. There is one potential problem, you
are not specified a different list of options. Thus if you use
\RequirePackage{something} without any options, it is harmless. If a
user needs something with some options, he or she must load it
explicitely with these options in advance.
The option lists may differ. But the requirement of LaTeX is that
the option list of the first load request is the superset of
the options in all load requests.
(load request: \RequirePackage, \usepackage, (\PassOptionsToPackage))
\usepackage[foo,bar,xyz]{something}
\usepackage[bar,foo,xyz]{something}
\usepackage[bar]{something}
\usepackage{something}
is ok, but any new option given later
\usepackage[foo,bar,xyz]{something}
\usepackage[new]{something}% throws an error
If there is an option clash, the user can press h to get
the exented help text of the error and LaTeX shows the options.
Then the user can resolve it by calling the package earlier with
the option superset as option list. And the package documentation
needs to be checked, if options of this package might overwrite
each other.
Agreed. What I meant was if package anything contains
\RequirePackage{something} without any options but user needs
something with some option, then the correct way is
\usepackage[options]{something}
\usepackage{anything}
I am not sure whether the same effect can be achieved by giving the
option in \documentclass, probably yes but I would have to check it. I
agree that it is a bug if a package relies that a requested package
will be loaded by some automagic mechanism.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Wed, Sep 21, 2011 at 03:19:29PM +0200, Zdenek Wagner wrote:
Agreed. What I meant was if package anything contains
\RequirePackage{something} without any options but user needs
something with some option, then the correct way is
\usepackage[options]{something}
\usepackage{anything}
I am not sure whether the same effect can be achieved by giving the
option in \documentclass, probably yes but I would have to check it.
Usually yes.
There is an alternative way, that does not change package
loading order:
\PassOptionsToPackage{options}{something}
\usepackage{anything}
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
Thanks for all the posts. Vafa's mail below answers my question about recent
changes.
Loading xkeyval before polyglossia takes care of the problem in the minimal
example, but not in my actual document where I also load exaccent. In this
case I receive complaints about \upperaccent and other commands being already
defined.
Arash
On Wednesday 21 September 2011, VAFA KHALIGHI wrote:
I do not know about your other error messages but I guess they all should
be related to fontspec. A similar questions was asked on the TeXLive
mailing list and Wagner perhaps thought that your question was on the
TeXLive mailng list; that is why...
fontspec does not load xkeyval anymore (but used to load xkeyval),
polyglossia uses xkeyval but does not load it since it loads fontspec and
fontspec used to load xkeyval anymore.
2011/9/21 Arash Zeini arash.ze...@gmail.com
On Wednesday 21 September 2011, Zdenek Wagner wrote:
2011/9/21 Arash Zeini arash.ze...@gmail.com:
Hello,
See the previous thread open by Alex Hamann
Thanks for your prompt response. I am unable to locate a recent and
relevant
thread started by Alex Hamann.
Vafa's suggestion of loading xkeyval before polyglossia reduces the
number of
errors drastically but brings up new ones related to exaccent, which I
load after xkeyval and polyglossia.
My apologies if I am missing the obvious. I am wondering what could have
changed in the past week or so.
Thanks and best wishes,
Arash
I updated my vanilla TexLive 2011 installation two days ago and have
since been unable to compile my document correctly. Nothing has
changed in my document but I now receive 181 error messages, most of
which relate to polyglossia. Here are some examples:
Package polyglossia Warning: \english@font@rm is not defined on input
line 27.
! Extra \fi.
\inlineextras@german ...ds \german@shorthands \fi
l.183 ...e (`\textgerman{individuelle Lebensdauer}
').\footnote{For an
altern...
My editor opens up this section of polyglossia.sty:
%% ensure localization of \markright and \markboth commands
%%% THIS IS NOW DISABLED BY DEFAULT
\define@boolkey{polyglossia}[xpg@]{localmarks}[false]{%
\ifbool{xpg@localmarks}{%
\xpg@info{Option:~ localmarks}%
...
And this minimal example successfully reproduces the errors:
\documentclass[a4paper,12pt,oneside]{memoir}
\usepackage{fontspec}
\setmainfont[Mapping=tex-text]{Linux Libertine O}
\usepackage{polyglossia}
\setdefaultlanguage[variant=british]{english}
\setotherlanguages{german, french}
\begin{document}
\begin{quote}
\textgerman{Die Wahrheit wird, auch hier, in der Mitte der
Gegensätze liegen \dots}
\end{quote}
\end{document}
Does anyone happen to know what might cause these errors?
Best wishes,
Arash
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
fontspec loads xunicode and xunicode has been updated recently. What happens
if you load exaccent before polyglossia?
On Thu, Sep 22, 2011 at 12:04 AM, Arash Zeini arash.ze...@gmail.com wrote:
Thanks for all the posts. Vafa's mail below answers my question about
recent
changes.
Loading xkeyval before polyglossia takes care of the problem in the minimal
example, but not in my actual document where I also load exaccent. In this
case I receive complaints about \upperaccent and other commands being
already
defined.
Arash
On Wednesday 21 September 2011, VAFA KHALIGHI wrote:
I do not know about your other error messages but I guess they all should
be related to fontspec. A similar questions was asked on the TeXLive
mailing list and Wagner perhaps thought that your question was on the
TeXLive mailng list; that is why...
fontspec does not load xkeyval anymore (but used to load xkeyval),
polyglossia uses xkeyval but does not load it since it loads fontspec and
fontspec used to load xkeyval anymore.
2011/9/21 Arash Zeini arash.ze...@gmail.com
On Wednesday 21 September 2011, Zdenek Wagner wrote:
2011/9/21 Arash Zeini arash.ze...@gmail.com:
Hello,
See the previous thread open by Alex Hamann
Thanks for your prompt response. I am unable to locate a recent and
relevant
thread started by Alex Hamann.
Vafa's suggestion of loading xkeyval before polyglossia reduces the
number of
errors drastically but brings up new ones related to exaccent, which I
load after xkeyval and polyglossia.
My apologies if I am missing the obvious. I am wondering what could
have
changed in the past week or so.
Thanks and best wishes,
Arash
I updated my vanilla TexLive 2011 installation two days ago and
have
since been unable to compile my document correctly. Nothing has
changed in my document but I now receive 181 error messages, most
of
which relate to polyglossia. Here are some examples:
Package polyglossia Warning: \english@font@rm is not defined on
input
line 27.
! Extra \fi.
\inlineextras@german ...ds \german@shorthands \fi
l.183 ...e (`\textgerman{individuelle Lebensdauer}
').\footnote{For
an
altern...
My editor opens up this section of polyglossia.sty:
%% ensure localization of \markright and \markboth commands
%%% THIS IS NOW DISABLED BY DEFAULT
\define@boolkey{polyglossia}[xpg@]{localmarks}[false]{%
\ifbool{xpg@localmarks}{%
\xpg@info{Option:~ localmarks}%
...
And this minimal example successfully reproduces the errors:
\documentclass[a4paper,12pt,oneside]{memoir}
\usepackage{fontspec}
\setmainfont[Mapping=tex-text]{Linux Libertine O}
\usepackage{polyglossia}
\setdefaultlanguage[variant=british]{english}
\setotherlanguages{german, french}
\begin{document}
\begin{quote}
\textgerman{Die Wahrheit wird, auch hier, in der Mitte der
Gegensätze liegen \dots}
\end{quote}
\end{document}
Does anyone happen to know what might cause these errors?
Best wishes,
Arash
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Wednesday 21 September 2011, VAFA KHALIGHI wrote:
fontspec loads xunicode and xunicode has been updated recently. What
happens if you load exaccent before polyglossia?
Nothing. I get the same error messages as before.
Arash
On Thu, Sep 22, 2011 at 12:04 AM, Arash Zeini arash.ze...@gmail.com wrote:
Thanks for all the posts. Vafa's mail below answers my question about
recent
changes.
Loading xkeyval before polyglossia takes care of the problem in the
minimal example, but not in my actual document where I also load
exaccent. In this case I receive complaints about \upperaccent and other
commands being already
defined.
Arash
On Wednesday 21 September 2011, VAFA KHALIGHI wrote:
I do not know about your other error messages but I guess they all
should be related to fontspec. A similar questions was asked on the
TeXLive mailing list and Wagner perhaps thought that your question was
on the TeXLive mailng list; that is why...
fontspec does not load xkeyval anymore (but used to load xkeyval),
polyglossia uses xkeyval but does not load it since it loads fontspec
and fontspec used to load xkeyval anymore.
2011/9/21 Arash Zeini arash.ze...@gmail.com
On Wednesday 21 September 2011, Zdenek Wagner wrote:
2011/9/21 Arash Zeini arash.ze...@gmail.com:
Hello,
See the previous thread open by Alex Hamann
Thanks for your prompt response. I am unable to locate a recent and
relevant
thread started by Alex Hamann.
Vafa's suggestion of loading xkeyval before polyglossia reduces the
number of
errors drastically but brings up new ones related to exaccent, which
I load after xkeyval and polyglossia.
My apologies if I am missing the obvious. I am wondering what could
have
changed in the past week or so.
Thanks and best wishes,
Arash
I updated my vanilla TexLive 2011 installation two days ago and
have
since been unable to compile my document correctly. Nothing has
changed in my document but I now receive 181 error messages, most
of
which relate to polyglossia. Here are some examples:
Package polyglossia Warning: \english@font@rm is not defined on
input
line 27.
! Extra \fi.
\inlineextras@german ...ds \german@shorthands \fi
l.183 ...e (`\textgerman{individuelle Lebensdauer}
').\footnote{For
an
altern...
My editor opens up this section of polyglossia.sty:
%% ensure localization of \markright and \markboth commands
%%% THIS IS NOW DISABLED BY DEFAULT
\define@boolkey{polyglossia}[xpg@]{localmarks}[false]{%
\ifbool{xpg@localmarks}{%
\xpg@info{Option:~ localmarks}%
...
And this minimal example successfully reproduces the errors:
\documentclass[a4paper,12pt,oneside]{memoir}
\usepackage{fontspec}
\setmainfont[Mapping=tex-text]{Linux Libertine O}
\usepackage{polyglossia}
\setdefaultlanguage[variant=british]{english}
\setotherlanguages{german, french}
\begin{document}
\begin{quote}
\textgerman{Die Wahrheit wird, auch hier, in der Mitte der
Gegensätze liegen \dots}
\end{quote}
\end{document}
Does anyone happen to know what might cause these errors?
Best wishes,
Arash
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
2011/9/21 Arash Zeini arash.ze...@gmail.com:
On Wednesday 21 September 2011, VAFA KHALIGHI wrote:
fontspec loads xunicode and xunicode has been updated recently. What
happens if you load exaccent before polyglossia?
Nothing. I get the same error messages as before.
What packages are loaded before exaccent? Suppose that both packages
foo and bar define macro \something. If you load
\usepackage{foo}
\usepackage{bar}
you will get an error in bar. If you change the order, you will get
the same error, but now in foo. This will inform you that two packages
define the same macro. You have to examine carefully the log file to
see where the error appears. It may be useful to set
\errorcontextlines to a higher value in order to see more details
(default value is zero) I usually put \errorcontextlines=999 just
below \documentclass.
Arash
On Thu, Sep 22, 2011 at 12:04 AM, Arash Zeini arash.ze...@gmail.com wrote:
Thanks for all the posts. Vafa's mail below answers my question about
recent
changes.
Loading xkeyval before polyglossia takes care of the problem in the
minimal example, but not in my actual document where I also load
exaccent. In this case I receive complaints about \upperaccent and other
commands being already
defined.
Arash
On Wednesday 21 September 2011, VAFA KHALIGHI wrote:
I do not know about your other error messages but I guess they all
should be related to fontspec. A similar questions was asked on the
TeXLive mailing list and Wagner perhaps thought that your question was
on the TeXLive mailng list; that is why...
fontspec does not load xkeyval anymore (but used to load xkeyval),
polyglossia uses xkeyval but does not load it since it loads fontspec
and fontspec used to load xkeyval anymore.
2011/9/21 Arash Zeini arash.ze...@gmail.com
On Wednesday 21 September 2011, Zdenek Wagner wrote:
2011/9/21 Arash Zeini arash.ze...@gmail.com:
Hello,
See the previous thread open by Alex Hamann
Thanks for your prompt response. I am unable to locate a recent and
relevant
thread started by Alex Hamann.
Vafa's suggestion of loading xkeyval before polyglossia reduces the
number of
errors drastically but brings up new ones related to exaccent, which
I load after xkeyval and polyglossia.
My apologies if I am missing the obvious. I am wondering what could
have
changed in the past week or so.
Thanks and best wishes,
Arash
I updated my vanilla TexLive 2011 installation two days ago and
have
since been unable to compile my document correctly. Nothing has
changed in my document but I now receive 181 error messages, most
of
which relate to polyglossia. Here are some examples:
Package polyglossia Warning: \english@font@rm is not defined on
input
line 27.
! Extra \fi.
\inlineextras@german ...ds \german@shorthands \fi
l.183 ...e (`\textgerman{individuelle Lebensdauer}
').\footnote{For
an
altern...
My editor opens up this section of polyglossia.sty:
%% ensure localization of \markright and \markboth commands
%%% THIS IS NOW DISABLED BY DEFAULT
\define@boolkey{polyglossia}[xpg@]{localmarks}[false]{%
\ifbool{xpg@localmarks}{%
\xpg@info{Option:~ localmarks}%
...
And this minimal example successfully reproduces the errors:
\documentclass[a4paper,12pt,oneside]{memoir}
\usepackage{fontspec}
\setmainfont[Mapping=tex-text]{Linux Libertine O}
\usepackage{polyglossia}
\setdefaultlanguage[variant=british]{english}
\setotherlanguages{german, french}
\begin{document}
\begin{quote}
\textgerman{Die Wahrheit wird, auch hier, in der Mitte der
Gegensätze liegen \dots}
\end{quote}
\end{document}
Does anyone happen to know what might cause these errors?
Best wishes,
Arash
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
Am Wed, 21 Sep 2011 15:23:50 +0100 schrieb Arash Zeini: fontspec loads xunicode and xunicode has been updated recently. What happens if you load exaccent before polyglossia? Nothing. I get the same error messages as before. Well loading exaccent before fontspec/xunicode should actually work (unless you are loading the definitions again in another place). But why do you use exaccent anyway? Why bother with such an old package? As the error message tell you xunicode actually makes the necessary definitions and quite probably it will adapt the commands to xetex if necessary. -- Ulrike Fischer -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
For me, the attached example gives no error.
On Thu, Sep 22, 2011 at 12:23 AM, Arash Zeini arash.ze...@gmail.com wrote:
On Wednesday 21 September 2011, VAFA KHALIGHI wrote:
fontspec loads xunicode and xunicode has been updated recently. What
happens if you load exaccent before polyglossia?
Nothing. I get the same error messages as before.
Arash
On Thu, Sep 22, 2011 at 12:04 AM, Arash Zeini arash.ze...@gmail.com
wrote:
Thanks for all the posts. Vafa's mail below answers my question about
recent
changes.
Loading xkeyval before polyglossia takes care of the problem in the
minimal example, but not in my actual document where I also load
exaccent. In this case I receive complaints about \upperaccent and
other
commands being already
defined.
Arash
On Wednesday 21 September 2011, VAFA KHALIGHI wrote:
I do not know about your other error messages but I guess they all
should be related to fontspec. A similar questions was asked on the
TeXLive mailing list and Wagner perhaps thought that your question
was
on the TeXLive mailng list; that is why...
fontspec does not load xkeyval anymore (but used to load xkeyval),
polyglossia uses xkeyval but does not load it since it loads fontspec
and fontspec used to load xkeyval anymore.
2011/9/21 Arash Zeini arash.ze...@gmail.com
On Wednesday 21 September 2011, Zdenek Wagner wrote:
2011/9/21 Arash Zeini arash.ze...@gmail.com:
Hello,
See the previous thread open by Alex Hamann
Thanks for your prompt response. I am unable to locate a recent and
relevant
thread started by Alex Hamann.
Vafa's suggestion of loading xkeyval before polyglossia reduces the
number of
errors drastically but brings up new ones related to exaccent,
which
I load after xkeyval and polyglossia.
My apologies if I am missing the obvious. I am wondering what could
have
changed in the past week or so.
Thanks and best wishes,
Arash
I updated my vanilla TexLive 2011 installation two days ago and
have
since been unable to compile my document correctly. Nothing has
changed in my document but I now receive 181 error messages,
most
of
which relate to polyglossia. Here are some examples:
Package polyglossia Warning: \english@font@rm is not defined
on
input
line 27.
! Extra \fi.
\inlineextras@german ...ds \german@shorthands \fi
l.183 ...e (`\textgerman{individuelle Lebensdauer}
').\footnote{For
an
altern...
My editor opens up this section of polyglossia.sty:
%% ensure localization of \markright and \markboth commands
%%% THIS IS NOW DISABLED BY DEFAULT
\define@boolkey{polyglossia}[xpg@]{localmarks}[false]{%
\ifbool{xpg@localmarks}{%
\xpg@info{Option:~ localmarks}%
...
And this minimal example successfully reproduces the errors:
\documentclass[a4paper,12pt,oneside]{memoir}
\usepackage{fontspec}
\setmainfont[Mapping=tex-text]{Linux Libertine O}
\usepackage{polyglossia}
\setdefaultlanguage[variant=british]{english}
\setotherlanguages{german, french}
\begin{document}
\begin{quote}
\textgerman{Die Wahrheit wird, auch hier, in der Mitte
der
Gegensätze liegen \dots}
\end{quote}
\end{document}
Does anyone happen to know what might cause these errors?
Best wishes,
Arash
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
test.tex
Description: TeX document
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
I do not agree but I usually do not load any packages for various reasons.
If I need a particular function of a particular package, I implement it
myself, and even if that is not possible, I take macros from that package
but obviously change the macro names (both internal and public macros)
completely.
On Wed, Sep 21, 2011 at 11:01 PM, Heiko Oberdiek
heiko.oberd...@googlemail.com wrote:
On Wed, Sep 21, 2011 at 10:21:46PM +1000, VAFA KHALIGHI wrote:
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Not really. fontspec used to load xkeyval and polyglossia loaded fontspec
so
there was no need for polyglossia to load xkeyval again.
No, packages *MUST* add packages for *all* required packages.
The use of xkeyval for fontspec was an *implementation* detail
that can change *any* time, like it has now happened.
AFAIK, the use of xkeyval was never part of the official interface
for fontspec. This would not make any sense, because fontspec deals
with fonts and is not a package for providing key value parsers.
Therefore it is a very clear bug of polyglossia, not to load
xkeyval. A package can be loaded many times using \usepackage
or \RequirePackage. LaTeX only loads the package at the first
request. At the later requests it only checks the date and options
of the request.
It is also good style to add a date, if a package must not be too old:
\RequirePackage{foo}[2010/04/20]
Then LaTeX will complain, if the loaded packages is too old.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia broken?
On Wednesday 21 September 2011, Ulrike Fischer wrote: Am Wed, 21 Sep 2011 15:23:50 +0100 schrieb Arash Zeini: fontspec loads xunicode and xunicode has been updated recently. What happens if you load exaccent before polyglossia? Nothing. I get the same error messages as before. Well loading exaccent before fontspec/xunicode should actually work (unless you are loading the definitions again in another place). Yes, this solves the problem. But why do you use exaccent anyway? Why bother with such an old package? As the error message tell you xunicode actually makes the necessary definitions and quite probably it will adapt the commands to xetex if necessary. You are absolutely right. exaccent was in my master document due to historical reasons, but I actually don't need it anymore. Thanks for pointing this out. Best, Arash -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
