date:20110905


Op 5-9-2011 1:37, Tommaso Cucinotta schreef:

Hi,

just reconnecting with the lyx@twitter proposal, I found these pages 
about LyX on FB:


  http://www.facebook.com/pages/LyX/166594390068533
  http://www.facebook.com/pages/LyX/112847072061085?sk=info
  http://www.facebook.com/group.php?gid=8353382319v=wall

I'm not such an expert user of this tool, however I cannot actually 
understand the difference among these (or, if there any any further 
pages like this around). Is it on purpose to have multiple pages like 
these ?


T.


I'm pretty sure no one of us knows anything about these pages.

Someone wants to step up to create order in the chaos ?

Vincent

Re: r39582 - in lyx-devel/trunk/development/Win32/packaging/installer: include setup


Op 5-9-2011 8:09, uwesto...@lyx.org schreef:

Author: uwestoehr
Date: Mon Sep  5 08:09:13 2011
New Revision: 39582
URL: http://www.lyx.org/trac/changeset/39582

Log:
installer:
- fix 2 uninstaller issues
- remove support for AFPL Ghostscript (license clash)
- only install Ghostscript if not already installed
- in case there are several Ghostscript installations, use the newest one
- remove an unused variable




 I thought there was a recent discussion about dropping the Ghostscript 
support ?


Vincent

Language changes within index entries (was: LyX 2.0.1 Sources Available)

2011-09-05 Thread Jean-Pierre Chrétien


Le 01/09/2011 16:15, Uwe Stöhr a écrit :

Am 01.09.2011 10:55, schrieb Jean-Pierre Chrétien:


Compilation of French versions of UserGuide and EmbeddedObjects fail
for a
similar reason: bad language change location in a sectioning heading.


Where? For me all documentation files for all languages compile.


On Linux/TexLive I get the following errors.

In UserGuide:

cite
Overfull \hbox (10.96574pt too wide) in paragraph at lines 103--104
[]\T1/lmr/bx/n/12 Environnements de Pa-ra-graphe, [][]18[][]--
 []

! Extra }, or forgotten \endgroup.
l.125 \subitem Details}
   \selectlanguage  {english} , \hyperpage{77}
I've deleted a group-closing symbol because it seems to be
spurious, as in `$x}$'. But perhaps the } is legitimate and
you forgot something else, as in `\hbox{$x}'. In such cases
the way to recover is to insert both the forgotten and the
deleted material, e.g., by typing `I$}'.
/cite

After investigation, this error is due to the fact that the word 'Flottants' is 
in French in the index inset within title of section 4.6.3. The exported latex 
construct


\subsection{More Information\index{Flottants@\selectlanguage{french}%
Flottants\foreignlanguage{english}{!Details@Details}\selectlanguage{english}
}}

creates the abovementioned error, as texindy creates line

   \subitem Details}\selectlanguage{english} , \hyperpage{79}

in UserGuide.ind.

This will be corrected when the section will be translated, but does this
deserve a ticket ? I wonder whether this is a LyX bug in the exported LaTeX
syntax or a index generator bug, which should not export 
'}\selectlanguage{english}'.


In EmbeddedObjects:

cite
Chapter 6.
Runaway argument?
! Paragraph ended before \def was complete.
to be read again
   \par
l.5632 ...anguage{french}{Flottants d'enrobage

I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
/cite

and a set of errors triggered by the first one.

Change of language in a header title again, the offending code reads in LaTeX:

\section{Flottant d'enrobage\label{sec:Flottant-d'enrobage}
\index{Flottants!Flottants d'enrobage}\foreignlanguage{english}
{\index{Surrounded by text!Flottants d'enrobage@\foreignlanguage{french}
{Flottants d'enrobage

on one single line.

Again the error is due to an incompletely translated index entry, but this time 
the error occurs at the first pdflatex pass. The recursive \foreignlanguage 
construct in an index entry seems there incorrect in LaTeX (no more errors if I 
remove the external \foreignlanguage{english}{...} command).


I wonder why you do not see these errors ? In the first case, this may be due to 
the indexing engine, but in the second one, this seems a native TeX error.


--
Jean-Pierre

Re: merging of external material and graphics interfaces

2011-09-05 Thread Helge Hafting


On 02. sep. 2011 02:45, Tommaso Cucinotta wrote:
[...]

I'm not sure why some of the external material contents are not
previewed on the screen.


External material is not necessarily images.

The spreadsheet inset is converted to a longtable, for example. A 
longtable may get broken up over several pages, and location of the 
breaks depends on where the previous pagebreak (in the document) 
happens. As we all know, LyX doesn't break the document into pages

in advance.

Helge Hafting

Re: LyX 2.0.1 Sources Available


Am 02.09.2011 08:41, schrieb Vincent van Ravesteijn:


In th merged installer MiKTeX is directly included. So even if you don't
have Internet access, you can install LyX and it will work with its basic
features. There were some reasonable user requests in the past to include
MiKTeX directly and the MiKTeX maintainer kindly built in some features for
us in his basic installer.


I would prefer not to include MikTeX in the installer. Most people that
download LyX already have MikTeX installed, so why would you bother them
with a huge download.


For these people we have the standard installer. The bundle installer is especially designed for new 
installations and therefore includes MiKTeX and JabRef (is optional). So the standard installer will 
not bother the user and is as small as possible to update existing LyX installations. This variant 
therefore expects an installed MiKTeX. If no MiKTeX or TeXLive is found, it will throw a warning 
that the bundle installer should be used.



Ah so.. but when the installer downloads MikTeX from the web, we better can
use the link without a build number. That was my point.


Sure, but this is only the case in Joost's installer not in the merged one which will be our new 
installer, hopefully to be ready for LyX 2.0.2. Despite of the installation without admin 
privileges, it is ready to use in my opinion, please check it out, if you find some time.


regards Uwe

Re: Language changes within index entries - French doc files uncompilable in LyX 2.0.1


Am 05.09.2011 08:49, schrieb Jean-Pierre Chrétien:


After investigation, this error is due to the fact that the word 'Flottants' is 
in French in the
index inset within title of section 4.6.3. The exported latex construct

\subsection{More Information\index{Flottants@\selectlanguage{french}%
Flottants\foreignlanguage{english}{!Details@Details}\selectlanguage{english}
}}

creates the abovementioned error, as texindy creates line

\subitem Details}\selectlanguage{english} , \hyperpage{79}

in UserGuide.ind.

This will be corrected when the section will be translated, but does this
deserve a ticket ?


I'm not seeing these issues because xindy is not available under Windows and thus makeindex is used 
as indexing program.
It seems that xindy doesn't support multiple languages in index entries while this works without 
problems with makeindex.
There is nothing we can do about it because denying multiple languages would change existing LyX 
files that compile fine with makeindex.
We have this problematic in other cases too, for example with tables. Depending on the document 
settings, multiple languages work, sometimes not.


For now, can you please translate the problematic cases right now?

Richard, what about LyX 2.0.1? Is it delayed, so that I can put this in?

regards Uwe

Re: LyX 2.0.1 Sources Available


Am 02.09.2011 15:46, schrieb Vincent van Ravesteijn:


Can you send me a link to this installer. I want to test it.


https://developer.berlios.de/project/showfiles.php?group_id=5117release_id=18767

regards Uwe

Re: r39582 - in lyx-devel/trunk/development/Win32/packaging/installer: include setup


Am 05.09.2011 08:13, schrieb Vincent van Ravesteijn:


I thought there was a recent discussion about dropping the Ghostscript support ?


This was about the support for GSview which has already been dropped.

We need Ghostscript to display PDF and EPS images within LyX.

regards Uwe

Re: first step of merging the Win installers

Am 21.08.2011 11:00, schrieb Vincent van Ravesteijn:

- I used the custom LaTeX installer page from my installer, only because
this is already translated to 22 languages. The page design is a matter of
taste, so we can also use yours if you prefer it for a certain reason.

This page doesn't fit in the framework of the installer and uses a deprecated
NSIS plug-in for the
GUI. We now have two different GUI codes in place, one using the modern
nsDialogs code and the old
code based on INI files.

If you don't mind I'll put back the nsDialogs version and we'll just transfer
the translations.

AFAICS this hasn't been done yet.

Uwe, are you still planning to revert to the nsDialogs version ?

For now not. This can be done any time later. Once this installer is ready for usage we will ask
people to translate it. Therefore the nsDialog strings are in the language files of the installer.
When we got them translated, we can switch.
Currently we have translations for 22 languages and thus should use them. For the nsDialog strings
we currently only have them for 3 languages.

Yea the detection of external programs became really messy now. We should merge
and clean this up.
What I don't like about this MiKTeX detection code is the lack of forward
compatibility (e.g.
MiKTeX 2.10 won't work) and the code duplication for each version.
What it wrong with the generic code that I used?

The problem with the generic code is that you expect every MiKTeX version to act the same. But this
was not the case in the past. Registry entries changed and even names of executables we need to
configure MikTeX. So we need to check each major release, e.g. the future MiKTeX 2.10 (which is
probably not released under this version number but as MiKTeX 3.0).

regards Uwe

LyX 2.0.1 Released


Public release of LyX version 2.0.1
===

We are pleased to announce the release of LyX 2.0.1. This is the first
maintenance release in the 2.0.x series.

LyX 2.0.1 is the result of on-going efforts to make our stable version
even more reliable and stable. We have fixed a number of bugs and made
a number of improvements. These are detailed below. We encourage all
LyX users to upgrade to this version.

LyX is a document processor that encourages an approach to writing based
on the structure of your documents and not simply their appearance. It is
released under a Free and Open Source Software license.

You can download LyX 2.0.1 from http://www.lyx.org/Download/.

If you think you found a bug in LyX 2.0.1, either e-mail the LyX
developers' mailing list (lyx-devel at lists.lyx.org), or open a bug
report at http://www.lyx.org/trac/wiki/BugTrackerHome.

If you have trouble using LyX or have a question, consult the
documentation that comes with LyX and the LyX wiki, which lives at
http://wiki.lyx.org/. If you can't find the answer there, e-mail the LyX
users' list (lyx-users at lists.lyx.org).

We hope you enjoy using LyX 2.0.1.

The LyX team.
http://www.lyx.org


What's new in LyX 2.0.1
===

The support for using external files in ERT has been improved by the
introduction of a prefix for the TEXINPUTS environment variable.
This prefix can be set in preferences and by default includes the
document directory (represented by a single '.'). The prefix can
be set to any list of paths separated by the default separator for
a given platform (':' on unix like systems and ';' on windows).
When a file should be included by LaTeX, the paths listed in TEXINPUTS
will be searched in turn for finding it. Note that any non-absolute
path listed in the TEXINPUTS prefix is considered to be relative to the
document directory, i.e., the directory where the LyX file lives.
Users are advised to always include '.' (the document dir) as one of
the path components, otherwise compilation may fail for some documents.
This is because the previous (undocumented) mechanism based on the use
of the \input@path macro has been dropped. The old mechanism did not
work in all cases and was kind of a hack. Old documents using that
undocumented hack for obtaining the path of the LyX file will have to
be revised. A clean way for obtaining the document path is using the
info inset through the info-insert buffer path LyX function.


** Updates:
***

* DOCUMENT INPUT/OUTPUT

- Allow for a maximum of 3 minutes for the completion of a spawned command
  except on Windows, where 30 minutes are allowed. This is because the
  Windows installer may trigger MiKTeX updates that suffer from network
  latencies.

- Improved XHTML output of various fractions.

- A prefix for the TEXINPUTS environment variable can be specified in the
  preferences. The directory of a LyX document is represented by a single
  dot '.' or by the prefix ./. Also, any non-absolute path will be
  prepended with the LyX document directory.

- Updated templates to current LyX format, so no conversion will be
  needed.

- Allow LaTeX import of \uline (bug 7640).

- Fix compilation error occurring when a LyX document resides in a directory
  whose name contains characters that are special to LaTeX (bug 6170).


* USER INTERFACE

- Updated Czech, French, German, Japanese, Interlingua, Italian, Polish,
  Portuguese, Serbian (Latin), Spanish, Swedish and Ukrainian User
  Interface Localization.

- Now it is not necessary to restart LyX after changing the default
  document directory and/or the PATH prefix in the preferences for them
  to take effect.

- Menu View-Source for documents with XHTML default output format now
displays
  only the current paragraph, except when complete source is requested
  (bug 7463).

- Size tab now enables and disables correctly depending on the capabilities
  configured for the current external template (selected via the combo).

- Sort entries in the More Formats and Options dialog (bug 7714).

- Enable Accept compound preference setting for Aspell backend only.
  Reconfigure the aspell backend when Accept compound preference is
  changed immediately.


* DOCUMENTATION AND LOCALIZATION

- UserGuide:
  - new section how to define custom header/footer lines
(bug 7196).
  - new section about customized lists
  - new section about comparison of LyX documents
  - new section about the document's colors settings
  - revised Appendix A and B

- EnbeddedObjects manual:
  - describe that LyX supports now the changing of the color of the
greyed-out box text
  - new chapter about objects surrounded by text

- Math manual: add a note about column limit for decorated matrices.

- Updated French documentation files.

- updated template file for the latest version of the ACM siggraph
  LaTeX-package.

- updated layout and template file for the latest version of the IJMPC
  LaTeX-package.

- updated layout and

Branch is Open


Branch is again open for commits, as LyX 2.0.1 is out.

Richard

Re: first step of merging the Win installers


Op 5-9-2011 17:39, Uwe Stöhr schreef:

Am 21.08.2011 11:00, schrieb Vincent van Ravesteijn:

- I used the custom LaTeX installer page from my installer, only 
because
this is already translated to 22 languages. The page design is a 
matter of
taste, so we can also use yours if you prefer it for a certain 
reason.


This page doesn't fit in the framework of the installer and uses a 
deprecated NSIS plug-in for the
GUI. We now have two different GUI codes in place, one using the 
modern nsDialogs code and the old

code based on INI files.

If you don't mind I'll put back the nsDialogs version and we'll just 
transfer the translations.


AFAICS this hasn't been done yet.

Uwe, are you still planning to revert to the nsDialogs version ?


For now not. This can be done any time later. Once this installer is 
ready for usage we will ask people to translate it. Therefore the 
nsDialog strings are in the language files of the installer. When we 
got them translated, we can switch.
Currently we have translations for 22 languages and thus should use 
them. For the nsDialog strings we currently only have them for 3 
languages.


I don't understand. Joost proposed to transfer the translations. I 
would expect them to use the same strings and thus the same translations.




Yea the detection of external programs became really messy now. We 
should merge and clean this up.
What I don't like about this MiKTeX detection code is the lack of 
forward compatibility (e.g.

MiKTeX 2.10 won't work) and the code duplication for each version.
What it wrong with the generic code that I used?


The problem with the generic code is that you expect every MiKTeX 
version to act the same. But this was not the case in the past. 
Registry entries changed and even names of executables we need to 
configure MikTeX. So we need to check each major release, e.g. the 
future MiKTeX 2.10 (which is probably not released under this version 
number but as MiKTeX 3.0).


So, if you have a newer MikTeX installed, you prefer to not be able to 
use it over the fact that people use it and it might not work completely 
right (in some exceptional cases) ?


Vincent

Re: r39337 - lyx-devel/trunk/src/frontends/qt4

for...@lyx.org wrote:
 Author: forenr
 Date: Mon Jul 18 10:10:20 2011
 New Revision: 39337
 URL: http://www.lyx.org/trac/changeset/39337
 
 Log:
 Limit fix for bug #6063 to math insets and only when inline completion
 is disabled in math.
 
 Modified:
lyx-devel/trunk/src/frontends/qt4/GuiCompleter.cpp
 
 Modified: lyx-devel/trunk/src/frontends/qt4/GuiCompleter.cpp
 ==
 --- lyx-devel/trunk/src/frontends/qt4/GuiCompleter.cppMon Jul 18 
 05:25:29 2011(r39336)
 +++ lyx-devel/trunk/src/frontends/qt4/GuiCompleter.cppMon Jul 18 
 10:10:20 2011(r39337)
 @@ -311,7 +311,7 @@
   if (!inlineVisible()  possibleInlineState  start
cur.inset().automaticInlineCompletion())
   inline_timer_.start(int(lyxrc.completion_inline_delay * 1000));
 - else {
 + else if (cur.inMathed()  !lyxrc.completion_inline_math) {
   // no inline completion, hence a metrics update is needed
   if (!(cur.result().screenUpdate()  Update::Force))
   cur.screenUpdateFlags(cur.result().screenUpdate() | 
 Update::SinglePar);

Enrico, this was for branch as well? p

Re: LyX 2.0.1 Sources Available

Uwe Stöhr wrote:
 Works fine and a Win installer is ready (the merged one). I'll leave the 
 installer for LyX 2.0.1 to Joost because the merged installer is not yet 
 able to install LyX if you install it without admin privileges (due to a 
 Imagemagick issue).

is this regression wrt 2.0.0 installer? if not why wait...
pavel

Re: LyX 2.0.1 Released

2011-09-05 Thread Jürgen Spitzmüller

Richard Heck wrote:
 Public release of LyX version 2.0.1
 ===
 
 We are pleased to announce the release of LyX 2.0.1. This is the first
 maintenance release in the 2.0.x series.

Congratulations, Richard!

Jürgen

Re: LyX 2.0.1 Sources Available



In th merged installer MiKTeX is directly included. So even if you 
don't
have Internet access, you can install LyX and it will work with its 
basic
features. There were some reasonable user requests in the past to 
include
MiKTeX directly and the MiKTeX maintainer kindly built in some 
features for

us in his basic installer.


I would prefer not to include MikTeX in the installer. Most people that
download LyX already have MikTeX installed, so why would you bother them
with a huge download.


For these people we have the standard installer. The bundle installer 
is especially designed for new installations and therefore includes 
MiKTeX and JabRef (is optional). So the standard installer will not 
bother the user and is as small as possible to update existing LyX 
installations. This variant therefore expects an installed MiKTeX. If 
no MiKTeX or TeXLive is found, it will throw a warning that the bundle 
installer should be used.


Why don't we download it anymore then ? We did this as long as I 
remember having Windows installers.


Vincent

Re: LyX 2.0.1 Released

On 09/05/2011 06:54 PM, Jürgen Spitzmüller wrote:
 Congratulations, Richard!

+1 the first time is always the most terrifying. ;-)

-- 
José Matos

Re: LyX 2.0.1 Released

On 09/05/2011 02:27 PM, José Matos wrote:
 On 09/05/2011 06:54 PM, Jürgen Spitzmüller wrote:
 Congratulations, Richard!
 +1 the first time is always the most terrifying. ;-)

I'm hoping that is true.

Richard

Re: LyX 2.0.1 Sources Available


Op 5-9-2011 17:28, Uwe Stöhr schreef:

Am 02.09.2011 15:46, schrieb Vincent van Ravesteijn:


Can you send me a link to this installer. I want to test it.


https://developer.berlios.de/project/showfiles.php?group_id=5117release_id=18767 



regards Uwe


Hi Uwe,


I tried the merged installer. Here is some feedback:

1. The icon is not the nicest one. We should have a transparent one.

2. I agree with Joost that the dialog to choose the start menu folder is 
not necessary anymore. It is not useful having only a single item in a map.


3. The start menu folder is called LyX 2.0.1. I don't like the version 
number in the name, there is no need for it.


4. In the MikTeX page is a spelling error in the dutch translation: 
LaTeX softare. Also in the MikTeX update page.


5. Why do we install the MikTeX packages without asking the user for 
permission? I determine whether I want to install tons of MikTeX 
packages or not and ,moreover, I have set the setting of MikTex to 
always ask before installing a package. LyX just overrides this. I don't 
accept this.


6. Joost had a reason to not allow to start the application from the 
installer. Isn't this a problem now anymore ?


7. Joost's LyX2.0 installer installed the folder AppData/Roaming/LyX2.0. 
Can we please have the same directory for newer installers instead of 
lyx20 ?


8. Joost's LyX2.0 installer installed in the folder Program Files/LyX20. 
The merged installer in Program Files/LyX 2.0.1. Can we please have the 
same directory for newer installers? Preferably without all the version 
numbers.


9. I found the following faulty registry entries. Where do they come from ?

HKEY_CLASSES_ROOT\LyX.Document\Shell\open\command
C:\Program Files (x86)\LyX 2.0.1\bin\LyXLauncher.exe %1

HKEY_CLASSES_ROOT\LyX.Document\DefaultIcon
C:\Program Files (x86)\LyX 2.0.1\bin\LyXLauncher.exe,0

HKEY_CLASSES_ROOT\Applications
C:\Program Files (x86)\LyX 2.0.1\imagemagick\convert.exe $

10. Now, I have both LyX2.0.0 and LyX2.0.1 installed on my pc ? 
Shouldn't we overwrite the previous version ?


Vincent

Re: merging of external material and graphics interfaces

2011-09-05 Thread Georg Baum

Tommaso Cucinotta wrote:

 Il 31/08/2011 21:19, Georg Baum ha scritto:
 This plan exists for ages. The graphics inset even was already ditched at
 some point in time, but it got reintroduced later, because the external
 inset did not work that well back then. IIRC there is also a bug entry
 for that. You will be a hero if you finally manage to do this!
 which bug number ? Or, what to exactly search for in the database ?

I searched now and did not find it, so probably my memory was wrong.

 that's also my feeling: external material seems more generic than
 graphics, and after all each graphics may be handled via the RasterImage
 external material, or probably a variation of it that merges together at
 least the RasterImage, Dia and XFig external material types (or the
 other way round, i.e., each different file type into its own external
 material kind -- which one is best?).

IMHO one template per file type is overkill. There should be as little 
templates as possible, and each template should handle a group of file types 
that have something in common. The RasterImage is a good example. A similar 
VectorImage template for generic vector images would also be useful. I 
believe that the Dia template is in fact a generic vector image template (or 
could be changed to be one). Only programs that support inline LaTeX and/or 
produce more than one file like XFig need a dedicated template

 I'm not sure why some of the external material contents are not
 previewed on the screen.

Which templates?


Georg

LyX 1.6.10 compilation problem in Fedora 15 - and one solution?

Hy
whem I try do compile LyX 1.6.10
in my fedora 15; X86_64, g++ (GCC) 4.6.0 20110603 (Red Hat 4.6.0-10)

a have the problem below

Mensagem de Erro:
make[4]: Entrando no diretório
`/home/bueno/Download/PacotesExtras/03-Editoracao-lyx-abntex/lyx-1.6.10/src'
  CXXInsetInclude.lo
