On Nov 23, 2007 3:11 PM, Arthur Reutenauer wrote:
... Hmmm .... when thinking agin ... I know that you asked me which regime name to pass to XeTeX and I said "don't worry, it should be more or less the same", but "8859-1" isn't valid regime name either. I'll take a look and report back.
The recent archives from the XeTeX list seem to yield \XeTeXinputencoding{utf8} or \XeTeXinputencoding "ISO-8859-1". I assume that both syntaxes are recognized by XeTeX (with curly braces or double quotes).
No, it's not about the syntax, but rather about the list of accepted names for input encodings. Apart from those three in regi-syn (only left for backward-compatibility): \defineregimesynonym [windows] [cp1252] \defineregimesynonym [grk] [8859-7] \defineregimesynonym [iso88595] [8859-5] and maybe some others in regi-cyp/cyr, XeTeX seems to accept a wide variety of names, so I would suggest the following fix in regi-ini.mkii: \beginXETEX % no idea what these do, but may be left if needed: \let\mkloadregime \gobbleoneargument \let\mkenableregime \gobbleoneargument \let\mkwalkregime \gobbleoneargument \let\mkautosetregime\gobbletwoarguments % sets input encoding to whatever the user asks for. utf is mapped to utf-8 \def\enableregime[#1]% {\doifelse{#1}{utf}% {\message{Specifying UTF-8 input encoding/regime is not needed in XeTeX, but if you do it,}% \message{please use [backslash] enableregime[utf-8] instead of [utf].}% \edef\currentregime{utf-8}}{\edef\currentregime{#1}}% \doifnot{\currentregime}{utf-8}{\message{You are highly encouraged to switch over to UTF-8 input encoding.}}% \XeTeXinputencoding{\currentregime}% \message{Using input encoding/regime \currentregime}} \endXETEX Mojca