> "Stephan" == Stephan Witt <[EMAIL PROTECTED]> writes:
Stephan> I read this in the lyxrc too, but I cannot find the code for
Stephan> that. My experience is that uncommenting \font_encoding
Stephan> yields better results. If not uncommented, there is no
Stephan> \usepackage[T1]{fontenc} in
Lars Gullik Bjønnes wrote:
>
> >> Daniel Naber writes:
>
> DN> Stephan Witt wrote:
> >> + uncomment the line \font_encoding T1 in your lyxrc + change in
> >> Layout->Document - Sprache (Language) => german - Kodierung (?)
> >> => latin1
> >>
> >> You shouldn't need to change the pr
>> Daniel Naber writes:
DN> Stephan Witt wrote:
>> + uncomment the line \font_encoding T1 in your lyxrc + change in
>> Layout->Document - Sprache (Language) => german - Kodierung (?)
>> => latin1
>>
>> You shouldn't need to change the preamble for this.
DN> I see. IMHO, we shoul
Stephan Witt wrote:
> + uncomment the line \font_encoding T1 in your lyxrc
> + change in Layout->Document
> - Sprache (Language) => german
> - Kodierung (?) => latin1
>
> You shouldn't need to change the preamble for this.
I see. IMHO, we should add to splash.lyx, how much you can conf
Daniel Naber wrote:
>
> Hi,
>
> I found this hint on the users mailing list. If you use long words
> containing german umlauts, the words won't break. This as an preamble
> fixes it (or works around it) - you need the babel package etc. installed,
> of course:
>
> % allow extended characters in
Hi,
I found this hint on the users mailing list. If you use long words
containing german umlauts, the words won't break. This as an preamble
fixes it (or works around it) - you need the babel package etc. installed,
of course:
% allow extended characters in fonts
% -- needed for automatic hyphe
