On Tue, Dec 30, 2014 at 7:33 AM, Georg Baum wrote:
> commit 33b059bd9d98e725500c48855d89986223b3
> Author: Georg Baum
> Date: Tue Dec 30 13:30:40 2014 +0100
>
> Make macro xhtml export more secure
>
> Actually I wanted to do that in cc87f8100 but forgot to adjust the
> original
>
On 2015-02-10, Lior Silberman wrote:
> On Tue, Feb 10, 2015 at 6:55 AM, Jean-Marc Lasgouttes
> wrote:
>> Le 10/02/2015 15:25, Scott Kostyshak a écrit :
>>> I'm curious -- what is the use case here? Do you have custom LaTeX
>>> definitions and you want to provide symbols for them? Or do you add
>>>
Le 15/02/2015 21:57, Jean-Marc Lasgouttes a écrit :
I'd prefer this solution, that would mean that the inset does not really
exist. I do not like the idea of having a thing that the user does not
understand because s/he cannot reproduce it.
I would think that something can be done in Text::readP
Le 15/02/2015 21:25, Georg Baum a écrit :
Only the last item can be easily implemented in lyx2lyx (and I did it). For
the first two we are missing some infrastructure. Therefore I came up with
the special inset which encapsulates all the old special logic. In
principle, this inset could also be r
Jean-Marc Lasgouttes wrote:
> Le 15/02/2015 20:43, Georg Baum a écrit :
>> The attached patch implements this behaviour. In an ideal world, the
>> backward compatibility would be handled completely by lyx2lyx, but this
>> is currently not possible, since we have no infrastructure in lyx2lyx to
>>
Le 15/02/2015 20:43, Georg Baum a écrit :
The attached patch implements this behaviour. In an ideal world, the
backward compatibility would be handled completely by lyx2lyx, but this is
currently not possible, since we have no infrastructure in lyx2lyx to track
the current font (including inherit
Richard Heck wrote:
> I think "PDF (E-book)" would be misleading. It suggests something more
> is going on than just a lower resolution.
+1
Another disadvantage is that users might think that this format is only
usable for ebooks, but this is not true.
Georg
Currently LyX treats consecutive hyphens like LaTeX: -- becomes – (endash)
and --- becomes — (emdash). This is true in most cases, but there are
exceptions (e.g. for IPA insets). Furthermore, this is completely ignored
for plain text export, and this is bug 3647.
IMO LyX should not mimic LaTeX
On 02/15/2015 10:52 AM, Uwe Stöhr wrote:
Am 15.02.2015 um 11:26 schrieb Georg Baum:
We could also name it "PDF (low resolution)", but this is much
longer, and I
thought the more accurate description would be better. The
overcrowded menu
is indeed not nice, so I am fine wth the current status a
Am 15.02.2015 um 11:26 schrieb Georg Baum:
We could also name it "PDF (low resolution)", but this is much longer, and I
thought the more accurate description would be better. The overcrowded menu
is indeed not nice, so I am fine wth the current status as well. Richard, I
guess this should also b
Am Sonntag, 15. Februar 2015 um 12:16:59, schrieb Jürgen Spitzmüller
> Am Sonntag 15 Februar 2015, 12:05:54 schrieb Kornel Benko:
> > How can one modify trac-description? Am I allowed to do so?
>
> Now you can (I've added you to the "developers" trac group, where you should
> have been added lo
Am Sonntag 15 Februar 2015, 12:05:54 schrieb Kornel Benko:
> How can one modify trac-description? Am I allowed to do so?
Now you can (I've added you to the "developers" trac group, where you should
have been added long ago anyway). This group has some extended ticket edition
rights.
Jürgen
>
Am Sonntag, 15. Februar 2015 um 11:46:41, schrieb Jürgen Spitzmüller
> Am Samstag 14 Februar 2015, 14:40:00 schrieb Richard Heck:
> > There's no special way. You just have to write "See also #9215" or
> > something like that. Trac is smart enough to know that #9215 is supposed
> > to be a link.
Am Samstag 14 Februar 2015, 14:40:00 schrieb Richard Heck:
> There's no special way. You just have to write "See also #9215" or
> something like that. Trac is smart enough to know that #9215 is supposed
> to be a link.
More importantly, add "#9412" to the description of bug #9215 (I've done
tha
Uwe Stöhr wrote:
> However, the export menu is now overcrowded in my opinion. The 150 dpi-
> converter has a very limited target audience and should therefore not be
> by default in the main export menu.
I put it there because the cropped pdf was already in the export menu (which
is IMHO needed
This error is in branch and in trunk. Independent of Qt version.
If I try to set e.g. horizontal space between xx with value like 130sp, the
dialog accepts it,
but saved lyx file is missing the value.
(This is not a too big value, it's about 7mm)
In lyx-file: Instead of having
x
16 matches
Mail list logo