insets/InsetInclude.cpp: In member function ‘const
lyx::support::FileNameList lyx::InsetInclude::getBibfilesCache(const
lyx::Buffer) const’:
insets/InsetInclude.cpp:809:37: error: uninitialized const ‘empty’
[-fpermissive]
./support/FileNameList.h:27:7: note: ‘const class
lyx::support::FileNameList’ has no user-provided default constructor
make[4]: ** [InsetInclude.lo] Erro 1
make[4]: Saindo do diretório
`/home/bueno/Download/PacotesExtras/03-Editoracao-lyx-abntex/lyx-1.6.10/src'
make[3]: ** [all-recursive] Erro 1
make[3]: Saindo do diretório
`/home/bueno/Download/PacotesExtras/03-Editoracao-lyx-abntex/lyx-1.6.10/src'
make[2]: ** [all] Erro 2
make[2]: Saindo do diretório
`/home/bueno/Download/PacotesExtras/03-Editoracao-lyx-abntex/lyx-1.6.10/src'
make[1]: ** [all-recursive] Erro 1
make[1]: Saindo do diretório
`/home/bueno/Download/PacotesExtras/03-Editoracao-lyx-abntex/lyx-1.6.10'
make: ** [all] Erro 2


I open file FileNameList and include 2 lines

class FileNameList: public std::vectorFileName
{
public: //new
FileNameList() : std::vectorFileName(){} //new
};

after this modification the program compile.
please verify thie problem and solution.



*Prof. André Duarte Bueno, Dr*
Engenharia de Software,  Análise e Processamento de Imagens
*UENF* - Universidade Estadual do Norte Fluminense - Darcy Ribeiro
*CCT *- Centro de Ciencias e Tecnologias
*LENEP* - Laboratório de Engenharia e Exploração de Petróleo
Rodovia Amaral Peixoto, km 163, Avenida Brenand S/N
CEP:   27925-310 - Imboassica - Macaé - RJ - Brasil
Fone:   +55 (22)  2765-6500 geral / *(22) 2765-6563 *sala / (22) 9954-2635
cel
Fax: +55 (22) 2765-6565
e-mail: *bu...@lenep.uenf.br*
http://www2.lenep.uenf.br/~buenohttp://www.lenep.uenf.br/%7Ebueno

Re: r39600 - in lyx-devel/branches/BRANCH_2_0_X: . src/frontends/qt4/ui

