On 2013-02-17, Georg Baum wrote:
> Guenter Milde wrote:
>> Dear LyX developers,
>> the "unicodesymbols" file contains many replacements that require the
>> "textcomp" package. Some are "forced", others not, e.g.
>> 0x00a9 "\\textcopyright" "textcomp" "" # COPYRIGHT SIGN
>> 0x00ac "\\textlnot" "textcomp" "force" "\\neg" "" # ¬ NOT
>> SIGN
>> In both cases, the textcomp package is autoloaded if the character exists
>> in the document.
>> With the LaTeX input encoding "Unicode (utf8)"
>> (i.e. \usepackage[utf8]{inputenc}), a set of 77 "textcomp"-symbols
>> can be input as literal Unicode character if the textcomp package is
>> loaded. These characters do not need "forced" replacement for "utf8".
>> I suggest a syntax enhancement "force!=..." matching the newly specified
>> "force=...":
> This is not needed: the simple force flag does not force for any utf8
> encoding. It worked always like that, but now I added an explanation to the
> unicodesymbols file.
The "force" flag is ignored for Unicode (XeTeX) and Unicode (utf8x) but
valid for Unicode (utf8). This is intentional, because inputenc's utf8
option supports only a relatively small subset of Unicode.
It used to be this way since I started working on the unicodesymbols file
and works still so in trunk as seen by this View>Source output:
% Quellcode vorschauen
%% LyX 2.1.0dev created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[english]{article}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{textcomp}
\usepackage{babel}
\begin{document}
Grüße \textlnot{}
\end{document}
This is also the reason for the problem described in bug
http://www.lyx.org/trac/ticket/8509 and its predecessor
http://www.lyx.org/trac/ticket/8040
Please adjust the explanation and reconsider.
Günter
