Angus Leeming wrote:
> to generate the QString. Something like this, perhaps:
Actually, reading the Qt docs, this is the way to do it:
#include
#include
#include
#include
#include
QString const toqstr(char const * str)
{
QTextCodec * codec = QTextCodec::codecForLocale();
ret
Jean-Marc Lasgouttes wrote:
> I think that everything would be working smoothly if we did not try
> to use QKeySequence instead of the text representation of bindings,
> but a smoother way would be to keep the unicode representation
> intact in the frontend.
>
> Ideas, anyone?
Jean-Marc,
am I co
tex2lyx has code to handle the following:
{\small bla} blubb
The size of bla is set to small. Unfortunately it is not reset afterwards,
i.e. blubb is also small.
Not only the size can be changed like this, but also the font shape, series
and family, but tex2lyx does not know about that.
This p
Jean-Marc Lasgouttes wrote:
> Does this means that we have perfect round-trip on the UserGuide now?
No, but almost. Apart from the whitespace changes that we agreed to not
handle some months ago, the preamble changes slightly, there is a problem
with \item[arg], and we have http://bugzilla.lyx.or
On Wednesday 23 June 2004 15:30, Juergen Spitzmueller wrote:
> Jose' Matos wrote:
> >> I agree with that, but we can't do it in 1.3.x. In 1.4.x it could be
> >> possible with proper support from lyx2lyx, but there is some work
> >> involved to make it work correctly in various point sizes.
>
> What
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jose' Matos wrote:
>>> I agree with that, but we can't do it in 1.3.x. In 1.4.x it could
>>> be possible with proper support from lyx2lyx, but there is some
>>> work involved to make it work correctly in various point siz
Jose' Matos wrote:
>> I agree with that, but we can't do it in 1.3.x. In 1.4.x it could be
>> possible with proper support from lyx2lyx, but there is some work
>> involved to make it work correctly in various point sizes.
What do you mean?
Anyway, I guess this is an 1.5. issue (I think we do not
On Wednesday 23 June 2004 15:15, Jean-Marc Lasgouttes wrote:
>
> I agree with that, but we can't do it in 1.3.x. In 1.4.x it could be
> possible with proper support from lyx2lyx, but there is some work
> involved to make it work correctly in various point sizes.
Did I hear lyx2lyx? ;-)
What n
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote: [...]
>> As you see the paperpackage setting is completely wrong. I suspect
>> there is an off-by-one error somewhere.
>>
>> Juergen, could you take a look at this?
Juergen> To be honest, I t
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> This is a fix for the tex2lyx nesting bug. It works, but I
Georg> guess this fix does not fit well into the design of the Context
Georg> class. Jean-Marc, could you comment, please? I have to admit
Georg> that I do not fully understand
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> Yes -- it's consistent with other Mac applications. I like
Bennett> it!
OK, I just applied it.
JMarc
On Jun 23, 2004, at 8:33 AM, Jean-Marc Lasgouttes wrote:
"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> Done -- deleting the "{" in line 257 fixes the compile
Bennett> problem.
Indeed. I will correct this.
Bennett> Better yet, the patch does what it should: menus remain, but
Bennett
I had high hopes that the fact that I used native Qt menu shortcuts in
menus would make LyX/Mac magically display the shortcuts, but it turns
out that I have been overoptimistic.
Currently the shortcuts do not appear, and it seems to be due to the
following explanation from qkeysequence.cpp:
/*!
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> Done -- deleting the "{" in line 257 fixes the compile
Bennett> problem.
Indeed. I will correct this.
Bennett> Better yet, the patch does what it should: menus remain, but
Bennett> the right things are greyed out.
And does it
14 matches
Mail list logo
