Michael Gerz wrote:
> Herbert Voss schrieb:
>> Michael Gerz wrote:
>>
>>> this patch brings change tracking output to the PDF world.
>>>
>>
>>
>>> +static string const changetracking_xcolorsoul_def =
>>> + "\\newcommand{\\lyxinserted}[3]{\\textcolor{blue}{#3}}\n"
>>> + "\\newcommand{\\lyxdeleted}[3]{\\textcolor{red}{\\st{#3}}}\n";
>>>
>>
>> why are the colors hardcoded?
>>
>> better, _after_ the user preamble:
>>
>> \providecolor{lyxinserted}{rgb}{1,0,0}
>> \providecolor{lyxdeleted}{rgb}{0,0,1}
>>
>>
>> + "\\newcommand{\\lyxinserted}[3]{\\textcolor{lyxinserted}{#3}}\n"
>> +
>> "\\newcommand{\\lyxdeleted}[3]{\\textcolor{lyxdeleted}{\\st{#3}}}\n";
>>
>>
>> then the user can define his own colors in his own color model.
>>
> I may be wrong but AFAICS, all LyX header stuff is above the user
> preamble, probably in order to give the user the opportunity to
> overwrite the LyX settings.
>
> Isn't that possible in this scenario, too? Any help is greatly appreciated.
look for babel, it is loaded after the user stuff, see
BufferParams::writeLaTeX
at least you can define it by \AtBeginDocument{..., just like LyX
does for the itemize bullets.
Herbert
