Greetings, thanks to all four for replying and providing pointers to useful information.
On Mon, Jan 07, 2019 at 08:22:56AM +0000, Peter Flynn wrote:
Better still, if you have control of the origination, is to use UTF-8 character encoding and XeLaTeX, avoid character entity references entirely (except for & of course).
Your remark made me think of something: does there exist a clever program that parses LaTeX code and replaces all $\mu$ occurrences (and such) into their corresponding actual Unicode code so that these letters show properly when the document is opened in an Unicode-capable terminal (I use vim)? That might well be a solution to at least handle the situationr: going through the character selection process for each one is pedestrian! Regards, Filippo -- ⢀⣴⠾⠻⢶⣦⠀ Filippo Rusconi, PhD ⣾⠁⢠⠒⠀⣿⡁ Scientist at CNRS ⢿⡄⠘⠷⠚⠋⠀ Debian Developer ⠈⠳⣄⠀⠀⠀⠀ http://msxpertsuite.org http://www.debian.org ~~~~ book: http://www.lavoisier.fr/livre/notice.asp?id=3LKW2OAR2KROWZ http://books.google.fr/books?id=2NmguxmEI1sC&printsec=frontcover&dq=rusconi+f+lavoisier&hl=fr&sa=X&ei=nGGOUt2SH_Ly0gX0uIHoBQ&ved=0CDUQ6AEwAA#v=onepage&q&f=false ~~~~ Génétique Quantitative et Évolution & Plateforme PAPPSO UMR CNRS 8120 – INRA – Université Paris-Sud – AgroParisTech - Université Paris-Saclay http://moulon.inra.fr/ & http://pappso.inra.fr/ Ferme du Moulon 91190 Gif-sur-Yvette France Tel : +33 (0)1 69 33 23 54 Fax : +33 (0)1 69 33 23 40 --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
