On Thu, Jan 14, 2010 at 5:13 AM, Steve Litt wrote:
> On Wednesday 13 January 2010 13:36:09 José Matos wrote:
>> Hi all,
>>
>> I would like to start working on the goal of having lyx with an xml file
>> format.
>
> Once again I'd like to say that if not done exactly right, XMLizing LyX native
> for
On Wednesday 13 January 2010 19:39:40 José Matos wrote:
> OK, that would imply to bump Qt requirement to 4.3 (not too bad) but before
> doing that are we sure that this version works for our needs?
How does one tell what version of Qt is on his computer?
SteveT
Steve Litt
Recession Relief Pack
On Wed, Jan 13, 2010 at 8:46 PM, Uwe Stöhr wrote:
> Dear colleagues,
>
> I think it is time to finalize the next major LyX release. Pavel today
> posted the first related issue - the version number. (I don't have a strong
> opinion but as this version includes less new stuff than 1.6, we should
>
Dear colleagues,
I think it is time to finalize the next major LyX release. Pavel today posted the first related
issue - the version number. (I don't have a strong opinion but as this version includes less new
stuff than 1.6, we should perhaps name it 1.7.)
The important issue is the roadmap:
Am 13.01.2010 15:54, schrieb Jean-Marc Lasgouttes:
This is not correct, neither the Unicode standard nor typographic
books know a ligature of dashes, see also
http://en.wikipedia.org/wiki/Typographic_ligature
-- and -- are implemented in TeX as ligatures in the font, as are ?`,
!`, `` and ''.
José Matos wrote:
> > >+ libxml2
> > >+ boost variant
> >
> > Qt ? http://qt.nokia.com/doc/4.6/xml-processing.html
are there some differences as far as 'stability' is concerned?
because while its acceptible that we have multiple ifdefs which fixes changing
behaviour of Qt in UI it would
On Thursday 14 January 2010 00:28:23 Vincent van Ravesteijn wrote:
> QXmlReader is there at least since Qt4.0, QXmlStreamReader was
> introduced in Qt4.3.
OK, that would imply to bump Qt requirement to 4.3 (not too bad) but before
doing that are we sure that this version works for our needs?
I
José Matos wrote:
> But sure I am open for the next release to be made without XML.
considering rather finishing status of work on bigger features i think
this is the reasonable way. even before few months people asked about
intermediate release which raises few questions on our release maintainer
On Wednesday 13 January 2010 19:08:30 rgheck wrote:
> FYI, I think one write_xml() routine is enough. ;-)
:-)
I can change the name if you insist. :-)
> rh
--
José Abílio
José Matos schreef:
On Wednesday 13 January 2010 18:40:59 Vincent van Ravesteijn - TNW wrote:
Hi all,
I would like to start working on the goal of having lyx
with an xml file format.
Some of the issues we will have to tackle:
- what parser library to use?
+ libxml2
+ boost variant
On Wednesday 13 January 2010 18:51:19 Andre Poenitz wrote:
> Any reason not to use QXmlStreamReader?
None other, as I said before to Vincent, as to understand how Qt 4.2 of it
behaves.
> > - what to do with math?
>
> Try to use the 'layout oriented' bits of MathML and invent our own for
> the
Hi,
I propose the following patch, which:
- makes the Dialog::bufferview() call virtual
- in Dialog.cpp tries to rely as much as possible on
Dialog::bufferview() rather than directly calling
view_->[current/document]bufferview()
- overrides the method in GuiDocument.cpp, so as to operate on the
On Wednesday 13 January 2010 19:12:12 Pavel Sanda wrote:
> major features freeze and release of alpha was my thought behind.
> all advertised (big) features are basically in trunk plus minus some
> finishing.
>
> with pusing xml in i expect again next year without release.
XML file format is well
On Wednesday 13 January 2010 18:40:59 Vincent van Ravesteijn - TNW wrote:
> >Hi all,
> >
> >I would like to start working on the goal of having lyx
> >with an xml file format.
> >
> >Some of the issues we will have to tackle:
> > - what parser library to use?
> >
> >+ libxml2
> >+ boost
Pavel Sanda schreef:
Pavel Sanda wrote:
Vincent van Ravesteijn - TNW wrote:
No, like you tend to say.. "I'm not at that box now."
once you move out of your girlsfriend flat, can you still reproduce (the
crash)? :)
i see it no more after r33013.
pavel
No, the crash is gone.
rgheck wrote:
> Note, by the way, that the new "advanced find and replace" feature is
going to make sure scripts a lot less necessary.
Probably true if you're thinking of interactive find/replace actions
that people usually do by editing the .lyx file by hand (and I'm equally
scared about x^2
Richard Heck wrote:
> Yes, I know, but that's what I meant about the macros. I'm not sure why we
> even use this constuct:
> lyxerr << stuff
> anymore, instead of:
> LYXERR0(stuff);
> The latter ends the newline that always seems to be needed, and gives the
> file position and stuff, too.
On 01/13/2010 03:38 PM, Pavel Sanda wrote:
Richard Heck wrote:
I guess the only thing to do would be to have a way of locking the stream,
e.g.:
out<< Lock()<< t1a<< t1b<< Unlock();
Things coming from elsewhere could be cached until the lock is released.
Perhaps this is not so diffi
On 01/13/2010 04:13 PM, Steve Litt wrote:
On Wednesday 13 January 2010 13:36:09 José Matos wrote:
Hi all,
I would like to start working on the goal of having lyx with an xml file
format.
Once again I'd like to say that if not done exactly right, XMLizing LyX native
format will disenf
Pavel Sanda wrote:
> Vincent van Ravesteijn - TNW wrote:
> > No, like you tend to say.. "I'm not at that box now."
once you move out of your girlsfriend flat, can you still reproduce (the
crash)? :)
i see it no more after r33013.
pavel
On Wednesday 13 January 2010 13:36:09 José Matos wrote:
> Hi all,
>
> I would like to start working on the goal of having lyx with an xml file
> format.
Once again I'd like to say that if not done exactly right, XMLizing LyX native
format will disenfranchise the significant minority of users who
Abdelrazak Younes wrote:
>> no more qsettings! :) if they wont get restarted every other day and we
>> have it in
>> normal preferences then there was no need for this thread.
>>
>
> I don't understand this QSettings animosity. It's quite a fine class. Maybe
> the problem lies in our way to us
Hi Vincent,
- compare seems to do different things when i do comparison
for the second time on the same couple of documents - seeing big
time differences here. this is correct?
- i see strange things when (errorneously) tried to do comparison
on the same file. first time ok, second time pro
Richard Heck wrote:
> I guess the only thing to do would be to have a way of locking the stream,
> e.g.:
> out << Lock() << t1a << t1b << Unlock();
> Things coming from elsewhere could be cached until the lock is released.
>
> Perhaps this is not so difficult, even, if we use the LYXERR macros
v...@lyx.org wrote:
> Author: vfr
> Date: Wed Jan 13 21:25:17 2010
> New Revision: 33015
> URL: http://www.lyx.org/trac/changeset/33015
>
> Log:
> Fix (partly?) bug #6451: Crash when interacting with buffer-dependent dialog
> with no buffer open.
>
> It seems to be a good idea to close all buffe
>Author: younes
>Date: Sun Sep 27 12:29:13 2009
>New Revision: 31472
>URL: http://www.lyx.org/trac/changeset/31472
>
>Log:
>Transfer LFUN_INSET_APPLY from GuiView to BufferView.
>The list of dialog edited inset is now stored in BufferView.
>
Before this commit, dialogs that were connected to an
On 01/13/2010 02:07 PM, sa...@lyx.org wrote:
Author: sanda
Date: Wed Jan 13 20:07:18 2010
New Revision: 33013
URL: http://www.lyx.org/trac/changeset/33013
Log:
Move lyxerrFlush() out of singnal/slot business.
Under massive load of lyxerr<< messages we lose synchronization in ui
and messages ge
Richard Heck wrote:
>>> Any other points that I had forget?
>>>
>> i didnt get one thing - you intend to push this into the current trunk or
>> after next lyx release?
>>
>>
> Speaking of the next release, I think we should also think about that. We
> have a LOT of new features, so unles
+ the code that I already have in lyx2lyx deals easily with all the other
stuff (the patch I was working follows attached, this is only an hint we could
use a different implementation but I think that this server as a good first
step to boost the discussion on the topic).
FYI, I think
On 01/13/2010 01:36 PM, José Matos wrote:
- how to proceed in the mean time?
+ using an iterative approach we will have a file that will be xml-ized by
parts
I think the incremental approach will actually be much less intrusive
than it might at first seem, and some of it, not necess
On 01/13/2010 01:41 PM, Pavel Sanda wrote:
José Matos wrote:
Any other points that I had forget?
i didnt get one thing - you intend to push this into the current trunk or
after next lyx release?
Speaking of the next release, I think we should also think about that.
We have a LOT
On Wed, Jan 13, 2010 at 06:36:09PM +, José Matos wrote:
> Hi all,
>
> I would like to start working on the goal of having lyx with an xml file
> format.
>
> Some of the issues we will have to tackle:
> - what parser library to use?
> + libxml2
> + boost variant
Any reason not to u
José Matos wrote:
> Any other points that I had forget?
i didnt get one thing - you intend to push this into the current trunk or
after next lyx release?
pavel
>Hi all,
>
>I would like to start working on the goal of having lyx
>with an xml file format.
>
>Some of the issues we will have to tackle:
> - what parser library to use?
>+ libxml2
>+ boost variant
>
Qt ? http://qt.nokia.com/doc/4.6/xml-processing.html
Vincent
Hi all,
I would like to start working on the goal of having lyx with an xml file
format.
Some of the issues we will have to tackle:
- what parser library to use?
+ libxml2
+ boost variant
- how to proceed in the mean time?
+ using an iterative approach we will have a file that w
On 01/13/2010 12:02 PM, Pavel Sanda wrote:
HTML is an easier to navigate format -- especially for newbies that are
(yet) uncommon with the LyX way to navigate a document. While the lyx
format should remain accessible to users (for better examples), the
WYSIWYM markup at other places
Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
> > Anyway, the crash wasn't there anymore.
>
> unfortunately i just got crash even with the mutex patch.
no backtraces available but it maybe not your version since i get consistenly
#0 0xb797e90d in QTextEngine::itemize() const () from
/usr/l
Vincent van Ravesteijn - TNW wrote:
> No, like you tend to say.. "I'm not at that box now."
:)
pavel
>>I had to do some ugly things with a global variable.
>
>can you show your patch?
>
No, like you tend to say.. "I'm not at that box now."
>pavel
Vincent
Vincent van Ravesteijn - TNW wrote:
> >> Anyway, the crash wasn't there anymore.
> >
> >Unfortunately i just got crash even with the mutex patch.
> >pavel
> >
>
> How did you use the mutex?
just started to play with the last patch posted here trying to reproduce the
deadlock.
>I had to do some
>> Anyway, the crash wasn't there anymore.
>
>Unfortunately i just got crash even with the mutex patch.
>pavel
>
How did you use the mutex? I had to do some ugly things with a global
variable.
Vincent
Vincent van Ravesteijn wrote:
> Anyway, the crash wasn't there anymore.
unfortunately i just got crash even with the mutex patch.
pavel
Vincent van Ravesteijn - TNW wrote:
> >doesn't work because of different preambles and different
> >needs of manuals.
> >
>
> Which I still don't understand.
http://www.lyx.org/trac/ticket/5460
pavel
>> Therefore I propose:
>>
>> * Organize the help documents as children of one master LyX Guide.
>> (enables easier cross-links and a common index).
>
>doesn't work because of different preambles and different
>needs of manuals.
>
Which I still don't understand.
Vincent
Guenter Milde wrote:
> Therefore I propose:
>
> * Organize the help documents as children of one master LyX Guide.
> (enables easier cross-links and a common index).
doesn't work because of different preambles and different needs of manuals.
> * Convert the LyX Guide to a set of HTML and publi
On 2010-01-13, rgheck wrote:
> On 01/13/2010 02:28 AM, Guenter Milde wrote:
>> However, pointing out the distinction between a LateX
>> documentclass/-style and a LyX layout file and pointing to the
>> relevant parts of the documentation will help them and, by reduced
>> faqs, us.
> Some of that
On 13 jan 2010, at 17.30, Vincent van Ravesteijn - TNW wrote:
>
>>> thats simply configurable through keybindings editor.
>>> pavel
>>
>> Thanks!
>> But this should be rather annoying for a beginner. Maybe it would
>> be good to go through the Mac keybindings and make them more Mac-like?
>> (I'
>> thats simply configurable through keybindings editor.
>> pavel
>
>Thanks!
>But this should be rather annoying for a beginner. Maybe it would
>be good to go through the Mac keybindings and make them more Mac-like?
>(I'll put on my todo-list to make a suggestion unless someone jumps
>to it, but
On 13 jan 2010, at 14.23, Pavel Sanda wrote:
> Anders Ekberg wrote:
>> The main problem for me (latest version on Mac OSX 10.6) is that inserting
>> an en-dash (which is "alt -" on my Swedish keyboard) zooms out the
>> window
>> "--" is fine (if I can suppress the "alt -" reflex), but cause
On 01/13/2010 06:21 AM, Jürgen Spitzmüller wrote:
Uwe Stöhr wrote:
Sure, because you do the same in all other text editors and Word-like
applications. I was often asked in the past why there are two or three
subsequent dashes and it is hard to explain that they become one in the
outpu
On 01/13/2010 06:34 AM, Jean-Marc Lasgouttes wrote:
Of course, a better UI could be to
transform a - into a -- (I do not have the unicode codepoint handy,
sorry) when typing - after it (like spaces in math).
A better UI *might* (and I do mean *might*) be to display it as a
unicode em-dash.
On 01/13/2010 02:28 AM, Guenter Milde wrote:
On 2010-01-13, Uwe Stöhr wrote:
Am 13.01.2010 01:54, schrieb rgheck:
This can be done, however users with LaTeX classes we don't have a
layout file are usually LaTeX experts.
Not always. It could also be students given a university documen
Pavel Sanda wrote:
> > Why not simply "View Messages"?
i put it in menu and let more detailed message in the window.
pavel
Uwe Stöhr writes:
>> --- is not a command in TeX, it is a ligature.
>
> This is not correct, neither the Unicode standard nor typographic
> books know a ligature of dashes, see also
> http://en.wikipedia.org/wiki/Typographic_ligature
-- and -- are implemented in TeX as ligatures in the font, as
Anders Ekberg wrote:
> The main problem for me (latest version on Mac OSX 10.6) is that inserting an
> en-dash (which is "alt -" on my Swedish keyboard) zooms out the window
> "--" is fine (if I can suppress the "alt -" reflex), but causes problems when
> pasting in Word (which I am frequent
On 13 jan 2010, at 13.59, Pavel Sanda wrote:
> Uwe Stöhr wrote:
>>> Because it is an easy way to get it?
>>
>> But an unintuitive way, otherwise I wouldn't have been asked.
>
> it depends from which background do the newbie comes. if its the tex one
> then --- is pretty intuitive. if they are of
Uwe Stöhr wrote:
>> Because it is an easy way to get it?
>
> But an unintuitive way, otherwise I wouldn't have been asked.
it depends from which background do the newbie comes. if its the tex one
then --- is pretty intuitive. if they are office descendands then i suspect
they have never heard abou
Jean-Marc Lasgouttes schrieb:
Because it is an easy way to get it?
But an unintuitive way, otherwise I wouldn't have been asked.
At least our documentation files should therefore contain the correct
characters. People can copy/paste them to their documents.
Another point is that "---" is a c
Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>> Of course, a better UI could be to
>> transform a - into a -- (I do not have the unicode codepoint handy,
>> sorry) when typing - after it (like spaces in math).
>
> But this should be customizable, then.
> Personally, I find -- much eas
Jean-Marc Lasgouttes wrote:
> Of course, a better UI could be to
> transform a - into a -- (I do not have the unicode codepoint handy,
> sorry) when typing - after it (like spaces in math).
But this should be customizable, then.
Personally, I find -- much easier to identify and to distinguish from
Jürgen Spitzmüller writes:
> My experience is that wrong dashes is the most recurrent typographic
> error in Word and OOo documents (next to wrong closing single
> quotation marks).
You forgot repeated spaces between words.
JMarc
Uwe Stöhr writes:
> Sure, because you do the same in all other text editors and Word-like
> applications. I was often asked in the past why there are two or three
> subsequent dashes and it is hard to explain that they become one in
> the output but not within LyX.
Because it is an easy way to ge
Uwe Stöhr wrote:
> Sure, because you do the same in all other text editors and Word-like
> applications. I was often asked in the past why there are two or three
> subsequent dashes and it is hard to explain that they become one in the
> output but not within LyX.
> At least our documentation f
Jean-Marc Lasgouttes schrieb:
You did similar changes in the past. Why did you remove long dashes by
"---"? Using three characters to get one in the output is unintuitive
and confuses newbies. Thanks to our Unicode support we can directly
use all types of dashes.
You mean searching in the Symb
Uwe Stöhr wrote:
> >> Besides this, please do all changes that are not specific to trunk in
> >> the versions in branch!
> >
> > I thought I should ask Jurgen?
>
> We agreed some time ago that changes are made in the files using change
> tracking, except of the files that you maintain. Changes t
Uwe Stöhr writes:
> Am 13.01.2010 01:51, schrieb rgheck:
>
>>> Tutorial.lyx: revert r33004 (I guess this was accidentally committed.)
>>>
>> Yes, sorry.
>
> You did similar changes in the past. Why did you remove long dashes by
> "---"? Using three characters to get one in the output is unintuitiv
66 matches
Mail list logo
