Richard Heck wrote:
>>
>> "Herbert" == Herbert Voss
>> <[EMAIL PROTECTED]> writes:
>> Herbert> sorry, I cannot follow here
>>
>> Herbert> dvips -Pabc uses a config.abc file which declares
>> Herbert> resolution, font
Richard Heck wrote:
> Herbert Voss wrote:
>> Richard Heck wrote:
>>
>>> [EMAIL PROTECTED] src]$ find /usr/share/texmf/dvips/ -name 'config.*'
>>> /usr/share/texmf/dvips/tetex/config.www
>>> /usr/share/texmf/dvips/tetex/config.download35
>>> /u
Enrico Forestieri wrote:
>> config. is misleading. For example: config.pdf is a config file
>> to use always Type 1 fonts but I can print the ps file on _every_ printer
>
> Granted. But what if you have 300, 600, and 1200 dpi printers?
> The "Adapt Output" thing let you adapt (sic!) the pk fonts
Michael Gerz wrote:
- What happens if neither floating nor inline is activated? (Confusing)
I suppose that the user gets a listing, which is not a flot and not in a
line ... ;-)
How could this be confusing??? A listing is in the first case a listing
and it can be inlined or not or a float or
Uwe Stöhr wrote:
Andre Poenitz schrieb:
(Using \={} is too short for the OVERLINE, it has to be the same
length as \_ )
\raisebox{1.3ex}{\_}
This is too low, the overline has to be in the same height as the bar
above an M: \=M
I found out that this would then be
\raisebox{2.61ex}{\_}
Uwe Stöhr wrote:
\newcommand*\LyXrightangle{{\usefont{U}{msa}{m}{n}\char120}}
Many thanks.
Where is a table to look what number corresponds to what character in
the font files? I seared for a code chart table for msam and msbm but
couldn't found this character there.
Now only these
Juergen Spitzmueller wrote:
Herbert Voss wrote:
\newcommand*\DEL{{\fontencoding{U}\fontfamily{ascii}\selectfont\char127}}
perhaps \providecommand (in case the ascii package is already loaded).
but only in this case, the other way round works ... :-)
Herbert
Uwe Stöhr wrote:
yes, that's right, but is save to use
\newcommand*\oline{\ensuremath{\overline{\phantom{A
But then the line is a bit too long when I compare:
_
\ensuremath{\underline{\overline{\phantom{A
replace the A bei I
2302 HOUSE: ⌂
Michael Gerz wrote:
> - What happens if neither "floating" nor "inline" is activated? (Confusing)
I suppose that the user gets a listing, which is not a flot and not in a
line ... ;-)
How could this be confusing??? A listing is in the first case a listing
and it can be inlined or not or a float
Uwe Stöhr wrote:
> Andre Poenitz schrieb:
>
>>> (Using \={} is too short for the OVERLINE, it has to be the same
>>> length as \_ )
>>
>> \raisebox{1.3ex}{\_}
>
> This is too low, the overline has to be in the same height as the bar
> above an "M": \=M
> I found out that this would then be
>
Uwe Stöhr wrote:
>> \newcommand*\LyXrightangle{{\usefont{U}{msa}{m}{n}\char120}}
>
> Many thanks.
> Where is a table to look what number corresponds to what character in
> the font files? I seared for a code chart table for msam and msbm but
> couldn't found this character there.
>
> Now only
Juergen Spitzmueller wrote:
> Herbert Voss wrote:
>
>> \newcommand*\DEL{{\fontencoding{U}\fontfamily{ascii}\selectfont\char127}}
>
> perhaps \providecommand (in case the ascii package is already loaded).
but only in this case, the other way round works ... :-)
Herbert
Uwe Stöhr wrote:
>> yes, that's right, but is save to use
>>
>> \newcommand*\oline{\ensuremath{\overline{\phantom{A
>
> But then the line is a bit too long when I compare:
>
> _
> \ensuremath{\underline{\overline{\phantom{A
replace the A bei I
>
>
>>> 2302 HOUSE:
Uwe Stöhr wrote:
\\newcommand{\\lyxcareof}{\\leavevmode\\hbox{\\raise.75ex\\hbox{c}\\kern-.15em/\\kern-.125em\\smash{\\lower.3ex\\hbox{o}}}\\ignorespaces}
\newcommand*\lyxcareof{%
\mbox{\raisebox{.8ex}{c}\kern-.175em\raisebox{.2ex}{/}%
\kern-.18em\raisebox{-.2ex}{o}}}
Thanks I use now
Uwe Stöhr wrote:
>>>"\\newcommand{\\lyxcareof}{\\leavevmode\\hbox{\\raise.75ex\\hbox{c}\\kern-.15em/\\kern-.125em\\smash{\\lower.3ex\\hbox{o}}}\\ignorespaces}"
>
>>> ""
>>
>> \newcommand*\lyxcareof{%
>> \mbox{\raisebox{.8ex}{c}\kern-.175em\raisebox{.2ex}{/}%
>> \kern-.18em\raisebox{-.2ex}{o}}}
Uwe Stöhr wrote:
But I would do it like this:
0x2105 \\lyxcareof \\newcommand{\\lyxcareof}
{\\leavevmode\\hbox{\\raise.75ex\\hbox{c}\\kern-.15em/\\kern-.125em\\smash{\\lower.3ex\\hbox{o}}}\\ignorespaces}
# CARE OF
This doesn't work but this:
# following macro for the CARE OF
Uwe Stöhr wrote:
>> But I would do it like this:
>>
>> 0x2105 "\\lyxcareof" "" "\\newcommand{\\lyxcareof}
>>
> {\\leavevmode\\hbox{\\raise.75ex\\hbox{c}\\kern-.15em/\\kern-.125em\\smash{\\lower.3ex\\hbox{o}}}\\ignorespaces}"
>
>>
>> # CARE OF
>
> This doesn't work but this:
>
> # following
Jürgen Spitzmüller wrote:
Michael Gerz wrote:
I wonder whether we should drop the dvipdfm path for 1.5.X. Is anybody
actually using this (possibly outdated) tool? Offering tree ways to
generate PDF may cause more confusion than it brings benefits.
No.
dvipdfmx is neither useless nor
Jürgen Spitzmüller wrote:
Herbert Voss wrote:
dvipdfmx is neither useless nor outdated:
http://project.ktug.or.kr/dvipdfmx/
dvipdfm is useless ...
But we use dvipdfmx (if available).
there is also a xdvipdfmx
what's its benefit?
- XeTeX
Herbert
Jürgen Spitzmüller wrote:
Herbert Voss wrote:
- XeTeX
So dvipdfmx is still the right thing to choose, unless people use XeTeX
(where
they currently need to change the converters manually anyway).
I never used it but I suppose, that using xdvipdfmx doesn't hurt, it
does the same
[EMAIL PROTECTED]
as inline listing doesn't work, because the inset uses
# as delimiter, which is not allowed.
-- let the user choose from a list a delimiter, or
-- do not choose \ @ # ^ _ ~ $ as delimiter
Herbert
Bo Peng wrote:
On 5/26/07, Herbert Voss
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]
as inline listing doesn't work, because the inset uses
# as delimiter, which is not allowed.
-- let the user choose from a list a delimiter, or
-- do not choose \ @ # ^ _ ~ $ as delimiter
I think I
Jürgen Spitzmüller wrote:
> Michael Gerz wrote:
>> I wonder whether we should drop the dvipdfm path for 1.5.X. Is anybody
>> actually using this (possibly outdated) tool? Offering tree ways to
>> generate PDF may cause more confusion than it brings benefits.
>
> No.
> dvipdfmx is neither useless
Jürgen Spitzmüller wrote:
> Herbert Voss wrote:
>>> dvipdfmx is neither useless nor outdated:
>>> http://project.ktug.or.kr/dvipdfmx/
>> dvipdfm is useless ...
>
> But we use dvipdfmx (if available).
>
>> there is also a xdvipdfmx
>
> what's its benefit?
-> XeTeX
Herbert
Jürgen Spitzmüller wrote:
> Herbert Voss wrote:
>> -> XeTeX
>
> So dvipdfmx is still the right thing to choose, unless people use XeTeX
> (where
> they currently need to change the converters manually anyway).
I never used it but I suppose, that using xdvipdfmx doesn'
[EMAIL PROTECTED]
as inline listing doesn't work, because the inset uses
# as delimiter, which is not allowed.
-- let the user choose from a list a delimiter, or
-- do not choose \ & @ # ^ _ ~ $ as delimiter
Herbert
Bo Peng wrote:
> On 5/26/07, Herbert Voss
> <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED]
>> as inline listing doesn't work, because the inset uses
>> # as delimiter, which is not allowed.
>>
>> -- let the user choose from a list a delimiter, or
>&g
Bo Peng wrote:
you cannot export \lstinline{foo}, ist must be something of
\lstinlinecharfoochar
where char is a free choosen delimiter. Otherwise you cannot write
something like \lstinline{\textbf{foo}}. Must be
\lstinline|\textbf{foo}| or any other character than |.
The listings manual
Bo Peng wrote:
>> you cannot export \lstinline{foo}, ist must be something of
>> \lstinlinefoo
>> where is a free choosen delimiter. Otherwise you cannot write
>> something like \lstinline{\textbf{foo}}. Must be
>> \lstinline|\textbf{foo}| or any other character than |.
>
> The listings manual
Helge Hafting wrote:
%% LyX 1.5.0svn created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[a4paper,twoside,norsk,smallheadings]{article}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
Bo Peng wrote:
On 5/24/07, Helge Hafting
[EMAIL PROTECTED] wrote:
A lyx file and the resulting tex file.
latexing this:
No file listinginline.aux.
)
Runaway argument?
{test}^^M\end{document}^^M
! File ended while scanning use of [EMAIL PROTECTED]
inserted text
\par
*
Helge Hafting wrote:
> %% LyX 1.5.0svn created this file. For more info, see http://www.lyx.org/.
> %% Do not edit unless you really know what you are doing.
> \documentclass[a4paper,twoside,norsk,smallheadings]{article}
> \usepackage[T1]{fontenc}
> \usepackage[latin9]{inputenc}
>
Bo Peng wrote:
> On 5/24/07, Helge Hafting
> <[EMAIL PROTECTED]> wrote:
>> A lyx file and the resulting tex file.
>>
>> latexing this:
>> No file listinginline.aux.
>> )
>> Runaway argument?
>> {test}^^M\end{document}^^M
>> ! File ended while scanning use of [EMAIL PROTECTED]
>>
>>
Jürgen Spitzmüller wrote:
Jürgen Spitzmüller wrote:
Fine with me. Please commit once you got another OK.
Thanks for committing. I've found one remainder in my tree, an adjustment to
a
comment. I let you decide on that (and commit).
I'm away from my machine now.
Jürgen
Uwe Stöhr wrote:
I don't like this. Both the old tooltip and icon were correct.
It is not correct, please look at the bugreport. The user thinks when
clicking on this button that these settings are about sums or limits but
both is incorrect. You can use these commands for all constructs!
Juergen Spitzmueller wrote:
Bo Peng wrote:
I think Herbert refers to the ! character, as in !ht.
I do not see this anywhere in the manual.
From what I understand in the listings sourcde, only tbp are valid.
from the _manual_ *tbph for float and tbp for floatplacement
Herbert
Uwe Stöhr wrote:
I find them very useful when I don't like
the default sizes TeX uses in fractions, for example.
Better use the commands \cfrac, \tfrac, etc. in this case.
I would not use
them simply for changing the limits style.
But this is not the intention of these commands, they
Enrico Forestieri wrote:
On Wed, May 23, 2007 at 05:38:21PM +0200, Jean-Marc Lasgouttes wrote:
Enrico == Enrico Forestieri [EMAIL PROTECTED] writes:
Enrico Going further in your reasoning we should also make difficult
Enrico the use of tables as many people misuse them, too!
I know you
Jürgen Spitzmüller wrote:
> Jürgen Spitzmüller wrote:
>> Fine with me. Please commit once you got another OK.
>
> Thanks for committing. I've found one remainder in my tree, an adjustment to
> a
> comment. I let you decide on that (and commit).
> I'm away from my machine now.
>
> Jürgen
>
>
Uwe Stöhr wrote:
>> I don't like this. Both the old tooltip and icon were correct.
>
> It is not correct, please look at the bugreport. The user thinks when
> clicking on this button that these settings are about sums or limits but
> both is incorrect. You can use these commands for all
Juergen Spitzmueller wrote:
> Bo Peng wrote:
>
>>> I think Herbert refers to the character, as in "!ht".
>> I do not see this anywhere in the manual.
>
> From what I understand in the listings sourcde, only "tbp" are valid.
from the _manual_ *tbph for float and tbp for floatplacement
Herbert
Uwe Stöhr wrote:
>> I find them very useful when I don't like
>> the default sizes TeX uses in fractions, for example.
>
> Better use the commands \cfrac, \tfrac, etc. in this case.
>
>> I would not use
>> them simply for changing the limits style.
>
> But this is not the intention of these
Enrico Forestieri wrote:
> On Wed, May 23, 2007 at 05:38:21PM +0200, Jean-Marc Lasgouttes wrote:
>>> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
>> Enrico> Going further in your reasoning we should also make difficult
>> Enrico> the use of tables as many people misuse them,
Enrico Forestieri wrote:
On Mon, May 21, 2007 at 05:21:51PM +0200, Jean-Marc Lasgouttes wrote:
Darren == Darren Freeman [EMAIL PROTECTED] writes:
Darren On Mon, 2007-05-21 at 16:16 +0200, Herbert Voss wrote:
{Ge}^3 is different to
Ge^3 and G^3 and e^3, which have all the same vertical
Enrico Forestieri wrote:
On Mon, May 21, 2007 at 07:28:40PM +0200, Andre Poenitz wrote:
On Mon, May 21, 2007 at 11:12:33PM +1000, Darren Freeman wrote:
On Mon, 2007-05-21 at 14:52 +0200, Abdelrazak Younes wrote:
Darren Freeman wrote:
Is this sensible? Does it have meaning at the LaTeX level
Richard Heck wrote:
This patch has been to the list previously and been more or less
approved. I'm sending it again, however, as I've made some additional
changes and it should be tested by at least one other person, I think,
before I commit. If you do test, please test: (i) ViewHTML; (ii)
Georg Baum wrote:
??
With latin9 you get a working \textdegree ...
and also some other symbols different to latin1
Sure, \textdegree does not depend on the inputenc package.
??? \inputenc does nothing else than loading
the definition file ...
What does not work with
Jürgen Spitzmüller wrote:
So the problem is: what can we do with $\textdegree$ and $°$ in case textcomp
is requested?
a _correct_ and save way is to do nothing inside LyX and using
always the LaTeX definitions. In fact of some compatibility
you can do inside LyX
Enrico Forestieri wrote:
> On Mon, May 21, 2007 at 05:21:51PM +0200, Jean-Marc Lasgouttes wrote:
>
>>>>>>> "Darren" == Darren Freeman <[EMAIL PROTECTED]> writes:
>> Darren> On Mon, 2007-05-21 at 16:16 +0200, Herbert Voss wrote:
>>>&
Enrico Forestieri wrote:
> On Mon, May 21, 2007 at 07:28:40PM +0200, Andre Poenitz wrote:
>
>> On Mon, May 21, 2007 at 11:12:33PM +1000, Darren Freeman wrote:
>>> On Mon, 2007-05-21 at 14:52 +0200, Abdelrazak Younes wrote:
Darren Freeman wrote:
> Is this sensible? Does it have meaning at
Richard Heck wrote:
> This patch has been to the list previously and been more or less
> approved. I'm sending it again, however, as I've made some additional
> changes and it should be tested by at least one other person, I think,
> before I commit. If you do test, please test: (i) View>HTML;
Georg Baum wrote:
>>
>> ??
>> With latin9 you get a working \textdegree ...
>> and also some other symbols different to latin1
>
> Sure, \textdegree does not depend on the inputenc package.
??? \inputenc does nothing else than loading
the definition file ...
> What does not work with
Jürgen Spitzmüller wrote:
> So the problem is: what can we do with $\textdegree$ and $°$ in case textcomp
> is requested?
a _correct_ and save way is to do nothing inside LyX and using
always the LaTeX definitions. In fact of some compatibility
you can do inside LyX
Jean-Marc Lasgouttes wrote:
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
As I was asking, does this really mean anything?
Abdelrazak I _don't_ know. But I guess that if the TeX source is
Abdelrazak different, there should be a reason.
The vertical alignment depends on the
Abdelrazak Younes wrote:
There's some problems with \textdegree reported on the users list that I
can easily reproduce. With the attached LyX file, the LateX export will
translate the degree symbol in mathed to \textdegree.
Neither the dvi nor the pdf (pdflatex) file shows the \textdegree
Georg Baum wrote:
Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
There's some problems with \textdegree reported on the users list that I
can easily reproduce. With the attached LyX file, the LateX export will
translate the degree symbol in mathed to
Abdelrazak Younes wrote:
Right, if I insert \textdegree inside an ERT, the degree symbol is
shown. So, the correction would be to automatically encapsulate
\textdegree inside an mbox when with mathed. Is it possible to do that
thanks to some definition in lib/symbols?
No. With ERT you are
Jürgen Spitzmüller wrote:
Herbert Voss wrote:
with latin9 encoding it works in math and text mode anymay.
but as soon as textcomp is loaded, it fails:
\documentclass[english]{article}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage{textcomp} %---
\usepackage{babel
Jean-Marc Lasgouttes wrote:
>> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
>>> As I was asking, does this really mean anything?
>
> Abdelrazak> I _don't_ know. But I guess that if the TeX source is
> Abdelrazak> different, there should be a reason.
>
> The vertical
Abdelrazak Younes wrote:
> There's some problems with \textdegree reported on the users list that I
> can easily reproduce. With the attached LyX file, the LateX export will
> translate the degree symbol in mathed to \textdegree.
>
> Neither the dvi nor the pdf (pdflatex) file shows the
Georg Baum wrote:
> Abdelrazak Younes wrote:
>
>> Jürgen Spitzmüller wrote:
>>> Abdelrazak Younes wrote:
There's some problems with \textdegree reported on the users list that I
can easily reproduce. With the attached LyX file, the LateX export will
translate the degree symbol in
Abdelrazak Younes wrote:
>>> Right, if I insert \textdegree inside an ERT, the degree symbol is
>>> shown. So, the correction would be to automatically encapsulate
>>> \textdegree inside an mbox when with mathed. Is it possible to do that
>>> thanks to some definition in lib/symbols?
>>
>> No.
Jürgen Spitzmüller wrote:
> Herbert Voss wrote:
>> with latin9 encoding it works in math and text mode anymay.
>
> but as soon as textcomp is loaded, it fails:
>
> \documentclass[english]{article}
> \usepackage[T1]{fontenc}
> \usepackage[latin9]{input
Martin Vermeer wrote:
On Thu, May 17, 2007 at 11:32:54PM +0100, José Matos wrote:
On Monday 07 May 2007 11:02:29 pm Micha Feigin wrote:
Sorry, got it wrong, missed the special == none in the lyx file and the
not is binary instead of logical (too many programing languages in parallel
... )
Martin Vermeer wrote:
On Fri, May 18, 2007 at 09:04:39AM +0200, Herbert Voss wrote:
Martin Vermeer wrote:
On Thu, May 17, 2007 at 11:32:54PM +0100, José Matos wrote:
On Monday 07 May 2007 11:02:29 pm Micha Feigin wrote:
Sorry, got it wrong, missed the special == none in the lyx file
Herbert Voss wrote:
Martin Vermeer wrote:
On Fri, May 18, 2007 at 09:04:39AM +0200, Herbert Voss wrote:
Martin Vermeer wrote:
On Thu, May 17, 2007 at 11:32:54PM +0100, José Matos wrote:
On Monday 07 May 2007 11:02:29 pm Micha Feigin wrote:
Sorry, got it wrong, missed the special == none
Martin Vermeer wrote:
> On Thu, May 17, 2007 at 11:32:54PM +0100, José Matos wrote:
>> On Monday 07 May 2007 11:02:29 pm Micha Feigin wrote:
>>> Sorry, got it wrong, missed the special == "none" in the lyx file and the
>>> not is binary instead of logical (too many programing languages in parallel
Martin Vermeer wrote:
> On Fri, May 18, 2007 at 09:04:39AM +0200, Herbert Voss wrote:
>> Martin Vermeer wrote:
>>> On Thu, May 17, 2007 at 11:32:54PM +0100, José Matos wrote:
>>>> On Monday 07 May 2007 11:02:29 pm Micha Feigin wrote:
>>>>> Sor
Herbert Voss wrote:
> Martin Vermeer wrote:
>> On Fri, May 18, 2007 at 09:04:39AM +0200, Herbert Voss wrote:
>>> Martin Vermeer wrote:
>>>> On Thu, May 17, 2007 at 11:32:54PM +0100, José Matos wrote:
>>>>> On Monday 07 May 2007 11:02:29 pm Micha Fei
Bo Peng wrote:
On 5/16/07, Bo Peng [EMAIL PROTECTED]
wrote:
I did :-) and I am glad that it works! See commit below. What do you
have at the console?
Here is what I get from the console.
% pplatex: Process input file 0lyxpreview.dvi
pplatex: Copy data to 0lyxpreview.dvi
This is
Jean-Marc Lasgouttes wrote:
Yet another glossary package...
no another, the successor ... :-)
Herbert
Bo Peng wrote:
> On 5/16/07, Bo Peng <[EMAIL PROTECTED]>
> wrote:
>> > I did :-) and I am glad that it works! See commit below. What do you
>> > have at the console?
>>
>> Here is what I get from the console.
>>
>> % pplatex: Process input file 0lyxpreview.dvi
>> pplatex: Copy data to
Jean-Marc Lasgouttes wrote:
> Yet another glossary package...
no another, the successor ... :-)
Herbert
Michael Gerz wrote:
Herbert Voss schrieb:
Michael Gerz wrote:
+\TestPackage{pdfcolmk}
is senseless for the current pdftex, which has it already builtin
But there are people with elder versions of pdflatex, I guess. The
latest MikTeX has
MiKTeX-pdfetex 2.5.2645 (1.30.6
Michael Gerz wrote:
> Herbert Voss schrieb:
>> Michael Gerz wrote:
>>
>>
>>> +\TestPackage{pdfcolmk}
>>>
>>
>> is senseless for the current pdftex, which has it already builtin
>>
> But there are people with elder versions
Andre Poenitz wrote:
On Sat, May 12, 2007 at 11:18:50PM +0200, Herbert Voss wrote:
Michael Gerz wrote:
+ \\newcommand{\\lyxinserted}[3]{\\textcolor{blue}{#3}}\n
+ \\newcommand{\\lyxdeleted}[3]{\\textcolor{red}{\\st{#3}}}\n;
I forgot to say, that you should choose names like
[EMAIL
Michael Gerz wrote:
+\TestPackage{pdfcolmk}
is senseless for the current pdftex, which has it already builtin
\TestPackage{prettyref}
\TestPackage{preview}
\TestPackage{rotating}
\TestPackage{setspace}
+\TestPackage{soul}
\TestPackage{subfigure}
subfigure is superseeded by subfig
Jürgen Spitzmüller wrote:
Michael Gerz wrote:
After Wednesday. Currently, I am swamped with work.
I'll do that. Furthermore, I have fixed an assert because lyxasserted and
lyxdeleted did not have proper x11 names. I wonder why you did not run
accross that.
I detected another problem:
Jürgen Spitzmüller wrote:
Herbert Voss wrote:
where is the sense having the spaces inside the argument?
The macro embraces all newly added text. So if I have a phrase
this is it.
and add
this is it now.
the lyxdeleted macro includes the preceding blank, because it belongs to the
added
Andre Poenitz wrote:
> On Sat, May 12, 2007 at 11:18:50PM +0200, Herbert Voss wrote:
>> Michael Gerz wrote:
>>
>>> + "\\newcommand{\\lyxinserted}[3]{\\textcolor{blue}{#3}}\n"
>>> + "\\newcommand{\\lyxdeleted}[3]{\\textcolor{red}{\\st{#3}}}\n
Michael Gerz wrote:
> +\TestPackage{pdfcolmk}
is senseless for the current pdftex, which has it already builtin
> \TestPackage{prettyref}
> \TestPackage{preview}
> \TestPackage{rotating}
> \TestPackage{setspace}
> +\TestPackage{soul}
> \TestPackage{subfigure}
subfigure is superseeded by
Jürgen Spitzmüller wrote:
> Michael Gerz wrote:
>> After Wednesday. Currently, I am swamped with work.
>
> I'll do that. Furthermore, I have fixed an assert because lyxasserted and
> lyxdeleted did not have proper x11 names. I wonder why you did not run
> accross that.
>
> I detected another
Jürgen Spitzmüller wrote:
> Herbert Voss wrote:
>> where is the sense having the spaces inside the argument?
>
> The macro embraces all newly added text. So if I have a phrase
> "this is it."
> and add
> "this is it now."
> the lyxdeleted macro i
Michael Gerz wrote:
does anybody know why the following LaTeX construct (soul + xcolor) does
not work:
\st{\textcolor{red}{hello world}}}
Error message:
Package xcolor Error: Undefined color `{red}'.
...
It seems like soul is very picky about its arguments. If nobody knows a
Michael Gerz wrote:
Herbert Voss schrieb:
Michael Gerz wrote:
does anybody know why the following LaTeX construct (soul + xcolor) does
not work:
\st{\textcolor{red}{hello world}}}
Error message:
Package xcolor Error: Undefined color `{red}'.
...
file:///C:/Dokumente%20und
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?
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
Michael Gerz wrote:
+ \\newcommand{\\lyxinserted}[3]{\\textcolor{blue}{#3}}\n
+ \\newcommand{\\lyxdeleted}[3]{\\textcolor{red}{\\st{#3}}}\n;
I forgot to say, that you should choose names like
[EMAIL PROTECTED] and [EMAIL PROTECTED]
Then it is not so easy, that a user chooses such
Michael Gerz wrote:
> does anybody know why the following LaTeX construct (soul + xcolor) does
> not work:
>
> \st{\textcolor{red}{hello world}}}
>
> Error message:
>
> Package xcolor Error: Undefined color `{red}'.
> ...
>
> It seems like soul is very picky about its arguments. If
Michael Gerz wrote:
> Herbert Voss schrieb:
>> Michael Gerz wrote:
>>
>>
>>> does anybody know why the following LaTeX construct (soul + xcolor) does
>>> not work:
>>>
>>> \st{\textcolor{red}{hello world}}}
>>>
>&g
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
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 =
>>> +"\\newcomman
Michael Gerz wrote:
> + "\\newcommand{\\lyxinserted}[3]{\\textcolor{blue}{#3}}\n"
> + "\\newcommand{\\lyxdeleted}[3]{\\textcolor{red}{\\st{#3}}}\n";
I forgot to say, that you should choose names like
[EMAIL PROTECTED] and [EMAIL PROTECTED]
Then it is not so easy, that a user chooses
Jean-Marc Lasgouttes wrote:
Uwe == Uwe Stöhr [EMAIL PROTECTED] writes:
Uwe, I do not understand why lang_opts is passed to babel in the
second if() when lyxrc.language_global_options is true. What was
your intention?
Uwe When lyxrc.language_global_options is true babel is not called
Uwe
Jean-Marc Lasgouttes wrote:
Herbert == Herbert Voss [EMAIL PROTECTED] writes:
Herbert there is a third variant to prevent an option clash if
Herbert another package already loads babel (same for other packages)
Herbert \PassOptionsToPackage{lang1,lang2}{babel}
Herbert before
Jean-Marc Lasgouttes wrote:
>> "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes:
>
>>> Uwe, I do not understand why lang_opts is passed to babel in the
>>> second if() when lyxrc.language_global_options is true. What was
>>> your intention?
>
> Uwe> When lyxrc.language_global_options is true
Jean-Marc Lasgouttes wrote:
>>>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>
> Herbert> there is a third variant to prevent an option clash if
> Herbert> another package already loads babel (same for other packages)
>
Bo Peng wrote:
130 parameters is sheer madness. :-)
+1, sorry Bo...
What are you sorry for? I am not going to validate all 130 parameters
right now, and there will be the GUI designer's decision how to choose
and present the most important parameters, and leave others may be to
a
Bo Peng wrote:
>> > 130 parameters is sheer madness. :-)
>>
>> +1, sorry Bo...
>
> What are you sorry for? I am not going to validate all 130 parameters
> right now, and there will be the GUI designer's decision how to choose
> and present the most important parameters, and leave others may be
Bo Peng wrote:
Attached please find a much improved InsetListings patch. The
implementation can now be reviewed...
Changes:
Better organized InsetListingsParams functions
Autotools support
InsetListings now derives from InsetERT
Use LISTINS_CODE
Code cleaning
and more...
listings
101 - 200 of 2868 matches
Mail list logo