rgh...@lyx.org wrote:
 Author: rgheck
 Date: Mon Sep  5 21:27:10 2011
 New Revision: 39600
 URL: http://www.lyx.org/trac/changeset/39600
 
 Log:
 Fix tab order and shortcuts for crossref dialog (#7576).
 
 Modified:
lyx-devel/branches/BRANCH_2_0_X/src/frontends/qt4/ui/RefUi.ui
lyx-devel/branches/BRANCH_2_0_X/status.20x
 
 Modified: lyx-devel/branches/BRANCH_2_0_X/src/frontends/qt4/ui/RefUi.ui
 ==
 --- lyx-devel/branches/BRANCH_2_0_X/src/frontends/qt4/ui/RefUi.ui Mon Sep 
  5 21:25:15 2011(r39599)
 +++ lyx-devel/branches/BRANCH_2_0_X/src/frontends/qt4/ui/RefUi.ui Mon Sep 
  5 21:27:10 2011(r39600)
 @@ -1,193 +1,156 @@
 -ui version=4.0 
 +?xml version=1.0 encoding=UTF-8?

xml line...
p

Re: LyX 1.6.10 compilation problem in Fedora 15 - and one solution?

andre duarte bueno wrote:
 Hy
 whem I try do compile LyX 1.6.10
 in my fedora 15; X86_64, g++ (GCC) 4.6.0 20110603 (Red Hat 4.6.0-10)

either use lyx 2.0 or get lyx 1.6 from svn where it should be fixed.
newer lyx 1.6.11 won't be released.
pavel

Re: LyX 1.6.10 compilation problem in Fedora 15 - and one solution?

thanks

*Prof. André Duarte Bueno, Dr*
Engenharia de Software,  Análise e Processamento de Imagens
*UENF* - Universidade Estadual do Norte Fluminense - Darcy Ribeiro
*CCT *- Centro de Ciencias e Tecnologias
*LENEP* - Laboratório de Engenharia e Exploração de Petróleo
Rodovia Amaral Peixoto, km 163, Avenida Brenand S/N
CEP:   27925-310 - Imboassica - Macaé - RJ - Brasil
Fone:   +55 (22)  2765-6500 geral / *(22) 2765-6563 *sala / (22) 9954-2635
cel
Fax: +55 (22) 2765-6565
e-mail: *bu...@lenep.uenf.br*
http://www2.lenep.uenf.br/~buenohttp://www.lenep.uenf.br/%7Ebueno




2011/9/5 Pavel Sanda sa...@lyx.org

 andre duarte bueno wrote:
  Hy
  whem I try do compile LyX 1.6.10
  in my fedora 15; X86_64, g++ (GCC) 4.6.0 20110603 (Red Hat 4.6.0-10)

 either use lyx 2.0 or get lyx 1.6 from svn where it should be fixed.
 newer lyx 1.6.11 won't be released.
 pavel

[patch] allow to assign several extensions to a file format


log:
 Allow to assign several extension to a given file format (#4798).
 Additionnal extensions are separated by commas (,). Spaces are
 ignored. Preference (lyxrc) file format incremented to 2.

 A lot of the diff is renaming extension - extensions

See issues
http://www.lyx.org/trac/ticket/4798
http://www.lyx.org/trac/ticket/6340

Comments welcome!

Regards,
Julien
diff --git a/lib/configure.py b/lib/configure.py
index 908c211..d4ceebb 100644
--- a/lib/configure.py
+++ b/lib/configure.py
@@ -476,7 +476,7 @@ def checkFormatEntries(dtl_tools):
 path, iv = checkViewerNoRC('a raster image viewer', ['xv', 'kview', 'gimp-remote', 'gimp'],
 rc_entry = [r'''\Format bmpbmp BMP %s	%s	
 \Format gifgif GIF %s	%s	
-\Format jpgjpg JPEG%s	%s	
+\Format jpg   jpg, jpeg JPEG %s	%s	
 \Format pbmpbm PBM %s	%s	
 \Format pgmpgm PGM %s	%s	
 \Format pngpng PNG %s	%s	
@@ -487,7 +487,7 @@ def checkFormatEntries(dtl_tools):
 path, ie = checkEditorNoRC('a raster image editor', ['gimp-remote', 'gimp'],
 rc_entry = [r'''\Format bmpbmp BMP %s	%s	
 \Format gifgif GIF %s	%s	
-\Format jpgjpg JPEG%s	%s	
+\Format jpg   jpg, jpeg JPEG %s	%s	
 \Format pbmpbm PBM %s	%s	
 \Format pgmpgm PGM %s	%s	
 \Format pngpng PNG %s	%s	
@@ -497,7 +497,7 @@ def checkFormatEntries(dtl_tools):
 \Format xpmxpm XPM %s	%s	'''])
 addToRC(r'''\Format bmpbmp BMP %s	%s	
 \Format gifgif GIF %s	%s	
-\Format jpgjpg JPEG%s	%s	
+\Format jpg   jpg, jpeg JPEG %s	%s	
 \Format pbmpbm PBM %s	%s	
 \Format pgmpgm PGM %s	%s	
 \Format pngpng PNG %s	%s	
@@ -571,7 +571,7 @@ def checkFormatEntries(dtl_tools):
 addToRC(r'\Format dvi2   dvi DraftDVI   			vector')
 #
 checkViewer('an HTML previewer', ['firefox', 'mozilla file://$$p$$i', 'netscape'],
-rc_entry = [r'\Format html   htmlHTML   H  %%		document,menu=export'])
+rc_entry = [r'\Format html  html, htm HTMLH  %%		document,menu=export'])
 #
 checkViewerEditor('Noteedit', ['noteedit'],
 rc_entry = [r'\Format noteedit   not Noteedit%%	%%	vector'])
@@ -605,7 +605,7 @@ def checkFormatEntries(dtl_tools):
 \Format pstex  pstex_t PSTEX   		
 \Format wmfwmfWindows Metafile   		vector
 \Format emfemfEnhanced Metafile  		vector
-\Format wordhtml   html   HTML (MS Word)  	document
+\Format wordhtml  html, htm HTML (MS Word)  	document
 ''')
 
 
diff --git a/lib/scripts/prefs2prefs_prefs.py b/lib/scripts/prefs2prefs_prefs.py
index 7a2cdd6..47ec155 100644
--- a/lib/scripts/prefs2prefs_prefs.py
+++ b/lib/scripts/prefs2prefs_prefs.py
@@ -108,4 +108,5 @@ conversions = [
 		language_use_babel,
 		language_package
 	] # end conversions for format 0
+	,[]
 ]
diff --git a/src/Format.cpp b/src/Format.cpp
index cd2d238..c7bd65f 100644
--- a/src/Format.cpp
+++ b/src/Format.cpp
@@ -69,6 +69,7 @@ public:
 		: extension_(extension) {}
 	bool operator()(Format const  f) const
 	{
+		// FIXME: loop through f.extensions()
 		return f.extension() == extension_;
 	}
 private:
@@ -90,9 +91,14 @@ bool operator(Format const  a, Format const  b)
 Format::Format(string const  n, string const  e, string const  p,
 	   string const  s, string const  v, string const  ed,
 	   int flags)
-	: name_(n), extension_(e), prettyname_(p), shortcut_(s), viewer_(v),
+	: name_(n), extensions_(e), prettyname_(p), shortcut_(s), viewer_(v),
 	  editor_(ed), flags_(flags)
-{}
+{
+	string e1;
+	split(e, e1, ',');
+	extension_ = e1;
+	extensions_ = e;
+}
 
 
 bool Format::dummy() const
@@ -115,6 +121,15 @@ string const Format::parentFormat() const
 }
 
 
+void Format::setExtensions(string const  e)
+{
+	string e1;
+	split(e, e1, ',');
+	extension_ = e1;
+	extensions_ = e;
+}
+
+
 // This method should return a reference, and throw an exception
 // if the format named name cannot be found (Lgb)
 Format const * Formats::getFormat(string const  name) const
@@ -207,7 +222,7 @@ void Formats::add(string const  name)
 }
 
 
-void Formats::add(string const  name, string const  extension,
+void Formats::add(string const  name, string const  extensions,
 		  string const  prettyname, string const  shortcut,
 		  string const  viewer, string const  editor,
 		  int flags)
@@ -216,10 +231,10 @@ void

Re: [patch] allow to assign several extensions to a file format


On 05/09/2011 11:33 PM, Julien Rioux wrote:

loop through f.extensions()


Forgot to mention, as this is a preliminary patch, I still have to 
implement looping through extensions, but everything else works.


--
Julien

Re: lyx@fb ?


Il 05/09/2011 08:09, Vincent van Ravesteijn ha scritto:

Op 5-9-2011 1:37, Tommaso Cucinotta schreef:

  http://www.facebook.com/pages/LyX/166594390068533
  http://www.facebook.com/pages/LyX/112847072061085?sk=info
  http://www.facebook.com/group.php?gid=8353382319v=wall


I'm pretty sure no one of us knows anything about these pages.

Someone wants to step up to create order in the chaos ?


among the various ones, the only one that seems to have gained some 
users is:


  http://www.facebook.com/group.php?gid=8353382319
  (134 members, against around 10 for the others)

with explicit references to the official lyx webpage and e-mail 
archives, created by Michael Reed


  http://lyx.475766.n2.nabble.com/LyX-facebook-group-td478290.html

According to this last message, there used to be also some pro-lyx  
anti-M$ group, but I couldn't find it.


The only reason I'm asking is that, if anyone of these groups deserves 
to be considered an official source of information, then it might be 
appropriate:

-) to advertise new releases and other related news about LyX also there
-) to monitor from time to time discussions occurring on the 
corresponding wall.


FB seems to be a promising communication media, and I wouldn't be 
surprised if it helped to get people interested in the tool.


Bye,

T.

Re: LyX 1.6.10 compilation problem in Fedora 15 - and one solution?

On 09/05/2011 08:26 PM, andre duarte bueno wrote:
 Hy
 whem I try do compile LyX 1.6.10
 in my fedora 15; X86_64, g++ (GCC) 4.6.0 20110603 (Red Hat 4.6.0-10)

Is there any specific reason for not to use lyx 2.0 from the distribution?

Regards,

-- 
José Matos

Re: LyX 2.0.1 Released

2011-09-05 Thread Liviu Andronic

On Mon, Sep 5, 2011 at 6:03 PM, Richard Heck rgh...@comcast.net wrote:
 * BUILD/INSTALLATION

 - Using pkgconfig to configure hunspell (hunspell 1.3 was not correctly
  recognized).

 - Using explicit header and library detection as fallback to configure
  hunspell in case pkgconfig is missing in build environment.

As with 2.0.0, I cannot get LyX to work with hunspell 1.2.8 on Xubuntu
10.04 Lucid (x64), even though ./configure ends up with:
Configuration
  Host type:x86_64-unknown-linux-gnu
  Special build flags:  build=release use-aspell use-enchant
use-hunspell
[..]

Am I doing something wrong or is there some incompatibility? LyX works
fine with hunspell via Enchant. Also, 'pkg-config' v0.22 is installed.

Regards
Liviu

Re: [patch] allow to assign several extensions to a file format


Il 05/09/2011 23:33, Julien Rioux ha scritto:

log:
 Allow to assign several extension to a given file format (#4798).
 Additionnal extensions are separated by commas (,). Spaces are
 ignored. Preference (lyxrc) file format incremented to 2.


For example, a LibreOffice/OpenOffice/StarOffice drawing (.odg, .sxd) 
would be one single format with 2 extensions ?


T.

Re: [patch] allow to assign several extensions to a file format


On 06/09/2011 12:55 AM, Tommaso Cucinotta wrote:

Il 05/09/2011 23:33, Julien Rioux ha scritto:

log:
Allow to assign several extension to a given file format (#4798).
Additionnal extensions are separated by commas (,). Spaces are
ignored. Preference (lyxrc) file format incremented to 2.


For example, a LibreOffice/OpenOffice/StarOffice drawing (.odg, .sxd)
would be one single format with 2 extensions ?

T.



I don't use those formats, but if that makes sense, why not. In the 
patch I just treat .html, .htm as one and .jpg, .jpeg as another. These 
formats were the two reported as bugs.


--
Julien

LyX odg drawings


Hi,

[... extracted from the Image Lifecycle Patch ...]

the attached patch adds the OpenOffice drawing format (.odg). With it 
you can:


-) include in LyX OpenOffice drawings
-) preview them on the screen
-) view them in the final .ps/.pdf output
-) edit them externally via libreoffice, ooffice or soffice.

Notes:
1) It includes a trick to avoid detecting .odg as a zipped format, 
unfortunately

I had to replicate it both in Format.cpp and in FileName.cpp.
Any hint on how to possible make the design better ?

Would adding a method

  static bool FileName::isZippedExtension(string const ext);

and using it from within Format.cpp be better ?

2) I guess sxd can be handled once the patch for multi-extension formats 
is cooked.


Thanks,

T.

Index: src/support/FileName.cpp
===
--- src/support/FileName.cpp	(revisione 39605)
+++ src/support/FileName.cpp	(copia locale)
@@ -950,6 +950,13 @@
 
 bool FileName::isZippedFile() const
 {
+	string const  ex = extension();
+	bool zipped_format = (ex == odg || ex == sxd
+		|| ex == odt || ex == sxw || ex == docx
+		|| ex == ods || ex == sxc || ex == xlsx
+		|| ex == gnumeric || ex == dia);
+	if (zipped_format)
+		return false;
 	string const type = guessFormatFromContents();
 	return contains(gzip zip compress, type)  !type.empty();
 }
Index: src/Format.cpp
===
--- src/Format.cpp	(revisione 39605)
+++ src/Format.cpp	(copia locale)
@@ -129,15 +129,25 @@
 }
 
 
+/// For a zipped format, try the filename extension first, then the contents
+/// (otherwise it is always guessed as zip and we're in trouble)
 string Formats::getFormatFromFile(FileName const  filename) const
 {
 	if (filename.empty())
 		return string();
 
-	string const format = filename.guessFormatFromContents();
-	if (!format.empty())
-		return format;
+	string const  ex = filename.extension();
+	bool zipped_format = (ex == odg || ex == sxd
+		|| ex == odt || ex == sxw || ex == docx
+		|| ex == ods || ex == sxc || ex == xlsx
+		|| ex == gnumeric || ex == dia);
 
+	if (!zipped_format) {
+		string const format = filename.guessFormatFromContents();
+		if (!format.empty())
+			return format;
+	}
+
 	// try to find a format from the file extension.
 	string const ext = getExtension(filename.absFileName());
 	if (!ext.empty()) {
@@ -152,6 +162,12 @@
 			return cit-name();
 		}
 	}
+
+	if (zipped_format) {
+		string const format = filename.guessFormatFromContents();
+		if (!format.empty())
+			return format;
+	}
 	return string();
 }
 
Index: lib/scripts/libreoffice2ps.sh
===
--- lib/scripts/libreoffice2ps.sh	(revisione 0)
+++ lib/scripts/libreoffice2ps.sh	(revisione 0)
@@ -0,0 +1,14 @@
+#!/bin/bash
+
+tmpdir=$(mktemp -d)
+fname=$(basename $1)
+for sfx in odg odt ods odp; do
+if echo $fname | grep \\.${sfx}\$; then
+	fname=${fname%%.$sfx}
+	break;
+fi;
+done
+
+libreoffice -nologo -convert-to eps -outdir $tmpdir $1
+mv $tmpdir/$fname.eps $2
+rmdir $tmpdir

ProprietÃ  modificate su: lib/scripts/libreoffice2ps.sh
___
Added: svn:executable
   + *

Index: lib/configure.py
===
--- lib/configure.py	(revisione 39605)
+++ lib/configure.py	(copia locale)
@@ -464,6 +464,9 @@
 checkViewerEditor('a Dia viewer and editor', ['dia'],
 rc_entry = [r'\Format diadia DIA %%	%%	vector'])
 #
+checkProg('an OpenOffice drawing viewer and editor', ['libreoffice', 'ooffice', 'soffice'],
+rc_entry = [r'\Format odgodg ODG %%	%%	vector'])
+#
 checkViewerEditor('a Grace viewer and editor', ['xmgrace'],
 rc_entry = [r'\Format agragr Grace   %%	%%	vector'])
 #
@@ -827,6 +830,10 @@
 \converter xls latex ssconvert --export-type=Gnumeric_html:latex $$i $$o ''',
 ''])
 
+# odg to ps
+checkProg('an OpenOffice drawing - ps converter', ['libreoffice'],
+   rc_entry = [ r'\converter odg ps $$s/scripts/libreoffice2ps.sh $$i $$o '])
+
 path, lilypond = checkProg('a LilyPond - EPS/PDF/PNG converter', ['lilypond'])
 if (lilypond != ''):
 version_string = cmdOutput(lilypond --version)
Index: lib/Makefile.am
===
--- lib/Makefile.am	(revisione 39605)
+++ lib/Makefile.am	(copia locale)
@@ -1512,7 +1512,8 @@
 	scripts/prefs2prefs_lfuns.py \
 	scripts/prefs2prefs_prefs.py \
 	scripts/tex_copy.py \
-	scripts/TeXFiles.py
+	scripts/TeXFiles.py \
+	scripts/libreoffice2ps.sh
 
 templatesdir = $(pkgdatadir)/templates
 dist_templates_DATA = \
@@ -1578,7 +1579,7 @@
 	templates/springer/svmult_part.lyx \
 	templates/springer/svmult_preface.lyx \
 	templates/springer/svmult_referenc.lyx
-	
+
 thesistemplatesdir

Re: [patch] allow to assign several extensions to a file format

On 09/05/2011 05:33 PM, Julien Rioux wrote:
 log:
  Allow to assign several extension to a given file format (#4798).
  Additionnal extensions are separated by commas (,). Spaces are
  ignored. Preference (lyxrc) file format incremented to 2.

Thanks for taking care of this.

  A lot of the diff is renaming extension - extensions

 See issues
 http://www.lyx.org/trac/ticket/4798
 http://www.lyx.org/trac/ticket/6340

 Comments welcome!

If you make the extensions_ member a vectorstring or liststring, it
will make looping and such a lot easier. You might then just have:
 string extension() { return extensions_[0]; }
which I guess is supposed to be the default extension? You're basically
then just caching the result of the split call that turns up from time
to time.

Richard

Re: LyX odg drawings

On 09/05/2011 07:51 PM, Tommaso Cucinotta wrote:
 Hi,

 [... extracted from the Image Lifecycle Patch ...]

 the attached patch adds the OpenOffice drawing format (.odg). With it
 you can:

 -) include in LyX OpenOffice drawings
 -) preview them on the screen
 -) view them in the final .ps/.pdf output
 -) edit them externally via libreoffice, ooffice or soffice.

 Notes:
 1) It includes a trick to avoid detecting .odg as a zipped format,
 unfortunately
 I had to replicate it both in Format.cpp and in FileName.cpp.
 Any hint on how to possible make the design better ?
 z
 Would adding a method

   static bool FileName::isZippedExtension(string const ext);

 and using it from within Format.cpp be better ?

