Re: 2.0.6 on OS X: Window resizing from the edges is no longer possible

[Stephan Witt]

Am 11.05.2013 um 05:25 schrieb Jerry lancebo...@qwest.net:

 Hi,
 
 I just downloaded the OS X binary of LyX 2.0.6 and immediately saw a new 
 problem concerning the way windows work. 2.0.5 did not have this problem.
 
 In OS X beginning I believe with 10.7 it is possible to resize windows from 
 any edge, not just the lower left corner. (Windows users are stunned.) When 
 the cursor is moved over any edge (left, right, top, bottom) of the front 
 window, it turns into a tiny two-ended arrow, unless the edge is already at 
 the screen's boundary in which case it is a one-ended arrow. Clicking and 
 dragging then resizes the window from that edge.
 
 LyX 2.0.5, thanks probably to the underlying Qt stuff, handled this correctly.
 
 LyX 2.0.6 does not--the little arrow cursor does not appear, and clicking 
 does not allow resizing in this manner--the click is handled as if window 
 resizing is not active. Resizing by the lower right corner however does still 
 work.
 
 I use a utility called Flexiglass which extends window-sizing, dragging, etc. 
 and it is hobbled now in 2.0.6. For example, dragging a window using a 
 Flexiglass feature which does not require using the normal drag region of a 
 window now allows the window to be dragged beyond the e.g. top of the screen, 
 where normally (and in 2.0.5) the drag was limited to the top of the screen. 
 I have disabled this utility and 2.0.6 still behaves as described above.
 
 Possibly the Qt framework is defective or was configured wrong.

Yes, it's the Qt framework. More precisely it is the Mac OS X API the Qt 
framework is made for.

With LyX 2.0.5.1 we got so many crash reports related to the Qt for Cocoa 
framework I decided
to switch back to the Carbon based Qt until LyX with Qt for Cocoa is stable 
enough.

Stephan

Re: R Journal template and layout

[Jean-Marc Lasgouttes]

Le 12/05/2013 07:22, Scott Kostyshak a écrit :

Can I commit a layout and template for the R Journal? Information on
the journal is here: http://journal.r-project.org/

Yihui made the files and I've tweaked and tested them. They are here:

https://github.com/yihui/lyx/blob/master/templates/RJournal.lyx
https://github.com/yihui/lyx/blob/master/layouts/RJournal.layout


Yes, this makes sense.

JMarc

Re: CMake for Apple?

[Abdelrazak Younes]

On Sat, May 11, 2013 at 11:02 PM, Stephan Witt st.w...@gmx.net wrote:

 Am 11.05.2013 um 17:50 schrieb Abdelrazak Younes you...@lyx.org:

  Hi Stephan,
 
  At LyX meeting we are wondering why you are still using autotools for
 Mac packaging. Do you miss anything from CMake that is not implemented yet?

 Hi all at the LyX meeting,

 I hope you're well and someone is drinking wine too… :)


I had some ;-)



 Regarding the CMake question - I never tried it for a long time.


Ah? I got the impression you were developping using cmake and xcode... But
I see in your other email that this does not work anymore...



 So I cannot answer the question. Isn't the autotools build the official
 one?


Up to now yes, except for Windows.

I was trying to advocate yesterday that we should really move to cmake on
all platforms. I guess this is already a lost battle...

Cheers,
Abdel

Re: patch for scrolling issue - LyXscrollpatch20130302.diff (1/1) - LyXscrollpatch20130421.diff (1/1) - LyXscrollpatch20130427.diff (1/1)

[Jean-Marc Lasgouttes]

Le 09/05/2013 09:43, pdv a écrit :

Yes, I'm available.
I've posted another version as you might already have noticed.


Unfortunately it seems that we will not have time to look at it 
seriously :( This stuff is complicated to get right...


JMarc

Re: Beamer goto buttons and text hyperlinks

[Jean-Marc Lasgouttes]

Le 07/05/2013 07:54, Scott Kostyshak a écrit :

On Tue, Apr 23, 2013 at 11:32 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:

We could maybe have an inset that is only a button when no extra text is
needed and a collapsablme inset otherwise. Somethin in between InsetCommand
and InsetCollapsable.


How difficult would it be to implement this new inset?


I do not really know. Probably not too much. It would have ti inherit 
InsetCollapsable and override the right methods. It might not so difficult.


JMarc

Re: CMake for Apple?

[Vincent van Ravesteijn]

So I cannot answer the question. Isn't the autotools build the
official one?


Up to now yes, except for Windows.

I was trying to advocate yesterday that we should really move to cmake 
on all platforms. I guess this is already a lost battle...


Hmm.. your chances are not that bad really.

Vincent

Re: CMake for Apple?

[Stephan Witt]

Am 12.05.2013 um 11:18 schrieb Abdelrazak Younes you...@lyx.org:

 On Sat, May 11, 2013 at 11:02 PM, Stephan Witt st.w...@gmx.net wrote:
 Am 11.05.2013 um 17:50 schrieb Abdelrazak Younes you...@lyx.org:
 
  Hi Stephan,
 
  At LyX meeting we are wondering why you are still using autotools for Mac 
  packaging. Do you miss anything from CMake that is not implemented yet?
 
 Hi all at the LyX meeting,
 
 I hope you're well and someone is drinking wine too… :)
 
 I had some ;-)
  
 
 Regarding the CMake question - I never tried it for a long time.
 
 Ah? I got the impression you were developping using cmake and xcode... But I 
 see in your other email that this does not work anymore...
 
  
 So I cannot answer the question. Isn't the autotools build the official one?
 
 Up to now yes, except for Windows.
 
 I was trying to advocate yesterday that we should really move to cmake on all 
 platforms. I guess this is already a lost battle…

I'm using CMake to generate the Xcode-project for debugging purposes.

The packaging is done by a shell script to wrap all needed resources into one 
bundle.
The first step is making the pure LyX.app bundle (make install).
Then the additional parts are copied into this app bundle. The used frameworks
(spell checker libraries, gettext and Qt4) needs to be adjusted to make them 
relocatable.
The dictionaries and thesauri are simply copied into it too.

Of course one can do these steps with CMake but I never got a friend of it's 
language
and I'm loosing to much time to find my mistakes when using it. If it had the 
ability to
tell me what it's doing and why… sorry, the verbose option of it is not enough 
for me.

Stephan

Re: XML Parsing Library [was Re: XML For LyX]

[Richard Heck]

On 05/11/2013 07:11 AM, Abdelrazak Younes wrote:
On Sat, May 11, 2013 at 12:03 PM, Abdelrazak Younes you...@lyx.org 
mailto:you...@lyx.org wrote:


On Sat, May 11, 2013 at 8:40 AM, Pavel Sanda sa...@lyx.org
mailto:sa...@lyx.org wrote:

Abdelrazak Younes wrote:
 I will discuss that face2face during the meeting.

You should bring mirror then, no one else in this thread is in
Milano.
Anyway it's too late, Richard already barricaded in
underground garage of his
house and won't show until 378 patches implementing xml is
done as I infer
from the last testament.


I just discussed with Lars. He agrees that using Qt is a good
option... what a shock ! :-)
Vincent and JMarc don't care what we use.

I am talking about QXmlStreamReader and (as a second step)
QXmlStreamWriter. Our lexer class can just use QXmlStreamReader
internally, we don't have to spread the use of this call all other
the place.

So Richard, let's use a new feature repo for that. This is
agreed with Lars, Vincent and JMarc. Then we would create an xml
branch in that repo.

Lars and Vincent are setting this up right now :-)


So now it is set up, look (and check) at the documentation here:

http://wiki.lyx.org/Devel/LyXGit

I have erased all old branches because we want only feature branches 
based on master.


I just created xml branch in there.

Richard, I guess you are still sleeping so I hope you agree with all 
that. My goal is that we  collaborate on the XML support using this 
shared branch and repo.


This is all fine with me. I'll look at the feature branch business 
probably tomorrow. Busy today.


My intention was to work on writing a LyX file first, to try to 
stabilize the format, and then work on reading it.


As far as the Lexer goes, is the proposal to add some XML methods that 
will be implemented using QXmlStreamReader? If so, I'm not sure I see 
the advantage of adding them to the Lexer, as opposed to creating a new 
class for reading XML files.


Is the suggestion then also to write some sort of wrapper for 
QXmlStreamWriter rather than to use its methods directly?


While we're at this, I note that QXmlStream* wants a QIoDevice on which 
to operate, probably a QFile in our case. Any idea about how that should 
be handled? What about zipped files?


Richard

Alignment toolbar

[Alessandro Di Federico]

At the meeting we discussed about introducing some toolbar buttons for
alignment, which is something users request very frequently. I think the
best idea is to move out of the table toolbar the alignment buttons and
make them working for paragraphs too, creating a new toolbar.

I've removed the black border from the icons of the classic set, since
they now don't mean align center the cell content but just align
center (see attachments).

For the oxygen set, I think they're already OK, except for the fact that
in the KDE oxygen package [1] I couldn't find an icon similar to the one
we have for the block alignment. Actually I couldn't find them at all,
where did we get them from? Should I manually create one as I did for
the classic set?

-- 
Ale

[1] http://download.kde.org/stable/4.10.3/src/oxygen-icons-4.10.3.tar.xz
Removes alignment buttons from the table toolbar and introduce the alignment 
toolbar, which works both for table columns and standard paragraphs.

