Philippe Charpentier wrote:
> I did not follow this discussion but I hope that this patch does not
> suppress the
> possibility to create its own format to be able to use its own compiler.
Of course not.
Jürgen
uwesto...@lyx.org wrote:
> Log:
> GuiDocument.cpp: remove unneeded prefix since we are there already in
> namespace lyx
[...]
> @@ -2185,9 +2185,9 @@
> if (index == -1)
> index = 0;
> outputModule->defaultFormatCO->setCurrentIndex(index);
> - outputModule->xete
Abdelrazak Younes wrote:
> On 10/04/2009 11:58, Jean-Marc Lasgouttes wrote:
>> Abdelrazak Younes writes:
>>
>>> I agree that scanning the .svn dir is the best option. But I suspect
>>> that just doing directly won't take more time than trying to reuse svn
>>> source code. But I may be wrong of
On 10/04/2009 21:15, Vincent van Ravesteijn wrote:
Abdelrazak Younes schreef:
On 10/04/2009 14:43, v...@lyx.org wrote:
> Author: vfr
> Date: Fri Apr 10 14:43:35 2009
> New Revision: 29185
> URL: http://www.lyx.org/trac/changeset/29185
>
> Log:
> * compile_uic.sh: Add OutputUi.
Is this still us
Abdelrazak Younes schreef:
On 10/04/2009 14:43, v...@lyx.org wrote:
> Author: vfr
> Date: Fri Apr 10 14:43:35 2009
> New Revision: 29185
> URL: http://www.lyx.org/trac/changeset/29185
>
> Log:
> * compile_uic.sh: Add OutputUi.
Is this still used? I did this script 3 years ago when I did the ini
On 10/04/2009 14:43, v...@lyx.org wrote:
Author: vfr
Date: Fri Apr 10 14:43:35 2009
New Revision: 29185
URL: http://www.lyx.org/trac/changeset/29185
Log:
* compile_uic.sh: Add OutputUi.
Is this still used? I did this script 3 years ago when I did the initial
port to Qt4...
Abdel.
a écrit :
Jürgen Spitzmüller wrote:
AFAICS these are leftovers from the pre-converters era. Although GuiSendto
still considers custom_export_command, I doubt anyone is actually using
this (there is no GUI). And if so, we better use session for this.
OK to remove (see attached patch)?
Jean-Marc Lasgouttes wrote:
> > And a couple of different packages for specific tasks (font handling,
> > language support, color handling etc.). Of course it's not as far
> > apart as context, which is a different macro language to tex, but
> > still it's significantly more apart than pdflatex, be
Jean-Marc Lasgouttes wrote:
> I really preferred it in the font pane. As it is, nobody who does not
> know that xetex exists will find this thing.
This is intended (at least as long as both our support and XeTeX itself are in
a rather experimental stage). I'd expect the people who use this to hav
Jürgen Spitzmüller writes:
>> This is still LaTeX with a couple more macros, right?
>
> And a couple of different packages for specific tasks (font handling,
> language support, color handling etc.). Of course it's not as far
> apart as context, which is a different macro language to tex, but
> st
On Fri, Apr 10, 2009 at 05:28:27PM +0200, Andre Poenitz wrote:
> On Fri, Apr 10, 2009 at 03:59:50PM +0200, Jean-Marc Lasgouttes wrote:
> > Vincent van Ravesteijn writes:
> > > Basically it means that the edit() functions could be renamed to
> > > highlyEdit() functions.
> >
> > Except that highly
On Fri, Apr 10, 2009 at 03:59:50PM +0200, Jean-Marc Lasgouttes wrote:
> Vincent van Ravesteijn writes:
> > Basically it means that the edit() functions could be renamed to
> > highlyEdit() functions.
>
> Except that highlyEdit is ugly and that we could rename as EDITABLE what
> was highly_editabl
Jean-Marc Lasgouttes wrote:
> > Also, note that there is a huge difference between latex/pdflatex and
> > latex/xetex, because in the latter case, a different source file (with
> > differing syntax) is needed, while latex/pdflatex are basically two
> > different compilers that compile the same sour
Jürgen Spitzmüller writes:
> Jürgen Spitzmüller wrote:
>> > So basically xetex should be only a new output format like pdflatex is.
>>
>> I do not see how this should work, especially wrt the font selection (which
>> is actually the main reason for people to use XeTeX, AFAICS).
>
> Also, note tha
Jürgen Spitzmüller writes:
> What need to be changed eventually is the language handling. XeTeX comes with
> its own language package, polyglossia. Apparently, babel only works for latin-
> scripted languages but miserably fails for languages where babel changes the
> encoding, such as Greek. CJ
Jürgen Spitzmüller wrote:
> > So basically xetex should be only a new output format like pdflatex is.
>
> I do not see how this should work, especially wrt the font selection (which
> is actually the main reason for people to use XeTeX, AFAICS).
Also, note that there is a huge difference between l
Jean-Marc Lasgouttes wrote:
> So basically xetex should be only a new output format like pdflatex is.
I do not see how this should work, especially wrt the font selection (which is
actually the main reason for people to use XeTeX, AFAICS).
> I do not think it is a good idea to make it such a spe
Vincent van Ravesteijn writes:
> Yes, I could use that when I move the LFUN_INSET_SETTINGS to the
> getStatus function of Inset, return true or false according to
> hasInsetDialog(). The advantage would be that I have to implement the
> check for the inset parameter of the LFUN at only one place.
Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>> > I thought about disabling the xetex checkbox if xetex is not found.
>> > But I came to the conclusing that one should nevertheless be able to
>> > edit or produce a xetex-enabled file. What is missing is probably a
>> > warning, similar
Jean-Marc Lasgouttes schreef:
Vincent van Ravesteijn writes:
Basically it means that the edit() functions could be renamed to
highlyEdit() functions.
Except that highlyEdit is ugly and that we could rename as EDITABLE what
was highly_editable, the old notion of editable would be a has
Vincent van Ravesteijn writes:
> Basically it means that the edit() functions could be renamed to
> highlyEdit() functions.
Except that highlyEdit is ugly and that we could rename as EDITABLE what
was highly_editable, the old notion of editable would be a hasSettings()
method, or something like t
Jean-Marc Lasgouttes wrote:
> > I thought about disabling the xetex checkbox if xetex is not found.
> > But I came to the conclusing that one should nevertheless be able to
> > edit or produce a xetex-enabled file. What is missing is probably a
> > warning, similar to the warning if LaTeX is not fo
Jean-Marc Lasgouttes schreef:
v...@lyx.org writes:
> Move handling of LFUN_MOUSE_RELEASE up to Inset and remove the
edit() functions for insets that do not derive from InsetCollapsable.
Does it mean that you should rethink the editable() enum, which return
currently EDITABLE for thinks like l
Jürgen Spitzmüller writes:
> Could we check the availability of the patterns in the moment where a user
> sets a document language and provide a way to enable missing patterns?
Note that chkconfig.ltx already outputs a list of patterns known to this
latex installation.
JMarc
rgheck writes:
> v...@lyx.org wrote:
>> Author: vfr
>> Date: Fri Apr 10 13:07:54 2009
>> New Revision: 29182
>> URL: http://www.lyx.org/trac/changeset/29182
>>
>> Log:
>> Show inset-toggle in the ShortCuts dialog. (Why was this Hidden ?)
>>
>>
> Where there several different uses of it before?
Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>> But can a xetex-enabled LyX document still be typeset if xetex is
>> disabled?
>
> No. As less as LaTeX documents cannot be typeset if latex is not
> installed.
>
> I thought about disabling the xetex checkbox if xetex is not found.
> B
v...@lyx.org writes:
> Move handling of LFUN_MOUSE_RELEASE up to Inset and remove the edit()
> functions for insets that do not derive from InsetCollapsable.
Does it mean that you should rethink the editable() enum, which return
currently EDITABLE for thinks like labels? We could turn it into a b
On Fri, 10 Apr 2009, rgheck wrote:
This is a bug.
Oh. Not a new feature of 1.6.2? :-)
The language has been set to "latex", which I think needs to be done for
some reason, and of course the spellchecker isn't going to find that.
Cross-posting to devel
Thank you.
FWIW, I killed
rgheck wrote:
> The attached patch backports r27635, r28193, r28194, r28220, r29094, and
> r29095. The point of these, taken together, is to improve the display of
> information in InsetCitation and GuiCitation, by gathering missing data
> from the crossref, if one is defined, basically as BibTeX d
Uwe Stöhr wrote:
> To solve this problem, I can implement a solution only for the LyX
> installer, where I modify the chkconfig.ltx file depending on the language
> the user has chosen in the installer for LyX's menus.
>
> The other solution would be to add all hyphenation patters for all
> support
v...@lyx.org wrote:
Author: vfr
Date: Fri Apr 10 13:07:54 2009
New Revision: 29182
URL: http://www.lyx.org/trac/changeset/29182
Log:
Show inset-toggle in the ShortCuts dialog. (Why was this Hidden ?)
Where there several different uses of it before?
Anyway, let me add my praise for this las
Rich Shepard wrote:
In all the years I've used LyX I've never seen this before: while
checking
the spelling of my document, a message box popped up reading, "The
spellchecker has failed. No word lists can be found for the language
'latex'."
The last word checked (which I had added to my persona
On 10/04/2009 11:58, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes writes:
I agree that scanning the .svn dir is the best option. But I suspect
that just doing directly won't take more time than trying to reuse svn
source code. But I may be wrong of course.
I thought the format chan
Jürgen Spitzmüller wrote:
> AFAICS these are leftovers from the pre-converters era. Although GuiSendto
> still considers custom_export_command, I doubt anyone is actually using
> this (there is no GUI). And if so, we better use session for this.
>
> OK to remove (see attached patch)?
Since nobody
Jean-Marc Lasgouttes wrote:
> But can a xetex-enabled LyX document still be typeset if xetex is
> disabled?
No. As less as LaTeX documents cannot be typeset if latex is not installed.
I thought about disabling the xetex checkbox if xetex is not found. But I came
to the conclusing that one shoul
Definitely. You may want to experiment with the new AtPoint LyXAction
flag.
Done.
Some other points:
1. The Inset::edit functions should not be implemented other than for
InsetCollapsables (which are editable).
2. LFUN_MOUSE_RELEASE of insets should dispatch an LFUN_INSET_SETTINGS
(for
Vincent van Ravesteijn wrote:
> > please make sure that doxygen comments are still valid for the lfuns you
> > changed pavel
> >
>
> I'll take care of it.. (when things are not changing anymore).
Also please document the changing functions in the RELEASE_NOTES.
Jürgen
Abdelrazak Younes writes:
> I agree that scanning the .svn dir is the best option. But I suspect
> that just doing directly won't take more time than trying to reuse svn
> source code. But I may be wrong of course.
I thought the format changed between svn versions...
JMarc
On 10/04/2009 10:43, Pavel Sanda wrote:
Abdelrazak Younes wrote:
On 09/04/2009 23:47, Pavel Sanda wrote:
Pavel Sanda wrote:
I am not sure this idea is better than just parsing "svn status -v"...
Further ideas? Opinions?
another idea - svn is gpl-ed righ
Abdelrazak Younes wrote:
> On 09/04/2009 23:47, Pavel Sanda wrote:
>> Pavel Sanda wrote:
>>
I am not sure this idea is better than just parsing "svn status -v"...
Further ideas? Opinions?
>>
>> another idea - svn is gpl-ed right? then what about to steal few lines
Abdelrazak Younes wrote:
> I don't follow you, how would you set 'revision_insetinfo_used' ?
by revision_insetinfo_used i mean something like scanning file for the
presence of either revision-inset-info inset or \svn_revision_info_rev
tag in header.
> Yes, but we must respect svn syntax so that w
On 10/04/2009 09:26, Jean-Marc Lasgouttes wrote:
v...@lyx.org writes:
Author: vfr
Date: Fri Apr 10 03:40:16 2009
New Revision: 29179
URL: http://www.lyx.org/trac/changeset/29179
Log:
Remove last bits of LFUN_INSET_TOGGLE that is used to show the inset settings.
This series of patch
On 09/04/2009 23:39, Pavel Sanda wrote:
Abdelrazak Younes wrote:
1) When a document "doc.lyx" is under version control, we can check its svn
properties:
svn propget svn:keywords dot.lyx
hopefully we can avoid this by checking (under_svn_control&&
revision_insetinfo_used)
I d
On 09/04/2009 23:47, Pavel Sanda wrote:
Pavel Sanda wrote:
I am not sure this idea is better than just parsing "svn status -v"...
Further ideas? Opinions?
another idea - svn is gpl-ed right? then what about to steal few lines of
code parsing .svn directory from svn status -
Jürgen Spitzmüller writes:
> Because XeTeX is significantly different from the other tex processors
> (LaTeX, PDFLaTeX). We have to do many specific things when XeTeX is selected
> (starting from the encoding, ending at specific packages and font
> interfaces). The bool just helps identifying t
v...@lyx.org writes:
> Author: vfr
> Date: Fri Apr 10 03:40:16 2009
> New Revision: 29179
> URL: http://www.lyx.org/trac/changeset/29179
>
> Log:
> Remove last bits of LFUN_INSET_TOGGLE that is used to show the inset settings.
This series of patch looks good Vincent. Congrats.
JMarc
46 matches
Mail list logo