Just have a standalone function:
bool isZippedFormat(string ext)
and call that from both FileName and Format. I guess it would make sense
in support/filetools.{h,cpp}. Though I wonder if there is a better way
than checking extensions

 Index: src/support/FileName.cpp
 ===
 --- src/support/FileName.cpp  (revisione 39605)
 +++ src/support/FileName.cpp  (copia locale)
 @@ -950,6 +950,13 @@
  
  bool FileName::isZippedFile() const
  {
 + string const  ex = extension();
 + bool zipped_format = (ex == odg || ex == sxd
 + || ex == odt || ex == sxw || ex == docx
 + || ex == ods || ex == sxc || ex == xlsx
 + || ex == gnumeric || ex == dia);
 + if (zipped_format)
 + return false;

Shouldn't that be return true?

rh

Re: LyX 2.0.1 Sources Available


Am 05.09.2011 19:54, schrieb Pavel Sanda:

Uwe Stöhr wrote:

Works fine and a Win installer is ready (the merged one). I'll leave the
installer for LyX 2.0.1 to Joost because the merged installer is not yet
able to install LyX if you install it without admin privileges (due to a
Imagemagick issue).


is this regression wrt 2.0.0 installer? if not why wait...


Yes, Joost's installer is able to install LyX without admin priviledges. To achieve this, he use 
special compiled version of ImageMagick. This is not a suitable solution because we should rely on 
official releases. Moreover ImageMagick releases very often and our goal was that more than one 
developer is able to build the Win installer. Therefore we should concentrate on the LyX stuff and 
use the official releases.
The next time I find time, I'll work on the remaining ImageMagick issue. The problem is that 
ImageMagick requires a registry entry in HKLM but this can only be set with admin priviledges.


Besides this, the new installer was not yet tested by users.

regards Uwe

Re: LyX 2.0.1 Sources Available


Am 05.09.2011 20:01, schrieb Vincent van Ravesteijn:


For these people we have the standard installer. The bundle installer is 
especially designed for
new installations and therefore includes MiKTeX and JabRef (is optional). So 
the standard
installer will not bother the user and is as small as possible to update 
existing LyX
installations. This variant therefore expects an installed MiKTeX. If no MiKTeX 
or TeXLive is
found, it will throw a warning that the bundle installer should be used.


Why don't we download it anymore then ?


Then we would have the same trouble as we have now in the installer for 2.0.0 with broken download 
links and we need more complicated installer code.
Besides this there are from time to time bugs in MiKTeX releases that break LaTeX packages. By 
including MiKTeX we assure that we are shipping a tested MiKTeX build.



We did this as long as I remember having Windows installers.


Never with my installer. I provide the solution with the two installer variants since I'm involved 
to LyX and I never had complaints that new users used the standard installer without having LaTeX 
installed.


regards Uwe

Re: LyX 2.0.1 Sources Available

Am 05.09.2011 20:43, schrieb Vincent van Ravesteijn:

I tried the merged installer.

Many thanks!

Here is some feedback:

1. The icon is not the nicest one. We should have a transparent one.

What icon do you mean? The installer uses the icon of the lyx.exe file. If you want another icon, we
must change the build code to link it to the lyx.exe.

2. I agree with Joost that the dialog to choose the start menu folder is not
necessary anymore. It
is not useful having only a single item in a map.

People requested to choose the start menu folder and almost all installers I know provide this
feature. There is also only one programs on my PC (Inkscape) that is not following the Windows
guideline to have its own folder in the start menu.
This is also necessary to distinguish between different LyX versions. For example I have LyX 1.4.5,
1.5.7, 1.6.10. 2.0.1 and 2.1.0svn installed. Without a folder for each program, I would have 5
entries with the same name LyX.
(Initially in the LyX folder there was also the link to uninstall LyX but Joost were opposed to
this, so I dropped it.)

3. The start menu folder is called LyX 2.0.1. I don't like the version number
in the name, there
is no need for it.

We need the version number to distinguish between different versions. Many users I know are still
using LyX 1.6.x side by side to LyX 2.0.x in case there are regression bugs in LyX 2.0.x. For the
same reason we got reports that users even do this for a stable LyX series. So the might have LyX
2.0.0 _and_ 2.0.1 installed.

4. In the MikTeX page is a spelling error in the dutch translation: LaTeX
softare. Also in the
MikTeX update page.

Thanks, fixed now.

5. Why do we install the MikTeX packages without asking the user for permission?

Because new user cannot know what a package is and what is it about. Their cryptic names are also
meaningless, even if you know some basics about LaTeX.
We can also not let new users about 50 times read popup dialog with lots of information that are
cryptic and he should decide what to do. We therefore install all available packages that are needed
by LyX. This way the user is not bothered and he gets a full functional LyX. The installation
progress is made visible in the installer.

This is one of the key features of the installer!

I determine whether
I want to install tons of MikTeX packages or not and ,moreover, I have set the
setting of MikTex to
always ask before installing a package. LyX just overrides this. I don't accept
this.

You can reset the settings any time.

6. Joost had a reason to not allow to start the application from the installer.
Isn't this a problem
now anymore ?

I don't know what you are referring to.

7. Joost's LyX2.0 installer installed the folder AppData/Roaming/LyX2.0. Can we
please have the same
directory for newer installers instead of lyx20 ?

What do you mean? LyX's settings folder is on my PC
C:\Documents and Settings\Uwe\Application Data\lyx20

All LyX 2.0.x releases share the same folder. The 1.6.x series uses the folder lyx16. What is
wrong with that?
I don't know why Joost's installer creates a folder LyX2.0 instead of lyx20. For me this folder
is created automatically when LyX.exe is called the first time. So he must be using a special
compilation setting.

8. Joost's LyX2.0 installer installed in the folder Program Files/LyX20. The
merged installer in
Program Files/LyX 2.0.1. Can we please have the same directory for newer
installers? Preferably
without all the version numbers.

This is not possible, because how would yo then distinguish between the different installations? You
can have LyX 1.6.4 installed besides 1.6.10. And we have user who are actually using this as I
stated above. (I did the same when I wrote my thesis.)

9. I found the following faulty registry entries. Where do they come from ?

HKEY_CLASSES_ROOT\LyX.Document\Shell\open\command
C:\Program Files (x86)\LyX 2.0.1\bin\LyXLauncher.exe %1

HKEY_CLASSES_ROOT\LyX.Document\DefaultIcon
C:\Program Files (x86)\LyX 2.0.1\bin\LyXLauncher.exe,0

LyXLauncher is the executable that hides LyX's console Window. Joost doesn't need this anymore since
he found a way to compile LyX without its console window. But I was not able to do the same. No
matter if I compile with SCons or CMake, I always get a lyx.exe that comes with a console window.

HKEY_CLASSES_ROOT\Applications
C:\Program Files (x86)\LyX 2.0.1\imagemagick\convert.exe $

This is ImageMagick's converter executable. This entry is set by ImageMagick.

10. Now, I have both LyX2.0.0 and LyX2.0.1 installed on my pc ? Shouldn't we
overwrite the previous
version ?

No. See the reasons above.

thanks and regards
Uwe

Re: first step of merging the Win installers

Am 05.09.2011 19:44, schrieb Vincent van Ravesteijn:

I don't understand. Joost proposed to transfer the translations. I would
expect them to use the
same strings and thus the same translations.

The strings are different due to the different layout of the 2 installer pages.

The problem with the generic code is that you expect every MiKTeX version to
act the same. But
this was not the case in the past. Registry entries changed and even names of
executables we need
to configure MikTeX. So we need to check each major release, e.g. the future
MiKTeX 2.10 (which is
probably not released under this version number but as MiKTeX 3.0).

So, if you have a newer MikTeX installed, you prefer to not be able to use it
over the fact that
people use it and it might not work completely right (in some exceptional
cases) ?

What are you referring to? The installer needs to check the LaTeX system. If more than one system is
installed, it should use the newest one, if TeXLive and MiKTeX is installed, we use MiKTeX. Each
MiKTeX release requires different registry settings (in this case these are the MiKTeX settings) and
there own executable names. We need to configure MiKTeX in any case, for example to install
LyX-specific packages like broadway. To do this, we copy the files to MiKTeX's repository and thus
need to know its location. Then we need to refresh MiKTeX's package file name database. This is done
by executing one of MiKTeX's programs (maybe with parameters). So we need to know the name of the
executable and its location. Perhaps we also need to set some special registry entry before. This is
just one example and this procedure changes from version to version of MiKTeX.

regards Uwe

Re: LyX 2.0.1 Released

2011-09-05 Thread Stephan Witt

Am 06.09.2011 um 00:32 schrieb Liviu Andronic:

 On Mon, Sep 5, 2011 at 6:03 PM, Richard Heck rgh...@comcast.net wrote:
 * BUILD/INSTALLATION
 
 - Using pkgconfig to configure hunspell (hunspell 1.3 was not correctly
  recognized).
 
 - Using explicit header and library detection as fallback to configure
  hunspell in case pkgconfig is missing in build environment.
 
 As with 2.0.0, I cannot get LyX to work with hunspell 1.2.8 on Xubuntu
 10.04 Lucid (x64), even though ./configure ends up with:
 Configuration
  Host type:x86_64-unknown-linux-gnu
  Special build flags:  build=release use-aspell use-enchant
 use-hunspell
 [..]

So configure could detect the location of header and library and the final 
binary should provide the hunspell spellchecker backend.

 Am I doing something wrong or is there some incompatibility? LyX works
 fine with hunspell via Enchant. Also, 'pkg-config' v0.22 is installed.

At runtime LyX needs to find the dictionaries. Did you set the path in the
preferences? Alternatively you may copy them from LyX's SVN repository
in dictionaries/dicts to the subdirectory dicts in the system directory of LyX.
You may copy the dictionaries/thes contents to the thes subdirectory to get
a working thesaurus.

Stephan

Re: lyx@fb ?


Op 5-9-2011 1:37, Tommaso Cucinotta schreef:

Hi,

just reconnecting with the lyx@twitter proposal, I found these pages 
about LyX on FB:


  http://www.facebook.com/pages/LyX/166594390068533
  http://www.facebook.com/pages/LyX/112847072061085?sk=info
  http://www.facebook.com/group.php?gid=8353382319=wall

I'm not such an expert user of this tool, however I cannot actually 
understand the difference among these (or, if there any any further 
pages like this around). Is it on purpose to have multiple pages like 
these ?


T.


I'm pretty sure no one of us knows anything about these pages.

Someone wants to step up to create order in the chaos ?

Vincent

Re: r39582 - in lyx-devel/trunk/development/Win32/packaging/installer: include setup


Op 5-9-2011 8:09, uwesto...@lyx.org schreef:

Author: uwestoehr
Date: Mon Sep  5 08:09:13 2011
New Revision: 39582
URL: http://www.lyx.org/trac/changeset/39582

Log:
installer:
- fix 2 uninstaller issues
- remove support for AFPL Ghostscript (license clash)
- only install Ghostscript if not already installed
- in case there are several Ghostscript installations, use the newest one
- remove an unused variable




 I thought there was a recent discussion about dropping the Ghostscript 
support ?


Vincent

Language changes within index entries (was: LyX 2.0.1 Sources Available)

2011-09-05 Thread Jean-Pierre Chrétien


Le 01/09/2011 16:15, Uwe Stöhr a écrit :

Am 01.09.2011 10:55, schrieb Jean-Pierre Chrétien:


Compilation of French versions of UserGuide and EmbeddedObjects fail
for a
similar reason: bad language change location in a sectioning heading.


Where? For me all documentation files for all languages compile.


On Linux/TexLive I get the following errors.

In UserGuide:


Overfull \hbox (10.96574pt too wide) in paragraph at lines 103--104
[]\T1/lmr/bx/n/12 Environnements de Pa-ra-graphe, [][]18[][]--
 []

! Extra }, or forgotten \endgroup.
l.125 \subitem Details}
   \selectlanguage  {english} , \hyperpage{77}