diff --git a/lib/ui/stdtoolbars.inc b/lib/ui/stdtoolbars.inc
index ad4fa74..b8e911f 100644
--- a/lib/ui/stdtoolbars.inc
+++ b/lib/ui/stdtoolbars.inc
@@ -158,11 +158,6 @@ ToolbarSet
 		Item Set all lines inset-modify tabular set-all-lines
 		Item Unset all lines inset-modify tabular unset-all-lines
 		Separator
-		Item Align left command-alternatives inset-modify tabular m-align-left;inset-modify tabular align-left
-		Item Align center command-alternatives inset-modify tabular m-align-center;inset-modify tabular align-center
-		Item Align right command-alternatives inset-modify tabular m-align-right;inset-modify tabular align-right
-		Item Align on decimal inset-modify tabular align-decimal
-		Separator
 		Item Align top command-alternatives inset-modify tabular m-valign-top;inset-modify tabular valign-top
 		Item Align middle command-alternatives inset-modify tabular m-valign-middle;inset-modify tabular valign-middle
 		Item Align bottom command-alternatives inset-modify tabular m-valign-bottom;inset-modify tabular valign-bottom
@@ -1444,4 +1439,12 @@ ToolbarSet
 		Item Global fall unicode-insert 0x2198
 	End
 
+	Toolbar alignment Alignment
+		Item Align left command-alternatives inset-modify tabular m-align-left;inset-modify tabular align-left;paragraph-params \align left
+		Item Align center command-alternatives inset-modify tabular m-align-center;inset-modify tabular align-center;paragraph-params \align center
+		Item Align right command-alternatives inset-modify tabular m-align-right;inset-modify tabular align-right;paragraph-params \align right
+		Item Align block paragraph-params \align block
+		Item Align on decimal inset-modify tabular align-decimal
+	End
+
 End
attachment: tabular-feature_m-align-right.pngattachment: tabular-feature_m-align-left.pngattachment: tabular-feature_m-align-center.pngattachment: paragraph-params_backslashalign_block.png

Re: CMake for Apple?

[Benjamin Piwowarski]

Hi,

I would be happy to participate (in July/August) to make the cmake building 
process complete and more fool-proof on mac (a few months ago I was able to 
build successfully a working bundle). If some are interested to do the same 
effort for the linux platform, then it could be an occasion to get rid of the 
old auto-tools chain since windows is already not using it. Maintaining two 
build systems is cumbersome and may introduce lots of compilation errors when 
switching from one tool to the other (this happened when I submitted patches to 
LyX).

benjamin

On May 12, 2013, at 13:41 , Stephan Witt st.w...@gmx.net wrote:

 Am 12.05.2013 um 11:18 schrieb Abdelrazak Younes you...@lyx.org:
 
 On Sat, May 11, 2013 at 11:02 PM, Stephan Witt st.w...@gmx.net wrote:
 Am 11.05.2013 um 17:50 schrieb Abdelrazak Younes you...@lyx.org:
 
 Hi Stephan,
 
 At LyX meeting we are wondering why you are still using autotools for Mac 
 packaging. Do you miss anything from CMake that is not implemented yet?
 
 Hi all at the LyX meeting,
 
 I hope you're well and someone is drinking wine too… :)
 
 I had some ;-)
 
 
 Regarding the CMake question - I never tried it for a long time.
 
 Ah? I got the impression you were developping using cmake and xcode... But I 
 see in your other email that this does not work anymore...
 
 
 So I cannot answer the question. Isn't the autotools build the official one?
 
 Up to now yes, except for Windows.
 
 I was trying to advocate yesterday that we should really move to cmake on 
 all platforms. I guess this is already a lost battle…
 
 I'm using CMake to generate the Xcode-project for debugging purposes.
 
 The packaging is done by a shell script to wrap all needed resources into one 
 bundle.
 The first step is making the pure LyX.app bundle (make install).
 Then the additional parts are copied into this app bundle. The used frameworks
 (spell checker libraries, gettext and Qt4) needs to be adjusted to make them 
 relocatable.
 The dictionaries and thesauri are simply copied into it too.
 
 Of course one can do these steps with CMake but I never got a friend of it's 
 language
 and I'm loosing to much time to find my mistakes when using it. If it had the 
 ability to
 tell me what it's doing and why… sorry, the verbose option of it is not 
 enough for me.
 
 Stephan

Re: Slide preview

[Alessandro Di Federico]

On Sat, 2013-05-11 at 00:36 -0700, Pavel Sanda wrote:
  The idea would be to render a single page at a time, so we can
 re-render
 
 It will be very tricky to get correct numbering for e.g. equations.

Yeah, but we have the same problem with instant preview in equations,
I'll look if we can do something about it.
We are already able to show the correct numbering in the formula, so it
should be possible to initialize the counter at the beginning of the
preview document correctly.

  them in the background now and then (when the cursor leaves the
  interested area?) without having to re-generate the whole document,
  which wouldn't scale well.
 
 If you are going along the lines above, please note that there is
 reoccuring request for automatic background updates for (pre)viewed
 document, so you can instantly see the result of your editation
 without need for ctrl+shift+t/r.
 Consider to make the infrastructure generic enough so this is easy to
 add as a new lfun or similar.

I'll take that into account, but as I said the idea is to make the
preview page by page.

-- 
Ale

Re: [features/refs/heads/kill-gettext] UserGuide.lyx: next revision step

[Stephan Witt]

Am 12.05.2013 um 16:51 schrieb v...@lyx.org:

 Author: Uwe Stöhr uwesto...@lyx.org
 Date: Sun, 12 May 2013 12:57:14 +0200
 New Commit: 1fded6e8175e92c1eaa1e85db7c3f8187e47e602
 URL: 
 http://git.lyx.org/?p=features.git;a=commit;h=1fded6e8175e92c1eaa1e85db7c3f8187e47e602
 
 Log:
 UserGuide.lyx: next revision step
 
 - sec. 6.7 - 6.13
 

Since commit 704328d3488c75733ddeb9ad5439b1907e323e39 there is no diff sent to 
the list anymore.

Stephan

BTW: The german users guide is not compilable anymore. Am I the only one seeing 
this?

The LaTeX log:
LaTeX Warning: Reference `sec:Umgebungen-schachteln' on page 27 undefined on in
put line 1612.
LaTeX Warning: Reference `sub:Variabler-horiz-Abstand' on page 27 undefined on 
input line 1619.
[27]
LaTeX Warning: Reference `sec:TeX-Code' on page 28 undefined on input line 1648.
[28]
LaTeX Warning: Citation `enumitem' on page 29 undefined on input line 1762.
[29]
! Missing \endcsname inserted.
to be read again 
   \protect 
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
The control sequence marked to be read again should
not appear between \csname and \endcsname.

! Extra \endcsname.
\enitkv@split ...enitkv@prefix \@tempa \endcsname 
  \ifx \@tempc \relax \enitk...
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
I'm ignoring this, since I wasn't doing a \csname.

! Missing \endcsname inserted.
to be read again 
   \protect 
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
The control sequence marked to be read again should
not appear between \csname and \endcsname.

! Extra \endcsname.
\@ifundefined ...dafter \ifx \csname #1\endcsname 
  \relax \expandafter \@firs...
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
I'm ignoring this, since I wasn't doing a \csname.

! Missing \endcsname inserted.
to be read again 
   \protect 
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
The control sequence marked to be read again should
not appear between \csname and \endcsname.

! Extra \endcsname.
\enitkv@split ...enitkv@prefix \@tempa \endcsname 
  \ifx \@tempc \relax \enitk...
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
I'm ignoring this, since I wasn't doing a \csname.

! Missing \endcsname inserted.
to be read again 
   \protect 
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
The control sequence marked to be read again should
not appear between \csname and \endcsname.

! Extra \endcsname.
\@ifundefined ...dafter \ifx \csname #1\endcsname 
  \relax \expandafter \@firs...
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
I'm ignoring this, since I wasn't doing a \csname.


! Package enumitem Error: \csnameforeignlanguage \endcsname {ngerman}{labelinde
nt=0pt, labelsep=1cm, font=\itshape , style=nextline} undefined.

See the enumitem package documentation for explanation.
Type  H return  for immediate help.
 ...  
  
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
Try typing  return  to proceed.
If that doesn't work, type  X return  to quit.


Overfull \hbox (22.13562pt too wide) in paragraph at lines 1790--1792
[]\T1/cmr/m/n/12 verwendet wird: [][][][]la-be-lin-dent=0pt, la-bel-sep=1cm, fo
nt=\T1/cmr/m/it/12 , sty-le=nextline\T1/cmr/m/n/12 labelindent=0pt,
 []

Re: CMake for Apple?

[Stephan Witt]

Am 12.05.2013 um 17:04 schrieb Benjamin Piwowarski 
benjamin.piwowar...@lip6.fr:

 Hi,
 
 I would be happy to participate (in July/August) to make the cmake building 
 process complete and more fool-proof on mac (a few months ago I was able to 
 build successfully a working bundle).

What do you call a working bundle? It has to contain the frameworks it depends 
on.
Anyway, I have no preference for one build system or the other. And of course 
your
support would be greatly appreciated.

