Bo Peng wrote:
> 2. This does not conflict with our XML transition because no lyx2lyx
> is needed. Actually, the use of manifest (not the ODF one though) and
> zip format makes .lyx closer to ODF.
>
It is a great idea.
Have you considered going even closer to an odt file with the mimetype, the
Peter Kümmel wrote:
>
> I don't know what's the best way to go, but we could start a new
> endless discussion. (Have you registered that there wasn't such a
> beast within the last months? There was more coding than
> discussing. LyX is changing.)
Maybe have a schedule like KDE. You have a wiki
Andre Poenitz wrote:
>
> Think privacy.
>
> Now try again.
>
You have all this metainformation fields in a pdf file. It is rather
uninformative now then when you create a pdf file from LyX the creator
field in the pdf file is 'TeX
Metadata repository and search possibilities like Nepomuk ar
Timothy Reaves wrote:
>> There are several classes in the preferences, and I'm sure several
>> 'features' no one will be able to use unless these third-party files are
>> added. A lot of users that would otherwise use LyX won't; they'll give
>> it a try, see something they want to use (the Do
Hello,
While everybody is working on the Qt Dialogs, I've spotted that in LyX 1.4
and 1.5 there is no shortcut (Alt-C) for the Close button while if you open
the ui file in Qt Designer it is there.
I've grepped the code and cannot find anything related to redefining
shortcuts.
Strange,
Charles
Jean-Marc Lasgouttes wrote:
>>>>>> "cmiramon" == cmiramon
>>>>>> <[EMAIL PROTECTED]> writes:
>
> cmiramon> Hello, While everybody is working on the Qt Dialogs, I've
> cmiramon> spotted that in LyX 1.4 and 1.5 there is no sh
> This is the minimal example I could find.
>
> I have just added frenchb to the document class and the
> \usepackage{babel} to the lyx generated file.
>
> %% 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. \do
> Strange. I am on Ubuntu feisty so the differences with SID should be
> minimal. Can you post the latex file correponding ?
>
The file you posted compile cleanly here.
Cheers,
Charles
Hello,
I've compiled LyX 5.0 svn.
1) Open User Guide
2) Tools -> outline
3) Document -> Next cross-reference
4) Click in the Toc Widget on the second section
5) Boum with this (rather unhelpful message)
/usr/include/c++/4.1.3/debug/safe_iterator.h:130:error: attempt to copy-
construct an ite
Done
#3843
Jose' Matos wrote:
> I have today officially delivered my thesis. It
Congratulations. Finishing a thesis is like lifting a heavy weight from your
stomach.
Cheers,
Charles
With your patch, it compiles but stops with the qt4 frontend :
scons frontend=qt4 qt_dir=/usr/share/qt4 qt_lib_path=/usr/lib/qt4 -j3 lyx
g++ -o
debug/common/frontends/qt4/Action.o -c -g -O -DHAVE_CONFIG_H
-DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_STL -DQT_NO_KEYWORDS -DQT_GUI_LIB
-Idebug
Hello,
I'm making progress :
- installing libqt4-debug and libqt4-dev-debug
- Running update-alternatives --config moc and update-alternatives --config
uic to point to qt4 version
- changing QTDIR to /usr/share/qt4 (don't know if its necessary)
I'm able to compile lyx-qt4
But when I execute it,
Hello,
I have the same error executing LyX after applying Peter's patch and trying
Georg's workaround.
Trying to go the autotools way leads to an error in the ld phase :
g++ -g -O -o lyx-qt4 main.o Bidi.o BufferView.o BufferView_pimpl.o Bullet.o
BranchList.o Chktex.o Color.o CutAndPaste.
o DepTa
Hello,
I'm reading arguments to and fro about the fastness of the new Qt4 frontend.
Just a question. Has someone tried Valgrind / Cachegrind / KCachegrind on
the Qt4 frontend and the last working Qt3 frontend after the unicode
transition, and a 1.4 version ?
At least, it would give more scienti
Jean-Marc Lasgouttes wrote:
> The few times I tried cachegrind, it was making lyx so slow that any
> testing concerning the GUI was too difficult to do. How do KDE people
> do it? Is there some documentation somewhere?
>
> It seems to me that oprofile is much faster.
>
It is slow but it works.
Hello,
I've tried the new full screen mode. It is a very nice addition. Thanks
Pavel.
Some observations :
- I would keep the menu bar, and the standard toolbar (with maybe an option
to auto-hide them)
- I would also keep the status bar (people like to have feedback, like when
they save a file)
-
rgheck wrote:
>
> Could someone do me a big favor implement this? I'm forever hitting F3
> and expecting it to advance me to the next search item.
>
> rh
+1... Grrr
Pavel Sanda wrote:
>
> what do you think about integrating this support to lyx?
>
I think it is a great idea to add a generic RCS framework with a git plugin
for LyX.
I have never used a RCS with LyX because there is no easy way to have a
visual diff between two versions of the same LyX file.
Hello,
I've found tonight that tex2lyx does not seem to work if you try to convert
a file with a path with a non ascii character (here a French accent).
I'm using LyX 1.5.5. Can you confirm that it is also the case with LyX svn
and I'll file a bug.
Cheers,
Charles
John Levon wrote:
> - what the biggest problems are with the current structure
Some statistics : first figure is the number of menu items, the second
number the total menu + sub-menus + sub-sub-menus items
LyX svn blank document with a table
File : 17 ; 53
Edit : 17 ; 79
View : 19 ; 55
Insert :
> Format. Probably at the top.
>
+1
Pavel Sanda wrote:
> Hello,
>
> among others I use LyX for translation work and as I saw on users list I'm
> not the only one. There are few features which would help me a lot,
> namely:
>
> - displaying the appropriate parts of texts in parallel in some sensible
> GUI (I
> had to run two wind
http://www.tuxfamily.org/en/main
pmwiki
git
svn
mail
but no trac and bugzilla
Cheers,
Charles
I vote also for inclusion.
== C++ or Python ==
eLyXer code is easy to understand even for hobbyist programmers like me.
Hacking exporting is something that could be done by power users or
beginner developers. Embedding it in the C++ maze of LyX code would make it
easier for Abdel and the core de
rgheck wrote:
> There are more and less complicated ways to do this. You could have a
> new format, like DocBook, but I think what's really wanted is something
> that would work more like plaintext, so that you can output any document
> as HTML. So we'd have a set of ashtml() routines in the inset
26 matches
Mail list logo