I've deleted a group-closing symbol because it seems to be
spurious, as in `$x}$'. But perhaps the } is legitimate and
you forgot something else, as in `\hbox{$x}'. In such cases
the way to recover is to insert both the forgotten and the
deleted material, e.g., by typing `I$}'.


After investigation, this error is due to the fact that the word 'Flottants' is 
in French in the index inset within title of section 4.6.3. The exported latex 
construct


\subsection{More Information\index{Flottants@\selectlanguage{french}%
Flottants\foreignlanguage{english}{!Details@Details}\selectlanguage{english}
}}

creates the abovementioned error, as texindy creates line

   \subitem Details}\selectlanguage{english} , \hyperpage{79}

in UserGuide.ind.

This will be corrected when the section will be translated, but does this
deserve a ticket ? I wonder whether this is a LyX bug in the exported LaTeX
syntax or a index generator bug, which should not export 
'}\selectlanguage{english}'.


In EmbeddedObjects:


Chapter 6.
Runaway argument?
! Paragraph ended before \def was complete.

   \par
l.5632 ...anguage{french}{Flottants d'enrobage

I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.


and a set of errors triggered by the first one.

Change of language in a header title again, the offending code reads in LaTeX:

\section{Flottant d'enrobage\label{sec:Flottant-d'enrobage}
\index{Flottants!Flottants d'enrobage}\foreignlanguage{english}
{\index{Surrounded by text!Flottants d'enrobage@\foreignlanguage{french}
{Flottants d'enrobage

on one single line.

Again the error is due to an incompletely translated index entry, but this time 
the error occurs at the first pdflatex pass. The recursive \foreignlanguage 
construct in an index entry seems there incorrect in LaTeX (no more errors if I 
remove the external \foreignlanguage{english}{...} command).


I wonder why you do not see these errors ? In the first case, this may be due to 
the indexing engine, but in the second one, this seems a native TeX error.


--
Jean-Pierre

Re: merging of external material and graphics interfaces

2011-09-05 Thread Helge Hafting


On 02. sep. 2011 02:45, Tommaso Cucinotta wrote:
[...]

I'm not sure why some of the external material contents are not
previewed on the screen.


External material is not necessarily images.

The spreadsheet inset is converted to a longtable, for example. A 
longtable may get broken up over several pages, and location of the 
breaks depends on where the previous pagebreak (in the document) 
happens. As we all know, LyX doesn't break the document into pages

in advance.

Helge Hafting

Re: LyX 2.0.1 Sources Available


Am 02.09.2011 08:41, schrieb Vincent van Ravesteijn:


In th merged installer MiKTeX is directly included. So even if you don't
have Internet access, you can install LyX and it will work with its basic
features. There were some reasonable user requests in the past to include
MiKTeX directly and the MiKTeX maintainer kindly built in some features for
us in his basic installer.


I would prefer not to include MikTeX in the installer. Most people that
download LyX already have MikTeX installed, so why would you bother them
with a huge download.


For these people we have the standard installer. The bundle installer is especially designed for new 
installations and therefore includes MiKTeX and JabRef (is optional). So the standard installer will 
not bother the user and is as small as possible to update existing LyX installations. This variant 
therefore expects an installed MiKTeX. If no MiKTeX or TeXLive is found, it will throw a warning 
that the bundle installer should be used.



Ah so.. but when the installer downloads MikTeX from the web, we better can
use the link without a build number. That was my point.


Sure, but this is only the case in Joost's installer not in the merged one which will be our new 
installer, hopefully to be ready for LyX 2.0.2. Despite of the installation without admin 
privileges, it is ready to use in my opinion, please check it out, if you find some time.


regards Uwe

Re: Language changes within index entries - French doc files uncompilable in LyX 2.0.1


Am 05.09.2011 08:49, schrieb Jean-Pierre Chrétien:


After investigation, this error is due to the fact that the word 'Flottants' is 
in French in the
index inset within title of section 4.6.3. The exported latex construct

\subsection{More Information\index{Flottants@\selectlanguage{french}%
Flottants\foreignlanguage{english}{!Details@Details}\selectlanguage{english}
}}

creates the abovementioned error, as texindy creates line

\subitem Details}\selectlanguage{english} , \hyperpage{79}

in UserGuide.ind.

This will be corrected when the section will be translated, but does this
deserve a ticket ?


I'm not seeing these issues because xindy is not available under Windows and thus makeindex is used 
as indexing program.
It seems that xindy doesn't support multiple languages in index entries while this works without 
problems with makeindex.
There is nothing we can do about it because denying multiple languages would change existing LyX 
files that compile fine with makeindex.
We have this problematic in other cases too, for example with tables. Depending on the document 
settings, multiple languages work, sometimes not.


For now, can you please translate the problematic cases right now?

Richard, what about LyX 2.0.1? Is it delayed, so that I can put this in?

regards Uwe

Re: LyX 2.0.1 Sources Available


Am 02.09.2011 15:46, schrieb Vincent van Ravesteijn:


Can you send me a link to this installer. I want to test it.


https://developer.berlios.de/project/showfiles.php?group_id=5117_id=18767

regards Uwe

Re: r39582 - in lyx-devel/trunk/development/Win32/packaging/installer: include setup


Am 05.09.2011 08:13, schrieb Vincent van Ravesteijn:


I thought there was a recent discussion about dropping the Ghostscript support ?


This was about the support for GSview which has already been dropped.

We need Ghostscript to display PDF and EPS images within LyX.

regards Uwe

Re: first step of merging the Win installers

Am 21.08.2011 11:00, schrieb Vincent van Ravesteijn:

If you don't mind I'll put back the nsDialogs version and we'll just transfer
the translations.

AFAICS this hasn't been done yet.

Uwe, are you still planning to revert to the nsDialogs version ?

regards Uwe

LyX 2.0.1 Released


Public release of LyX version 2.0.1
===

We are pleased to announce the release of LyX 2.0.1. This is the first
maintenance release in the 2.0.x series.

LyX 2.0.1 is the result of on-going efforts to make our stable version
even more reliable and stable. We have fixed a number of bugs and made
a number of improvements. These are detailed below. We encourage all
LyX users to upgrade to this version.

LyX is a document processor that encourages an approach to writing based
on the structure of your documents and not simply their appearance. It is
released under a Free and Open Source Software license.

You can download LyX 2.0.1 from http://www.lyx.org/Download/.

If you think you found a bug in LyX 2.0.1, either e-mail the LyX
developers' mailing list (lyx-devel  lists.lyx.org), or open a bug
report at http://www.lyx.org/trac/wiki/BugTrackerHome.

If you have trouble using LyX or have a question, consult the
documentation that comes with LyX and the LyX wiki, which lives at
http://wiki.lyx.org/. If you can't find the answer there, e-mail the LyX
users' list (lyx-users at lists.lyx.org).

We hope you enjoy using LyX 2.0.1.

The LyX team.
http://www.lyx.org


What's new in LyX 2.0.1
===

The support for using external files in ERT has been improved by the
introduction of a prefix for the TEXINPUTS environment variable.
This prefix can be set in preferences and by default includes the
document directory (represented by a single '.'). The prefix can
be set to any list of paths separated by the default separator for
a given platform (':' on unix like systems and ';' on windows).
When a file should be included by LaTeX, the paths listed in TEXINPUTS
will be searched in turn for finding it. Note that any non-absolute
path listed in the TEXINPUTS prefix is considered to be relative to the
document directory, i.e., the directory where the LyX file lives.
Users are advised to always include '.' (the document dir) as one of
the path components, otherwise compilation may fail for some documents.
This is because the previous (undocumented) mechanism based on the use
of the \input@path macro has been dropped. The old mechanism did not
work in all cases and was kind of a hack. Old documents using that
undocumented hack for obtaining the path of the LyX file will have to
be revised. A clean way for obtaining the document path is using the
info inset through the "info-insert buffer path" LyX function.


** Updates:
***

* DOCUMENT INPUT/OUTPUT

- Allow for a maximum of 3 minutes for the completion of a spawned command
  except on Windows, where 30 minutes are allowed. This is because the
  Windows installer may trigger MiKTeX updates that suffer from network
  latencies.

- Improved XHTML output of various fractions.

- A prefix for the TEXINPUTS environment variable can be specified in the
  preferences. The directory of a LyX document is represented by a single
  dot '.' or by the prefix "./". Also, any non-absolute path will be
  prepended with the LyX document directory.

- Updated templates to current LyX format, so no conversion will be
  needed.

- Allow LaTeX import of \uline (bug 7640).

- Fix compilation error occurring when a LyX document resides in a directory
  whose name contains characters that are special to LaTeX (bug 6170).


* USER INTERFACE

- Updated Czech, French, German, Japanese, Interlingua, Italian, Polish,
  Portuguese, Serbian (Latin), Spanish, Swedish and Ukrainian User
  Interface Localization.

- Now it is not necessary to restart LyX after changing the default
  document directory and/or the PATH prefix in the preferences for them
  to take effect.

- Menu View->Source for documents with XHTML default output format now
displays
  only the current paragraph, except when complete source is requested
  (bug 7463).

- Size tab now enables and disables correctly depending on the capabilities
  configured for the current external template (selected via the combo).

- Sort entries in the "More Formats and Options" dialog (bug 7714).

- Enable "Accept compound" preference setting for Aspell backend only.
  Reconfigure the aspell backend when "Accept compound" preference is
  changed immediately.


* DOCUMENTATION AND LOCALIZATION

- UserGuide:
  - new section how to define custom header/footer lines
(bug 7196).
  - new section about customized lists
  - new section about comparison of LyX documents
  - new section about the document's colors settings
  - revised Appendix A and B

- EnbeddedObjects manual:
  - describe that LyX supports now the changing of the color of the
greyed-out box text
  - new chapter about objects surrounded by text

- Math manual: add a note about column limit for decorated matrices.

- Updated French documentation files.

- updated template file for the latest version of the ACM siggraph
  LaTeX-package.

- updated layout and template file for the latest version of the IJMPC
  LaTeX-package.

- updated

Branch is Open


Branch is again open for commits, as LyX 2.0.1 is out.

Richard

Re: first step of merging the Win installers


Op 5-9-2011 17:39, Uwe Stöhr schreef:

Am 21.08.2011 11:00, schrieb Vincent van Ravesteijn:

- I used the custom LaTeX installer page from my installer, only 
because
this is already translated to 22 languages. The page design is a 
matter of
taste, so we can also use yours if you prefer it for a certain 
reason.


This page doesn't fit in the framework of the installer and uses a 
deprecated NSIS plug-in for the
GUI. We now have two different GUI codes in place, one using the 
modern nsDialogs code and the old

code based on INI files.

If you don't mind I'll put back the nsDialogs version and we'll just 
transfer the translations.


AFAICS this hasn't been done yet.

Uwe, are you still planning to revert to the nsDialogs version ?


For now not. This can be done any time later. Once this installer is 
ready for usage we will ask people to translate it. Therefore the 
nsDialog strings are in the language files of the installer. When we 
got them translated, we can switch.
Currently we have translations for 22 languages and thus should use 
them. For the nsDialog strings we currently only have them for 3 
languages.


I don't understand. Joost proposed to "transfer the translations". I 
would expect them to use the same strings and thus the same translations.




Yea the detection of external programs became really messy now. We 
should merge and clean this up.
What I don't like about this MiKTeX detection code is the lack of 
forward compatibility (e.g.

MiKTeX 2.10 won't work) and the code duplication for each version.
What it wrong with the generic code that I used?


The problem with the generic code is that you expect every MiKTeX 
version to act the same. But this was not the case in the past. 
Registry entries changed and even names of executables we need to 
configure MikTeX. So we need to check each major release, e.g. the 
future MiKTeX 2.10 (which is probably not released under this version 
number but as MiKTeX 3.0).


So, if you have a newer MikTeX installed, you prefer to not be able to 
use it over the fact that people use it and it might not work completely 
right (in some exceptional cases) ?


Vincent

Re: r39337 - lyx-devel/trunk/src/frontends/qt4

for...@lyx.org wrote:
> Author: forenr
> Date: Mon Jul 18 10:10:20 2011
> New Revision: 39337
> URL: http://www.lyx.org/trac/changeset/39337
> 
> Log:
> Limit fix for bug #6063 to math insets and only when inline completion
> is disabled in math.
> 
> Modified:
>lyx-devel/trunk/src/frontends/qt4/GuiCompleter.cpp
> 
> Modified: lyx-devel/trunk/src/frontends/qt4/GuiCompleter.cpp
> ==
> --- lyx-devel/trunk/src/frontends/qt4/GuiCompleter.cppMon Jul 18 
> 05:25:29 2011(r39336)
> +++ lyx-devel/trunk/src/frontends/qt4/GuiCompleter.cppMon Jul 18 
> 10:10:20 2011(r39337)
> @@ -311,7 +311,7 @@
>   if (!inlineVisible() && possibleInlineState && start
>   && cur.inset().automaticInlineCompletion())
>   inline_timer_.start(int(lyxrc.completion_inline_delay * 1000));
> - else {
> + else if (cur.inMathed() && !lyxrc.completion_inline_math) {
>   // no inline completion, hence a metrics update is needed
>   if (!(cur.result().screenUpdate() & Update::Force))
>   cur.screenUpdateFlags(cur.result().screenUpdate() | 
> Update::SinglePar);

Enrico, this was for branch as well? p

Re: LyX 2.0.1 Sources Available

Uwe Stöhr wrote:
> Works fine and a Win installer is ready (the merged one). I'll leave the 
> installer for LyX 2.0.1 to Joost because the merged installer is not yet 
> able to install LyX if you install it without admin privileges (due to a 
> Imagemagick issue).

is this regression wrt 2.0.0 installer? if not why wait...
pavel

Re: LyX 2.0.1 Released

2011-09-05 Thread Jürgen Spitzmüller

Richard Heck wrote:
> Public release of LyX version 2.0.1
> ===
> 
> We are pleased to announce the release of LyX 2.0.1. This is the first
> maintenance release in the 2.0.x series.

Congratulations, Richard!

Jürgen

Re: LyX 2.0.1 Sources Available



In th merged installer MiKTeX is directly included. So even if you 
don't
have Internet access, you can install LyX and it will work with its 
basic
features. There were some reasonable user requests in the past to 
include
MiKTeX directly and the MiKTeX maintainer kindly built in some 
features for

us in his basic installer.


I would prefer not to include MikTeX in the installer. Most people that
download LyX already have MikTeX installed, so why would you bother them
with a huge download.


For these people we have the standard installer. The bundle installer 
is especially designed for new installations and therefore includes 
MiKTeX and JabRef (is optional). So the standard installer will not 
bother the user and is as small as possible to update existing LyX 
installations. This variant therefore expects an installed MiKTeX. If 
no MiKTeX or TeXLive is found, it will throw a warning that the bundle 
installer should be used.


Why don't we download it anymore then ? We did this as long as I 
remember having Windows installers.


Vincent

Re: LyX 2.0.1 Released

On 09/05/2011 06:54 PM, Jürgen Spitzmüller wrote:
> Congratulations, Richard!

+1 the first time is always the most terrifying. ;-)

-- 
José Matos

Re: LyX 2.0.1 Released

On 09/05/2011 02:27 PM, José Matos wrote:
> On 09/05/2011 06:54 PM, Jürgen Spitzmüller wrote:
>> Congratulations, Richard!
> +1 the first time is always the most terrifying. ;-)
>
I'm hoping that is true.

Richard

Re: LyX 2.0.1 Sources Available


Op 5-9-2011 17:28, Uwe Stöhr schreef:

Am 02.09.2011 15:46, schrieb Vincent van Ravesteijn:


Can you send me a link to this installer. I want to test it.


https://developer.berlios.de/project/showfiles.php?group_id=5117_id=18767 



regards Uwe


Hi Uwe,


I tried the merged installer. Here is some feedback:

1. The icon is not the nicest one. We should have a transparent one.

2. I agree with Joost that the dialog to choose the start menu folder is 
not necessary anymore. It is not useful having only a single item in a map.


3. The start menu folder is called "LyX 2.0.1". I don't like the version 
number in the name, there is no need for it.


4. In the MikTeX page is a spelling error in the dutch translation: 
LaTeX softare. Also in the MikTeX update page.


5. Why do we install the MikTeX packages without asking the user for 
permission? I determine whether I want to install tons of MikTeX 
packages or not and ,moreover, I have set the setting of MikTex to 
always ask before installing a package. LyX just overrides this. I don't 
accept this.


6. Joost had a reason to not allow to start the application from the 
installer. Isn't this a problem now anymore ?


7. Joost's LyX2.0 installer installed the folder AppData/Roaming/LyX2.0. 
Can we please have the same directory for newer installers instead of 
lyx20 ?


8. Joost's LyX2.0 installer installed in the folder Program Files/LyX20. 
The merged installer in Program Files/LyX 2.0.1. Can we please have the 
same directory for newer installers? Preferably without all the version 
numbers.


9. I found the following faulty registry entries. Where do they come from ?

HKEY_CLASSES_ROOT\LyX.Document\Shell\open\command
"C:\Program Files (x86)\LyX 2.0.1\bin\LyXLauncher.exe" "%1"

HKEY_CLASSES_ROOT\LyX.Document\DefaultIcon
C:\Program Files (x86)\LyX 2.0.1\bin\LyXLauncher.exe,0

HKEY_CLASSES_ROOT\Applications
C:\Program Files (x86)\LyX 2.0.1\imagemagick\convert.exe $

10. Now, I have both LyX2.0.0 and LyX2.0.1 installed on my pc ? 
Shouldn't we overwrite the previous version ?


Vincent

Re: merging of external material and graphics interfaces

2011-09-05 Thread Georg Baum

Tommaso Cucinotta wrote:

> Il 31/08/2011 21:19, Georg Baum ha scritto:
>> This plan exists for ages. The graphics inset even was already ditched at
>> some point in time, but it got reintroduced later, because the external
>> inset did not work that well back then. IIRC there is also a bug entry
>> for that. You will be a hero if you finally manage to do this!
> which bug number ? Or, what to exactly search for in the database ?

I searched now and did not find it, so probably my memory was wrong.

> that's also my feeling: external material seems more generic than
> graphics, and after all each graphics may be handled via the RasterImage
> external material, or probably a variation of it that merges together at
> least the RasterImage, Dia and XFig external material types (or the
> other way round, i.e., each different file type into its own external
> material kind -- which one is best?).

IMHO one template per file type is overkill. There should be as little 
templates as possible, and each template should handle a group of file types 
that have something in common. The RasterImage is a good example. A similar 
VectorImage template for generic vector images would also be useful. I 
believe that the Dia template is in fact a generic vector image template (or 
could be changed to be one). Only programs that support inline LaTeX and/or 
produce more than one file like XFig need a dedicated template

> I'm not sure why some of the external material contents are not
> previewed on the screen.

Which templates?

Georg

LyX 1.6.10 compilation problem in Fedora 15 - and one solution?

Hy
whem I try do compile LyX 1.6.10
in my fedora 15; X86_64, g++ (GCC) 4.6.0 20110603 (Red Hat 4.6.0-10)

a have the problem below

Mensagem de Erro:
make[4]: Entrando no diretório
`/home/bueno/Download/PacotesExtras/03-Editoracao-lyx-abntex/lyx-1.6.10/src'
  CXXInsetInclude.lo