Stephan

 If some are interested to do the same effort for the linux platform, then it 
 could be an occasion to get rid of the old auto-tools chain since windows is 
 already not using it. Maintaining two build systems is cumbersome and may 
 introduce lots of compilation errors when switching from one tool to the 
 other (this happened when I submitted patches to LyX).
 
 benjamin
 
 On May 12, 2013, at 13:41 , Stephan Witt st.w...@gmx.net wrote:
 
 Am 12.05.2013 um 11:18 schrieb Abdelrazak Younes you...@lyx.org:
 
 On Sat, May 11, 2013 at 11:02 PM, Stephan Witt st.w...@gmx.net wrote:
 Am 11.05.2013 um 17:50 schrieb Abdelrazak Younes you...@lyx.org:
 
 Hi Stephan,
 
 At LyX meeting we are wondering why you are still using autotools for Mac 
 packaging. Do you miss anything from CMake that is not implemented yet?
 
 Hi all at the LyX meeting,
 
 I hope you're well and someone is drinking wine too… :)
 
 I had some ;-)
 
 
 Regarding the CMake question - I never tried it for a long time.
 
 Ah? I got the impression you were developping using cmake and xcode... But 
 I see in your other email that this does not work anymore...
 
 
 So I cannot answer the question. Isn't the autotools build the official 
 one?
 
 Up to now yes, except for Windows.
 
 I was trying to advocate yesterday that we should really move to cmake on 
 all platforms. I guess this is already a lost battle…
 
 I'm using CMake to generate the Xcode-project for debugging purposes.
 
 The packaging is done by a shell script to wrap all needed resources into 
 one bundle.
 The first step is making the pure LyX.app bundle (make install).
 Then the additional parts are copied into this app bundle. The used 
 frameworks
 (spell checker libraries, gettext and Qt4) needs to be adjusted to make them 
 relocatable.
 The dictionaries and thesauri are simply copied into it too.
 
 Of course one can do these steps with CMake but I never got a friend of it's 
 language
 and I'm loosing to much time to find my mistakes when using it. If it had 
 the ability to
 tell me what it's doing and why… sorry, the verbose option of it is not 
 enough for me.
 
 Stephan
 
 
 

Re: [features/refs/heads/kill-gettext] UserGuide.lyx: next revision step

[Vincent van Ravesteijn]

Since commit 704328d3488c75733ddeb9ad5439b1907e323e39 there is no diff sent to 
the list anymore.

Stephan



This commit is not sent to the list indeed.  Commit  03f98402f (Fix 
crash with FindAndReplaceUi) is sent to the list twice ;)..


Vincent

Re: Slide preview

[Pavel Sanda]

Alessandro Di Federico wrote:
 We are already able to show the correct numbering in the formula, so it

IIRC only because we flush all equation to one file and process them together.
The moment you separate it into single page, correct numbering is gone.

Pavel

Re: bug on Lyx 2.0.6?

[Julien Rioux]

On 09/05/2013 5:05 PM, Nicola Scafetta, Ph. D. wrote:

The bug with LyXHTML, which is different from that encountered with
elyxer.py, is the following.

See the attached files.

In the .xhtml file the reference in the text appears with a symbol after
the year that should not be there.



I see this too. The modifier, which is an additional letter used if 
you have more than one reference with the same author and year, isn't 
initialized properly. We should fix this in LyX, so thanks for your 
report of the problem.



The reference in the Bibliography starts with [White(2010)] that
should not be visible.



This is at the moment not customizable, so you would have to remove it 
yourself, unfortunately. Maybe we can have this customizable in LyX 2.1.



Compare the .xhtml file with the .pdf of the same .lyx file.


nicola



Cheers,
Julien

Re: [PATCH] WIP Make python scripts work with python3

[Julien Rioux]

On 12/05/2013 10:07 AM, Lars Gullik Bjønnes wrote:

---
  development/autotests/keytest.py | 112 ++--
  development/cmake/doc/ReplaceValues.py   |   4 +-
  development/cmake/po/cat.py  |   2 +-
  development/keystest/cache-bisect.py |  78 +--
  development/keystest/keytest.py  |  62 +--
  development/keystest/make_screenshot_html.py |  20 +-
  development/tools/convert_kmap.py|  18 +-
  development/tools/generate_symbols_images.py |  14 +-
  development/tools/generate_symbols_list.py   |  28 +-
  development/tools/unicodesymbols.py  |   2 +-
  lib/configure.py |  14 +-
  lib/generate_contributions.py| 786 +--
  lib/lyx2lyx/LyX.py   |   8 +-
  lib/lyx2lyx/generate_encoding_info.py|   8 +-
  lib/lyx2lyx/lyx2lyx_tools.py |   2 +-
  lib/lyx2lyx/lyx_1_2.py   |   6 +-
  lib/lyx2lyx/lyx_1_4.py   |   4 +-
  lib/lyx2lyx/lyx_1_5.py   |  70 +--
  lib/lyx2lyx/lyx_1_6.py   |  10 +-
  lib/lyx2lyx/lyx_2_1.py   |  24 +-
  lib/lyx2lyx/parser_tools.py  |  12 +-
  lib/lyx2lyx/unicode_symbols.py   |   6 +-
  lib/scripts/TeXFiles.py  |  10 +-
  lib/scripts/convertDefault.py|   4 +-
  lib/scripts/date.py  |   2 +-
  lib/scripts/fen2ascii.py |   8 +-
  lib/scripts/fig2pdftex.py|   6 +-
  lib/scripts/fig2pstex.py |   2 +-
  lib/scripts/fig_copy.py  |   8 +-
  lib/scripts/html2latexwrapper.py |   2 +-
  lib/scripts/include_bib.py   |   8 +-
  lib/scripts/legacy_lyxpreview2ppm.py |   6 +-
  lib/scripts/lyxpak.py|   4 +-
  lib/scripts/lyxpreview2bitmap.py |   6 +-
  lib/scripts/lyxpreview_tools.py  |   2 +-
  lib/scripts/prefs2prefs.py   |  18 +-
  lib/scripts/prefs2prefs_prefs.py |   4 +-
  po/lyx_pot.py|  74 +--
  po/postats.py|   6 +-
  src/tex2lyx/test/runtests.py |   2 +-
  40 files changed, 731 insertions(+), 731 deletions(-)

diff --git a/development/autotests/keytest.py b/development/autotests/keytest.py
index a510a3f..5331348 100755
--- a/development/autotests/keytest.py
+++ b/development/autotests/keytest.py
@@ -16,7 +16,7 @@ import time
  #from subprocess import call
  import subprocess

-print 'Beginning keytest.py'
+print('Beginning keytest.py')

  FNULL = open('/dev/null', 'w')

@@ -78,7 +78,7 @@ class CommandSourceFromFile(CommandSource):
  self.infile.close()
  linesbak = self.lines
  self.p = p
-print p, self.p, 'self.p'
+print(p, self.p, 'self.p')


Is this intended to support both python 2 and 3? From a quick glance I 
do not see from __future__ import print_function anywhere.


--
Julien

Re: [features/refs/heads/kill-gettext] UserGuide.lyx: next revision step

[Pavel Sanda]

