Non-TeX Fonts (via XeTeX/LuaTeX) don't work
Code: Select all
\usepackage{fontspec}
Code: Select all
This is XeTeX, Version 3.141592653-2.6-0.999995 (MiKTeX 24.1 Portable) (preloaded format=xelatex 2024.12.6) 10 DEC 2024 08:36
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**./***.tex
(***.tex
LaTeX2e <2023-11-01> patch level 1
L3 programming layer <2024-01-04>
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/dinbrief\dinbr
ief.cls
Document Class/Style 'dinbrief' - Version 1.73
University of Karlsruhe - 2000/03/02 12:49:21
*** dinbrief: Running in LaTeX 2e mode!
*** dinbrief: NFSS 2!
Document Class: dinbrief 2000/03/02 LaTeX2e class
\ka@db@tmpdima=\dimen140
\ka@db@tmpdimb=\dimen141
\@mainlbl=\write3
\GZA=\dimen142
\ltf@headheight=\dimen143
\lts@headheight=\dimen144
\ltf@headsep=\dimen145
\lts@headsep=\dimen146
\ltf@textheight=\dimen147
\lts@textheight=\dimen148
\ka@db@txtlmarg=\dimen149
\addrhpos=\dimen150
\addrvpos=\dimen151
\addrwd=\dimen152
\addrht=\dimen153
\addroffset=\dimen154
\ka@db@addrhoffs=\dimen155
\backaddrht=\dimen156
\reflinevpos=\dimen157
\ufldmarkvpos=\dimen158
\lfldmarkvpos=\dimen159
\perfmarkvpos=\dimen160
\ka@db@foldmarkhoffs=\dimen161
\ka@db@perfmarkhoffs=\dimen162
\ka@db@foldmarklen=\dimen163
\ka@db@perfmarklen=\dimen164
\bottomtextvpos=\dimen165
\ka@db@headup=\dimen166
\ka@db@vfuzz=\dimen167
\ka@db@stdskip=\dimen168
\ka@db@fieldwd=\dimen169
\ka@db@fldskip=\dimen170
\ka@db@shfldwd=\dimen171
\ka@db@indadr=\dimen172
\dlabelheight=\dimen173
\dlabeltopmargin=\dimen174
\dlabelwidth=\dimen175
\clabelnumber=\count183
\cspare=\count184
\c@lt@state=\count185
\c@letter=\count186
\labelcount=\count187
\c@labelgen=\count188
\yearcnt=\count189
\@betr=\box51
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/dinbrief\dinbr
ief.cfg))
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/fontspec\fonts
pec.sty
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/l3packages/xpa
rse\xparse.sty
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/l3kernel\expl3
.sty
Package: expl3 2024-01-04 L3 programming layer (loader)
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/l3backend\l3ba
ckend-xetex.def
File: l3backend-xetex.def 2024-01-04 L3 backend support: XeTeX
\g__graphics_track_int=\count190
\l__pdf_internal_box=\box52
\g__pdf_backend_object_int=\count191
\g__pdf_backend_annotation_int=\count192
\g__pdf_backend_link_int=\count193
))
Package: xparse 2023-10-10 L3 Experimental document command parser
)
Package: fontspec 2022/01/15 v2.8a Font selection for XeLaTeX and LuaLaTeX
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/fontspec\fonts
pec-xetex.sty
Package: fontspec-xetex 2022/01/15 v2.8a Font selection for XeLaTeX and LuaLaTe
X
\l__fontspec_script_int=\count194
\l__fontspec_language_int=\count195
\l__fontspec_strnum_int=\count196
\l__fontspec_tmp_int=\count197
\l__fontspec_tmpa_int=\count198
\l__fontspec_tmpb_int=\count199
\l__fontspec_tmpc_int=\count266
\l__fontspec_em_int=\count267
\l__fontspec_emdef_int=\count268
\l__fontspec_strong_int=\count269
\l__fontspec_strongdef_int=\count270
\l__fontspec_tmpa_dim=\dimen176
\l__fontspec_tmpb_dim=\dimen177
\l__fontspec_tmpc_dim=\dimen178
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/base\fontenc.s
ty
Package: fontenc 2021/04/29 v2.0v Standard LaTeX package
)
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/fontspec\fonts
pec.cfg)))
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/unicode-math\u
nicode-math.sty
Package: unicode-math 2023/08/13 v0.8r Unicode maths in XeLaTeX and LuaLaTeX
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/unicode-math\u
nicode-math-xetex.sty
Package: unicode-math-xetex 2023/08/13 v0.8r Unicode maths in XeLaTeX and LuaLa
TeX
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/l3packages/l3k
eys2e\l3keys2e.sty
Package: l3keys2e 2023-10-10 LaTeX2e option processing using LaTeX3 keys
)
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/base\fix-cm.st
y
Package: fix-cm 2020/11/24 v1.1t fixes to LaTeX
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/base\ts1enc.de
f
File: ts1enc.def 2001/06/05 v3.0e (jk/car/fm) Standard LaTeX file
LaTeX Font Info: Redeclaring font encoding TS1 on input line 47.
))
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/amsmath\amsmat
h.sty
Package: amsmath 2023/05/13 v2.17o AMS math features
\@mathmargin=\skip48
For additional information on amsmath, use the `?' option.
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/amsmath\amstex
t.sty
Package: amstext 2021/08/26 v2.01 AMS text
(C:\Users\Jan\scoop\apps\miktex\current\texmfs\install\tex/latex/amsmath\amsgen
.sty
File: amsgen.sty 1999/11/30 v2.0 generic functions
\@emptytoks=\toks17
\ex@=\dimen179
))
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/amsmath\amsbsy
.sty
Package: amsbsy 1999/11/29 v1.2d Bold Symbols
\pmbraise@=\dimen180
)
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/amsmath\amsopn
.sty
Package: amsopn 2022/04/08 v2.04 operator names
)
\inf@bad=\count271
LaTeX Info: Redefining \frac on input line 234.
\uproot@=\count272
\leftroot@=\count273
LaTeX Info: Redefining \overline on input line 399.
LaTeX Info: Redefining \colon on input line 410.
\classnum@=\count274
\DOTSCASE@=\count275
LaTeX Info: Redefining \ldots on input line 496.
LaTeX Info: Redefining \dots on input line 499.
LaTeX Info: Redefining \cdots on input line 620.
\Mathstrutbox@=\box53
\strutbox@=\box54
LaTeX Info: Redefining \big on input line 722.
LaTeX Info: Redefining \Big on input line 723.
LaTeX Info: Redefining \bigg on input line 724.
LaTeX Info: Redefining \Bigg on input line 725.
\big@size=\dimen181
LaTeX Font Info: Redeclaring font encoding OML on input line 743.
LaTeX Font Info: Redeclaring font encoding OMS on input line 744.
\macc@depth=\count276
LaTeX Info: Redefining \bmod on input line 905.
LaTeX Info: Redefining \pmod on input line 910.
LaTeX Info: Redefining \smash on input line 940.
LaTeX Info: Redefining \relbar on input line 970.
LaTeX Info: Redefining \Relbar on input line 971.
\c@MaxMatrixCols=\count277
\dotsspace@=\muskip16
\c@parentequation=\count278
\dspbrk@lvl=\count279
\tag@help=\toks18
\row@=\count280
\column@=\count281
\maxfields@=\count282
\andhelp@=\toks19
\eqnshift@=\dimen182
\alignsep@=\dimen183
\tagshift@=\dimen184
\tagwidth@=\dimen185
\totwidth@=\dimen186
\lineht@=\dimen187
\@envbody=\toks20
\multlinegap=\skip49
\multlinetaggap=\skip50
\mathdisplay@stack=\toks21
LaTeX Info: Redefining \[ on input line 2953.
LaTeX Info: Redefining \] on input line 2954.
)
\g__um_fam_int=\count283
\g__um_fonts_used_int=\count284
\l__um_primecount_int=\count285
\g__um_primekern_muskip=\muskip17
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/unicode-math\u
nicode-math-table.tex)))
(***n\scoop\apps\miktex\current\texmfs\install\tex/latex/parskip\parski
p.sty
Package: parskip 2021-03-14 v2.0h non-zero parskip adjustments
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/kvoptions\kvop
tions.sty
Package: kvoptions 2022-06-15 v3.15 Key value format for package options (HO)
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/graphics\keyva
l.sty
Package: keyval 2022/05/29 v1.15 key=value parser (DPC)
\KV@toks@=\toks22
)
(***\scoop\apps\miktex\current\texmfs\install\tex/generic/ltxcmds\ltxc
mds.sty
Package: ltxcmds 2023-12-04 v1.26 LaTeX kernel commands for general use (HO)
)
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/kvsetkeys\kvse
tkeys.sty
Package: kvsetkeys 2022-10-05 v1.19 Key value parser (HO)
))
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/etoolbox\etool
box.sty
Package: etoolbox 2020/10/05 v2.5k e-TeX tools for LaTeX (JAW)
\etb@tempcnta=\count286
))
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/microtype\micr
otype.sty
Package: microtype 2023/03/13 v3.1a Micro-typographical refinements (RS)
\MT@toks=\toks23
\MT@tempbox=\box55
\MT@count=\count287
LaTeX Info: Redefining \noprotrusionifhmode on input line 1059.
LaTeX Info: Redefining \leftprotrusion on input line 1060.
\MT@prot@toks=\toks24
LaTeX Info: Redefining \rightprotrusion on input line 1078.
LaTeX Info: Redefining \textls on input line 1368.
\MT@outer@kern=\dimen188
LaTeX Info: Redefining \textmicrotypecontext on input line 1988.
\MT@listname@count=\count288
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/microtype\micr
otype-xetex.def
File: microtype-xetex.def 2023/03/13 v3.1a Definitions specific to xetex (RS)
LaTeX Info: Redefining \lsstyle on input line 238.
)
Package microtype Info: Loading configuration file microtype.cfg.
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/microtype\micr
otype.cfg
File: microtype.cfg 2023/03/13 v3.1a microtype main configuration file (RS)
))
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/polyglossia\po
lyglossia.sty
Package: polyglossia 2024/09/23 v2.3 Modern multilingual typesetting with XeLaT
eX and LuaLaTeX
(***\scoop\apps\miktex\current\texmfs\install\tex/generic/iftex\iftex.
sty
Package: iftex 2022/02/03 v1.0f TeX engine tests
)
! Undefined control sequence.
l.505 \prop_new_linked:N
\l_xpg_langsetup_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.505 \prop_new_linked:N \l_xpg_langsetup_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1104 \prop_new_linked:N
\__xpg_alias
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1104 \prop_new_linked:N \__xpg_alias
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1283 \prop_new_linked:N
\l_xpg_curropt_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1283 \prop_new_linked:N \l_xpg_curropt_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
\l_xpg_alias_keyvals_int=\count289
(C:\Users\Jan\scoop\apps\miktex\current\texmfs\install\tex/latex/polyglossia\gl
oss-latex.ldf
File: gloss-latex.ldf polyglossia: module for default language
! Undefined control sequence.
<argument> \l_xpg_langsetup_prop
\__prop_split_aux:NnTF ...N \__prop_split_aux:w #1
\s__prop_mark \use_i:nn \_...
<argument> ...langsetup_prop {latex/script}{latin}
\prop_put:Nne \l_xpg_langs...
\use:n #1->#1
<inserted text> ...{latex/script.initial:n}{latin}
\__keys_define:nn {latex/s...
<inserted text> ...pg_define_language_commands:e}}
\keyval_parse:NNn ...l_mark #3,\s__keyval_tail ,}}
\__keys_define:nnn ...ine:n \__keys_define:nn {#3}
\str_set:Nn \l__keys_modul...
\PolyglossiaSetup code ..._keys_define_lang:n {#1}
\keys_set:nn {polyglossia/...
l.16 }
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
<argument> \l_xpg_langsetup_prop
\exp_not:o ...__kernel_exp_not:w \exp_after:wN {#1
}
<argument> ...{\exp_not:o {\l_xpg_langsetup_prop }
\l__prop_internal_tl }
\use_ii:nn #1#2->#2
<argument> ...langsetup_prop {latex/script}{latin}
\prop_put:Nne \l_xpg_langs...
\use:n #1->#1
<inserted text> ...{latex/script.initial:n}{latin}
\__keys_define:nn {latex/s...
<inserted text> ...pg_define_language_commands:e}}
\keyval_parse:NNn ...l_mark #3,\s__keyval_tail ,}}
\__keys_define:nnn ...ine:n \__keys_define:nn {#3}
\str_set:Nn \l__keys_modul...
\PolyglossiaSetup code ..._keys_define_lang:n {#1}
\keys_set:nn {polyglossia/...
l.16 }
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
\prop_map_tokens:Nn ...prop_map_break: \s__prop {}
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
\prop_map_tokens:Nn ...prop_map_break: \s__prop {}
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
\prop_map_tokens:Nn ...prop_map_break: \s__prop {}
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphennames}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
\prop_map_tokens:Nn ...prop_map_break: \s__prop {}
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...up_prop {#1/hyphennames}}
\bool_set_false:N \l__xpg_...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Missing \endcsname inserted.
<to be read again>
\scan_stop:
\par ->\scan_stop:
\mode_if_horizontal:TF {\mode_if_inner:F {\tex_unskip:D \...
<argument> l@{\par
}latex/script\s__prop {latin}{latex/lcscript}{latin}{\par...
\cs_if_exist_p:c #1->\if_cs_exist:w #1
\cs_end: \exp_after:wN \use_i:nn \else...
\exp_args:Nf ...N {\exp:w \exp_end_continue_f:w #2
}
\bool_if:nTF #1->\if_predicate:w \bool_if_p:n {#1}
\__prg_TF_true:w \fi: \use...
\bool_lazy_and:nnTF ...edicate:w \bool_if:nTF {#1}
{\bool_if_p:n {#2}}{\c_fal...
\__xpg_pattern_check_if_exists:nTF ...phenation})}
{\prg_return_true: }{\prg_...
\xpg_if_language_defined:nT ..._if_exists:nTF {#1}
{\prg_return_true: }{\prg_...
<argument> ...atex/DefineCommandsCmd}{use_none:n}}
{\cs_if_eq:cNTF {l@latex}{...
\use_ii:nn #1#2->#2
...
l.16 }
The control sequence marked <to be read again> should
not appear between \csname and \endcsname.
Package polyglossia Warning: No hyphenation patterns were loaded for `latex'
(polyglossia) I will use \language=\l@nohyphenation instead.
\l@latex = a dialect from \language\l@nohyphenation
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...wn latex/bcp47-script\s__prop {Latn}
\__prop_pair:wn latex/lc-b...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...n latex/bcp47-extension-u\s__prop {}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...pair:wn latex/direction\s__prop {LR}
\__prop_pair:wn latex/hyph...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #6\fi: \use:n {#1}
{#6}{#7}\if_false: #8\fi: ...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #8\fi: \use:n {#1}
{#8}{#9}\__prop_map_tokens...
<argument> ...eral\s__prop {xpg_C_localnumeral:nn}
\__prop_pair:wn latex/Loca...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
\prop_map_tokens:Nn ...prop_map_break: \s__prop {}
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
\prop_map_tokens:Nn ...prop_map_break: \s__prop {}
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
\prop_map_tokens:Nn ...prop_map_break: \s__prop {}
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/hyphenmins}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
\prop_map_tokens:Nn ...prop_map_break: \s__prop {}
\__prop_pair:wn \fi: \prop...
\exp_args:NNe ...p_after:wN #2\tex_expanded:D {{#3
}}
\__xpg_setup_hyphen:n ...tup_prop {#1/hyphenmins}}
\cs_if_eq:cNF {l@#1}\l@noh...
\PolyglossiaSetup code ..._xpg_setup_hyphen:n {#1}
\cs_gset:cpn {init@extras@...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/lcscript}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\str_if_eq:eeTF #1#2->\if:w 0\__str_if_eq:nn {#1
}{#2}\__prg_TF_true:w \fi: \...
<argument> ...setup_prop }{latex/lcscript}}{latin}
{\SetupLatinPolyglossiaFon...
\use_i:nn #1#2->#1
...
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/lcscript}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #2\fi: \use:n {#1}
{#2}{#3}\if_false: #4\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\str_if_eq:eeTF #1#2->\if:w 0\__str_if_eq:nn {#1
}{#2}\__prg_TF_true:w \fi: \...
<argument> ...setup_prop }{latex/lcscript}}{latin}
{\SetupLatinPolyglossiaFon...
\use_i:nn #1#2->#1
...
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
<to be read again>
}
<argument> {\__prop_item:nnn {latex/lcscript}}
latex/script\s__prop {latin}
\use:n #1->#1
\__prop_map_tokens:nw ...false: #4\fi: \use:n {#1}
{#4}{#5}\if_false: #6\fi: ...
<argument> ..._pair:wn latex/langtag\s__prop {ENG}
\__prop_pair:wn latex/bcp4...
\__exp_arg_last_unbraced:nn #1#2->#2#1
\prop_map_tokens:Nn ..._prop_map_tokens:nw {#2}}#1
\__prop_pair:wn \fi: \prop...
\str_if_eq:eeTF #1#2->\if:w 0\__str_if_eq:nn {#1
}{#2}\__prg_TF_true:w \fi: \...
<argument> ...setup_prop }{latex/lcscript}}{latin}
{\SetupLatinPolyglossiaFon...
\use_i:nn #1#2->#1
...
l.16 }
(That makes 100 errors; please try again.)
Here is how much of TeX's memory you used:
10058 strings out of 409617
206895 string characters out of 5772186
1917191 words of memory out of 5000000
32142 multiletter control sequences out of 15000+600000
558085 words of font info for 38 fonts, out of 8000000 for 9000
1348 hyphenation exceptions out of 8191
86i,0n,93p,541b,154s stack positions out of 10000i,1000n,20000p,200000b,200000s
No pages of output.
There's no such error related to fontspec. The errors occur because the dinbrief class is too old and not updated, to work with a modern LaTeX installation.jxx66 wrote:a similar issue again in LyX 2.4.2.1
Code: Select all
(***\scoop\apps\miktex\current\texmfs\install\tex/latex/dinbrief\dinbr
ief.cls
Document Class/Style 'dinbrief' - Version 1.73
University of Karlsruhe - 2000/03/02 12:49:21
*** dinbrief: Running in LaTeX 2e mode!
*** dinbrief: NFSS 2!
Document Class: dinbrief 2000/03/02 LaTeX2e class
Code: Select all
This is XeTeX, Version 3.141592653-2.6-0.999995 (MiKTeX 24.1 Portable) (preloaded format=xelatex 2024.12.6) 11 DEC 2024 09:05
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**./Neues_Dokument1.tex
(Neues_Dokument1.tex
LaTeX2e <2023-11-01> patch level 1
L3 programming layer <2024-01-04>
(<...>\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rlttr2.cls
Document Class: scrlttr2 2024/10/24 v3.43 KOMA-Script document class (letter)
(<...>\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rkbase.sty
Package: scrkbase 2024/10/24 v3.43 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(<...>\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rbase.sty
Package: scrbase 2024/10/24 v3.43 KOMA-Script package (KOMA-Script-independent
basics and keyval usage)
(<...>\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rlfile.sty
Package: scrlfile 2024/10/24 v3.43 KOMA-Script package (file load hooks)
(<...>\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rlfile-hook.sty
Package: scrlfile-hook 2024/10/24 v3.43 KOMA-Script package (using LaTeX hooks)
(<...>\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rlogo.sty
Package: scrlogo 2024/10/24 v3.43 KOMA-Script package (logo)
)))
(<...>\apps\miktex\current\texmfs\install\tex/latex/graphics\keyva
l.sty
Package: keyval 2022/05/29 v1.15 key=value parser (DPC)
\KV@toks@=\toks17
)
Applying: [2021/05/01] Usage of raw or classic option list on input line 254.
Already applied: [0000/00/00] Usage of raw or classic option list on input line
370.
))
Package scrlttr2 Info: You've used standard option `11pt'.
(scrlttr2) This is correct!
(scrlttr2) Internally I'm using `fontsize=11pt'.
(scrlttr2) If you'd like to set the option with \KOMAoptions,
(scrlttr2) you'd have to use `fontsize=11pt' there
(scrlttr2) instead of `11pt', too.
Class scrlttr2 Info: File `scrsize11pt.clo' used to setup font sizes on input l
ine 2047.
(<...>\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rsize11pt.clo
File: scrsize11pt.clo 2024/10/24 v3.43 KOMA-Script font size class option (11pt
)
)
(<...>\apps\miktex\current\texmfs\install\tex/latex/koma-script\ty
pearea.sty
Package: typearea 2024/10/24 v3.43 KOMA-Script package (type area)
\ta@bcor=\skip48
\ta@div=\count183
\ta@hblk=\skip49
\ta@vblk=\skip50
\ta@temp=\skip51
\footheight=\skip52
Package typearea Info: These are the values describing the layout:
(typearea) DIV = 10
(typearea) BCOR = 0.0pt
(typearea) \paperwidth = 597.50793pt
(typearea) \textwidth = 418.25555pt
(typearea) DIV departure = -6%
(typearea) \evensidemargin = 17.3562pt
(typearea) \oddsidemargin = 17.3562pt
(typearea) \paperheight = 845.04694pt
(typearea) \textheight = 595.80026pt
(typearea) \topmargin = -25.16531pt
(typearea) \headheight = 17.0pt
(typearea) \headsep = 20.40001pt
(typearea) \topskip = 11.0pt
(typearea) \footskip = 47.6pt
(typearea) \baselineskip = 13.6pt
(typearea) on input line 1802.
)
\c@letter=\count184
)
Class scrlttr2 Info: Letter-Class-Option `DIN' loaded on input line 6.
(<...>\apps\miktex\current\texmfs\install\tex/latex/koma-script\DI
N.lco
File: DIN.lco 2024/10/24 v3.43 KOMA-Script letter-class-option
)
(<...>\apps\miktex\current\texmfs\install\tex/latex/fontspec\fonts
pec.sty
(<...>\apps\miktex\current\texmfs\install\tex/latex/l3packages/xpa
rse\xparse.sty
(<...>\apps\miktex\current\texmfs\install\tex/latex/l3kernel\expl3
.sty
Package: expl3 2024-01-04 L3 programming layer (loader)
(<...>\apps\miktex\current\texmfs\install\tex/latex/l3backend\l3ba
ckend-xetex.def
File: l3backend-xetex.def 2024-01-04 L3 backend support: XeTeX
\g__graphics_track_int=\count185
\l__pdf_internal_box=\box51
\g__pdf_backend_object_int=\count186
\g__pdf_backend_annotation_int=\count187
\g__pdf_backend_link_int=\count188
))
Package: xparse 2023-10-10 L3 Experimental document command parser
)
Package: fontspec 2022/01/15 v2.8a Font selection for XeLaTeX and LuaLaTeX
(<...>\apps\miktex\current\texmfs\install\tex/latex/fontspec\fonts
pec-xetex.sty
Package: fontspec-xetex 2022/01/15 v2.8a Font selection for XeLaTeX and LuaLaTe
X
\l__fontspec_script_int=\count189
\l__fontspec_language_int=\count190
\l__fontspec_strnum_int=\count191
\l__fontspec_tmp_int=\count192
\l__fontspec_tmpa_int=\count193
\l__fontspec_tmpb_int=\count194
\l__fontspec_tmpc_int=\count195
\l__fontspec_em_int=\count196
\l__fontspec_emdef_int=\count197
\l__fontspec_strong_int=\count198
\l__fontspec_strongdef_int=\count199
\l__fontspec_tmpa_dim=\dimen140
\l__fontspec_tmpb_dim=\dimen141
\l__fontspec_tmpc_dim=\dimen142
(<...>\apps\miktex\current\texmfs\install\tex/latex/base\fontenc.s
ty
Package: fontenc 2021/04/29 v2.0v Standard LaTeX package
)
(<...>\apps\miktex\current\texmfs\install\tex/latex/fontspec\fonts
pec.cfg)))
(<...>\apps\miktex\current\texmfs\install\tex/latex/setspace\setsp
ace.sty
Package: setspace 2022/12/04 v6.7b set line spacing
)
Class scrlttr2 Info: Letter-Class-Option `DIN' loaded on input line 33.
(<...>\apps\miktex\current\texmfs\install\tex/latex/koma-script\DI
N.lco
File: DIN.lco 2024/10/24 v3.43 KOMA-Script letter-class-option
)
(<...>\apps\miktex\current\texmfs\install\tex/latex/polyglossia\po
lyglossia.sty
Package: polyglossia 2024/09/23 v2.3 Modern multilingual typesetting with XeLaT
eX and LuaLaTeX
(<...>\apps\miktex\current\texmfs\install\tex/latex/etoolbox\etool
box.sty
Package: etoolbox 2020/10/05 v2.5k e-TeX tools for LaTeX (JAW)
\etb@tempcnta=\count266
)
(<...>\apps\miktex\current\texmfs\install\tex/generic/iftex\iftex.
sty
Package: iftex 2022/02/03 v1.0f TeX engine tests
)
! Undefined control sequence.
l.505 \prop_new_linked:N
\l_xpg_langsetup_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.505 \prop_new_linked:N \l_xpg_langsetup_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1104 \prop_new_linked:N
\__xpg_alias
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1104 \prop_new_linked:N \__xpg_alias
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1283 \prop_new_linked:N
\l_xpg_curropt_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1283 \prop_new_linked:N \l_xpg_curropt_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
\l_xpg_alias_keyvals_int=\count267
(<...>\apps\miktex\current\texmfs\install\tex/latex/polyglossia\gl
oss-latex.ldf
File: gloss-latex.ldf polyglossia: module for default language
! Undefined control sequence.
<argument> \l_xpg_langsetup_prop
l.16 }
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
<argument> \l_xpg_langsetup_prop
l.16 }
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Missing \endcsname inserted.
<to be read again>
\scan_stop:
l.16 }
The control sequence marked <to be read again> should
not appear between \csname and \endcsname.
Package polyglossia Warning: No hyphenation patterns were loaded for `latex'
(polyglossia) I will use \language=\l@nohyphenation instead.
\l@latex = a dialect from \language\l@nohyphenation
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
(That makes 100 errors; please try again.)
Here is how much of TeX's memory you used:
5307 strings out of 409617
143618 string characters out of 5772186
1917191 words of memory out of 5000000
27413 multiletter control sequences out of 15000+600000
558085 words of font info for 38 fonts, out of 8000000 for 9000
1348 hyphenation exceptions out of 8191
108i,1n,107p,299b,100s stack positions out of 10000i,1000n,20000p,200000b,200000s
No pages of output.
expl3 and all packages starting with l3). From l3prop.dtx on Github I can see that the undefined command \prop_new_linked:N has been introduced 2024-02-12:Code: Select all
\begin{function}[added = 2024-02-12]{\prop_new_linked:N, \prop_new_linked:c}Code: Select all
L3 programming layer <2024-01-04>Code: Select all
This is XeTeX, Version 3.141592653-2.6-0.999995 (MiKTeX 24.1 Portable) (preloaded format=xelatex 2024.12.12) 12 DEC 2024 11:09
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**./Neues_Dokument1.tex
(Neues_Dokument1.tex
LaTeX2e <2023-11-01> patch level 1
L3 programming layer <2024-01-04>
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rlttr2.cls
Document Class: scrlttr2 2024/10/24 v3.43 KOMA-Script document class (letter)
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rkbase.sty
Package: scrkbase 2024/10/24 v3.43 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rbase.sty
Package: scrbase 2024/10/24 v3.43 KOMA-Script package (KOMA-Script-independent
basics and keyval usage)
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rlfile.sty
Package: scrlfile 2024/10/24 v3.43 KOMA-Script package (file load hooks)
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rlfile-hook.sty
Package: scrlfile-hook 2024/10/24 v3.43 KOMA-Script package (using LaTeX hooks)
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rlogo.sty
Package: scrlogo 2024/10/24 v3.43 KOMA-Script package (logo)
)))
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/graphics\keyva
l.sty
Package: keyval 2022/05/29 v1.15 key=value parser (DPC)
\KV@toks@=\toks17
)
Applying: [2021/05/01] Usage of raw or classic option list on input line 254.
Already applied: [0000/00/00] Usage of raw or classic option list on input line
370.
))
Package scrlttr2 Info: You've used standard option `11pt'.
(scrlttr2) This is correct!
(scrlttr2) Internally I'm using `fontsize=11pt'.
(scrlttr2) If you'd like to set the option with \KOMAoptions,
(scrlttr2) you'd have to use `fontsize=11pt' there
(scrlttr2) instead of `11pt', too.
Class scrlttr2 Info: File `scrsize11pt.clo' used to setup font sizes on input l
ine 2047.
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/koma-script\sc
rsize11pt.clo
File: scrsize11pt.clo 2024/10/24 v3.43 KOMA-Script font size class option (11pt
)
)
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/koma-script\ty
pearea.sty
Package: typearea 2024/10/24 v3.43 KOMA-Script package (type area)
\ta@bcor=\skip48
\ta@div=\count183
\ta@hblk=\skip49
\ta@vblk=\skip50
\ta@temp=\skip51
\footheight=\skip52
Package typearea Info: These are the values describing the layout:
(typearea) DIV = 10
(typearea) BCOR = 0.0pt
(typearea) \paperwidth = 597.50793pt
(typearea) \textwidth = 418.25555pt
(typearea) DIV departure = -6%
(typearea) \evensidemargin = 17.3562pt
(typearea) \oddsidemargin = 17.3562pt
(typearea) \paperheight = 845.04694pt
(typearea) \textheight = 595.80026pt
(typearea) \topmargin = -25.16531pt
(typearea) \headheight = 17.0pt
(typearea) \headsep = 20.40001pt
(typearea) \topskip = 11.0pt
(typearea) \footskip = 47.6pt
(typearea) \baselineskip = 13.6pt
(typearea) on input line 1802.
)
\c@letter=\count184
)
Class scrlttr2 Info: Letter-Class-Option `DIN' loaded on input line 6.
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/koma-script\DI
N.lco
File: DIN.lco 2024/10/24 v3.43 KOMA-Script letter-class-option
)
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/fontspec\fonts
pec.sty
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/l3packages/xpa
rse\xparse.sty
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/l3kernel\expl3
.sty
Package: expl3 2024-01-04 L3 programming layer (loader)
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/l3backend\l3ba
ckend-xetex.def
File: l3backend-xetex.def 2024-01-04 L3 backend support: XeTeX
\g__graphics_track_int=\count185
\l__pdf_internal_box=\box51
\g__pdf_backend_object_int=\count186
\g__pdf_backend_annotation_int=\count187
\g__pdf_backend_link_int=\count188
))
Package: xparse 2023-10-10 L3 Experimental document command parser
)
Package: fontspec 2022/01/15 v2.8a Font selection for XeLaTeX and LuaLaTeX
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/fontspec\fonts
pec-xetex.sty
Package: fontspec-xetex 2022/01/15 v2.8a Font selection for XeLaTeX and LuaLaTe
X
\l__fontspec_script_int=\count189
\l__fontspec_language_int=\count190
\l__fontspec_strnum_int=\count191
\l__fontspec_tmp_int=\count192
\l__fontspec_tmpa_int=\count193
\l__fontspec_tmpb_int=\count194
\l__fontspec_tmpc_int=\count195
\l__fontspec_em_int=\count196
\l__fontspec_emdef_int=\count197
\l__fontspec_strong_int=\count198
\l__fontspec_strongdef_int=\count199
\l__fontspec_tmpa_dim=\dimen140
\l__fontspec_tmpb_dim=\dimen141
\l__fontspec_tmpc_dim=\dimen142
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/base\fontenc.s
ty
Package: fontenc 2021/04/29 v2.0v Standard LaTeX package
)
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/fontspec\fonts
pec.cfg)))
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/setspace\setsp
ace.sty
Package: setspace 2022/12/04 v6.7b set line spacing
)
Class scrlttr2 Info: Letter-Class-Option `DIN' loaded on input line 33.
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/koma-script\DI
N.lco
File: DIN.lco 2024/10/24 v3.43 KOMA-Script letter-class-option
)
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/polyglossia\po
lyglossia.sty
Package: polyglossia 2024/09/23 v2.3 Modern multilingual typesetting with XeLaT
eX and LuaLaTeX
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/etoolbox\etool
box.sty
Package: etoolbox 2020/10/05 v2.5k e-TeX tools for LaTeX (JAW)
\etb@tempcnta=\count266
)
(<...>scoop\apps\miktex\current\texmfs\install\tex/generic/iftex\iftex.
sty
Package: iftex 2022/02/03 v1.0f TeX engine tests
)
! Undefined control sequence.
l.505 \prop_new_linked:N
\l_xpg_langsetup_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.505 \prop_new_linked:N \l_xpg_langsetup_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1104 \prop_new_linked:N
\__xpg_alias
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1104 \prop_new_linked:N \__xpg_alias
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1283 \prop_new_linked:N
\l_xpg_curropt_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
l.1283 \prop_new_linked:N \l_xpg_curropt_prop
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
\l_xpg_alias_keyvals_int=\count267
(<...>scoop\apps\miktex\current\texmfs\install\tex/latex/polyglossia\gl
oss-latex.ldf
File: gloss-latex.ldf polyglossia: module for default language
! Undefined control sequence.
<argument> \l_xpg_langsetup_prop
l.16 }
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
<argument> \l_xpg_langsetup_prop
l.16 }
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Missing \endcsname inserted.
<to be read again>
\scan_stop:
l.16 }
The control sequence marked <to be read again> should
not appear between \csname and \endcsname.
Package polyglossia Warning: No hyphenation patterns were loaded for `latex'
(polyglossia) I will use \language=\l@nohyphenation instead.
\l@latex = a dialect from \language\l@nohyphenation
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \__prop_item:nnn was complete.
<to be read again>
\par
l.16 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Argument of \__prop_item:nnn has an extra }.
<inserted text>
\par
l.16 }
(That makes 100 errors; please try again.)
Here is how much of TeX's memory you used:
5307 strings out of 409617
143618 string characters out of 5772185
1917191 words of memory out of 5000000
27413 multiletter control sequences out of 15000+600000
558085 words of font info for 38 fonts, out of 8000000 for 9000
1348 hyphenation exceptions out of 8191
108i,1n,107p,299b,100s stack positions out of 10000i,1000n,20000p,200000b,200000s
No pages of output.