I try to to make agda code using unicode characters such as greek characters readable in a LaTeX2e file (which uses a lmcs.cls file http://www.lmcs-online.org/Information/lmcs.cls ). So, I cannot use XeLaTeX instead as recommended to similar problem.
More precisely I added the necessary lines from http://wiki.portal.chalmers.se/agda/pmwiki.php?n=Main.LiterateAgda to my file. As described there, it can happen that certain unicode characters are still not yet available and need to be declared separately.
Here is a (possibly minimal) example:
\documentclass{lmcs}
\usepackage{ucs}
\usepackage[utf8x]{inputenc}
\usepackage{autofe}
\usepackage[greek,english]{babel} %note: after loading autofe
\DeclareUnicodeCharacter{"03B9}{\textiota} % ι
\DeclareUnicodeCharacter{"27E6}{\llbracket}
\begin{document}
ι
⟦
\end{document}
The problems with this are: 1)even if there is no error message, \textiota is not displayed in the pdf output, 2) there is an error message Undefined control sequence. \u-document-10214 #1->\llbracket
\DeclareUnicodeCharacter{"03B9}{\textiota}- note the use of". – Werner Feb 24 '17 at 01:17”! The correct character is". – Paul Gaborit Feb 24 '17 at 06:06utf8xoption, what do you expect? [Not sure aboutucs- is that useful?] – cfr Feb 25 '17 at 00:45\DeclareUnicodeCharacter{”03B9}{\textiota}instead of\DeclareUnicodeCharacter{"03B9}{\textiota}(note the difference between”and"). – Paul Gaborit Feb 25 '17 at 06:35articleit works for me. If not , please give a link for the class. – cfr Mar 07 '17 at 02:14lmcs.clsworks fine when processing with XeLaTeX. LaTeX2e is a format; XeTeX is an engine; XeLaTeX is shorthand for LaTeX to be processed by XeTeX. There are a few instances where your choice of engine matters, but this does not appear to be the case. Perhaps this glorified glossary will help. – Sean Allred Mar 07 '17 at 03:06\documentclassmeans you are using the LaTeX format. But why can't you use a different engine? There is nothing in theclsfile that seems to forbid it. More importantly, however, the usual advice is to avoid theucspackage andutf8xencoding. See, e.g., this answer; but I think you can find the advice repeated fairly often in different questions (here's the search results). – jon Mar 07 '17 at 03:45