On Tue, Apr 2, 2013 at 4:23 AM, Guenter Milde <mi...@users.sf.net> wrote: > On 2013-04-01, Scott Kostyshak wrote: >> On Mon, Apr 1, 2013 at 6:37 PM, Scott Kostyshak <skost...@lyx.org> wrote: >>> As Georg explained, files included via \verbatiminput need to be in >>> the currently active encoding (where \verbatiminput is placed). Since >>> the encoding is set to auto in the .lyx file, the encoding of the .tex >>> file is latin9 in case of output for standard latex/pdflatex, and it >>> is utf8 for xetex/luatex. > > Please note, that this problem is not constrained to "verbatim" input, but > to all kinds of input files!
OK. > Pardon my ignorance. How does the patch solve/work around the problem? The idea is that many users have the default output format set in their preferences (File Handling > File Formats). If they have it set to PDF (luatex), then when they go to view the help file they will get errors. The document default output format overrides the preferences default output format. So if that is set to PDF (pdflatex), then no matter what they have in preferences the document will compile for them. >> Is this acceptable for now? > > I would either set the "LaTeX encoding" to utf8 and provide the > to-be-included file in utf8 encoding I think that Georg suggested that it's possible this could have other side effects. > , or use a to-be-included file with > only ASCII characters (i.e. compatible with all latin-* encodings and > utf-8). I sent an email to the French list and got no response for changing the example. I'm guessing this problem happens with other manuals and finding native speakers for each one seems difficult. I could replace the included file with something in English as the content does not really matter, but I'm not sure what others think of this. >> If so, I will open a ticket that suggests removing the default format >> if UTF-8 becomes the default. This depends on #8600, #8408, and #6789. > > * As a first step, I would rename the "default encoding". > (Maybe something like "8-bit language default (multi)"). > > * Then, we can change the "LaTeX encoding" default value: > > - Without prerequisites, we may set the default to the language's > default 8-bit encoding (latin-* from "languages") for the complete > document (i.e. also for included text in other languages). The > translations in "unicodesymbols" will ensure proper compilation of > all characters that can be represented with 8-bit LaTeX. > > While this will not solve the problem of a different encoding with > Lua/XeLaTex, it will ensure a uniform encoding (and hence edibility and > conversabitily) of the exported LaTeX source. > > - At least on systems with uft8 support (almost all systems nowadays), > utf8 seems the best choice for the exported LaTeX file's encoding. > >> This depends on #8600, #8408, and #6789. OK, I guess I'm not the best one to open that ticket then because I understand very little of this. > Bug #6789 is about the non-standard "utf8x" (ucs enhanced utf8) > encoding and not related to the "standard" utf8. OK. Thanks for the response and explanations, Guenter. Scott