insets/InsetInclude.cpp: In member function ‘const
lyx::support::FileNameList& lyx::InsetInclude::getBibfilesCache(const
lyx::Buffer&) const’:
insets/InsetInclude.cpp:809:37: error: uninitialized const ‘empty’
[-fpermissive]
./support/FileNameList.h:27:7: note: ‘const class
lyx::support::FileNameList’ has no user-provided default constructor
make[4]: ** [InsetInclude.lo] Erro 1
make[4]: Saindo do diretório
`/home/bueno/Download/PacotesExtras/03-Editoracao-lyx-abntex/lyx-1.6.10/src'
make[3]: ** [all-recursive] Erro 1
make[3]: Saindo do diretório
`/home/bueno/Download/PacotesExtras/03-Editoracao-lyx-abntex/lyx-1.6.10/src'
make[2]: ** [all] Erro 2
make[2]: Saindo do diretório
`/home/bueno/Download/PacotesExtras/03-Editoracao-lyx-abntex/lyx-1.6.10/src'
make[1]: ** [all-recursive] Erro 1
make[1]: Saindo do diretório
`/home/bueno/Download/PacotesExtras/03-Editoracao-lyx-abntex/lyx-1.6.10'
make: ** [all] Erro 2


I open file FileNameList and include 2 lines

class FileNameList: public std::vector
{
public: //new
FileNameList() : std::vector(){} //new
};

after this modification the program compile.
please verify thie problem and solution.