Vincent van Ravesteijn wrote:
 This commit is not sent to the list indeed.  Commit  03f98402f (Fix crash 

I guess because it's in features repository. Some hook from normal
repo should be taken?
Pavel

Re: Re: [PATCH] WIP Make python scripts work with python3

[José Matos]

On Sunday 12 May 2013 12:46:26 Julien Rioux wrote:
 Is this intended to support both python 2 and 3? From a quick glance I 
 do not see from __future__ import print_function anywhere.

If it did that then the minimal version required would need to be 2.6.

As it is the parenthesis are ignore in python 2 and required in python 3.

FWIW I don't understand why this patch dropped the _u _ prefix as it is valid 
python 3.3 and honestly we should not care about previous python 3 versions.

-- 
José Abílio

Re: [features/refs/heads/kill-gettext] UserGuide.lyx: next revision step

[Pavel Sanda]

Pavel Sanda wrote:
 Vincent van Ravesteijn wrote:
  This commit is not sent to the list indeed.  Commit  03f98402f (Fix crash 
 
 I guess because it's in features repository. Some hook from normal
 repo should be taken?

And no matter who commits, the email sender of all commits is v...@lyx.org ;(
P

Re: [features/refs/heads/kill-gettext] UserGuide.lyx: next revision step

[Pavel Sanda]

v...@lyx.org wrote:
 Author: Uwe Stöhr uwesto...@lyx.org
 Date: Sun, 12 May 2013 12:57:14 +0200
 New Commit: 1fded6e8175e92c1eaa1e85db7c3f8187e47e602
 URL: 
 http://git.lyx.org/?p=features.git;a=commit;h=1fded6e8175e92c1eaa1e85db7c3f8187e47e602

Uwe, you scatter eoln conversion all over the place, just click on the link 
above.
Can't you ask all the git gurus around you?
Pavel

Re: Re: Appendix sections are numbered incorrectly on screen (but do appear correctly on DVI/PDF)

[José Matos]

On Friday 10 May 2013 16:23:26 Richard Heck wrote:
 I think I will probably release 2.0.7 fairly early, as well. There are 
 some important fixes in it already, including this one. And, of course, 
 there's the update to the Portuguese translation to include. 
 
 Richard

I only take the bait on Fridays. :-)

-- 
José Abílio

Re: [PATCH] WIP Make python scripts work with python3

[Julien Rioux]

On 12/05/2013 1:00 PM, José Matos wrote:

On Sunday 12 May 2013 12:46:26 Julien Rioux wrote:

Is this intended to support both python 2 and 3? From a quick glance I
do not see from __future__ import print_function anywhere.


If it did that then the minimal version required would need to be 2.6.

As it is the parenthesis are ignore in python 2 and required in python 3.



Not quite ignored, if you have comma-delimited stuff and add () then 
python 2 prints a tuple:


$ python
Python 2.7 (r27:82500, Aug 07 2010, 16:54:59) [GCC] on linux2
Type help, copyright, credits or license for more information.
 print 'h', 0
h 0
 print('h', 0)
('h', 0)
 from __future__ import print_function
 print('h', 0)
h 0

--
Julien

Re: Alignment toolbar

[Liviu Andronic]

Dear Alessandro,


On Sun, May 12, 2013 at 4:29 PM, Alessandro Di Federico
a...@clearmind.me wrote:
 At the meeting we discussed about introducing some toolbar buttons for
 alignment, which is something users request very frequently. I think the
 best idea is to move out of the table toolbar the alignment buttons and
 make them working for paragraphs too, creating a new toolbar.

If we start playing around with toolbar refinements, then I would
suggest to review an older (and long!) discussion on the topic, and
more specifically some toolbar-UI arguments and work that Rob has
done:
http://thread.gmane.org/gmane.editors.lyx.devel/133311/focus=133420
http://thread.gmane.org/gmane.editors.lyx.devel/133311/focus=133438
http://thread.gmane.org/gmane.editors.lyx.devel/133311/focus=133477

He has then proposed a clean-up and redesign of the toolbars in LyX,
to make them more professional. Here's a screenshot of what he had
in mind:
http://thread.gmane.org/gmane.editors.lyx.devel/133587/focus=133587

It's worth revisiting this if we start changing the toolbars.

Regards,
Liviu


 I've removed the black border from the icons of the classic set, since
 they now don't mean align center the cell content but just align
 center (see attachments).

 For the oxygen set, I think they're already OK, except for the fact that
 in the KDE oxygen package [1] I couldn't find an icon similar to the one
 we have for the block alignment. Actually I couldn't find them at all,
 where did we get them from? Should I manually create one as I did for
 the classic set?

 --
 Ale

 [1] http://download.kde.org/stable/4.10.3/src/oxygen-icons-4.10.3.tar.xz



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Trac mails b0rken

[Pavel Sanda]

Seems I'm no more getting mails when bugs are changed in trac.
Anyone else?

Re: Trac mails b0rken

[Liviu Andronic]

On Sun, May 12, 2013 at 7:52 PM, Pavel Sanda sa...@lyx.org wrote:
 Seems I'm no more getting mails when bugs are changed in trac.
 Anyone else?

I'm getting mines.

Liviu


-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: Trac mails b0rken

[Pavel Sanda]

Liviu Andronic wrote:
 On Sun, May 12, 2013 at 7:52 PM, Pavel Sanda sa...@lyx.org wrote:
  Seems I'm no more getting mails when bugs are changed in trac.
  Anyone else?
 
 I'm getting mines.

Indeed it seems if CC myself with lyx unrelated email it works, if I'm CC-ed
either as sanda or sa...@lyx.org I get nothing (the @lyx.org mail work fine
itself though).

Pavel

Re: Trac mails b0rken

[Georg Baum]

Pavel Sanda wrote:

 Liviu Andronic wrote:
 On Sun, May 12, 2013 at 7:52 PM, Pavel Sanda sa...@lyx.org wrote:
  Seems I'm no more getting mails when bugs are changed in trac.
  Anyone else?
 
 I'm getting mines.
 
 Indeed it seems if CC myself with lyx unrelated email it works, if I'm
 CC-ed either as sanda or sa...@lyx.org I get nothing (the @lyx.org mail
 work fine itself though).

I don't get any trac mail either, but I do get the cvs list emails to the 
.lyx.org address.


Georg

Re: Trac mails b0rken

[Pavel Sanda]

Georg Baum wrote:
  Indeed it seems if CC myself with lyx unrelated email it works, if I'm
  CC-ed either as sanda or sa...@lyx.org I get nothing (the @lyx.org mail
  work fine itself though).
 
 I don't get any trac mail either, but I do get the cvs list emails to the 
 .lyx.org address.

Hm. That means that all the mass triage of 2.1 milestoned bugs with all
the posted questions will be ignored.

Pavel

Re: Trac mails b0rken

[Julien Rioux]

On 12/05/2013 2:56 PM, Pavel Sanda wrote:

Georg Baum wrote:

Indeed it seems if CC myself with lyx unrelated email it works, if I'm
CC-ed either as sanda or sa...@lyx.org I get nothing (the @lyx.org mail
work fine itself though).


I don't get any trac mail either, but I do get the cvs list emails to the
.lyx.org address.


Hm. That means that all the mass triage of 2.1 milestoned bugs with all
the posted questions will be ignored.

Pavel



I did get a couple ticket emails to @lyx.org, don't know if I missed 
any. Is the plan to release LyX 2.1 this month?


--
Julien

Re: Trac mails b0rken

[Vincent van Ravesteijn]

Op 12-5-2013 20:56, Pavel Sanda schreef:

Georg Baum wrote:

Indeed it seems if CC myself with lyx unrelated email it works, if I'm
CC-ed either as sanda or sa...@lyx.org I get nothing (the @lyx.org mail
work fine itself though).

I don't get any trac mail either, but I do get the cvs list emails to the
.lyx.org address.

Hm. That means that all the mass triage of 2.1 milestoned bugs with all
the posted questions will be ignored.

Pavel


I got them all.

Vincent

Re: Slide preview

[Alessandro Di Federico]

On Sun, 2013-05-12 at 09:38 -0700, Pavel Sanda wrote:
 IIRC only because we flush all equation to one file and process them
 together.
 The moment you separate it into single page, correct numbering is
 gone.

Actually Richard implemented counter saving for XHTML export, attached
there's a patch which saves the counters also in normal situations. It
also works if the Number equations by section module is enabled, as
you can see with the attached document. 
I don't know if it's appropriate to save counters each time the math
inset is modified, maybe we should introduce a new UpdateType for
instant preview, or just reuse UpdateType::OutputUpdate for IP.
Let me know what you think.

Currently we just save equation, chapter and section counters. I wonder
if there's a reason against saving all the possible counters, just to be
sure, in case the user wants to do custom stuffs (e.g. number equations
by subsections). Richard?

Maybe I can reuse (and factorize) Richard's code also for page preview.

-- 
Ale


numbered-formulas.lyx
Description: application/lyx
Fix for instant preview equation numbering: save counters also in normal
rendering, not just when exporting.

diff --git a/src/mathed/InsetMathHull.cpp b/src/mathed/InsetMathHull.cpp
index 7059914..9e7a3a0 100644
--- a/src/mathed/InsetMathHull.cpp
+++ b/src/mathed/InsetMathHull.cpp
@@ -251,19 +251,16 @@ void InsetMathHull::updateBuffer(ParIterator const  it, UpdateType utype)
 			buffer_-masterBuffer()-params().documentClass().counters();
 
 		// right now, we only need to do this at export time
-		if (utype == OutputUpdate) {
-			for (size_t i = 0; i  numcnts; ++i) {
-docstring const cnt = from_ascii(counters_to_save[i]);
-if (cnts.hasCounter(cnt))
-	counter_map[cnt] = cnts.value(cnt);
-			}
+		for (size_t i = 0; i  numcnts; ++i) {
+			docstring const cnt = from_ascii(counters_to_save[i]);
+			if (cnts.hasCounter(cnt))
+counter_map[cnt] = cnts.value(cnt);
 		}
 
 		// this has to be done separately
 		docstring const eqstr = from_ascii(equation);
 		if (cnts.hasCounter(eqstr)) {
-			if (utype == OutputUpdate)
-counter_map[eqstr] = cnts.value(eqstr);
+			counter_map[eqstr] = cnts.value(eqstr);
 			for (size_t i = 0; i != label_.size(); ++i) {
 if (numbered(i)) {
 	cnts.step(eqstr, utype);
@@ -609,7 +606,7 @@ void InsetMathHull::preparePreview(DocIterator const  pos,
 	}
 
 	docstring setcnt;
-	if (forexport  haveNumbers()) {
+	if (haveNumbers()) {
 		docstring eqstr = from_ascii(equation);
 		CounterMap::const_iterator it = counter_map.find(eqstr);
 		if (it != counter_map.end()) {

Re: Trac mails b0rken

[Pavel Sanda]

Vincent van Ravesteijn wrote:
 I got them all.

ldm conspiracy  :))

Re: Trac mails b0rken

[Vincent van Ravesteijn]

On Sunday, May 12, 2013, Pavel Sanda sa...@lyx.org wrote:
 Vincent van Ravesteijn wrote:
 I got them all.

 ldm conspiracy  :))


We really thought you received everything, because you agreed on everything
that we decided.

Vincent

Re: Slide preview

[Richard Heck]

I had the idea at one time to use this code for better on screen numbering
of something and restricted it to OutputUpdate only so as not to waste
memory and time unnecessarily. As for saving all counters, I'd try to save
only what you need. If that fails, we can do otherwise.

R
On May 12, 2013 3:45 PM, Alessandro Di Federico a...@clearmind.me wrote:

 On Sun, 2013-05-12 at 09:38 -0700, Pavel Sanda wrote:
  IIRC only because we flush all equation to one file and process them
  together.
  The moment you separate it into single page, correct numbering is
  gone.

 Actually Richard implemented counter saving for XHTML export, attached
 there's a patch which saves the counters also in normal situations. It
 also works if the Number equations by section module is enabled, as
 you can see with the attached document.
 I don't know if it's appropriate to save counters each time the math
 inset is modified, maybe we should introduce a new UpdateType for
 instant preview, or just reuse UpdateType::OutputUpdate for IP.
 Let me know what you think.

 Currently we just save equation, chapter and section counters. I wonder
 if there's a reason against saving all the possible counters, just to be
 sure, in case the user wants to do custom stuffs (e.g. number equations
 by subsections). Richard?

 Maybe I can reuse (and factorize) Richard's code also for page preview.

 --
 Ale

Re: 2.0.6 on OS X: Window resizing from the edges is no longer possible

[Stephan Witt]

Am 11.05.2013 um 05:25 schrieb Jerry :

> Hi,
> 
> I just downloaded the OS X binary of LyX 2.0.6 and immediately saw a new 
> problem concerning the way windows work. 2.0.5 did not have this problem.
> 
> In OS X beginning I believe with 10.7 it is possible to resize windows from 
> any edge, not just the lower left corner. (Windows users are stunned.) When 
> the cursor is moved over any edge (left, right, top, bottom) of the front 
> window, it turns into a tiny two-ended arrow, unless the edge is already at 
> the screen's boundary in which case it is a one-ended arrow. Clicking and 
> dragging then resizes the window from that edge.
> 
> LyX 2.0.5, thanks probably to the underlying Qt stuff, handled this correctly.
> 
> LyX 2.0.6 does not--the little arrow cursor does not appear, and clicking 
> does not allow resizing in this manner--the click is handled as if window 
> resizing is not active. Resizing by the lower right corner however does still 
> work.
> 
> I use a utility called Flexiglass which extends window-sizing, dragging, etc. 
> and it is hobbled now in 2.0.6. For example, dragging a window using a 
> Flexiglass feature which does not require using the normal drag region of a 
> window now allows the window to be dragged beyond the e.g. top of the screen, 
> where normally (and in 2.0.5) the drag was limited to the top of the screen. 
> I have disabled this utility and 2.0.6 still behaves as described above.
> 
> Possibly the Qt framework is defective or was configured wrong.

Yes, it's the Qt framework. More precisely it is the Mac OS X API the Qt 
framework is made for.

With LyX 2.0.5.1 we got so many crash reports related to the Qt for Cocoa 
framework I decided
to switch back to the Carbon based Qt until LyX with Qt for Cocoa is stable 
enough.

Stephan

Re: R Journal template and layout

[Jean-Marc Lasgouttes]

Le 12/05/2013 07:22, Scott Kostyshak a écrit :

Can I commit a layout and template for the R Journal? Information on
the journal is here: http://journal.r-project.org/

Yihui made the files and I've tweaked and tested them. They are here:

https://github.com/yihui/lyx/blob/master/templates/RJournal.lyx
https://github.com/yihui/lyx/blob/master/layouts/RJournal.layout


Yes, this makes sense.

JMarc

Re: CMake for Apple?

[Abdelrazak Younes]

On Sat, May 11, 2013 at 11:02 PM, Stephan Witt  wrote:

> Am 11.05.2013 um 17:50 schrieb Abdelrazak Younes :
>
> > Hi Stephan,
> >
> > At LyX meeting we are wondering why you are still using autotools for
> Mac packaging. Do you miss anything from CMake that is not implemented yet?
>
> Hi all at the LyX meeting,
>
> I hope you're well and someone is drinking wine too… :)
>

I had some ;-)


>
> Regarding the CMake question - I never tried it for a long time.
>

Ah? I got the impression you were developping using cmake and xcode... But
I see in your other email that this does not work anymore...



> So I cannot answer the question. Isn't the autotools build the official
> one?
>

Up to now yes, except for Windows.

I was trying to advocate yesterday that we should really move to cmake on
all platforms. I guess this is already a lost battle...

Cheers,
Abdel

Re: patch for scrolling issue - LyXscrollpatch20130302.diff (1/1) - LyXscrollpatch20130421.diff (1/1) - LyXscrollpatch20130427.diff (1/1)

[Jean-Marc Lasgouttes]

Le 09/05/2013 09:43, pdv a écrit :

Yes, I'm available.
I've posted another version as you might already have noticed.


Unfortunately it seems that we will not have time to look at it 
seriously :( This stuff is complicated to get right...


JMarc

Re: Beamer goto buttons and text hyperlinks

[Jean-Marc Lasgouttes]

Le 07/05/2013 07:54, Scott Kostyshak a écrit :

On Tue, Apr 23, 2013 at 11:32 AM, Jean-Marc Lasgouttes
 wrote:

We could maybe have an inset that is only a button when no extra text is
needed and a collapsablme inset otherwise. Somethin in between InsetCommand
and InsetCollapsable.


How difficult would it be to implement this new inset?


I do not really know. Probably not too much. It would have ti inherit 
InsetCollapsable and override the right methods. It might not so difficult.


JMarc

Re: CMake for Apple?

[Vincent van Ravesteijn]

So I cannot answer the question. Isn't the autotools build the
official one?


Up to now yes, except for Windows.

I was trying to advocate yesterday that we should really move to cmake 
on all platforms. I guess this is already a lost battle...


Hmm.. your chances are not that bad really.

Vincent

Re: CMake for Apple?

[Stephan Witt]

Am 12.05.2013 um 11:18 schrieb Abdelrazak Younes :

> On Sat, May 11, 2013 at 11:02 PM, Stephan Witt  wrote:
>> Am 11.05.2013 um 17:50 schrieb Abdelrazak Younes :
>> 
>> > Hi Stephan,
>> >
>> > At LyX meeting we are wondering why you are still using autotools for Mac 
>> > packaging. Do you miss anything from CMake that is not implemented yet?
>> 
>> Hi all at the LyX meeting,
>> 
>> I hope you're well and someone is drinking wine too… :)
>> 
> I had some ;-)
>  
> 
>> Regarding the CMake question - I never tried it for a long time.
>> 
> Ah? I got the impression you were developping using cmake and xcode... But I 
> see in your other email that this does not work anymore...
> 
>>  
>> So I cannot answer the question. Isn't the autotools build the official one?
>> 
> Up to now yes, except for Windows.
> 
> I was trying to advocate yesterday that we should really move to cmake on all 
> platforms. I guess this is already a lost battle…

I'm using CMake to generate the Xcode-project for debugging purposes.

The packaging is done by a shell script to wrap all needed resources into one 
bundle.
The first step is making the pure LyX.app bundle (make install).
Then the additional parts are copied into this app bundle. The used frameworks
(spell checker libraries, gettext and Qt4) needs to be adjusted to make them 
relocatable.
The dictionaries and thesauri are simply copied into it too.

Of course one can do these steps with CMake but I never got a friend of it's 
language
and I'm loosing to much time to find my mistakes when using it. If it had the 
ability to
tell me what it's doing and why… sorry, the verbose option of it is not enough 
for me.

Stephan

Re: XML Parsing Library [was Re: XML For LyX]

[Richard Heck]

On 05/11/2013 07:11 AM, Abdelrazak Younes wrote:
On Sat, May 11, 2013 at 12:03 PM, Abdelrazak Younes > wrote:


On Sat, May 11, 2013 at 8:40 AM, Pavel Sanda > wrote:

Abdelrazak Younes wrote:
> I will discuss that face2face during the meeting.

You should bring mirror then, no one else in this thread is in
Milano.
Anyway it's too late, Richard already barricaded in
underground garage of his
house and won't show until 378 patches implementing xml is
done as I infer
from the last testament.


I just discussed with Lars. He agrees that using Qt is a good
option... what a shock ! :-)
Vincent and JMarc don't care what we use.

I am talking about QXmlStreamReader and (as a second step)
QXmlStreamWriter. Our lexer class can just use QXmlStreamReader
internally, we don't have to spread the use of this call all other
the place.

So Richard, let's use a new "feature" repo for that. This is
agreed with Lars, Vincent and JMarc. Then we would create an "xml"
branch in that repo.

Lars and Vincent are setting this up right now :-)


So now it is set up, look (and check) at the documentation here:

http://wiki.lyx.org/Devel/LyXGit

I have erased all old branches because we want only feature branches 
based on "master".


I just created "xml" branch in there.

Richard, I guess you are still sleeping so I hope you agree with all 
that. My goal is that we  collaborate on the XML support using this 
shared branch and repo.


This is all fine with me. I'll look at the feature branch business 
probably tomorrow. Busy today.


My intention was to work on writing a LyX file first, to try to 
stabilize the format, and then work on reading it.


As far as the Lexer goes, is the proposal to add some XML methods that 
will be implemented using QXmlStreamReader? If so, I'm not sure I see 
the advantage of adding them to the Lexer, as opposed to creating a new 
class for reading XML files.


Is the suggestion then also to write some sort of wrapper for 
QXmlStreamWriter rather than to use its methods directly?


While we're at this, I note that QXmlStream* wants a QIoDevice on which 
to operate, probably a QFile in our case. Any idea about how that should 
be handled? What about zipped files?


Richard

Alignment toolbar

[Alessandro Di Federico]

At the meeting we discussed about introducing some toolbar buttons for
alignment, which is something users request very frequently. I think the
best idea is to move out of the table toolbar the alignment buttons and
make them working for paragraphs too, creating a new toolbar.

I've removed the black border from the icons of the classic set, since
they now don't mean "align center the cell content" but just "align
center" (see attachments).

For the oxygen set, I think they're already OK, except for the fact that
in the KDE oxygen package [1] I couldn't find an icon similar to the one
we have for the "block" alignment. Actually I couldn't find them at all,
where did we get them from? Should I manually create one as I did for
the classic set?

-- 
Ale

[1] http://download.kde.org/stable/4.10.3/src/oxygen-icons-4.10.3.tar.xz
Removes alignment buttons from the table toolbar and introduce the alignment 
toolbar, which works both for table columns and standard paragraphs.

diff --git a/lib/ui/stdtoolbars.inc b/lib/ui/stdtoolbars.inc
index ad4fa74..b8e911f 100644
--- a/lib/ui/stdtoolbars.inc
+++ b/lib/ui/stdtoolbars.inc
@@ -158,11 +158,6 @@ ToolbarSet
 		Item "Set all lines" "inset-modify tabular set-all-lines"
 		Item "Unset all lines" "inset-modify tabular unset-all-lines"
 		Separator
-		Item "Align left" "command-alternatives inset-modify tabular m-align-left;inset-modify tabular align-left"
-		Item "Align center" "command-alternatives inset-modify tabular m-align-center;inset-modify tabular align-center"
-		Item "Align right" "command-alternatives inset-modify tabular m-align-right;inset-modify tabular align-right"
-		Item "Align on decimal" "inset-modify tabular align-decimal"
-		Separator
 		Item "Align top" "command-alternatives inset-modify tabular m-valign-top;inset-modify tabular valign-top"
 		Item "Align middle" "command-alternatives inset-modify tabular m-valign-middle;inset-modify tabular valign-middle"
 		Item "Align bottom" "command-alternatives inset-modify tabular m-valign-bottom;inset-modify tabular valign-bottom"
@@ -1444,4 +1439,12 @@ ToolbarSet
 		Item "Global fall" "unicode-insert 0x2198"
 	End
 
+	Toolbar "alignment" "Alignment"
+		Item "Align left" "command-alternatives inset-modify tabular m-align-left;inset-modify tabular align-left;paragraph-params \align left"
+		Item "Align center" "command-alternatives inset-modify tabular m-align-center;inset-modify tabular align-center;paragraph-params \align center"
+		Item "Align right" "command-alternatives inset-modify tabular m-align-right;inset-modify tabular align-right;paragraph-params \align right"
+		Item "Align block" "paragraph-params \align block"
+		Item "Align on decimal" "inset-modify tabular align-decimal"
+	End
+
 End
<><><><>

Re: CMake for Apple?

[Benjamin Piwowarski]

Hi,

I would be happy to participate (in July/August) to make the cmake building 
process complete and more fool-proof on mac (a few months ago I was able to 
build successfully a working bundle). If some are interested to do the same 
effort for the linux platform, then it could be an occasion to get rid of the 
old auto-tools chain since windows is already not using it. Maintaining two 
build systems is cumbersome and may introduce lots of compilation errors when 
switching from one tool to the other (this happened when I submitted patches to 
LyX).

benjamin

On May 12, 2013, at 13:41 , Stephan Witt  wrote:

> Am 12.05.2013 um 11:18 schrieb Abdelrazak Younes :
> 
>> On Sat, May 11, 2013 at 11:02 PM, Stephan Witt  wrote:
>>> Am 11.05.2013 um 17:50 schrieb Abdelrazak Younes :
>>> 
 Hi Stephan,
 
 At LyX meeting we are wondering why you are still using autotools for Mac 
 packaging. Do you miss anything from CMake that is not implemented yet?
>>> 
>>> Hi all at the LyX meeting,
>>> 
>>> I hope you're well and someone is drinking wine too… :)
>>> 
>> I had some ;-)
>> 
>> 
>>> Regarding the CMake question - I never tried it for a long time.
>>> 
>> Ah? I got the impression you were developping using cmake and xcode... But I 
>> see in your other email that this does not work anymore...
>> 
>>> 
>>> So I cannot answer the question. Isn't the autotools build the official one?
>>> 
>> Up to now yes, except for Windows.
>> 
>> I was trying to advocate yesterday that we should really move to cmake on 
>> all platforms. I guess this is already a lost battle…
> 
> I'm using CMake to generate the Xcode-project for debugging purposes.
> 
> The packaging is done by a shell script to wrap all needed resources into one 
> bundle.
> The first step is making the pure LyX.app bundle (make install).
> Then the additional parts are copied into this app bundle. The used frameworks
> (spell checker libraries, gettext and Qt4) needs to be adjusted to make them 
> relocatable.
> The dictionaries and thesauri are simply copied into it too.
> 
> Of course one can do these steps with CMake but I never got a friend of it's 
> language
> and I'm loosing to much time to find my mistakes when using it. If it had the 
> ability to
> tell me what it's doing and why… sorry, the verbose option of it is not 
> enough for me.
> 
> Stephan

Re: Slide preview

[Alessandro Di Federico]

On Sat, 2013-05-11 at 00:36 -0700, Pavel Sanda wrote:
> > The idea would be to render a single page at a time, so we can
> re-render
> 
> It will be very tricky to get correct numbering for e.g. equations.

Yeah, but we have the same problem with instant preview in equations,
I'll look if we can do something about it.
We are already able to show the correct numbering in the formula, so it
should be possible to initialize the counter at the beginning of the
preview document correctly.

> > them in the background now and then (when the cursor leaves the
> > interested area?) without having to re-generate the whole document,
> > which wouldn't scale well.
> 
> If you are going along the lines above, please note that there is
> reoccuring request for automatic background updates for (pre)viewed
> document, so you can instantly see the result of your editation
> without need for ctrl+shift+t/r.
> Consider to make the infrastructure generic enough so this is easy to
> add as a new lfun or similar.

I'll take that into account, but as I said the idea is to make the
preview page by page.

-- 
Ale

Re: [features/refs/heads/kill-gettext] UserGuide.lyx: next revision step

[Stephan Witt]

Am 12.05.2013 um 16:51 schrieb v...@lyx.org:

> Author: Uwe Stöhr 
> Date: Sun, 12 May 2013 12:57:14 +0200
> New Commit: 1fded6e8175e92c1eaa1e85db7c3f8187e47e602
> URL: 
> http://git.lyx.org/?p=features.git;a=commit;h=1fded6e8175e92c1eaa1e85db7c3f8187e47e602
> 
> Log:
> UserGuide.lyx: next revision step
> 
> - sec. 6.7 - 6.13
> 

Since commit 704328d3488c75733ddeb9ad5439b1907e323e39 there is no diff sent to 
the list anymore.

Stephan

BTW: The german users guide is not compilable anymore. Am I the only one seeing 
this?

The LaTeX log:
LaTeX Warning: Reference `sec:Umgebungen-schachteln' on page 27 undefined on in
put line 1612.
LaTeX Warning: Reference `sub:Variabler-horiz-Abstand' on page 27 undefined on 
input line 1619.
[27]
LaTeX Warning: Reference `sec:TeX-Code' on page 28 undefined on input line 1648.
[28]
LaTeX Warning: Citation `enumitem' on page 29 undefined on input line 1762.
[29]
! Missing \endcsname inserted.
 
   \protect 
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
The control sequence marked  should
not appear between \csname and \endcsname.

! Extra \endcsname.
\enitkv@split ...enitkv@prefix \@tempa \endcsname 
  \ifx \@tempc \relax \enitk...
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
I'm ignoring this, since I wasn't doing a \csname.

! Missing \endcsname inserted.
 
   \protect 
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
The control sequence marked  should
not appear between \csname and \endcsname.

! Extra \endcsname.
\@ifundefined ...dafter \ifx \csname #1\endcsname 
  \relax \expandafter \@firs...
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
I'm ignoring this, since I wasn't doing a \csname.

! Missing \endcsname inserted.
 
   \protect 
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
The control sequence marked  should
not appear between \csname and \endcsname.

! Extra \endcsname.
\enitkv@split ...enitkv@prefix \@tempa \endcsname 
  \ifx \@tempc \relax \enitk...
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
I'm ignoring this, since I wasn't doing a \csname.

! Missing \endcsname inserted.
 
   \protect 
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
The control sequence marked  should
not appear between \csname and \endcsname.

! Extra \endcsname.
\@ifundefined ...dafter \ifx \csname #1\endcsname 
  \relax \expandafter \@firs...
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
I'm ignoring this, since I wasn't doing a \csname.


! Package enumitem Error: \csnameforeignlanguage \endcsname {ngerman}{labelinde
nt=0pt, labelsep=1cm, font=\itshape , style=nextline} undefined.

See the enumitem package documentation for explanation.
Type  H   for immediate help.
 ...  
  
l.1792 ...sep=1cm, font=\itshape, style=nextline}]
  
