On Mon, Oct 15, 2007 at 02:49:27PM +0200, Jean-Marc Lasgouttes wrote: > Enrico Forestieri <[EMAIL PROTECTED]> writes: > > > That's in response to a precise request from me and not done without > > my consent. For example, the first thing I do when forced to use Word, > > is deactivating that stupid "feature" about underlining in red unknown > > words. > > If the error happens at latex export time, it would be trivial to add > error to the errorlist, like we already do for a few errors (I think).
Yes, it happens at export time. I also think that it would be trivial dealing with this kind of error, when you already know the code... > >> > A quick way to discover if there's a problem, is activating View->Source > >> > and looking at the warnings in the terminal from where you started LyX. > >> > >> This is not user friendly. Average users will be lost when they get the > >> encoding error, because they don't know LaTeX's error handling. > > I agree with Uwe here. This is a highly technical and unpleasant side > of LaTeX. Note that it is LyX issuing the warnings when you View->Source: Could not find LaTeX command for character 0x3e2. LaTeX export will fail. -- Enrico
