Christian Ridderström wrote:
>> > I've _suffered_ this "feature" in MS-Word... for me, the main problem
>> > was the distraction from content. E.g., I frequently found myself
>> > spending time on fixing spelling(*) instead of content -- I prefer
>> > checking spelling at the end, when the content
Angus Leeming wrote:
> However, the main point of this mail is to ask what I need to do to
> get the Qt frontend to understand the filter
> "*.(gif|png|jpg|bmp|pbm|ppm|tga|tif|xpm|xbm)"
>
> Any idea what the Qt-version would need to be?
H. I've just realised that
"*.(gif|png|j
The patch below prevents a crash in the xforms frontend when launching
the File Browser dialog from the External dialog.
The problem was that this string, used to specify the file filter:
"*.(gif|png|jpg|bmp|pbm|ppm|tga|tif|xpm|xbm)"
was being modified in ControlExternal to this:
-BEGIN PGP SIGNED MESSAGE-
On Sonntag, 21. Dezember 2003 14:32, Atsushi Shimmra wrote:
> Kornel Benko wrote:
>
> > Upgrading to SuSE 9.0 (with QT 3.2.1-56 and gcc 3.3.1), I have now problems to
> > launch the qt-lyx.
> >
> > It crashes in call to QFontInfo() in src/frontends/qt2/lyx_gui
On Mon, Dec 29, 2003 at 12:29:57PM +0100, Jean-Marc Lasgouttes spake thusly:
>
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> See the attached. The idea is to make it possible to use
> Martin> LatexParam more flexibly to add attributes to opening tags.
> Martin> Work i
The attached patch to 1.3.4cvs -- suggested by Jean-Marc -- lets
LyX/Mac find additional fonts in its own application bundle. The
addFontPath code works, but does not get called by
qfont_loader::available. Instead, Qt finds fonts in the teTeX
hierarchy which do the math symbols wrong. The o
Angus Leeming wrote:
> > Is the attached better?
>
> My opinion?
If you are in the mood...
> Yes.
OK, then I apply this and hope to close the chapter "minipage insets" finally.
Jürgen.
Juergen Spitzmueller wrote:
>> The bare bones lyxconvert_228.py and lyxrevert_229.py are pointless
>> (as you say). Personally I'd move the conversion code into them.
>> The more of these tiny files we have, the more likely José is to
>> come up with a versioning system that separates file from for
Angus Leeming wrote:
> What I meant was that this 'removal of InsetMinipage/conversion of
> InsetMinipage to InsetBox' is a format change and so should
> 1 be documented
> 2 be placed in its own lyx2lyx files, lyxconvert_228.py and
> lyxrevert_229.py.
Yes, this is certainly much cleaner.
> The ba
Juergen Spitzmueller wrote:
> Angus Leeming wrote:
>> Could you increase the LyX format by one please (src/buffer.C) and
>> add a note to this effect in development/FORMAT. To that end, it
>> would probably be best to create new lyxconvert/lyxrevert files
>> too...
>
> I don't quite understand wh
Angus Leeming wrote:
> Could you increase the LyX format by one please (src/buffer.C) and add
> a note to this effect in development/FORMAT. To that end, it would
> probably be best to create new lyxconvert/lyxrevert files too...
I don't quite understand why this is necessary here, but anyway. Can
José, just before Christmas you asked why we always copied external
files (graphics, xfig, gnuplot etc) to the tmp directory even when no
modifications were needed.
I've just remembered an additional reason: LaTeX can't cope with
spaces in the path. When we copy the file to the temp directory w
Angus Leeming wrote:
> Juergen Spitzmueller wrote:
>> IMHO Michael's patch could go in now. Can I apply it?
>
> Go for it.
I see you did indeed go for it.
Could you increase the LyX format by one please (src/buffer.C) and add
a note to this effect in development/FORMAT. To that end, it would
If you open the External dialog in order to insert a new inset, you're
currently faced with the combox of available templates being set to
'RasterImage', thanks to this code in insetexternal.C
namespace {
string const defaultTemplateName = "RasterImage";
} // namespace anon
InsetExterna
Juergen Spitzmueller wrote:
> IMHO Michael's patch could go in now. Can I apply it?
Go for it.
--
Angus
Jose' Matos wrote:
> The code look correct and all the individual converter are self-contained.
> The only thing that could go wrong is come missing import statement, but
> those seem ok.
>
> Does it works?
Yes. It works on Kornel's test file.
> If yes then apply it. :-)
Done. Thanks.
IMHO M
Jean-Marc Lasgouttes wrote:
>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Attached are the changes in my 1.3.x tree.
>
> Angus> * src/frontends/qt2 intelligent scrolling for Qt. This patch
> Angus> has been in the 1.4.x tree for weeks and no problems have
> been Angus> r
Well, I can confirm that something is going wrong with the loading of
fonts. I've seen that the ./configure command produce:
...
checking for TeX fonts
checking [for cmex10]... no
checking [for cmmi10]... no
checking [for cmr10]... no
checking [for cmsy10]... no
checking [for eufm10]... no
checkin
On Monday 29 December 2003 11:20, Juergen Spitzmueller wrote:
> Angus Leeming wrote:
> > My opinion? Move it.
>
> I do not much understand lyx2lyx. Is the attached correct?
The code look correct and all the individual converter are self-contained.
The only thing that could go wrong is come miss
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> See the attached. The idea is to make it possible to use
Martin> LatexParam more flexibly to add attributes to opening tags.
Martin> Work in progress.
Martin> OK to commit?
What does the # in latexparam mean?
Do you really nee
Angus Leeming wrote:
> My opinion? Move it.
I do not much understand lyx2lyx. Is the attached correct?
Jürgen.
Index: lyxconvert_224.py
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/lyx2lyx/lyxconvert_224.py,v
retrieving revisio
Juergen Spitzmueller wrote:
> about bleeding edge file formats or not? (the slution would be easy,
> as proposed by Angus: just move the conversion from
> lyxconvert_224.py to lyxconvert_227.py).
My opinion? Move it.
--
Angus
On Sun, 28 Dec 2003, Christian Ridderström wrote:
> People work differently and there's nothing wrong with that... However, the
> way it works in Word isn't necessarily the best way, so one reason for this
> discussion is to find out what people _really_ want. E.g., the reason 'used
> to since
On Monday 29 December 2003 10:33, Jean-Marc Lasgouttes wrote:
> Christian> * Automatic mode where (minor) misspellings automatically
> Christian> are corrected.
>
> We should definitely avoid that. This causes endless frustration.
Agree! I want fully control over my own document. This auto-corre
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Attached are the changes in my 1.3.x tree.
Angus> * src/frontends/qt2 intelligent scrolling for Qt. This patch
Angus> has been in the 1.4.x tree for weeks and no problems have been
Angus> reported.
Yes. Actually I intended to ask
> "Christian" == Christian Ridderström <[EMAIL PROTECTED]> writes:
Christian> It's actually a serious question... IMO we need to
Christian> distinguish between:
Christian> * Manual mode where misspelled words are only marked (eg.
Christian> by a wavy underline) and the user manually corrects
Michael Schmitt wrote:
> Hm... I think there _is_ a minipage->box conversion available in
> lyxconvert_224.py. Loading a LyX 1.3.4 document works as expected, at
> least. So what exactly is missing?
OK, short summary: The problem is that the minipage->box conversion happens
from 223->224 whil
27 matches
Mail list logo
