Am 20.02.2019 um 22:27 schrieb Stephan Witt <st.w...@gmx.net>: > > Am 20.02.2019 um 20:42 schrieb Joseph M. Kelly <joe61ve...@comcast.net>: >> >> Hi: >> >> First, thanks for making LyX available. I hope to use it to replace Word >> and MathType completely. >> >> I am running Mac OS X 10.13.6. I downloaded and installed the binary of LyX >> v. 2.3.2 thereby replacing an older version. I started reading tutorial and >> decided to convert it to a PDF. That is when I got the export error: >> >> Could not find LaTeX command for character '⌃' (code point 0x2303) >> >> Some characters of your document are probably not representable in the >> chosen encoding. >> Changing the document encoding to utf8 could help. >> >> So, I downloaded and installed the latest Latex version using MacTex >> 20180417. I then deleted LyX from my applications folder and reinstalled it. >> >> Same problem when I try to export either the Tutorial or the User’s Guide. >> >> I tried to run unicode-insert 0x2303 using the LyX command palette but as >> these are read only documents no luck >> >> Any suggestions on how to fix this for all future documents as an up caret ^ >> is used a lot. > > First, I’m able to confirm your issue. The unicode "UP ARROWHEAD“ is > generated by the info-inset for the short-cuts. > > Somehow this is solved with LyX 2.4 but I don’t know how. > > A possible workaround for 2.3 could be to place some TeX code for 0x2303 in > the file unicodesymbols. > You may copy the file /Applications/LyX.app/Contents/Resources/unicodesymbols > to the folder > ~/Library/Application\ Support/LyX-2.3/unicodesymbols and add the TeX code > for it there.
Sorry, I have to correct my wording: you should copy the file unicodesymbols from the folder /Applications/LyX.app/Contents/Resources to the folder ~/Library/Application\ Support/LyX-2.3. Stephan > > I’m not familiar with the syntax of this file and also don’t know the best > TeX code to typeset the character '⌃'. > I’ve tried it with a line like this: > > 0x2303 "Ctrl" "" "" "" "" # UP ARROWHEAD > > and this worked for me. Perhaps some other developer can chime in and propose > a proper solution. > > Hope this helps, > Stephan