*Prof. André Duarte Bueno, Dr*
Engenharia de Software,  Análise e Processamento de Imagens
*UENF* - Universidade Estadual do Norte Fluminense - Darcy Ribeiro
*CCT *- Centro de Ciencias e Tecnologias
*LENEP* - Laboratório de Engenharia e Exploração de Petróleo
Rodovia Amaral Peixoto, km 163, Avenida Brenand S/N
CEP:   27925-310 - Imboassica - Macaé - RJ - Brasil
Fone:   +55 (22)  2765-6500 geral / *(22) 2765-6563 *sala / (22) 9954-2635
cel
Fax: +55 (22) 2765-6565
e-mail: *bu...@lenep.uenf.br*
http://www2.lenep.uenf.br/~bueno

Re: r39600 - in lyx-devel/branches/BRANCH_2_0_X: . src/frontends/qt4/ui

rgh...@lyx.org wrote:
> Author: rgheck
> Date: Mon Sep  5 21:27:10 2011
> New Revision: 39600
> URL: http://www.lyx.org/trac/changeset/39600
> 
> Log:
> Fix tab order and shortcuts for crossref dialog (#7576).
> 
> Modified:
>lyx-devel/branches/BRANCH_2_0_X/src/frontends/qt4/ui/RefUi.ui
>lyx-devel/branches/BRANCH_2_0_X/status.20x
> 
> Modified: lyx-devel/branches/BRANCH_2_0_X/src/frontends/qt4/ui/RefUi.ui
> ==
> --- lyx-devel/branches/BRANCH_2_0_X/src/frontends/qt4/ui/RefUi.ui Mon Sep 
>  5 21:25:15 2011(r39599)
> +++ lyx-devel/branches/BRANCH_2_0_X/src/frontends/qt4/ui/RefUi.ui Mon Sep 
>  5 21:27:10 2011(r39600)
> @@ -1,193 +1,156 @@
> -
> +

xml line...
p

Re: LyX 1.6.10 compilation problem in Fedora 15 - and one solution?

andre duarte bueno wrote:
> Hy
> whem I try do compile LyX 1.6.10
> in my fedora 15; X86_64, g++ (GCC) 4.6.0 20110603 (Red Hat 4.6.0-10)

either use lyx 2.0 or get lyx 1.6 from svn where it should be fixed.
newer lyx 1.6.11 won't be released.
pavel

Re: LyX 1.6.10 compilation problem in Fedora 15 - and one solution?

thanks

*Prof. André Duarte Bueno, Dr*
Engenharia de Software,  Análise e Processamento de Imagens
*UENF* - Universidade Estadual do Norte Fluminense - Darcy Ribeiro
*CCT *- Centro de Ciencias e Tecnologias
*LENEP* - Laboratório de Engenharia e Exploração de Petróleo
Rodovia Amaral Peixoto, km 163, Avenida Brenand S/N
CEP:   27925-310 - Imboassica - Macaé - RJ - Brasil
Fone:   +55 (22)  2765-6500 geral / *(22) 2765-6563 *sala / (22) 9954-2635
cel
Fax: +55 (22) 2765-6565
e-mail: *bu...@lenep.uenf.br*
http://www2.lenep.uenf.br/~bueno

2011/9/5 Pavel Sanda 

> andre duarte bueno wrote:
> > Hy
> > whem I try do compile LyX 1.6.10
> > in my fedora 15; X86_64, g++ (GCC) 4.6.0 20110603 (Red Hat 4.6.0-10)
>
> either use lyx 2.0 or get lyx 1.6 from svn where it should be fixed.
> newer lyx 1.6.11 won't be released.
> pavel
>

[patch] allow to assign several extensions to a file format


log:
 Allow to assign several extension to a given file format (#4798).
 Additionnal extensions are separated by commas (,). Spaces are
 ignored. Preference (lyxrc) file format incremented to 2.

 A lot of the diff is renaming extension -> extensions

See issues
http://www.lyx.org/trac/ticket/4798
http://www.lyx.org/trac/ticket/6340

Comments welcome!

Regards,
Julien
diff --git a/lib/configure.py b/lib/configure.py
index 908c211..d4ceebb 100644
--- a/lib/configure.py
+++ b/lib/configure.py
@@ -476,7 +476,7 @@ def checkFormatEntries(dtl_tools):
 path, iv = checkViewerNoRC('a raster image viewer', ['xv', 'kview', 'gimp-remote', 'gimp'],
 rc_entry = [r'''\Format bmpbmp BMP"" "%s"	"%s"	""
 \Format gifgif GIF"" "%s"	"%s"	""
-\Format jpgjpg JPEG   "" "%s"	"%s"	""
+\Format jpg   "jpg, jpeg" JPEG"" "%s"	"%s"	""
 \Format pbmpbm PBM"" "%s"	"%s"	""
 \Format pgmpgm PGM"" "%s"	"%s"	""
 \Format pngpng PNG"" "%s"	"%s"	""
@@ -487,7 +487,7 @@ def checkFormatEntries(dtl_tools):
 path, ie = checkEditorNoRC('a raster image editor', ['gimp-remote', 'gimp'],
 rc_entry = [r'''\Format bmpbmp BMP"" "%s"	"%s"	""
 \Format gifgif GIF"" "%s"	"%s"	""
-\Format jpgjpg JPEG   "" "%s"	"%s"	""
+\Format jpg   "jpg, jpeg" JPEG"" "%s"	"%s"	""
 \Format pbmpbm PBM"" "%s"	"%s"	""
 \Format pgmpgm PGM"" "%s"	"%s"	""
 \Format pngpng PNG"" "%s"	"%s"	""
@@ -497,7 +497,7 @@ def checkFormatEntries(dtl_tools):
 \Format xpmxpm XPM"" "%s"	"%s"	""'''])
 addToRC(r'''\Format bmpbmp BMP"" "%s"	"%s"	""
 \Format gifgif GIF"" "%s"	"%s"	""
-\Format jpgjpg JPEG   "" "%s"	"%s"	""
+\Format jpg   "jpg, jpeg" JPEG"" "%s"	"%s"	""
 \Format pbmpbm PBM"" "%s"	"%s"	""
 \Format pgmpgm PGM"" "%s"	"%s"	""
 \Format pngpng PNG"" "%s"	"%s"	""
@@ -571,7 +571,7 @@ def checkFormatEntries(dtl_tools):
 addToRC(r'\Format dvi2   dvi DraftDVI   ""	""	""	"vector"')
 #
 checkViewer('an HTML previewer', ['firefox', 'mozilla file://$$p$$i', 'netscape'],
-rc_entry = [r'\Format html   htmlHTML   H  "%%"	""	"document,menu=export"'])
+rc_entry = [r'\Format html  "html, htm" HTMLH  "%%"	""	"document,menu=export"'])
 #
 checkViewerEditor('Noteedit', ['noteedit'],
 rc_entry = [r'\Format noteedit   not Noteedit   "" "%%"	"%%"	"vector"'])
@@ -605,7 +605,7 @@ def checkFormatEntries(dtl_tools):
 \Format pstex  pstex_t PSTEX  "" ""	""	""
 \Format wmfwmf"Windows Metafile"  "" ""	""	"vector"
 \Format emfemf"Enhanced Metafile" "" ""	""	"vector"
-\Format wordhtml   html   "HTML (MS Word)""" "" ""	"document"
+\Format wordhtml  "html, htm" "HTML (MS Word)""" "" ""	"document"
 ''')
 
 
diff --git a/lib/scripts/prefs2prefs_prefs.py b/lib/scripts/prefs2prefs_prefs.py
index 7a2cdd6..47ec155 100644
--- a/lib/scripts/prefs2prefs_prefs.py
+++ b/lib/scripts/prefs2prefs_prefs.py
@@ -108,4 +108,5 @@ conversions = [
 		language_use_babel,
 		language_package
 	] # end conversions for format 0
+	,[]
 ]
diff --git a/src/Format.cpp b/src/Format.cpp
index cd2d238..c7bd65f 100644
--- a/src/Format.cpp
+++ b/src/Format.cpp
@@ -69,6 +69,7 @@ public:
 		: extension_(extension) {}
 	bool operator()(Format const & f) const
 	{
+		// FIXME: loop through f.extensions()
 		return f.extension() == extension_;
 	}
 private:
@@ -90,9 +91,14 @@ bool operator<(Format const & a, Format const & b)
 Format::Format(string const & n, string const & e, string const & p,
 	   string const & s, string const & v, string const & ed,
 	   int flags)
-	: name_(n), extension_(e), prettyname_(p), shortcut_(s), viewer_(v),
+	: name_(n), extensions_(e), prettyname_(p), shortcut_(s), viewer_(v),
 	  editor_(ed), flags_(flags)
-{}
+{
+	string e1;
+	split(e, e1, ',');
+	extension_ = e1;
+	extensions_ = e;
+}
 
 
 bool Format::dummy() const
@@ -115,6 +121,15 @@ string const Format::parentFormat() const
 }
 
 
+void Format::setExtensions(string const & e)
+{
+	string e1;
+	split(e, e1, ',');
+	extension_ = e1;
+	extensions_ = e;
+}
+
+
 // This method should return a reference, and throw an exception
 // if the format named name cannot be found (Lgb)
 Format const * Formats::getFormat(string const & name) const
@@ -207,7 +222,7 @@ void Formats::add(string const & name)
 }
 
 
-void

Re: [patch] allow to assign several extensions to a file format


On 05/09/2011 11:33 PM, Julien Rioux wrote:

loop through f.extensions()


Forgot to mention, as this is a preliminary patch, I still have to 
implement looping through extensions, but everything else works.


--
Julien

Re: lyx@fb ?


Il 05/09/2011 08:09, Vincent van Ravesteijn ha scritto:

Op 5-9-2011 1:37, Tommaso Cucinotta schreef:

  http://www.facebook.com/pages/LyX/166594390068533
  http://www.facebook.com/pages/LyX/112847072061085?sk=info
  http://www.facebook.com/group.php?gid=8353382319=wall


I'm pretty sure no one of us knows anything about these pages.

Someone wants to step up to create order in the chaos ?


among the various ones, the only one that seems to have gained some 
users is:


  http://www.facebook.com/group.php?gid=8353382319
  (134 members, against around 10 for the others)

with explicit references to the official lyx webpage and e-mail 
archives, created by Michael Reed


  http://lyx.475766.n2.nabble.com/LyX-facebook-group-td478290.html

According to this last message, there used to be also some pro-lyx & 
anti-M$ group, but I couldn't find it.


The only reason I'm asking is that, if anyone of these groups deserves 
to be considered an "official" source of information, then it might be 
appropriate:

-) to advertise new releases and other related news about LyX also there
-) to monitor from time to time discussions occurring on the 
corresponding "wall".


FB seems to be a promising communication media, and I wouldn't be 
surprised if it helped to get people interested in the tool.


Bye,

T.

Re: LyX 1.6.10 compilation problem in Fedora 15 - and one solution?

On 09/05/2011 08:26 PM, andre duarte bueno wrote:
> Hy
> whem I try do compile LyX 1.6.10
> in my fedora 15; X86_64, g++ (GCC) 4.6.0 20110603 (Red Hat 4.6.0-10)

Is there any specific reason for not to use lyx 2.0 from the distribution?

Regards,

-- 
José Matos

Re: LyX 2.0.1 Released

2011-09-05 Thread Liviu Andronic

On Mon, Sep 5, 2011 at 6:03 PM, Richard Heck  wrote:
> * BUILD/INSTALLATION
>
> - Using pkgconfig to configure hunspell (hunspell 1.3 was not correctly
>  recognized).
>
> - Using explicit header and library detection as fallback to configure
>  hunspell in case pkgconfig is missing in build environment.
>
As with 2.0.0, I cannot get LyX to work with hunspell 1.2.8 on Xubuntu
10.04 Lucid (x64), even though ./configure ends up with:
Configuration
  Host type:x86_64-unknown-linux-gnu
  Special build flags:  build=release use-aspell use-enchant
use-hunspell
[..]

Am I doing something wrong or is there some incompatibility? LyX works
fine with hunspell via Enchant. Also, 'pkg-config' v0.22 is installed.

Regards
Liviu

Re: [patch] allow to assign several extensions to a file format


Il 05/09/2011 23:33, Julien Rioux ha scritto:

log:
 Allow to assign several extension to a given file format (#4798).
 Additionnal extensions are separated by commas (,). Spaces are
 ignored. Preference (lyxrc) file format incremented to 2.


For example, a LibreOffice/OpenOffice/StarOffice drawing (.odg, .sxd) 
would be one single format with 2 extensions ?


T.

Re: [patch] allow to assign several extensions to a file format


On 06/09/2011 12:55 AM, Tommaso Cucinotta wrote:

Il 05/09/2011 23:33, Julien Rioux ha scritto:

log:
Allow to assign several extension to a given file format (#4798).
Additionnal extensions are separated by commas (,). Spaces are
ignored. Preference (lyxrc) file format incremented to 2.


For example, a LibreOffice/OpenOffice/StarOffice drawing (.odg, .sxd)
would be one single format with 2 extensions ?

T.



I don't use those formats, but if that makes sense, why not. In the 
patch I just treat .html, .htm as one and .jpg, .jpeg as another. These 
formats were the two reported as bugs.


--
Julien

LyX & odg drawings


Hi,

[... extracted from the Image Lifecycle Patch ...]

the attached patch adds the OpenOffice drawing format (.odg). With it 
you can:


-) include in LyX OpenOffice drawings
-) preview them on the screen
-) view them in the final .ps/.pdf output
-) edit them externally via libreoffice, ooffice or soffice.

Notes:
1) It includes a trick to avoid detecting .odg as a zipped format, 
unfortunately

I had to replicate it both in Format.cpp and in FileName.cpp.
Any hint on how to possible make the design better ?

Would adding a method

  static bool FileName::isZippedExtension(string const );

and using it from within Format.cpp be better ?

2) I guess sxd can be handled once the patch for multi-extension formats 
is cooked.


Thanks,

T.

Index: src/support/FileName.cpp
===
--- src/support/FileName.cpp	(revisione 39605)
+++ src/support/FileName.cpp	(copia locale)
@@ -950,6 +950,13 @@
 
 bool FileName::isZippedFile() const
 {
+	string const & ex = extension();
+	bool zipped_format = (ex == "odg" || ex == "sxd"
+		|| ex == "odt" || ex == "sxw" || ex == "docx"
+		|| ex == "ods" || ex == "sxc" || ex == "xlsx"
+		|| ex == "gnumeric" || ex == "dia");
+	if (zipped_format)
+		return false;
 	string const type = guessFormatFromContents();
 	return contains("gzip zip compress", type) && !type.empty();
 }
Index: src/Format.cpp
===
--- src/Format.cpp	(revisione 39605)
+++ src/Format.cpp	(copia locale)
@@ -129,15 +129,25 @@
 }
 
 
+/// For a zipped format, try the filename extension first, then the contents
+/// (otherwise it is always guessed as zip and we're in trouble)
 string Formats::getFormatFromFile(FileName const & filename) const
 {
 	if (filename.empty())
 		return string();
 
-	string const format = filename.guessFormatFromContents();
-	if (!format.empty())
-		return format;
+	string const & ex = filename.extension();
+	bool zipped_format = (ex == "odg" || ex == "sxd"
+		|| ex == "odt" || ex == "sxw" || ex == "docx"
+		|| ex == "ods" || ex == "sxc" || ex == "xlsx"
+		|| ex == "gnumeric" || ex == "dia");
 
+	if (!zipped_format) {
+		string const format = filename.guessFormatFromContents();
+		if (!format.empty())
+			return format;
+	}
+
 	// try to find a format from the file extension.
 	string const ext = getExtension(filename.absFileName());
 	if (!ext.empty()) {
@@ -152,6 +162,12 @@
 			return cit->name();
 		}
 	}
+
+	if (zipped_format) {
+		string const format = filename.guessFormatFromContents();
+		if (!format.empty())
+			return format;
+	}
 	return string();
 }
 
Index: lib/scripts/libreoffice2ps.sh
===
--- lib/scripts/libreoffice2ps.sh	(revisione 0)
+++ lib/scripts/libreoffice2ps.sh	(revisione 0)
@@ -0,0 +1,14 @@
+#!/bin/bash
+
+tmpdir=$(mktemp -d)
+fname=$(basename "$1")
+for sfx in odg odt ods odp; do
+if echo $fname | grep "\\.${sfx}\$"; then
+	fname=${fname%%.$sfx}
+	break;
+fi;
+done
+
+libreoffice -nologo -convert-to eps -outdir $tmpdir $1
+mv "$tmpdir/$fname.eps" "$2"
+rmdir $tmpdir

ProprietÃ  modificate su: lib/scripts/libreoffice2ps.sh
___
Added: svn:executable
   + *

Index: lib/configure.py
===
--- lib/configure.py	(revisione 39605)
+++ lib/configure.py	(copia locale)
@@ -464,6 +464,9 @@
 checkViewerEditor('a Dia viewer and editor', ['dia'],
 rc_entry = [r'\Format diadia DIA"" "%%"	"%%"	"vector"'])
 #
+checkProg('an OpenOffice drawing viewer and editor', ['libreoffice', 'ooffice', 'soffice'],
+rc_entry = [r'\Format odgodg ODG"" "%%"	"%%"	"vector"'])
+#
 checkViewerEditor('a Grace viewer and editor', ['xmgrace'],
 rc_entry = [r'\Format agragr Grace  "" "%%"	"%%"	"vector"'])
 #
@@ -827,6 +830,10 @@
 \converter xls latex "ssconvert --export-type=Gnumeric_html:latex $$i $$o" ""''',
 ''])
 
+# odg to ps
+checkProg('an OpenOffice drawing -> ps converter', ['libreoffice'],
+   rc_entry = [ r'\converter odg ps "$$s/scripts/libreoffice2ps.sh $$i $$o" ""'])
+
 path, lilypond = checkProg('a LilyPond -> EPS/PDF/PNG converter', ['lilypond'])
 if (lilypond != ''):
 version_string = cmdOutput("lilypond --version")
Index: lib/Makefile.am
===
--- lib/Makefile.am	(revisione 39605)
+++ lib/Makefile.am	(copia locale)
@@ -1512,7 +1512,8 @@
 	scripts/prefs2prefs_lfuns.py \
 	scripts/prefs2prefs_prefs.py \
 	scripts/tex_copy.py \
-	scripts/TeXFiles.py
+	scripts/TeXFiles.py \
+	scripts/libreoffice2ps.sh
 
 templatesdir = $(pkgdatadir)/templates
 dist_templates_DATA = \
@@ -1578,7 +1579,7 @@
 	templates/springer/svmult_part.lyx \

Re: [patch] allow to assign several extensions to a file format

On 09/05/2011 05:33 PM, Julien Rioux wrote:
> log:
>  Allow to assign several extension to a given file format (#4798).
>  Additionnal extensions are separated by commas (,). Spaces are
>  ignored. Preference (lyxrc) file format incremented to 2.
>
Thanks for taking care of this.

>  A lot of the diff is renaming extension -> extensions
>
> See issues
> http://www.lyx.org/trac/ticket/4798
> http://www.lyx.org/trac/ticket/6340
>
> Comments welcome!
>
If you make the extensions_ member a vector or list, it
will make looping and such a lot easier. You might then just have:
 string extension() { return extensions_[0]; }
which I guess is supposed to be the default extension? You're basically
then just caching the result of the split call that turns up from time
to time.

Richard

Re: LyX & odg drawings

On 09/05/2011 07:51 PM, Tommaso Cucinotta wrote:
> Hi,
>
> [... extracted from the Image Lifecycle Patch ...]
>
> the attached patch adds the OpenOffice drawing format (.odg). With it
> you can:
>
> -) include in LyX OpenOffice drawings
> -) preview them on the screen
> -) view them in the final .ps/.pdf output
> -) edit them externally via libreoffice, ooffice or soffice.
>
> Notes:
> 1) It includes a trick to avoid detecting .odg as a zipped format,
> unfortunately
> I had to replicate it both in Format.cpp and in FileName.cpp.
> Any hint on how to possible make the design better ?
> z
> Would adding a method
>
>   static bool FileName::isZippedExtension(string const );
>
> and using it from within Format.cpp be better ?
>
Just have a standalone function:
bool isZippedFormat(string ext)
and call that from both FileName and Format. I guess it would make sense
in support/filetools.{h,cpp}. Though I wonder if there is a better way
than checking extensions