Try typingto proceed.
If that doesn't work, type  X   to quit.


Overfull \hbox (22.13562pt too wide) in paragraph at lines 1790--1792
[]\T1/cmr/m/n/12 verwendet wird: [][][][]la-be-lin-dent=0pt, la-bel-sep=1cm, fo
nt=\T1/cmr/m/it/12 , sty-le=nextline\T1/cmr/m/n/12 labelindent=0pt,
 []

Re: CMake for Apple?

[Stephan Witt]

Am 12.05.2013 um 17:04 schrieb Benjamin Piwowarski 
:

> Hi,
> 
> I would be happy to participate (in July/August) to make the cmake building 
> process complete and more fool-proof on mac (a few months ago I was able to 
> build successfully a working bundle).

What do you call a working bundle? It has to contain the frameworks it depends 
on.
Anyway, I have no preference for one build system or the other. And of course 
your
support would be greatly appreciated.

Stephan

> If some are interested to do the same effort for the linux platform, then it 
> could be an occasion to get rid of the old auto-tools chain since windows is 
> already not using it. Maintaining two build systems is cumbersome and may 
> introduce lots of compilation errors when switching from one tool to the 
> other (this happened when I submitted patches to LyX).
> 
> benjamin
> 
> On May 12, 2013, at 13:41 , Stephan Witt  wrote:
> 
>> Am 12.05.2013 um 11:18 schrieb Abdelrazak Younes :
>> 
>>> On Sat, May 11, 2013 at 11:02 PM, Stephan Witt  wrote:
 Am 11.05.2013 um 17:50 schrieb Abdelrazak Younes :
 
