Re: #10685: Wrong language switches with no lang package and non-empty lang_end_command
Thanks for the tip. I added those lines into my document. Now, the document
seems to compile fine, but in between I get a bunch of errors of the
following type:
{{{
! Missing control sequence inserted.
\inaccessible
{
...ntroduction: \guillemotleft {}\def {
ngerman}\foreignlanguage {...
...
Please don't say `\def cs{...}', say `\def\cs{...}'.
I've inserted an inaccessible control sequence so that your
definition will be completed without mixing me up too badly.
}}}
Am I missing something else in my preamble, or can I just safely ignore
this warning?
On Sat, Jun 17, 2017 at 4:22 AM, LyX Ticket Tracker wrote:
> #10685: Wrong language switches with no lang package and non-empty
> lang_end_command
> -+-
> Reporter: ExecutorElassus | Owner: lasgouttes
> Type: defect | Status: fixed
> Priority: normal | Milestone: 2.2.4
> Component: general | Version: 2.2.3
> Severity: normal | Resolution:
> Keywords: patch|
> -+-
>
> Comment (by forenr):
>
> You are missing the following line from comment:33
> {{{
> \setotherlanguage[variant=german,spelling=new,
> babelshorthands=true]{german}
> }}}
> while the following two were in your polyglossiabreaker2.lyx but not in
> polyglossiabreaker2.3.tex
> {{{
> \newenvironment{ngerman}{\begin{german}}{\end{german}}
> \newenvironment{american}{\begin{english}[variant=
> american]}{\end{english}}
> }}}
>
> After adding these 3 lines to the preamble of polyglossiabreaker2.3.tex I
> was able to successfully compile it with xelatex.
>
> --
> Ticket URL:
> The LyX Project
Re: Update: polyglossia in 2.2.3
Hi Scott, thank you for your message. On Mon, Jun 5, 2017 at 3:08 AM, Scott Kostyshak <skost...@lyx.org> wrote: > On Fri, May 26, 2017 at 12:35:09PM +0200, Jürgen Spitzmüller wrote: > > Am Freitag, den 26.05.2017, 12:23 +0200 schrieb N. Andrew Walsh: > > > > > Or rather, the file will compile with 2.2.2, but not with 2.2.3 > > > (giving back the error about deleting a closing bracket as previously > > > described). > > > > You mean 2.2.3 not 2.3alpha, right? In any case, the file compiles fine > > for me both with recent stable (what will become 2.2.4) and master > > (what will become 2.3.0). > > > > Could you also post the LaTeX export (to LaTeX (XeTeX)) of this MWE? > > Andrew, I just wanted to make sure you saw the above message. > Yes, I saw. I'm copied on the bug report, and have since submitted several updates. There's a patch on the bug report that should resolve the issue (and is going into 2.3.0) that resolves it for other users. Thanks for keeping me informed. Sincerely, Andrew
Re: Update: polyglossia in 2.2.3
Hi Jürgen,
thanks for getting back to me.
The relevant settings are as follows:
Language Package: [none]
Command Start: \begin{$$lang}
Command End: \end{$$lang}
All four options below the "Default length unit" dropdown are checked, and
cursor movement is set to "logical."
It's possible that these are settings I put in earlier, when using
polyglossia, biblatex, biber, and xetex caused issues.
Anyway, thanks for the help.
Cheers,
Andrew
Re: Update: polyglossia in 2.2.3
Hi Jürgen, ach, whoops. I forgot to add that. Thanks for the reminder. Here attached is the (XeTeX-produced) LaTeX output from 2.2.3. Cheers, Andrew polyglossiabreaker2.tex Description: TeX document
Re: Update: polyglossia in 2.2.3
Hi Jürgen, thanks again. Yes, this is version 2.2.3, as released by gentoo Linux (if latest stable is already 2.2.4, then they seem to be a bit behind with their versions; or has 2.2.4 not yet been officially released?). In any case, is this something for which I should submit a bug report? Cheers, Andrew
Re: Update: polyglossia in 2.2.3
Hi Jürgen,
thanks for getting back to me. I'm attaching two files: the MWE
polyglossiabreaker2.lyx, and the necessary bibtex file. Put both in the
same directory, and it should work.
Or rather, the file will compile with 2.2.2, but not with 2.2.3 (giving
back the error about deleting a closing bracket as previously described).
Thanks for your help,
Andrew
polyglossiabreaker2.lyx
Description: application/lyx
@Book{butcher1917poetics,
Title= {The {P}oetics of {A}ristotle},
Author = {Butcher, Samuel H.},
Publisher= {Macmillan},
Year = {1917},
Address = {London}
}
Update: polyglossia in 2.2.3
Dear List:
In regards to the previous question about footnotes, I have isolated the
issue I'm having to the following:
in a \footnote block, if a block of text is both set to a different
language (invoking a polyglossia language definition) and contained in a
\quote block, the compiler will delete the last bracket of the footnote.
This causes all subsequent \footnote invocations to fail, as they now
appear as an attempt to insert a footnote within a footnote. Bigfoot
returns an error for the same reason.
Furthermore, Lyx codes ancient Greek in the .lyx file differently than the
polyglossia definition does. The preamble has the following:
\setotherlanguage[variant=ancient]{greek}
but within the .lyx file itself the following is used:
\lang ancientgreek
Might this also cause problems with polyglossia? Should I submit this/these
as a bug?
Lastly, the problems I'm having here do not occur with 2.2.2, so
downgrading provides me with a workaround at present.
Thanks in advance for your help.
Cheers,
Andrew Walsh
bigfoot failure with 2.2.3
Hi Devel-List,
I'm not sure if this is related to Biblatex/biber also going through an
update cycle the last week or so, but I suspect it's more likely related to
Lyx (as that was just released and the errors started afterwards).
I have a fairly large, complex file that is failing on xelatex pdf preview
with the following error:
Higher-placed footnotes can't be anchored in inferior ones.
I am not putting this text in a footnote. History:
\footinsdefault entered in line 24
! Package bigfoot Error: \footinsdefault forbidden in \footinsdefault ..
This error is preceded by the following one:
Package polyglossia Info: Option: english variant=american.
! Extra }, or forgotten \endgroup.
}
l.37 of imitation.''}
and antagonistic to the promulgated aims of their
venu...
I've deleted a group-closing symbol because it seems to be
spurious, as in `$x}$'. But perhaps the } is legitimate and
you forgot something else, as in `\hbox{$x}'. In such cases
the way to recover is to insert both the forgotten and the
deleted material, e.g., by typing `I$}'.
Those quote marks after "imitation" are smartquotes in the editing window,
and are at the end of a footnote citation that also includes a Quotation
block in the ancient variant of Greek. Is it possible that there's some
other conflict here between polyglossia, the smartquotes, and the citation
interface? Is deleting the curly bracket from the first citation causing
the next citation to fail? Is there a different polyglossia definition I
need to define ancient Greek in the preamble?
Thanks in advance for the help.
Cheers,
Andrew Walsh