> Index: src/support/FileName.cpp
> ===
> --- src/support/FileName.cpp  (revisione 39605)
> +++ src/support/FileName.cpp  (copia locale)
> @@ -950,6 +950,13 @@
>  
>  bool FileName::isZippedFile() const
>  {
> + string const & ex = extension();
> + bool zipped_format = (ex == "odg" || ex == "sxd"
> + || ex == "odt" || ex == "sxw" || ex == "docx"
> + || ex == "ods" || ex == "sxc" || ex == "xlsx"
> + || ex == "gnumeric" || ex == "dia");
> + if (zipped_format)
> + return false;
>
Shouldn't that be "return true"?

rh

Re: LyX 2.0.1 Sources Available


Am 05.09.2011 19:54, schrieb Pavel Sanda:

Uwe Stöhr wrote:

Works fine and a Win installer is ready (the merged one). I'll leave the
installer for LyX 2.0.1 to Joost because the merged installer is not yet
able to install LyX if you install it without admin privileges (due to a
Imagemagick issue).


is this regression wrt 2.0.0 installer? if not why wait...


Yes, Joost's installer is able to install LyX without admin priviledges. To achieve this, he use 
special compiled version of ImageMagick. This is not a suitable solution because we should rely on 
official releases. Moreover ImageMagick releases very often and our goal was that more than one 
developer is able to build the Win installer. Therefore we should concentrate on the LyX stuff and 
use the official releases.
The next time I find time, I'll work on the remaining ImageMagick issue. The problem is that 
ImageMagick requires a registry entry in HKLM but this can only be set with admin priviledges.


Besides this, the new installer was not yet tested by users.

regards Uwe

Re: LyX 2.0.1 Sources Available


Am 05.09.2011 20:01, schrieb Vincent van Ravesteijn:


For these people we have the standard installer. The bundle installer is 
especially designed for
new installations and therefore includes MiKTeX and JabRef (is optional). So 
the standard
installer will not bother the user and is as small as possible to update 
existing LyX
installations. This variant therefore expects an installed MiKTeX. If no MiKTeX 
or TeXLive is
found, it will throw a warning that the bundle installer should be used.


Why don't we download it anymore then ?


Then we would have the same trouble as we have now in the installer for 2.0.0 with broken download 
links and we need more complicated installer code.
Besides this there are from time to time bugs in MiKTeX releases that break LaTeX packages. By 
including MiKTeX we assure that we are shipping a tested MiKTeX build.



We did this as long as I remember having Windows installers.


Never with my installer. I provide the solution with the two installer variants since I'm involved 
to LyX and I never had complaints that new users used the standard installer without having LaTeX 
installed.


regards Uwe

Re: LyX 2.0.1 Sources Available

Am 05.09.2011 20:43, schrieb Vincent van Ravesteijn:

I tried the merged installer.

Many thanks!

Here is some feedback:

1. The icon is not the nicest one. We should have a transparent one.

What icon do you mean? The installer uses the icon of the lyx.exe file. If you want another icon, we
must change the build code to link it to the lyx.exe.

2. I agree with Joost that the dialog to choose the start menu folder is not
necessary anymore. It
is not useful having only a single item in a map.

People requested to choose the start menu folder and almost all installers I know provide this
feature. There is also only one programs on my PC (Inkscape) that is not following the Windows
guideline to have its own folder in the start menu.
This is also necessary to distinguish between different LyX versions. For example I have LyX 1.4.5,
1.5.7, 1.6.10. 2.0.1 and 2.1.0svn installed. Without a folder for each program, I would have 5
entries with the same name "LyX".
(Initially in the LyX folder there was also the link to uninstall LyX but Joost were opposed to
this, so I dropped it.)

3. The start menu folder is called "LyX 2.0.1". I don't like the version number
in the name, there
is no need for it.

4. In the MikTeX page is a spelling error in the dutch translation: LaTeX
softare. Also in the
MikTeX update page.

Thanks, fixed now.

5. Why do we install the MikTeX packages without asking the user for permission?

This is one of the key features of the installer!

You can reset the settings any time.

6. Joost had a reason to not allow to start the application from the installer.
Isn't this a problem
now anymore ?

I don't know what you are referring to.

7. Joost's LyX2.0 installer installed the folder AppData/Roaming/LyX2.0. Can we
please have the same
directory for newer installers instead of lyx20 ?

What do you mean? LyX's settings folder is on my PC
C:\Documents and Settings\Uwe\Application Data\lyx20

All LyX 2.0.x releases share the same folder. The 1.6.x series uses the folder "lyx16". What is
wrong with that?
I don't know why Joost's installer creates a folder "LyX2.0" instead of "lyx20". For me this folder
is created automatically when LyX.exe is called the first time. So he must be using a special
compilation setting.

9. I found the following faulty registry entries. Where do they come from ?

HKEY_CLASSES_ROOT\LyX.Document\Shell\open\command
"C:\Program Files (x86)\LyX 2.0.1\bin\LyXLauncher.exe" "%1"

HKEY_CLASSES_ROOT\LyX.Document\DefaultIcon
C:\Program Files (x86)\LyX 2.0.1\bin\LyXLauncher.exe,0

HKEY_CLASSES_ROOT\Applications
C:\Program Files (x86)\LyX 2.0.1\imagemagick\convert.exe $

This is ImageMagick's converter executable. This entry is set by ImageMagick.

10. Now, I have both LyX2.0.0 and LyX2.0.1 installed on my pc ? Shouldn't we
overwrite the previous
version ?

No. See the reasons above.

thanks and regards
Uwe

Re: first step of merging the Win installers