> Hi Stephan,
> 
> At LyX meeting we are wondering why you are still using autotools for Mac 
> packaging. Do you miss anything from CMake that is not implemented yet?
 
 Hi all at the LyX meeting,
 
 I hope you're well and someone is drinking wine too… :)
 
>>> I had some ;-)
>>> 
>>> 
 Regarding the CMake question - I never tried it for a long time.
 
>>> Ah? I got the impression you were developping using cmake and xcode... But 
>>> I see in your other email that this does not work anymore...
>>> 
 
 So I cannot answer the question. Isn't the autotools build the official 
 one?
 
>>> Up to now yes, except for Windows.
>>> 
>>> I was trying to advocate yesterday that we should really move to cmake on 
>>> all platforms. I guess this is already a lost battle…
>> 
>> I'm using CMake to generate the Xcode-project for debugging purposes.
>> 
>> The packaging is done by a shell script to wrap all needed resources into 
>> one bundle.
>> The first step is making the pure LyX.app bundle (make install).
>> Then the additional parts are copied into this app bundle. The used 
>> frameworks
>> (spell checker libraries, gettext and Qt4) needs to be adjusted to make them 
>> relocatable.
>> The dictionaries and thesauri are simply copied into it too.
>> 
>> Of course one can do these steps with CMake but I never got a friend of it's 
>> language
>> and I'm loosing to much time to find my mistakes when using it. If it had 
>> the ability to
>> tell me what it's doing and why… sorry, the verbose option of it is not 
>> enough for me.
>> 
>> Stephan
> 
> 
> 

