On 2010-11-23, Jürgen Spitzmüller wrote:
Again, we just need to know in advance if we use XeTeX/LuaTeX
HTML, LyXHTML, Docbook, (+ any custom output format that uses System
Fonts)
OR anything else (because this has consequences for the GUI, namely the
font combos). Everything else can be
On 2010-11-23, Enrico Forestieri wrote:
On Tue, Nov 23, 2010 at 04:58:19PM +0100, Liviu Andronic wrote:
On Tue, Nov 23, 2010 at 4:51 PM, Enrico Forestieri for...@lyx.org wrote:
A google search gives ~8000 hits for latex fonts and ~10 hits
for tex fonts. That's more that one order of
On 2010-11-23, Jürgen Spitzmüller wrote:
Jean-Marc Lasgouttes wrote:
What about useNonLaTeXFonts? useNormalFonts? Use OpenTypeFonts?
I still do not like System.
OK, I understand that. I'm fine with useNonLaTeXFonts. useOpenTypeFonts
is not really appropriate, since also TrueType can be
On 2010-11-23, Jürgen Spitzmüller wrote:
Guenter Milde wrote:
* XeTeX can also use OpenType fonts that are not system-wide installed as
well as traditional LaTeX fonts.
With System Fonts, I do not mean System-wide fonts, but fonts
avaliable to the OS (as opposed to specialized LaTeX fonts)
Le 25/11/2010 01:38, Pavel Sanda a écrit :
JMarc and others,
in lists of modules we have Sweave and Noweb literate programming
both described as a tool for literate programming, so i guess
we should call Sweave module as a Sweave literate programming.
I'd prefer R literate programming 'but I
this is interesting idea even for other backends like docbook
pavel
AFAIK this already works for docbook.
Vincent
I cannot figure out why LyX crashes (happens outside InsetTable) and are
therefore lost. Can you please have a look?
thanks and regards
Uwe
You miss quite some code ;).
1. drawRowSelection is located in TextMetrics and therefore ignores
the offset_valign_,
2. you now have the strange
Guenter Milde wrote:
Both xelatex and luatlaex can use TeX fonts and PSNFSS:
OK, another argument for the checkbox! We just need to add xetex (and maybe
luatex) to the non-texfonts list of possible output formats.
But this needs to be tested first (and can be added easily within the 2.0
Guenter Milde wrote:
Again, we just need to know in advance if we use XeTeX/LuaTeX
HTML, LyXHTML, Docbook, (+ any custom output format that uses System
Fonts)
DocBook is different. We have separate document classes. LyXHTML is not
different yet, since it does not use system fonts (but it
Jean-Marc Lasgouttes wrote:
Le 25/11/2010 01:38, Pavel Sanda a écrit :
JMarc and others,
in lists of modules we have Sweave and Noweb literate programming
both described as a tool for literate programming, so i guess
we should call Sweave module as a Sweave literate programming.
I'd prefer
Le 25/11/2010 10:38, Jürgen Spitzmüller a écrit :
And an argument against separate font combos. How should we know which font
(OpenType or tex) is desired without that checkbox?
Since xtex is not only about fonts, but also algorithms, what about
[ ] use extended typesetting capabilities
hi,
the newest changes in xetex are now in, the same almost holds for luatex -
so its time to start think about beta2 to test these changes.
i would like that some portion of regressions disappears too, so here is
the updated list of regression bugs:
tabular bugs: 6908, 7021
undo at point
Pavel Sanda wrote:
hi,
the newest changes in xetex are now in, the same almost holds for luatex -
so its time to start think about beta2 to test these changes.
i would like that some portion of regressions disappears too, so here is
the updated list of regression bugs:
tabular bugs:
Hi,
I can get no continuous spell check on beta1, but it works fine on svn. I
have attached the output of the .configure command on both trees. Nothing
that I can see points at lyx missing spelling libs on the beta1 (the diff
seems fine). Any idea what could be wrong? The checkbox for continuous
On Thu, Nov 25, 2010 at 2:29 PM, Pavel Sanda sa...@lyx.org wrote:
Jean-Marc Lasgouttes wrote:
in lists of modules we have Sweave and Noweb literate programming
both described as a tool for literate programming, so i guess
we should call Sweave module as a Sweave literate programming.
I'd
Le 25 nov. 2010 à 21:13, Liviu Andronic a écrit :
Hope it's not too late.. I'm not sure that R literate programming is
the best way to label the functionality. The main reason is that in
the R community Sweave is the one and only name for this.
Agreed. However, we need to make sure that
Am 25.11.2010 um 20:53 schrieb Jose Quesada:
Hi,
I can get no continuous spell check on beta1, but it works fine on svn. I
have attached the output of the .configure command on both trees. Nothing
that I can see points at lyx missing spelling libs on the beta1 (the diff
seems fine).
Jean-Marc Lasgouttes wrote:
Le 25 nov. 2010 ? 21:13, Liviu Andronic a écrit :
Hope it's not too late.. I'm not sure that R literate programming is
the best way to label the functionality. The main reason is that in
the R community Sweave is the one and only name for this.
Agreed.
Jose Quesada wrote:
Hi,
I can get no continuous spell check on beta1, but it works fine on svn. I
one solution could be that we fixed something meanwhile...
simply try update your svn tree revision to r36227 (beta1) and try
what happens...
pavel
Yes, this could indeed be a merge problem after svn update.
I had been out of office for several weeks, and svn updated across
hundreds of revisions. I will check out a clean repository again and
report back.
I assume this may resolve this problem, so you do not need to
investigate this
and #7035 (RCS ci fails) - Vincent you have different patch than Stephan
proposed?
pavel
Fixed at r36497.
Vincent
Am 25.11.2010 10:35, schrieb Vincent van Ravesteijn:
You miss quite some code ;).
1. drawRowSelection is located in TextMetrics and therefore ignores
the offset_valign_,
Ah.
2. you now have the strange convention that the offset is positive
when the inset is shifted upwards,
This is the
Btw., do you have a starting point for me how to fix #7056? Where in the
code do we set what is displayed in the context menu?
A good starting point is r36498 ;).
Vincent
Am 26.11.2010 04:32, schrieb Vincent van Ravesteijn:
Btw., do you have a starting point for me how to fix #7056? Where in the
code do we set what is displayed in the context menu?
A good starting point is r36498 ;).
Thank you. I wasn't yet aware of the command command-alternatives.
So we
This issue doesn't seem to have been raised in the bug tracker yet:
When I paste text containing straight quotation marks, I would expect
them to be automatically converted to a \begin_inset Quotes eld (or
erd). If Unicode text is pasted and it contains curly quote
characters, I would
On Mon, Nov 22, 2010 at 10:33 AM, Sebastian Guttenberg
sgut...@math.ist.utl.pt wrote:
This was changed to solve bug http://www.lyx.org/trac/ticket/6587.
Now we move the file to the backup file before saving the current file.
So, we basically do not overwrite the original file, but we move away
On 2010-11-23, Jürgen Spitzmüller wrote:
> Again, we just need to know in advance if we use XeTeX/LuaTeX
HTML, LyXHTML, Docbook, (+ any custom output format that uses System
Fonts)
> OR anything else (because this has consequences for the GUI, namely the
> font combos). Everything else can be
On 2010-11-23, Enrico Forestieri wrote:
> On Tue, Nov 23, 2010 at 04:58:19PM +0100, Liviu Andronic wrote:
>> On Tue, Nov 23, 2010 at 4:51 PM, Enrico Forestieri wrote:
>> > A google search gives ~8000 hits for "latex fonts" and ~10 hits
>> > for "tex fonts". That's more that
On 2010-11-23, Jürgen Spitzmüller wrote:
> Jean-Marc Lasgouttes wrote:
>> What about useNonLaTeXFonts? useNormalFonts? Use OpenTypeFonts?
>> I still do not like System.
> OK, I understand that. I'm fine with useNonLaTeXFonts. useOpenTypeFonts
> is not really appropriate, since also TrueType can
On 2010-11-23, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> * XeTeX can also use OpenType fonts that are not system-wide installed as
>> well as "traditional" LaTeX fonts.
> With "System Fonts", I do not mean "System-wide" fonts, but fonts
> avaliable to the OS (as opposed to specialized
Le 25/11/2010 01:38, Pavel Sanda a écrit :
JMarc and others,
in lists of modules we have "Sweave" and "Noweb literate programming"
both described as a tool for literate programming, so i guess
we should call "Sweave" module as a "Sweave literate programming".
I'd prefer "R literate
> this is interesting idea even for other backends like docbook
>
> pavel
>
AFAIK this already works for docbook.
Vincent
> I cannot figure out why LyX crashes (happens outside InsetTable) and are
> therefore lost. Can you please have a look?
>
> thanks and regards
> Uwe
>
You miss quite some code ;).
1. drawRowSelection is located in TextMetrics and therefore ignores
the offset_valign_,
2. you now have the
Guenter Milde wrote:
> Both xelatex and luatlaex can use TeX fonts and PSNFSS:
OK, another argument for the checkbox! We just need to add xetex (and maybe
luatex) to the non-texfonts list of possible output formats.
But this needs to be tested first (and can be added easily within the 2.0
Guenter Milde wrote:
>> Again, we just need to know in advance if we use XeTeX/LuaTeX
>
> HTML, LyXHTML, Docbook, (+ any custom output format that uses System
> Fonts)
DocBook is different. We have separate document classes. LyXHTML is not
different yet, since it does not use system fonts (but
Jean-Marc Lasgouttes wrote:
> Le 25/11/2010 01:38, Pavel Sanda a écrit :
>> JMarc and others,
>>
>> in lists of modules we have "Sweave" and "Noweb literate programming"
>> both described as a tool for literate programming, so i guess
>> we should call "Sweave" module as a "Sweave literate
Le 25/11/2010 10:38, Jürgen Spitzmüller a écrit :
And an argument against separate font combos. How should we know which font
(OpenType or tex) is desired without that checkbox?
Since xtex is not only about fonts, but also algorithms, what about
[ ] use extended typesetting capabilities
hi,
the newest changes in xetex are now in, the same almost holds for luatex -
so its time to start think about beta2 to test these changes.
i would like that some portion of regressions disappears too, so here is
the updated list of regression bugs:
tabular bugs: 6908, 7021
undo & at point
Pavel Sanda wrote:
> hi,
>
> the newest changes in xetex are now in, the same almost holds for luatex -
> so its time to start think about beta2 to test these changes.
>
> i would like that some portion of regressions disappears too, so here is
> the updated list of regression bugs:
>
> tabular
Hi,
I can get no continuous spell check on beta1, but it works fine on svn. I
have attached the output of the .configure command on both trees. Nothing
that I can see points at lyx missing spelling libs on the beta1 (the diff
seems fine). Any idea what could be wrong? The checkbox for continuous
On Thu, Nov 25, 2010 at 2:29 PM, Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
>>> in lists of modules we have "Sweave" and "Noweb literate programming"
>>> both described as a tool for literate programming, so i guess
>>> we should call "Sweave" module as a "Sweave literate
Le 25 nov. 2010 à 21:13, Liviu Andronic a écrit :
> Hope it's not too late.. I'm not sure that "R literate programming" is
> the best way to label the functionality. The main reason is that in
> the R community Sweave is the one and only name for this.
Agreed. However, we need to make sure that
Am 25.11.2010 um 20:53 schrieb Jose Quesada:
> Hi,
>
> I can get no continuous spell check on beta1, but it works fine on svn. I
> have attached the output of the .configure command on both trees. Nothing
> that I can see points at lyx missing spelling libs on the beta1 (the diff
> seems
Jean-Marc Lasgouttes wrote:
> Le 25 nov. 2010 ? 21:13, Liviu Andronic a écrit :
> > Hope it's not too late.. I'm not sure that "R literate programming" is
> > the best way to label the functionality. The main reason is that in
> > the R community Sweave is the one and only name for this.
>
>
Jose Quesada wrote:
> Hi,
>
> I can get no continuous spell check on beta1, but it works fine on svn. I
one solution could be that we fixed something meanwhile...
simply try update your svn tree revision to r36227 (beta1) and try
what happens...
pavel
Yes, this could indeed be a merge problem after svn update.
I had been out of office for several weeks, and svn updated across
hundreds of revisions. I will check out a clean repository again and
report back.
I assume this may resolve this problem, so you do not need to
investigate this
> and #7035 (RCS ci fails) - Vincent you have different patch than Stephan
> proposed?
>
> pavel
>
Fixed at r36497.
Vincent
Am 25.11.2010 10:35, schrieb Vincent van Ravesteijn:
You miss quite some code ;).
1. drawRowSelection is located in TextMetrics and therefore ignores
the offset_valign_,
Ah.
2. you now have the strange convention that the offset is positive
when the inset is shifted upwards,
This is the
> Btw., do you have a starting point for me how to fix #7056? Where in the
> code do we set what is displayed in the context menu?
>
A good starting point is r36498 ;).
Vincent
Am 26.11.2010 04:32, schrieb Vincent van Ravesteijn:
Btw., do you have a starting point for me how to fix #7056? Where in the
code do we set what is displayed in the context menu?
A good starting point is r36498 ;).
Thank you. I wasn't yet aware of the command "command-alternatives".
So we
This issue doesn't seem to have been raised in the bug tracker yet:
When I paste text containing straight quotation marks, I would expect
them to be automatically converted to a "\begin_inset Quotes eld" (or
erd). If Unicode text is pasted and it contains curly quote
characters, I would
On Mon, Nov 22, 2010 at 10:33 AM, Sebastian Guttenberg
wrote:
>> This was changed to solve bug http://www.lyx.org/trac/ticket/6587.
>>
>> Now we move the file to the backup file before saving the current file.
>> So, we basically do not overwrite the original file, but we
52 matches
Mail list logo