Uwe Stöhr wrote:
> you recently implemented support for some underlining styles. About a year
> ago I also planned this too and Jürgen convinced me that we need a method
> that works for Unicode too.
> The solution I see is to use the soulutf package while you used the ulem
> package. Have you t
Christian Ridderström wrote:
> It wasn't easy, but I've finally got something... please give it a try.
nice work! thank you :)
pavel
Alex Fernandez wrote:
> As to the first issue, what do you suggest? Maybe a custom copier
> could copy images to /tmp?
either reuse the the already existing copier(s) in our tree our writing
the new one. (i guess that the copiers we already have should be enough.
just look only ho other convetors
Hello Pavel,
you recently implemented support for some underlining styles. About a year ago I also planned this
too and Jürgen convinced me that we need a method that works for Unicode too.
The solution I see is to use the soulutf package while you used the ulem package. Have you tested
that th
Hi Pavel,
On Mon, May 4, 2009 at 12:48 PM, Pavel Sanda wrote:
>> Sorry, I must have missed the question in the turmoil. Can you give me
>> a pointer?
>
> tools -> preferences -> file formats -> html (elyxer) -> copier
>
> see copiers section in customization manual. this maybe the cause why image
Hi Pavel,
It wasn't easy, but I've finally got something... please give it a try.
/Christian
2009/5/3 Pavel Sanda :
> Hello Christian,
>
> have you looked on the issue of remapping
> http://bugzilla.lyx.org/show_bug.cgi?id=5480
> ->
> http://www.lyx.org/trac/ticket/5480
> ?
>
> its pain to rewri
should be this reported to the ulem (or cite) package maintainers?
also do we encounter this in our normal documents with citations?
if it cause too much problem, we can revert it back...
It happens that the author of both packages is Donald Arseneau (aka
one of the masters of the style files).
Isn't that what I was suggesting a few days ago? Well, not quite,
since I was suggesting we just put them all on the menu so that
they're all there to be chosen from, on an ad hoc basis, rather than
making the user go into the preferences or settings or something to
change them. JMarc, what
On Tue, May 05, 2009 at 09:50:04PM +0200, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > I think that ulem is better for underlining but switching to it
> > needs some clever thought... maybe reverting is the easiest thing
> > to do...
>
> no preference here. i will revert it for the time being
On Tue, May 05, 2009 at 09:51:15PM +0200, Peter Kümmel wrote:
> Andre Poenitz wrote:
> > On Sun, May 03, 2009 at 08:22:45PM +0200, Peter Kümmel wrote:
> >> Abdelrazak Younes wrote:
> >> >
> >>> I've been using QProcess extensively recently and it works perfectly
> >>> across platforms. I won't wor
Andre Poenitz wrote:
> On Sun, May 03, 2009 at 08:22:45PM +0200, Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>> >
>>> I've been using QProcess extensively recently and it works perfectly
>>> across platforms. I won't worry about that. The different signals it
>>> emits are very useful. I can c
Enrico Forestieri wrote:
> I think that ulem is better for underlining but switching to it
> needs some clever thought... maybe reverting is the easiest thing
> to do...
no preference here. i will revert it for the time being; whosoever want to make
it work even with citations, feel free to take t
On Tue, May 05, 2009 at 12:54:02PM -0400, rgheck wrote:
> Enrico Forestieri wrote:
> >
> > If someone incurs in this problem, this is the updated workaround:
> >
> > \usepackage{cite}
> > \let\olduline\uline
> > \newsavebox{\cbox}
> > \let\oldcite\cite
> > \newcommand{\newcite}[1]{\sbox\cbox{\oldci
On Tue, May 05, 2009 at 05:39:01PM +0200, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > You just broke a number of old documents of mine, but I guess that is
> > unavoidable. The problem is that ulem is incompatible with the cite
> > package and misterious errors occur when you underline a cita
Pavel Sanda wrote:
Jürgen Spitzmüller wrote:
Yes. In a strict sense, you would have to revert the stuff to ERT. But also
if you do not do that, an empty file format change would be advisable.
i would bet that when we changed from soul to ulem this didnt happen and the
same holds for th
Jürgen Spitzmüller wrote:
Jean-Marc Lasgouttes wrote:
Here comes the first step. This implements the possibility to record all
available programs of a sort in alternative RCs.
I would love to have that for converters, so that configure.py
configures all available converters/viewers,
Enrico Forestieri wrote:
On Tue, May 05, 2009 at 01:52:22PM +0200, Pavel Sanda wrote:
Pavel Sanda wrote:
Jürgen Spitzmüller wrote:
However, now that we have ulem in, we should use it for underlining (if
it is available), such that underlined text is broken across lines.
Pavel Sanda wrote:
> i would bet that when we changed from soul to ulem this didnt happen and
> the same holds for the switch for some boxes or subfloats we have changed
> last year even in branch (cant remember what it was exactly...) in fact i
> seem to be unable to recall when such bumps happen
Jürgen Spitzmüller wrote:
> Yes. In a strict sense, you would have to revert the stuff to ERT. But also
> if you do not do that, an empty file format change would be advisable.
i would bet that when we changed from soul to ulem this didnt happen and the
same holds for the switch for some boxes or
Enrico Forestieri wrote:
> You just broke a number of old documents of mine, but I guess that is
> unavoidable. The problem is that ulem is incompatible with the cite
> package and misterious errors occur when you underline a citation.
should be this reported to the ulem (or cite) package maintain
Pavel Sanda wrote:
>> But you need to bumo the file format.
>
> eh? we increase fileformat any time we change
> latex output?
Yes. In a strict sense, you would have to revert the stuff to ERT. But also
if you do not do that, an empty file format change would be advisable.
Jürgen
Jean-Marc Lasgouttes wrote:
>> Here comes the first step. This implements the possibility to record all
>> available programs of a sort in alternative RCs.
>
> I would love to have that for converters, so that configure.py
> configures all available converters/viewers, not only the first one that
Jürgen Spitzmüller writes:
> Here comes the first step. This implements the possibility to record all
> available programs of a sort in alternative RCs.
I would love to have that for converters, so that configure.py
configures all available converters/viewers, not only the first one that
fits.
On Tue, May 05, 2009 at 01:52:22PM +0200, Pavel Sanda wrote:
> Pavel Sanda wrote:
> > Jürgen Spitzmüller wrote:
> > > However, now that we have ulem in, we should use it for underlining (if
> > > it is available), such that underlined text is broken across lines.
> >
> > i will look whether ulem
Jürgen Spitzmüller wrote:
> But you need to bumo the file format.
eh? we increase fileformat any time we change
latex output?
pavel
Pavel Sanda wrote:
> if you implement only additional parameters for programs detected by
> configure and then run some kind of execvp call rather than the normal
> system call, no additional program can be run that way.
Thanks.
Here comes the first step. This implements the possibility to recor
Pavel Sanda wrote:
> checkout the current trunk if thats what you wanted.
I guess it is. Thanks.
But you need to bumo the file format.
Jürgen
Pavel Sanda wrote:
> Jürgen Spitzmüller wrote:
> > However, now that we have ulem in, we should use it for underlining (if
> > it is available), such that underlined text is broken across lines.
>
> i will look whether ulem supports across lines feature.
checkout the current trunk if thats what
Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>
>> It would be easier to have a nod from the author to include it as is.
>
> This would mean that the author would need to re-release MyThes under the
> GPL, right?
Maybe. I think that Abdel asked him for it, so we'll see.
JMarc
Jean-Marc Lasgouttes wrote:
> It would be easier to have a nod from the author to include it as is.
This would mean that the author would need to re-release MyThes under the
GPL, right?
Jürgen
Abdelrazak Younes wrote:
%\uuline{urgent} double-underlined text
%\uwave{boat}wavy underline
%\xout{removed} marked over with //.
it would be piece of cake to add any of these (until i remember the code
around). the question is - do we
Jürgen Spitzmüller writes:
> Anyway, the Sleepykat license requires us to
>
> * 2. Redistributions in binary form must reproduce the above copyright
> *notice, this list of conditions and the following disclaimer in the
> *documentation and/or other materials provided with the distrib
Pavel Sanda wrote:
> this is the same as with artistic license which we already include.
Still, I would be more confidet if we had some expert meaning.
Anyway, the Sleepykat license requires us to
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list o
33 matches
Mail list logo