Re: [features/refs/heads/kill-gettext] UserGuide.lyx: next revision step

[Vincent van Ravesteijn]

Since commit 704328d3488c75733ddeb9ad5439b1907e323e39 there is no diff sent to 
the list anymore.

Stephan



This commit is not sent to the list indeed.  Commit  03f98402f (Fix 
crash with FindAndReplaceUi) is sent to the list twice ;)..


Vincent

Re: Slide preview

[Pavel Sanda]

Alessandro Di Federico wrote:
> We are already able to show the correct numbering in the formula, so it

IIRC only because we flush all equation to one file and process them together.
The moment you separate it into single page, correct numbering is gone.

Pavel

Re: bug on Lyx 2.0.6?

[Julien Rioux]

On 09/05/2013 5:05 PM, Nicola Scafetta, Ph. D. wrote:

The bug with LyXHTML, which is different from that encountered with
elyxer.py, is the following.

See the attached files.

In the .xhtml file the reference in the text appears with a symbol after
the year that should not be there.



I see this too. The "modifier", which is an additional letter used if 
you have more than one reference with the same author and year, isn't 
initialized properly. We should fix this in LyX, so thanks for your 
report of the problem.



The reference in the Bibliography starts with "[White(2010)]" that
should not be visible.



This is at the moment not customizable, so you would have to remove it 
yourself, unfortunately. Maybe we can have this customizable in LyX 2.1.



Compare the .xhtml file with the .pdf of the same .lyx file.


nicola



Cheers,
Julien

Re: [PATCH] WIP Make python scripts work with python3

[Julien Rioux]

On 12/05/2013 10:07 AM, Lars Gullik Bjønnes wrote:

---
  development/autotests/keytest.py | 112 ++--
  development/cmake/doc/ReplaceValues.py   |   4 +-
  development/cmake/po/cat.py  |   2 +-
  development/keystest/cache-bisect.py |  78 +--
  development/keystest/keytest.py  |  62 +--
  development/keystest/make_screenshot_html.py |  20 +-
  development/tools/convert_kmap.py|  18 +-
  development/tools/generate_symbols_images.py |  14 +-
  development/tools/generate_symbols_list.py   |  28 +-
  development/tools/unicodesymbols.py  |   2 +-
  lib/configure.py |  14 +-
  lib/generate_contributions.py| 786 +--
  lib/lyx2lyx/LyX.py   |   8 +-
  lib/lyx2lyx/generate_encoding_info.py|   8 +-
  lib/lyx2lyx/lyx2lyx_tools.py |   2 +-
  lib/lyx2lyx/lyx_1_2.py   |   6 +-
  lib/lyx2lyx/lyx_1_4.py   |   4 +-
  lib/lyx2lyx/lyx_1_5.py   |  70 +--
  lib/lyx2lyx/lyx_1_6.py   |  10 +-
  lib/lyx2lyx/lyx_2_1.py   |  24 +-
  lib/lyx2lyx/parser_tools.py  |  12 +-
  lib/lyx2lyx/unicode_symbols.py   |   6 +-
  lib/scripts/TeXFiles.py  |  10 +-
  lib/scripts/convertDefault.py|   4 +-
  lib/scripts/date.py  |   2 +-
  lib/scripts/fen2ascii.py |   8 +-
  lib/scripts/fig2pdftex.py|   6 +-
  lib/scripts/fig2pstex.py |   2 +-
  lib/scripts/fig_copy.py  |   8 +-
  lib/scripts/html2latexwrapper.py |   2 +-
  lib/scripts/include_bib.py   |   8 +-
  lib/scripts/legacy_lyxpreview2ppm.py |   6 +-
  lib/scripts/lyxpak.py|   4 +-
  lib/scripts/lyxpreview2bitmap.py |   6 +-
  lib/scripts/lyxpreview_tools.py  |   2 +-
  lib/scripts/prefs2prefs.py   |  18 +-
  lib/scripts/prefs2prefs_prefs.py |   4 +-
  po/lyx_pot.py|  74 +--
  po/postats.py|   6 +-
  src/tex2lyx/test/runtests.py |   2 +-
  40 files changed, 731 insertions(+), 731 deletions(-)

diff --git a/development/autotests/keytest.py b/development/autotests/keytest.py
index a510a3f..5331348 100755
--- a/development/autotests/keytest.py
+++ b/development/autotests/keytest.py
@@ -16,7 +16,7 @@ import time
  #from subprocess import call
  import subprocess

-print 'Beginning keytest.py'
+print('Beginning keytest.py')

  FNULL = open('/dev/null', 'w')

@@ -78,7 +78,7 @@ class CommandSourceFromFile(CommandSource):
  self.infile.close()
  linesbak = self.lines
  self.p = p
-print p, self.p, 'self.p'
+print(p, self.p, 'self.p')


Is this intended to support both python 2 and 3? From a quick glance I 
do not see "from __future__ import print_function" anywhere.


--
Julien

Re: [features/refs/heads/kill-gettext] UserGuide.lyx: next revision step

[Pavel Sanda]

Vincent van Ravesteijn wrote:
> This commit is not sent to the list indeed.  Commit  03f98402f (Fix crash 

I guess because it's in features repository. Some hook from normal
repo should be taken?
Pavel

Re: Re: [PATCH] WIP Make python scripts work with python3

[José Matos]

On Sunday 12 May 2013 12:46:26 Julien Rioux wrote:
> Is this intended to support both python 2 and 3? From a quick glance I 
> do not see "from __future__ import print_function" anywhere.

If it did that then the minimal version required would need to be 2.6.

As it is the parenthesis are ignore in python 2 and required in python 3.

FWIW I don't understand why this patch dropped the _u _ prefix as it is valid 
python 3.3 and honestly we should not care about previous python 3 versions.

-- 
José Abílio

Re: [features/refs/heads/kill-gettext] UserGuide.lyx: next revision step

[Pavel Sanda]

Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
> > This commit is not sent to the list indeed.  Commit  03f98402f (Fix crash 
> 
> I guess because it's in features repository. Some hook from normal
> repo should be taken?

And no matter who commits, the email sender of all commits is v...@lyx.org ;(
P

Re: [features/refs/heads/kill-gettext] UserGuide.lyx: next revision step

[Pavel Sanda]

v...@lyx.org wrote:
> Author: Uwe Stöhr 
> Date: Sun, 12 May 2013 12:57:14 +0200
> New Commit: 1fded6e8175e92c1eaa1e85db7c3f8187e47e602
> URL: 
> http://git.lyx.org/?p=features.git;a=commit;h=1fded6e8175e92c1eaa1e85db7c3f8187e47e602

Uwe, you scatter eoln conversion all over the place, just click on the link 
above.
Can't you ask all the git gurus around you?
Pavel

Re: Re: Appendix sections are numbered incorrectly on screen (but do appear correctly on DVI/PDF)

[José Matos]

On Friday 10 May 2013 16:23:26 Richard Heck wrote:
> I think I will probably release 2.0.7 fairly early, as well. There are 
> some important fixes in it already, including this one. And, of course, 
> there's the update to the Portuguese translation to include. 
> 
> Richard

I only take the bait on Fridays. :-)

-- 
José Abílio

Re: [PATCH] WIP Make python scripts work with python3

[Julien Rioux]

On 12/05/2013 1:00 PM, José Matos wrote:

On Sunday 12 May 2013 12:46:26 Julien Rioux wrote:

Is this intended to support both python 2 and 3? From a quick glance I
do not see "from __future__ import print_function" anywhere.


If it did that then the minimal version required would need to be 2.6.

As it is the parenthesis are ignore in python 2 and required in python 3.



Not quite ignored, if you have comma-delimited stuff and add () then 
python 2 prints a tuple:


$ python
Python 2.7 (r27:82500, Aug 07 2010, 16:54:59) [GCC] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> print 'h', 0
h 0
>>> print('h', 0)
('h', 0)
>>> from __future__ import print_function
>>> print('h', 0)
h 0

--
Julien

Re: Alignment toolbar

[Liviu Andronic]

Dear Alessandro,


On Sun, May 12, 2013 at 4:29 PM, Alessandro Di Federico
 wrote:
> At the meeting we discussed about introducing some toolbar buttons for
> alignment, which is something users request very frequently. I think the
> best idea is to move out of the table toolbar the alignment buttons and
> make them working for paragraphs too, creating a new toolbar.
>
If we start playing around with toolbar refinements, then I would
suggest to review an older (and long!) discussion on the topic, and
more specifically some toolbar-UI arguments and work that Rob has
done:
http://thread.gmane.org/gmane.editors.lyx.devel/133311/focus=133420
http://thread.gmane.org/gmane.editors.lyx.devel/133311/focus=133438
http://thread.gmane.org/gmane.editors.lyx.devel/133311/focus=133477

He has then proposed a clean-up and redesign of the toolbars in LyX,
to make them more "professional". Here's a screenshot of what he had
in mind:
http://thread.gmane.org/gmane.editors.lyx.devel/133587/focus=133587

It's worth revisiting this if we start changing the toolbars.

Regards,
Liviu


> I've removed the black border from the icons of the classic set, since
> they now don't mean "align center the cell content" but just "align
> center" (see attachments).
>
> For the oxygen set, I think they're already OK, except for the fact that
> in the KDE oxygen package [1] I couldn't find an icon similar to the one
> we have for the "block" alignment. Actually I couldn't find them at all,
> where did we get them from? Should I manually create one as I did for
> the classic set?
>
> --
> Ale
>
> [1] http://download.kde.org/stable/4.10.3/src/oxygen-icons-4.10.3.tar.xz



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Trac mails b0rken

[Pavel Sanda]

Seems I'm no more getting mails when bugs are changed in trac.
Anyone else?

Re: Trac mails b0rken

[Liviu Andronic]

On Sun, May 12, 2013 at 7:52 PM, Pavel Sanda  wrote:
> Seems I'm no more getting mails when bugs are changed in trac.
> Anyone else?
>
I'm getting mines.

Liviu


-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: Trac mails b0rken

[Pavel Sanda]

Liviu Andronic wrote:
> On Sun, May 12, 2013 at 7:52 PM, Pavel Sanda  wrote:
> > Seems I'm no more getting mails when bugs are changed in trac.
> > Anyone else?
> >
> I'm getting mines.

Indeed it seems if CC myself with lyx unrelated email it works, if I'm CC-ed
either as sanda or sa...@lyx.org I get nothing (the @lyx.org mail work fine
itself though).

Pavel

Re: Trac mails b0rken

[Georg Baum]

Pavel Sanda wrote:

> Liviu Andronic wrote:
>> On Sun, May 12, 2013 at 7:52 PM, Pavel Sanda  wrote:
>> > Seems I'm no more getting mails when bugs are changed in trac.
>> > Anyone else?
>> >
>> I'm getting mines.
> 
> Indeed it seems if CC myself with lyx unrelated email it works, if I'm
> CC-ed either as sanda or sa...@lyx.org I get nothing (the @lyx.org mail
> work fine itself though).

I don't get any trac mail either, but I do get the cvs list emails to the 
.lyx.org address.


Georg

Re: Trac mails b0rken

[Pavel Sanda]

Georg Baum wrote:
> > Indeed it seems if CC myself with lyx unrelated email it works, if I'm
> > CC-ed either as sanda or sa...@lyx.org I get nothing (the @lyx.org mail
> > work fine itself though).
> 
> I don't get any trac mail either, but I do get the cvs list emails to the 
> .lyx.org address.

Hm. That means that all the mass triage of 2.1 milestoned bugs with all
the posted questions will be ignored.

Pavel

Re: Trac mails b0rken

[Julien Rioux]

On 12/05/2013 2:56 PM, Pavel Sanda wrote:

Georg Baum wrote:

Indeed it seems if CC myself with lyx unrelated email it works, if I'm
CC-ed either as sanda or sa...@lyx.org I get nothing (the @lyx.org mail
work fine itself though).


I don't get any trac mail either, but I do get the cvs list emails to the
.lyx.org address.


Hm. That means that all the mass triage of 2.1 milestoned bugs with all
the posted questions will be ignored.

Pavel



I did get a couple ticket emails to @lyx.org, don't know if I missed 
any. Is the plan to release LyX 2.1 this month?


--
Julien

Re: Trac mails b0rken

[Vincent van Ravesteijn]

Op 12-5-2013 20:56, Pavel Sanda schreef:

Georg Baum wrote:

Indeed it seems if CC myself with lyx unrelated email it works, if I'm
CC-ed either as sanda or sa...@lyx.org I get nothing (the @lyx.org mail
work fine itself though).

I don't get any trac mail either, but I do get the cvs list emails to the
.lyx.org address.

Hm. That means that all the mass triage of 2.1 milestoned bugs with all
the posted questions will be ignored.

Pavel


I got them all.

Vincent

Re: Slide preview

[Alessandro Di Federico]

On Sun, 2013-05-12 at 09:38 -0700, Pavel Sanda wrote:
> IIRC only because we flush all equation to one file and process them
> together.
> The moment you separate it into single page, correct numbering is
> gone.

Actually Richard implemented counter saving for XHTML export, attached
there's a patch which saves the counters also in normal situations. It
also works if the "Number equations by section" module is enabled, as
you can see with the attached document. 
I don't know if it's appropriate to save counters each time the math
inset is modified, maybe we should introduce a new UpdateType for
instant preview, or just reuse UpdateType::OutputUpdate for IP.
Let me know what you think.

Currently we just save equation, chapter and section counters. I wonder
if there's a reason against saving all the possible counters, just to be
sure, in case the user wants to do custom stuffs (e.g. number equations
by subsections). Richard?

Maybe I can reuse (and factorize) Richard's code also for page preview.

-- 
Ale


numbered-formulas.lyx
Description: application/lyx
Fix for instant preview equation numbering: save counters also in normal
rendering, not just when exporting.

diff --git a/src/mathed/InsetMathHull.cpp b/src/mathed/InsetMathHull.cpp
index 7059914..9e7a3a0 100644
--- a/src/mathed/InsetMathHull.cpp
+++ b/src/mathed/InsetMathHull.cpp
@@ -251,19 +251,16 @@ void InsetMathHull::updateBuffer(ParIterator const & it, UpdateType utype)
 			buffer_->masterBuffer()->params().documentClass().counters();
 
 		// right now, we only need to do this at export time
-		if (utype == OutputUpdate) {
-			for (size_t i = 0; i < numcnts; ++i) {
-docstring const cnt = from_ascii(counters_to_save[i]);
-if (cnts.hasCounter(cnt))
-	counter_map[cnt] = cnts.value(cnt);
-			}
+		for (size_t i = 0; i < numcnts; ++i) {
+			docstring const cnt = from_ascii(counters_to_save[i]);
+			if (cnts.hasCounter(cnt))
+counter_map[cnt] = cnts.value(cnt);
 		}
 
 		// this has to be done separately
 		docstring const eqstr = from_ascii("equation");
 		if (cnts.hasCounter(eqstr)) {
-			if (utype == OutputUpdate)
-counter_map[eqstr] = cnts.value(eqstr);
+			counter_map[eqstr] = cnts.value(eqstr);
 			for (size_t i = 0; i != label_.size(); ++i) {
 if (numbered(i)) {
 	cnts.step(eqstr, utype);
@@ -609,7 +606,7 @@ void InsetMathHull::preparePreview(DocIterator const & pos,
 	}
 
 	docstring setcnt;
-	if (forexport && haveNumbers()) {
+	if (haveNumbers()) {
 		docstring eqstr = from_ascii("equation");
 		CounterMap::const_iterator it = counter_map.find(eqstr);
 		if (it != counter_map.end()) {

Re: Trac mails b0rken

[Pavel Sanda]

Vincent van Ravesteijn wrote:
> I got them all.

ldm conspiracy  :))

Re: Trac mails b0rken

[Vincent van Ravesteijn]

On Sunday, May 12, 2013, Pavel Sanda  wrote:
> Vincent van Ravesteijn wrote:
>> I got them all.
>
> ldm conspiracy  :))
>

We really thought you received everything, because you agreed on everything
that we decided.

Vincent

Re: Slide preview

[Richard Heck]

I had the idea at one time to use this code for better on screen numbering
of something and restricted it to OutputUpdate only so as not to waste
memory and time unnecessarily. As for saving all counters, I'd try to save
only what you need. If that fails, we can do otherwise.

R
On May 12, 2013 3:45 PM, "Alessandro Di Federico"  wrote:

> On Sun, 2013-05-12 at 09:38 -0700, Pavel Sanda wrote:
> > IIRC only because we flush all equation to one file and process them
> > together.
> > The moment you separate it into single page, correct numbering is
> > gone.
>
> Actually Richard implemented counter saving for XHTML export, attached
> there's a patch which saves the counters also in normal situations. It
> also works if the "Number equations by section" module is enabled, as
> you can see with the attached document.
> I don't know if it's appropriate to save counters each time the math
> inset is modified, maybe we should introduce a new UpdateType for
> instant preview, or just reuse UpdateType::OutputUpdate for IP.
> Let me know what you think.
>
> Currently we just save equation, chapter and section counters. I wonder
> if there's a reason against saving all the possible counters, just to be
> sure, in case the user wants to do custom stuffs (e.g. number equations
> by subsections). Richard?
>
> Maybe I can reuse (and factorize) Richard's code also for page preview.
>
> --
> Ale
>