Re: Double dash in Lyx 2.2.1 is not printed correctly

2016-09-10 Thread Georg Baum
Danko Georgiev wrote:

> Dear Scott,
> 
> If you try typesetting time periods, in old LyX you could just type
> "2014--2016". When you print PDF you will read 2014[en-dash]2016. In
> other words, old Lyx printed the double dash as if it Latex code.

Yes. This behaviour caused lots of trouble (e.g. 
http://www.lyx.org/trac/ticket/3647, http://www.lyx.org/trac/ticket/8561) 
and has been changed in version 2.2. Now a hyphen that is stored in a LyX 
document is always typeset as a hyphen, even for two or more consecutive 
hyphens.

> Now in version 2.2.1 I tried to type 2014--2016 but Lyx automatically
> overwrites this double dash with en-dash. This is simply WRONG thing to
> do. en-dash is a special character that I do not want in my code!

This conversion was implemented in order to mimic the 2.1 behaviour. In 2.1 
if you enter two consecutive hyphens, you get an en-dash in the output. In 
2.2, if you enter two consecutive hyphens, you get an en-dash in the output 
as well. The only difference is that in 2.2, the display on screen and the 
contents in the .lyx file are also copnsistent with the output.

> To make it clear: imagine that I want to type $\mu$ and LyX starts to
> convert this to unicode character mu U+039C,  or whatever

You can always enter - - and then delete the space if you really need two 
consecutive hyphens.

> Lyx now behaves as MS Word instead as a LaTeX typesetter. I don't think
> the solution is to revert back my LyX to 2.1

We could of course change the automatic conversion of consecutive hyphens on 
input if there is popular demand. That would make entering of en-dashes and 
em-dashes more difficult, and currently I believe that the current behaviour 
is convenient for most users.

> On 07-Sep-16 19:06, Scott Kostyshak wrote:
>> On Wed, Sep 07, 2016 at 07:02:58PM +0300, Danko Georgiev wrote:
>>> Hello,
>>>
>>> I have just updated to the newest LyX 2.2.1. and immediately got a
>>> problem with automatic conversion of double dashes -- to en-dash in a
>>> manuscript written with Lyx 2.1. This en-dash replacement resulted in
>>> error message in index sorting when compiling PDF.

If a document that produces PDF output does not produce the same PDF output 
anymore after loading it in 2.2 then this is a bug. Please file it at 
http://www.lyx.org/trac/wiki/BugTrackerHome and include a test case in 2.1 
format.


Georg




Re: LyX 2.2.1 is not running

2016-07-26 Thread Georg Baum
Richard Heck wrote:

> On 07/26/2016 01:09 PM, Scott Kostyshak wrote:
>> On Tue, Jul 26, 2016 at 02:54:36PM +0100, Dr Eberhard Lisse wrote:
>>> But from another thread, have you tried to download and install:
>>>
>>> https://www.microsoft.com/en-US/download/details.aspx?id=48145
>> The above worked for another LyX user who had the same problem [1].
> 
> Uwe, is this an issue with the package we provide? Or is it independent?

It is an installer issue. The LyX installer does not call the official MSVC 
redistributables installer, but includes the MSVC dlls instead. This might 
work on some machines and might not work on some others (the official 
installer does more than just copying dlls to some place).


Georg



Re: forthcoming installation of Lyx 2.2

2016-06-19 Thread Georg Baum
Michael Berger wrote:

> Hi all,
> I have Mageia5 / KDE and just succeeded to install texlive2016.
> The next challenge is to install Lyx 2.2 from http://www.lyx.org/Download
> 
> i am addressing those of you who already successfully did this.
> 
> Is there anything to be observed/prepared/considered prior to starting
> the installation?

Since there is no binary package for Mageia5 you will need to compile from 
source. This is easy, the file INSTALL in the LyX source package lists some 
instructions. However, it might be a bit more difficult to find out how 
exactly the prerequisite packages are called on Mageia5, e.g. the 
development package for qt. If a prerequiste is missing then the configure 
script will tell you, and if you don't find the correct package to install 
then ask on the list, probably someone will know how to find the package 
from the configure error message.


Georg




Re: Missing icons after upgrading to LyX 2.2.0

2016-06-04 Thread Georg Baum
John Kane wrote:

> john@john-K53U:~$  apt-get -f install
> E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission
> denied)
> E: Unable to lock the administration directory (/var/lib/dpkg/), are you
> root?
> john@john-K53U:~$  apt-get -f install lyx
> E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission
> denied)
> E: Unable to lock the administration directory (/var/lib/dpkg/), are you
> root?
> john@john-K53U:~$

This happens if at the same time some other package management tool is 
running and holds a lock on the database. Assuming that you don't do that 
yourself, the most likely reason is an automatic 'apt-get update' running in 
the background from cron. You would see the process in the output of

ps -axu | grep root

and usually it would not take long to be finished, so you could try again.


Georg




Re: LyX-related Hiccup when installing system updates

2016-06-02 Thread Georg Baum
Jacob Bishop wrote:

> I am on Linux Mint 17, using the lyx-devel/release ppa. When I tried to
> install the regular system updates today using the update manager, it
> failed with the message,
> 
> E:/var/cache/apt/archives/lyx_2.2.0-1~trusty~ppa3_amd64.deb: trying to
> overwrite '/usr/share/icons/hicolor/scalable/apps/lyx.svg', which is also
> in package lyx-common 2.1.4-1~trusty~ppa1
> 
> I'm not sure I understand what exactly the problem is or was, but I
> resolved the problem by running.

It is a packaging error. lyx.svg should not be in 
lyx_2.2.0-1~trusty~ppa3_amd64.deb, but in lyx-
common_2.2.0-1~trusty~ppa3_amd64.deb. In case I missed something and the 
file was moved on purpose it was not done correctly: In this case the 
package lyx (version 2.2.0) needs to declare a conflict against lyx-common 
(versions older than 2.2.9). Then the package manager knows that the old 
lyx-common needs to be removed before installing thew new lyx.


Georg




Re: Missing icons after upgrading to LyX 2.2.0

2016-06-01 Thread Georg Baum
John Kane wrote:

> I installedl from what I believe is a prepackaged binary from Liviu
> Andronic's  stable PPA
>  which I have used
> before.

Good.

> My installed version of qt is qt4.5 which if I am reading the release
> notes correctly should be okay.

4.5 is really old, and although LyX should work with it in principle it is 
not well tested. Somehow I cannot believe that the ppa contains packages for 
such an old version, but Liviu will know more.


Georg



Re: Missing icons after upgrading to LyX 2.2.0

2016-06-01 Thread Georg Baum
John Kane wrote:

>  I just did an upgrade to LyX 2.2.0 successfully for the most part but my
> menu toolbar has turned to text—there are no icons! See attached
> screenshot. Note that the menu toolbar and the math toolbar are both in
> text. The splash screen icon is there.
> A quick look at usr/share/lyx/ui shows four files, default.ui,
> stdcontex.inc, stdmenus.inc, & stdtoolbars.inc, all of which look okay.
> Unfortunately I have no idea were to look for the actual icons (.svg
> files?).
> Any suggestions would be appreciated
> LyX 2.2.0 Ubuntu 16.04

LyX 2.2.0 requires a qt with SVG support compiled in (as mentioned in 
RELEASE_NOTES). This looks like your qt does not have proper SVG support. 
Which qt version are you using? Did you compile from source or install some 
prepackaged binary?


Georg



Re: lyx2.2.0rc1 and lyx2.2.0 identical?

2016-05-31 Thread Georg Baum
Scott Kostyshak wrote:

> On Tue, May 31, 2016 at 09:10:17AM +0200, Wolfgang Engelmann wrote:
>> 
>> How do I effectively remove the rc1 lyx. I have it and 2.2.0 (myx lyx22)
>> side by side
> 
> You're on Linux right? I'm not sure of the best way to remove it. We
> don't have an uninstall target (i.e. you can't do "make uninstall").

We do (at least with autotools). Simply call

make uninstall

from the rc1 build directory. If installation needed root privileges, then 
this needs root privileges as well.


Georg



Re: Help with math environment translations for LyX

2016-04-04 Thread Georg Baum
febty febriani wrote:

> Dear lyx team
> 
> The translation of some words in  Indonesia is not correct. How to correct
> them? Just write them in this thread?

Yes please do so.


Georg



Re: Help with math environment translations for LyX

2016-04-04 Thread Georg Baum
Helge Hafting wrote:

> The translation of  "List of listings" for Norwegian (nb) seems fine.

Many thanks for the review. The changed translation is in.


Georg



Re: Help with math environment translations for LyX

2016-04-03 Thread Georg Baum
edu Gpl wrote:

> Dearlyx team
> arabic translation is correct.
> 
> regards
> 
> lyx arabic translator

Many thanks for the review, I updated the translation status.


Georg





Re: trouble submitting IEEE conference article

2016-02-10 Thread Georg Baum
Neal Becker wrote:

> Seems pretty messed up.  If I don't check 'use non-tex fonts', and export
> via DVI (LuaTeX), I get a dvi, but no eps graphics.

This is a bug. It would be nice if you could attach a minimal example to the 
report you made.

> Finally, I tried export LaTeX (dviluatex), and THEN I got eps graphics,
> but without mangled names.

This is expected. If you export to LaTeX (any flavour) LyX assumes that you 
want to further edit the files. Thus it does not do any file name magic at 
all, and also keeps subdirectory structure intact. It only ensures that all 
images are present in the needed format for the chosen LaTeX flavour.

If you export to DVI then it assumes that you do not want to move a complete 
directpry structure around when you copy the DVI to some other location. 
Therefore it puts all files into one directory and needs tro make the names 
unique.


Georg






Re: trouble submitting IEEE conference article

2016-02-02 Thread Georg Baum
Neal Becker wrote:

> I'm submitting to IEEE VTC 2016 spring.  Article (written with LyX) is
> accepted (yay).

Congrats!

> 
http://www.ieee.org/conferences_events/conferences/publishing/vtc16spr.html
> says they only accept .dvi, and graphics in .eps, and they want to make
> the
> pdf.  I'm shocked, this is ancient obsolete tech.
>
> So I tried to follow this route, and uploaded a dvi and all graphics
> converted to eps, using pdftops -> pdf2epsi.  No doubt this will hurt the
> quality.

I would recommend to use LyX to do all these conversions. Exporting to DVI 
in LyX should produce the DVI file along with all needed .eps images. LyX 
does also know how to produce .eps images without quality loss (it uses 
pdftops with some flags, look at the "PDF (Graphics)" => EPS converter). 
Does viewing the DVI in LyX work?

> But conversion fails, I receive an email just saying
> The DVI source file you uploaded as a submission to the File Submission
> site failed to produce a postscript file.
> 
> If I try locally, I get:
> dvipdf ascma-paper.dvi ascma-paper.junk.pdf
> kpathsea:make_tex: Invalid fontname `"file:lmroman17-regular:script=latn;
> +trep;+tlig;"', contains '"'
> dvips: Font "file:lmroman17-regular:script=latn;+trep;+tlig;" not found;
> using cmr10
> dvips: Design size mismatch in font "file:lmroman17-regular:script=latn;
> +trep;+tlig;"
> dvips: ! invalid char 8211 from font "file:lmroman17-regular:script=latn;
> +trep;+tlig;"
> 
> Any ideas here?  I'm emailing them to see what can be done, but maybe you
> guys have suggestions?

Since they want to produce PS I would concentrate on the DVI => PS route, 
not DVI => PDF. You can narrow down the problem by previewing DVI or 
Postscript (or "PDF (dvipdfm)" if you want to stick to pdf). If this works, 
then something goes wrong with your conversion procedure. If it does not, 
then either the IEEE class needs some stuff you do not have installed, or 
something is wrong with your document.


Georg



Re: trouble submitting IEEE conference article

2016-02-02 Thread Georg Baum
Neal Becker wrote:

> Thanks!  It does appear to work to export to DVI (LuaTeX) _after_ I
> uncheck Document/settings/fonts use non-tex fonts.

You mean after you uncheck or after you check the button? It is supposed to 
work like this:

use non-tex fonts checked => DVI (LuaTeX) works, DVI does not work
use non-tex fonts unchecked => DVI works, DVI (LuaTeX) might work

I believe that the error handling in this area has been improved in the 
upcoming LyX 2.2.

> Yes, good EPS were created.  Unfortunately, the names of the EPS files
> were mangled, and I think those names don't match those in the DVI file,
> so I needed to manually create a bunch of symlinks from the names used in
> the dvi file to the mangled names, e.g.,
> 
> 0_home_nbecker_scma-unframed_frame_format-cropped.eps -> frame_format-
> cropped.eps
> 
> The whole process would've been automated nicely if not for this.

The files are referenced using the mangled names in the DVI (at least on my 
machine). If the DVI does not reference the mangled files then this would be 
a bug => please report at http://www.lyx.org/trac/wiki/BugTrackerHome in 
that case.

If you want a DVI which refernces images without mangled names you need to 
produce it manually: Export to "LaTeX (plain)", which will produce a .tex 
file + all .eps files (unmangled). Then run latex, bibtex and other aux 
programs as needed to produce the DVI.


Georg




Re: Aliasing, xyling, ps2pdf

2016-01-08 Thread Georg Baum
Guenter Milde wrote:

> If this is true, LyX configuration should choose "pdftops" if both tools
> are installed.
> 
> However, on my system this seems not to be the case:
> 
> * I have both, pdf2ps and pdftops (via package dependencies)
> 
> * still, the LyX-determined converter for 2.2dev is
>   pdf2ps $$i $$o
>   
> Can someone confirm/refute this finding?

Yes, the detection order in lib/configure.py is wrong.

> Should I file a bug report?

You couldd as well fix it directly in configure.py.


Georg




Re: Aliasing, xyling, ps2pdf

2016-01-07 Thread Georg Baum
Maria Gouskova wrote:

> On Wed, Jan 6, 2016 at 5:14 PM, Georg Baum
> <georg.b...@post.rwth-aachen.de> wrote:
>> Maria Gouskova wrote:
>>
>>> This is Mac OS 10.8.5, LyX 2.1.4. I suspect I need to define a
>>> converter in Preferences/File handling, but am not having much luck
>>> finding the answer anywhere.
>>
>> Correct. If pdftops is in the path, then LyX should automatically define
>> a converter
>>
>> pdftops -eps -f 1 -l 1 $$i $$o
>>
>> for conversion from PDF (Graphics) to EPS. This one works fine for me
>> with your test file. Which converter do you have configured for PDF
>> (Graphics) to EPS conversion?
>>
> 
> I didn't have one defined by default for PDF(graphics) at all. When I
> added a PDF(graphics) to EPS converter, it defaulted to:
> 
> python -tt $$s/lyx2lyx/lyx2lyx -c big5 $$i > $$o
> 
> Which still produces an aliased PDF.
> 
> I tried defining it your way, but it seems that pdftops is not
> available on my setup. LyX throws up a non-specific error.

Then you need to install pdftops and either put the executable in a 
directory which is listed in the PATH environment variable, or define the 
converter using the absolute path to the installed pdftops (e.g. if the 
executable is located in /opt/xpdf/bin/pdftops, the converter would read

/opt/xpdf/bin/pdftops -eps -f 1 -l 1 $$i $$o

). You can download a binary from http://www.foolabs.com/xpdf/download.html, 
but since I am not a Mac expert I do not know if there are better ways to 
install it.

> I can't debug this properly since I am away from my other machine,
> which has Mac OS 10.9x and (as far as I recall) does not have this
> problem. Could be a MacTeX version difference? Or just OS-specific?

Probably not MaCTeX speicfic. My guess would be that on the other machine 
either pdftops or ps2eps (from ghostscript) is installed and found by LyX. 
BTW, pdftops is better than pdf2ps according to 
http://stefaanlippens.net/pdf2ps_vs_pdftops and also my own experience.


Georg



Re: Nomenclature prints 'Seite' instead of 'page'

2016-01-07 Thread Georg Baum
Guenter Milde wrote:

> It is "Tools>Preferences>Language Settings>Language>Set languages
> globally" which controls whether the language options are passed as
> global options to the document or directly to babel.

Sorry, I was too tired yesterday, and did not recognize the text in my 
german UI.

> Generally, it is good to have the options globally, so that other packages
> can pick this up.
> 
> In this document, however, the indexing is confused somehow to use one of
> the secondary languages (given before "english").

Yes. It is a bug in nomencl.sty: It does not process global language options 
in the same (unintuitive) order as babel. The first language wins for 
nomencl.sty. I fear there is not much LyX can do, except looking for a 
better alternative for nomencl (it seems to be unmaintained).

> Maybe we need a document specific setting for this.
> (But see also my other post exploring the issue.)

I think so. In general, any lyxrc setting that changes how documents are 
exported to .tex is bad IMHO, since this makes documents depend on the 
installation. The lyxrc setting should be replacved by a document specific 
setting, and the default for this setting would then be determined by the 
template for new documents.


Georg



Re: Aliasing, xyling, ps2pdf

2016-01-06 Thread Georg Baum
Maria Gouskova wrote:

> This is Mac OS 10.8.5, LyX 2.1.4. I suspect I need to define a
> converter in Preferences/File handling, but am not having much luck
> finding the answer anywhere.

Correct. If pdftops is in the path, then LyX should automatically define a 
converter

pdftops -eps -f 1 -l 1 $$i $$o

for conversion from PDF (Graphics) to EPS. This one works fine for me with 
your test file. Which converter do you have configured for PDF (Graphics) to 
EPS conversion?


Georg




Re: Nomenclature prints 'Seite' instead of 'page'

2016-01-06 Thread Georg Baum
Michael Berger wrote:

> Hi Wolfgang, Robert, Kornel,
> thanks for your contributions.
> I just want to inform that in my case only one thing produces correct
> results and that is deactivating the global language settings. Here it
> does not matter whether or not the blue underlines are there or not.

What does "deactivating global language settings" mean? I am not aware of 
any global language setting that can be activated or decativated. Please 
tell us exactly which setting you change in Deocument->Settings->Language 
(or in Tools->Preferences)


Georg




Re: Render inkscape text with latex

2015-12-03 Thread Georg Baum
Rajil Saraswat wrote:

> Hello,
> 
> I want the text used in svg images to be rendered using latex.
> Inkscape provides instructions at
> http://wiki.inkscape.org/wiki/index.php/LaTeX on how to do this with
> Lyx. However this uses ERT and one loses the capability of seeing
> previews within Lyx.
> 
> Is it possible to modify the SVG convertor with lyx to automatically
> carry out the steps given on the inkscape wiki mentioned above?

Yes. LyX has so-called external templates, they are documented in the 
Customization Manual. Unfortunately they are not so easy to understand if 
one is not used to theem, but there is already a template which does the 
equivalent of what you want for Xfig figures.

You can define an inkscape template without modifying the LyX source code. 
If you do, it would be nice if you could contribute it. If you do not want 
to have ago yourself, please file an enhancement request at 
http://www.lyx.org/trac/wiki/BugTrackerHome (if none exists alreeady).


Georg




Re: Display SVG graphics in Lyx

2015-09-20 Thread Georg Baum
Rainer M Krug wrote:

> So this is a bug in qt (Linux (QT version ?) and OS X (Qt 4 version:
> 4.8.6)) - I have no idea about qt and it would not be possible for me to
> provide a bug report in a useful way.

I can confirm the bug with qt 4.8.6 and 5.3.2 on linux.

In order to report a qt bug it would be needed to write a small reproducer 
(starting from the code in src/frontends/qt4/GuiImage.cpp). As a preparation 
for that it would be nice if somebody could report it at 
http://www.lyx.org/trac/wiki/BugTrackerHome first (including the test case), 
then a LyX developer might report the qt problem later.


Georg




Re: Display SVG graphics in Lyx

2015-09-19 Thread Georg Baum
Rainer M Krug wrote:

> Hm - the output now works, but the preview still does not work. Which
> toolchain is actually used to create the preview?

Qt is used directly to display images in a number of formats, including svg. 
Therefore it would be a qt bug if the preview of an svg image is not 
displayed correctly.


Georg



Re: emf conversion on mac

2015-08-24 Thread Georg Baum
Rainer M Krug wrote:

 You have two options:
 
 1) use e.g. Irfanview (http://www.irfanview.com) in wine / PlayOnMac
(https://www.playonmac.com/) to convert the images to a different
format. Irfan view works very nicely on a mac.
 
 2) if you find a commandline tool for Mac (I didn't find one - please
keep us posted if you find one) and define your own copier in LyX to
convert the emf files.

3) Use our own metafile2eps with wine as documented in 
http://wiki.lyx.org/Windows/MetafileToEPSConverter. LyX will do eps-pdf 
automatically. The documentation is for linux, but I see no reason why it 
should not be applicable to OS X as well.

4) Find out how to use libreoffice on the command line to convert from emf 
to eps or pdf: libreoffice can read emf files even on non-windows platforms, 
and it is scriptable, so this should be possible in theory, but I have no 
idea whether it really works.


Georg




Re: emf conversion on mac

2015-08-24 Thread Georg Baum
Rainer M Krug wrote:

> You have two options:
> 
> 1) use e.g. Irfanview (http://www.irfanview.com) in wine / PlayOnMac
>(https://www.playonmac.com/) to convert the images to a different
>format. Irfan view works very nicely on a mac.
> 
> 2) if you find a commandline tool for Mac (I didn't find one - please
>keep us posted if you find one) and define your own copier in LyX to
>convert the emf files.

3) Use our own metafile2eps with wine as documented in 
http://wiki.lyx.org/Windows/MetafileToEPSConverter. LyX will do eps->pdf 
automatically. The documentation is for linux, but I see no reason why it 
should not be applicable to OS X as well.

4) Find out how to use libreoffice on the command line to convert from emf 
to eps or pdf: libreoffice can read emf files even on non-windows platforms, 
and it is scriptable, so this should be possible in theory, but I have no 
idea whether it really works.


Georg




Re: Lyx to Latex to Lyx

2015-08-15 Thread Georg Baum
Hal Kierstead wrote:

 First of all, tex2lyx already comes close to making a good LyX file.  The
 main problem is that there always seem to be a handful or errors that must
 be fixed before the file will run.  For some reason the program cannot
 handle options like \begin{thm}[Main Lemma], but also other options.  It
 also seems that comments in the Latex file can sometimes produce errors. 

Please report bugs for these errors at 
http://www.lyx.org/trac/wiki/BugTrackerHome and include an example .tex file 
that shows the bug. These problems are sometimes easy to fix, the only thing 
we need is to be aware of them and a test case.

 A huge annoyance is that theorems, etc. are displayed in ERT.

The problem with theorems is that they are only recognized if the preamble 
is the same that would be used by LyX. Otherwise it cannot be guaranteed 
that the PDF output will be the same as in the original document. If the 
origional .tex file was produced by LyX, and your co-author did not define a 
new theorem style, but only changed an existing theorem or added a new one, 
then the theorems should be imported correctrly by tex2lyx. If this is not 
the case then please file  bug report.

 I understand that for arbitrary LaTex files some of these issues maybe
 very complicated or impossible, but what I am asking for does not involve
 arbitrary files.  Let’s take an easy case.  Suppose my coauthor only makes
 changes between \begin{document} and \end{document} of the LaTex file, and
 does not use any new constructs.  Shouldn’t it be possible, perhaps with a
 helper file that records settings and any other special issues, to make a
 good LyX version?  Or even easier, shouldn’t I be able to export a Latex
 file and then without changing it, import it and get the same LyX file
 back.  Yes, I know there is no reason to do this, but it is a benchmark.

Yes, this should be possible (with one limitation): There are some 
constructs in LyX that cannot be expressed in LaTeX or are not exported 
(e.g. Notes). We discussed in the past how to get rid of this limitation, 
but, but we do not have a consensus on a good soluition yet. Again, if have 
documents that do not re-import correctly, please file a bug.


Georg



Re: Lyx to Latex to Lyx

2015-08-15 Thread Georg Baum
Hal Kierstead wrote:

> First of all, tex2lyx already comes close to making a good LyX file.  The
> main problem is that there always seem to be a handful or errors that must
> be fixed before the file will run.  For some reason the program cannot
> handle options like \begin{thm}[Main Lemma], but also other options.  It
> also seems that comments in the Latex file can sometimes produce errors. 

Please report bugs for these errors at 
http://www.lyx.org/trac/wiki/BugTrackerHome and include an example .tex file 
that shows the bug. These problems are sometimes easy to fix, the only thing 
we need is to be aware of them and a test case.

> A huge annoyance is that theorems, etc. are displayed in ERT.

The problem with theorems is that they are only recognized if the preamble 
is the same that would be used by LyX. Otherwise it cannot be guaranteed 
that the PDF output will be the same as in the original document. If the 
origional .tex file was produced by LyX, and your co-author did not define a 
new theorem style, but only changed an existing theorem or added a new one, 
then the theorems should be imported correctrly by tex2lyx. If this is not 
the case then please file  bug report.

> I understand that for arbitrary LaTex files some of these issues maybe
> very complicated or impossible, but what I am asking for does not involve
> arbitrary files.  Let’s take an easy case.  Suppose my coauthor only makes
> changes between \begin{document} and \end{document} of the LaTex file, and
> does not use any new constructs.  Shouldn’t it be possible, perhaps with a
> helper file that records settings and any other special issues, to make a
> good LyX version?  Or even easier, shouldn’t I be able to export a Latex
> file and then without changing it, import it and get the same LyX file
> back.  Yes, I know there is no reason to do this, but it is a benchmark.

Yes, this should be possible (with one limitation): There are some 
constructs in LyX that cannot be expressed in LaTeX or are not exported 
(e.g. Notes). We discussed in the past how to get rid of this limitation, 
but, but we do not have a consensus on a good soluition yet. Again, if have 
documents that do not re-import correctly, please file a bug.


Georg



Re: automatically updating latex code used in a LyX document

2015-07-11 Thread Georg Baum
Liviu Andronic wrote:

 On Thu, Jul 9, 2015 at 10:11 PM, Georg Baum
 georg.b...@post.rwth-aachen.de wrote:
 Ian wrote:

 Thanks Liviu. Inserting a Child document .tex file was exactly what I
 wanted to do. I just didn't know what it was called.

 Except for the fact that it is not automatically updated if the STATA
 file changes.

 If the content of the child .tex file changes, doesn't LyX
 automatically reflect those changes when recompiling the LyX document?

Yes it does. However, LyX does not recognize that the .tex file itself needs 
to be regenerated when the STATA file changes. The latter would be possible 
with an external inset.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-11 Thread Georg Baum
Liviu Andronic wrote:

 On Fri, Jul 10, 2015 at 11:23 AM, José Matos jama...@lyx.org wrote:
 On Thursday 09 July 2015 23:19:07 Liviu Andronic wrote:
 Perhaps we should consider renaming it to something like: Child
 Document (TeX or LyX)?

 Liviu

 Note that a child document can also be a programming listings or any
 other file to be included verbatim. :-)

 Absolutely, yet our naming is so terse so as to prove confusing.

Yes, it is confusing. The reason why the menu items are as they are is the 
implementation in three different insets: Include inset, graphics inset and 
external inset. However the functionality of those insets overlaps, and 
there is a very old plan to get rid of the graphics inset in favour of the 
external inset. We need some volunteers;-)

 Maybe
 we need a tooltip there, or a status message appearing when hovering
 the item, or something else. Otherwise people simply won't really know
 what that item is supposed to do, or worse assume that LyX is unable
 to do this at all (when it does!). I know RTFM would be one way to
 approach this, but maybe there is something we can do to ease
 confusion... Say, and yet another shot in the dark: Include Child
 Document (.tex, .lyx, etc.)

I guess it should be possible to rework the menu items independently of the 
insets, but I hjave no good idea myself.


Georg



Re: automatically updating latex code used in a LyX document

2015-07-11 Thread Georg Baum
Liviu Andronic wrote:

 On Thu, Jul 9, 2015 at 10:11 PM, Georg Baum
 georg.b...@post.rwth-aachen.de wrote:
 Ian wrote:

 Thanks Liviu. Inserting a Child document .tex file was exactly what I
 wanted to do. I just didn't know what it was called.

 Except for the fact that it is not automatically updated if the STATA
 file changes.

 If the content of the child .tex file changes, doesn't LyX
 automatically reflect those changes when recompiling the LyX document?

Yes it does. However, LyX does not recognize that the .tex file itself needs 
to be regenerated when the STATA file changes. The latter would be possible 
with an external inset.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-11 Thread Georg Baum
Liviu Andronic wrote:

 On Fri, Jul 10, 2015 at 11:23 AM, José Matos jama...@lyx.org wrote:
 On Thursday 09 July 2015 23:19:07 Liviu Andronic wrote:
 Perhaps we should consider renaming it to something like: Child
 Document (TeX or LyX)?

 Liviu

 Note that a child document can also be a programming listings or any
 other file to be included verbatim. :-)

 Absolutely, yet our naming is so terse so as to prove confusing.

Yes, it is confusing. The reason why the menu items are as they are is the 
implementation in three different insets: Include inset, graphics inset and 
external inset. However the functionality of those insets overlaps, and 
there is a very old plan to get rid of the graphics inset in favour of the 
external inset. We need some volunteers;-)

 Maybe
 we need a tooltip there, or a status message appearing when hovering
 the item, or something else. Otherwise people simply won't really know
 what that item is supposed to do, or worse assume that LyX is unable
 to do this at all (when it does!). I know RTFM would be one way to
 approach this, but maybe there is something we can do to ease
 confusion... Say, and yet another shot in the dark: Include Child
 Document (.tex, .lyx, etc.)

I guess it should be possible to rework the menu items independently of the 
insets, but I hjave no good idea myself.


Georg



Re: automatically updating latex code used in a LyX document

2015-07-11 Thread Georg Baum
Liviu Andronic wrote:

> On Thu, Jul 9, 2015 at 10:11 PM, Georg Baum
> <georg.b...@post.rwth-aachen.de> wrote:
>> Ian wrote:
>>
>>> Thanks Liviu. Inserting a Child document .tex file was exactly what I
>>> wanted to do. I just didn't know what it was called.
>>
>> Except for the fact that it is not automatically updated if the STATA
>> file changes.
>>
> If the content of the child .tex file changes, doesn't LyX
> automatically reflect those changes when recompiling the LyX document?

Yes it does. However, LyX does not recognize that the .tex file itself needs 
to be regenerated when the STATA file changes. The latter would be possible 
with an external inset.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-11 Thread Georg Baum
Liviu Andronic wrote:

> On Fri, Jul 10, 2015 at 11:23 AM, José Matos  wrote:
>> On Thursday 09 July 2015 23:19:07 Liviu Andronic wrote:
>>> Perhaps we should consider renaming it to something like: "Child
>>> Document (TeX or LyX)"?
>>>
>>> Liviu
>>
>> Note that a child document can also be a programming listings or any
>> other file to be included verbatim. :-)
>>
> Absolutely, yet our naming is so terse so as to prove confusing.

Yes, it is confusing. The reason why the menu items are as they are is the 
implementation in three different insets: Include inset, graphics inset and 
external inset. However the functionality of those insets overlaps, and 
there is a very old plan to get rid of the graphics inset in favour of the 
external inset. We need some volunteers;-)

> Maybe
> we need a tooltip there, or a status message appearing when hovering
> the item, or something else. Otherwise people simply won't really know
> what that item is supposed to do, or worse assume that LyX is unable
> to do this at all (when it does!). I know RTFM would be one way to
> approach this, but maybe there is something we can do to ease
> confusion... Say, and yet another shot in the dark: "Include Child
> Document (.tex, .lyx, etc.)"

I guess it should be possible to rework the menu items independently of the 
insets, but I hjave no good idea myself.


Georg



Re: automatically updating latex code used in a LyX document

2015-07-09 Thread Georg Baum
Steve Litt wrote:

 On Wed, 8 Jul 2015 06:24:52 + (UTC)
 Ian iank...@gmail.com wrote:
 
 Hi
 
 I want to automatically update latex code embedded in a LyX document
 that was produced as output from another program, in my case STATA.
 The Latex code contains table commands.
 
 The concept is similar to handling graphics in LyX: Insert  Graphic
  (attach file). If I change the graphic file content, keeping the
  file name
 and location the same, the graphic image will automatically update in
 LyX. I want to do the same thing, but with a .tex file in which
 contains the Latex code for a table produced by STATA. The .tex file
 name and location remain constant, but the content changes.
 
 I am sure this is an easy thing, but I just can't seem to find it on
 the web forums.

This is possible: LyX has a mechanism called external templates which can 
be seen as a generalization of the graphics inset: With an external 
template, you can tell LyX what it needs to do to convert your STATA file 
into LaTeX, and you also tell it how this LaTeX is to be included in the LyX 
document. The only requirement for this to work is that your application (or 
any other tool) allows to convert to LaTeX from the command line.

If you want to use this feature, you need to do two things:

1) Define a new external template for STATA as explained in chapter 6 6 
Including External Material in the Customization Manual. This neds to be 
once, and if you need help don't hesitate to ask on the list.

2) Each time you want to include  a STATA output, you use Insert - File - 
External Material.


 I do that kind of stuff all the time. The trick is to put some kind of
 an unmistakable token in your LyX doc. Then make a shellscript that
 cats your LyX into a script (I'd probably use AWK, your mileage may
 vary) to replace the token with the desired LaTeX, and then redirect
 the script's output to another LyX file. LyX --export latex
 tempfile.lyx;pdflatex tempfile.tex.

This is certainly technically interesting, but I would not recommend such a 
procedure to the original poster, since the builtin mechanism does not need 
those helper scripts, and all the export/view buttons in LyX do just work.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-09 Thread Georg Baum
Ian wrote:

 Thanks Liviu. Inserting a Child document .tex file was exactly what I
 wanted to do. I just didn't know what it was called.

Except for the fact that it is not automatically updated if the STATA file 
changes.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-09 Thread Georg Baum
Benedict Holland wrote:

 If you have generated the tex file in Stata, use ERT. It is much easier.

I am curious: What is easier if you include the file via ERT than with a 
child document? Note that I do not mean to convert the child document to LyX 
format, since LyX also allows to include child documents in LaTeX format.

 The command you want to look up is \input as in \input{table.tex}. This is
 the only way I generate, edit, and include tables now. This should also be
 the command that lyx uses... either that or include but I assume input
 would be a better use in this situation. I also use another application to
 edit the .tex because I need spell checking.

If you insert the .tex file as a child document you can do this as well: The 
child inset context menu provides an edit entry which fires up the .tex file 
in your favourite editor. I cannot imagine any easier way to reference child 
document in LaTeX format.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-09 Thread Georg Baum
Steve Litt wrote:

 On Wed, 8 Jul 2015 06:24:52 + (UTC)
 Ian iank...@gmail.com wrote:
 
 Hi
 
 I want to automatically update latex code embedded in a LyX document
 that was produced as output from another program, in my case STATA.
 The Latex code contains table commands.
 
 The concept is similar to handling graphics in LyX: Insert  Graphic
  (attach file). If I change the graphic file content, keeping the
  file name
 and location the same, the graphic image will automatically update in
 LyX. I want to do the same thing, but with a .tex file in which
 contains the Latex code for a table produced by STATA. The .tex file
 name and location remain constant, but the content changes.
 
 I am sure this is an easy thing, but I just can't seem to find it on
 the web forums.

This is possible: LyX has a mechanism called external templates which can 
be seen as a generalization of the graphics inset: With an external 
template, you can tell LyX what it needs to do to convert your STATA file 
into LaTeX, and you also tell it how this LaTeX is to be included in the LyX 
document. The only requirement for this to work is that your application (or 
any other tool) allows to convert to LaTeX from the command line.

If you want to use this feature, you need to do two things:

1) Define a new external template for STATA as explained in chapter 6 6 
Including External Material in the Customization Manual. This neds to be 
once, and if you need help don't hesitate to ask on the list.

2) Each time you want to include  a STATA output, you use Insert - File - 
External Material.


 I do that kind of stuff all the time. The trick is to put some kind of
 an unmistakable token in your LyX doc. Then make a shellscript that
 cats your LyX into a script (I'd probably use AWK, your mileage may
 vary) to replace the token with the desired LaTeX, and then redirect
 the script's output to another LyX file. LyX --export latex
 tempfile.lyx;pdflatex tempfile.tex.

This is certainly technically interesting, but I would not recommend such a 
procedure to the original poster, since the builtin mechanism does not need 
those helper scripts, and all the export/view buttons in LyX do just work.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-09 Thread Georg Baum
Ian wrote:

 Thanks Liviu. Inserting a Child document .tex file was exactly what I
 wanted to do. I just didn't know what it was called.

Except for the fact that it is not automatically updated if the STATA file 
changes.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-09 Thread Georg Baum
Benedict Holland wrote:

 If you have generated the tex file in Stata, use ERT. It is much easier.

I am curious: What is easier if you include the file via ERT than with a 
child document? Note that I do not mean to convert the child document to LyX 
format, since LyX also allows to include child documents in LaTeX format.

 The command you want to look up is \input as in \input{table.tex}. This is
 the only way I generate, edit, and include tables now. This should also be
 the command that lyx uses... either that or include but I assume input
 would be a better use in this situation. I also use another application to
 edit the .tex because I need spell checking.

If you insert the .tex file as a child document you can do this as well: The 
child inset context menu provides an edit entry which fires up the .tex file 
in your favourite editor. I cannot imagine any easier way to reference child 
document in LaTeX format.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-09 Thread Georg Baum
Steve Litt wrote:

> On Wed, 8 Jul 2015 06:24:52 + (UTC)
> Ian  wrote:
> 
>> Hi
>> 
>> I want to automatically update latex code embedded in a LyX document
>> that was produced as output from another program, in my case STATA.
>> The Latex code contains table commands.
>> 
>> The concept is similar to handling graphics in LyX: Insert >> Graphic
>> >> (attach file). If I change the graphic file content, keeping the
>> >> file name
>> and location the same, the graphic image will automatically update in
>> LyX. I want to do the same thing, but with a .tex file in which
>> contains the Latex code for a table produced by STATA. The .tex file
>> name and location remain constant, but the content changes.
>> 
>> I am sure this is an easy thing, but I just can't seem to find it on
>> the web forums.

This is possible: LyX has a mechanism called "external templates" which can 
be seen as a generalization of the graphics inset: With an external 
template, you can tell LyX what it needs to do to convert your STATA file 
into LaTeX, and you also tell it how this LaTeX is to be included in the LyX 
document. The only requirement for this to work is that your application (or 
any other tool) allows to convert to LaTeX from the command line.

If you want to use this feature, you need to do two things:

1) Define a new external template for STATA as explained in chapter 6 "6 
Including External Material" in the Customization Manual. This neds to be 
once, and if you need help don't hesitate to ask on the list.

2) Each time you want to include  a STATA output, you use Insert -> File -> 
External Material.


> I do that kind of stuff all the time. The trick is to put some kind of
> an unmistakable token in your LyX doc. Then make a shellscript that
> cats your LyX into a script (I'd probably use AWK, your mileage may
> vary) to replace the token with the desired LaTeX, and then redirect
> the script's output to another LyX file. LyX --export latex
> tempfile.lyx;pdflatex tempfile.tex.

This is certainly technically interesting, but I would not recommend such a 
procedure to the original poster, since the builtin mechanism does not need 
those helper scripts, and all the export/view buttons in LyX do just work.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-09 Thread Georg Baum
Ian wrote:

> Thanks Liviu. Inserting a Child document .tex file was exactly what I
> wanted to do. I just didn't know what it was called.

Except for the fact that it is not automatically updated if the STATA file 
changes.


Georg




Re: automatically updating latex code used in a LyX document

2015-07-09 Thread Georg Baum
Benedict Holland wrote:

> If you have generated the tex file in Stata, use ERT. It is much easier.

I am curious: What is easier if you include the file via ERT than with a 
child document? Note that I do not mean to convert the child document to LyX 
format, since LyX also allows to include child documents in LaTeX format.

> The command you want to look up is \input as in \input{table.tex}. This is
> the only way I generate, edit, and include tables now. This should also be
> the command that lyx uses... either that or include but I assume input
> would be a better use in this situation. I also use another application to
> edit the .tex because I need spell checking.

If you insert the .tex file as a child document you can do this as well: The 
child inset context menu provides an edit entry which fires up the .tex file 
in your favourite editor. I cannot imagine any easier way to reference child 
document in LaTeX format.


Georg




Re: Suggestion to improve Lyx for LaTEX users

2015-06-11 Thread Georg Baum
Liviu Andronic wrote:

 On Wed, Jun 10, 2015 at 2:34 PM, Richard Heck rgh...@lyx.org wrote:
 
 my case). I wonder if just having the option of opening an ERT itself in
 an external
 editor would help?

 As it happens, this is the subject of:
 http://www.lyx.org/trac/ticket/7404
 
 Georg even provided a patch, and I suspect it requires not much
 programming to polish up that patch for inclusion.

Indeed, at least a a part of the requested feature should be easy to 
integrate. However, I still don't have enough time, so if anybody wants to 
chime in it would be most welcome (and of course I'll happily answer any 
question).

 I suppose it might be an option to run tex2lyx on
 whatever we get,
 and replace the ERT inset with the result, in so far as that is possible.
 I.e., we'd have
 a sort of generic ERT--LyX routine.

 I think this would be a nice touch, indeed.

Should already work: Copy ERT, then Edit-Paste special-from LaTeX, then 
delete ERT. I guess you could even bind a command sequence to a custom key 
shortcut, so that you can type LaTeX, and having it interpreted by a single 
key combination.


Georg



Re: Suggestion to improve Lyx for LaTEX users

2015-06-11 Thread Georg Baum
Liviu Andronic wrote:

 On Wed, Jun 10, 2015 at 2:34 PM, Richard Heck rgh...@lyx.org wrote:
 
 my case). I wonder if just having the option of opening an ERT itself in
 an external
 editor would help?

 As it happens, this is the subject of:
 http://www.lyx.org/trac/ticket/7404
 
 Georg even provided a patch, and I suspect it requires not much
 programming to polish up that patch for inclusion.

Indeed, at least a a part of the requested feature should be easy to 
integrate. However, I still don't have enough time, so if anybody wants to 
chime in it would be most welcome (and of course I'll happily answer any 
question).

 I suppose it might be an option to run tex2lyx on
 whatever we get,
 and replace the ERT inset with the result, in so far as that is possible.
 I.e., we'd have
 a sort of generic ERT--LyX routine.

 I think this would be a nice touch, indeed.

Should already work: Copy ERT, then Edit-Paste special-from LaTeX, then 
delete ERT. I guess you could even bind a command sequence to a custom key 
shortcut, so that you can type LaTeX, and having it interpreted by a single 
key combination.


Georg



Re: Suggestion to improve Lyx for LaTEX users

2015-06-11 Thread Georg Baum
Liviu Andronic wrote:

> On Wed, Jun 10, 2015 at 2:34 PM, Richard Heck  wrote:
> 
>> my case). I wonder if just having the option of opening an ERT itself in
>> an external
>> editor would help?
>>
> As it happens, this is the subject of:
> http://www.lyx.org/trac/ticket/7404
> 
> Georg even provided a patch, and I suspect it requires not much
> programming to polish up that patch for inclusion.

Indeed, at least a a part of the requested feature should be easy to 
integrate. However, I still don't have enough time, so if anybody wants to 
chime in it would be most welcome (and of course I'll happily answer any 
question).

>> I suppose it might be an option to run tex2lyx on
>> whatever we get,
>> and replace the ERT inset with the result, in so far as that is possible.
>> I.e., we'd have
>> a sort of generic ERT-->LyX routine.
>>
> I think this would be a nice touch, indeed.

Should already work: Copy ERT, then Edit->Paste special->from LaTeX, then 
delete ERT. I guess you could even bind a command sequence to a custom key 
shortcut, so that you can type LaTeX, and having it interpreted by a single 
key combination.


Georg



Re: Strategies for locating errors

2015-05-07 Thread Georg Baum
Will Furnass wrote:

 On 5 May 2015 at 21:38, Georg Baum georg.b...@post.rwth-aachen.de wrote:
 

 If you select the error item in the error dialog then the corresponding
 LyX contents should should be selected in the main area as well. This is
 not always 100% correct, but usually the error cause is nearby. Does this
 not work in your case?

 
 Ah, I hadn't noticed that before!  That works perfectly if the error is in
 the master document but not if the error is in a child document (of which
 I have quite a few).
 
 If would be great if LyX would switch to/open the child document
 containing the likely location of the error and move the cursor to that
 location.

I agree. Please file an enhancement request at 
http://www.lyx.org/trac/wiki/BugTrackerHome. It should not be too difficult 
to implement, since LyX has all information which is needed (which file and 
which line number). I guess it was simply forgotten.


Georg



Re: Strategies for locating errors

2015-05-07 Thread Georg Baum
Will Furnass wrote:

 On 5 May 2015 at 21:38, Georg Baum georg.b...@post.rwth-aachen.de wrote:
 

 If you select the error item in the error dialog then the corresponding
 LyX contents should should be selected in the main area as well. This is
 not always 100% correct, but usually the error cause is nearby. Does this
 not work in your case?

 
 Ah, I hadn't noticed that before!  That works perfectly if the error is in
 the master document but not if the error is in a child document (of which
 I have quite a few).
 
 If would be great if LyX would switch to/open the child document
 containing the likely location of the error and move the cursor to that
 location.

I agree. Please file an enhancement request at 
http://www.lyx.org/trac/wiki/BugTrackerHome. It should not be too difficult 
to implement, since LyX has all information which is needed (which file and 
which line number). I guess it was simply forgotten.


Georg



Re: Strategies for locating errors

2015-05-07 Thread Georg Baum
Will Furnass wrote:

> On 5 May 2015 at 21:38, Georg Baum <georg.b...@post.rwth-aachen.de> wrote:
> 
>>
>> If you select the error item in the error dialog then the corresponding
>> LyX contents should should be selected in the main area as well. This is
>> not always 100% correct, but usually the error cause is nearby. Does this
>> not work in your case?
>>
> 
> Ah, I hadn't noticed that before!  That works perfectly if the error is in
> the master document but not if the error is in a child document (of which
> I have quite a few).
> 
> If would be great if LyX would switch to/open the child document
> containing the likely location of the error and move the cursor to that
> location.

I agree. Please file an enhancement request at 
http://www.lyx.org/trac/wiki/BugTrackerHome. It should not be too difficult 
to implement, since LyX has all information which is needed (which file and 
which line number). I guess it was simply forgotten.


Georg



Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
Will Furnass wrote:

 How do others locate compilation errors in large multi-file documents?
 
 I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
 relate that line number to the LyX source.  I then try exporting to tex
 using pdflatex into a temporary directory and search through all 16 tex
 files looking for errors on or near line 1052.

If you select the error item in the error dialog then the corresponding LyX 
contents should should be selected in the main area as well. This is not 
always 100% correct, but usually the error cause is nearby. Does this not 
work in your case?


Georg



Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
Wolfgang Engelmann wrote:

 That was the reason I was asking a while ago, whether the latex source
 panel (under view) could show the tex line number. But I was told it is
 not possible under lyx.

Why that? Of course it would only be possible if the panel is set to show 
the full source (otherwise the line number would be wrong), but in that case 
it should not be a problem.



Georg



Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
Wolfgang Engelmann wrote:

 That was the reason I was asking a while ago, whether the latex source
 panel (under view) could show the tex line number. But I was told it is
 not possible under lyx.

Why that? Of course it would only be possible if the panel is set to show 
the full source (otherwise the line number would be wrong), but in that case 
it should not be a problem.



Georg



Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
Will Furnass wrote:

 How do others locate compilation errors in large multi-file documents?
 
 I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
 relate that line number to the LyX source.  I then try exporting to tex
 using pdflatex into a temporary directory and search through all 16 tex
 files looking for errors on or near line 1052.

If you select the error item in the error dialog then the corresponding LyX 
contents should should be selected in the main area as well. This is not 
always 100% correct, but usually the error cause is nearby. Does this not 
work in your case?


Georg



Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
Wolfgang Engelmann wrote:

> That was the reason I was asking a while ago, whether the latex source
> panel (under >view) could show the tex line number. But I was told it is
> not possible under lyx.

Why that? Of course it would only be possible if the panel is set to show 
the full source (otherwise the line number would be wrong), but in that case 
it should not be a problem.



Georg



Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
Will Furnass wrote:

> How do others locate compilation errors in large multi-file documents?
> 
> I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
> relate that line number to the LyX source.  I then try exporting to tex
> using pdflatex into a temporary directory and search through all 16 tex
> files looking for errors on or near line 1052.

If you select the error item in the error dialog then the corresponding LyX 
contents should should be selected in the main area as well. This is not 
always 100% correct, but usually the error cause is nearby. Does this not 
work in your case?


Georg



Re: xtended arrows

2015-04-20 Thread Georg Baum
Elbert Branscomb wrote:

 Hello,
 
 I'm running lyx-2.1.3 on a 64 bit Linux box (Gentoo; up to date; except
 that the kernel is 3.12.13-gentoo).
 
 With all lyx-provided math packages set to load always, including
 specifically amsmath and mathtools  (and with lyx restarted) I still
 only have access to two of the extended horizontal arrows: xleftarrow
 and xrightarrow; not to any of the others listed in the math help
 document; most importantly for me at the moment: xrightleftharpoons.
 This seems to contradict what the math help doc says in section 6.1.
 
 Help?

The documentation is a bit terse here. The commands are not available in the 
sense known by LyX, i.e. recognized as symbols or appearing in a menu or 
toolbar, but available in the sense known by LaTeX, i.e. if you enter them 
as ERT in a math box, then the PDF output will be correct. This works for me 
(I suppose you know that \xrightleftharpoons needs an argument).

Not that you do not need to restart LyX (this is a document setting), and 
you only need to set mathtools to load always, amsmath can be left at 
auto.


If you like, you can file enhancement requests at 
http://www.lyx.org/trac/wiki/BugTrackerHome for

a) the documentation (it should make it clear that ERT is needed)

and

b) native support for the not yet supported macros from mathtools.sty.


If you do not get a correct PDF output you can also file a bug report, but 
please include a minimal test case, otherwise it will be likely to be closed 
as worksforme.


Georg



Re: xtended arrows

2015-04-20 Thread Georg Baum
Elbert Branscomb wrote:

 Hello,
 
 I'm running lyx-2.1.3 on a 64 bit Linux box (Gentoo; up to date; except
 that the kernel is 3.12.13-gentoo).
 
 With all lyx-provided math packages set to load always, including
 specifically amsmath and mathtools  (and with lyx restarted) I still
 only have access to two of the extended horizontal arrows: xleftarrow
 and xrightarrow; not to any of the others listed in the math help
 document; most importantly for me at the moment: xrightleftharpoons.
 This seems to contradict what the math help doc says in section 6.1.
 
 Help?

The documentation is a bit terse here. The commands are not available in the 
sense known by LyX, i.e. recognized as symbols or appearing in a menu or 
toolbar, but available in the sense known by LaTeX, i.e. if you enter them 
as ERT in a math box, then the PDF output will be correct. This works for me 
(I suppose you know that \xrightleftharpoons needs an argument).

Not that you do not need to restart LyX (this is a document setting), and 
you only need to set mathtools to load always, amsmath can be left at 
auto.


If you like, you can file enhancement requests at 
http://www.lyx.org/trac/wiki/BugTrackerHome for

a) the documentation (it should make it clear that ERT is needed)

and

b) native support for the not yet supported macros from mathtools.sty.


If you do not get a correct PDF output you can also file a bug report, but 
please include a minimal test case, otherwise it will be likely to be closed 
as worksforme.


Georg



Re: xtended arrows

2015-04-20 Thread Georg Baum
Elbert Branscomb wrote:

> Hello,
> 
> I'm running lyx-2.1.3 on a 64 bit Linux box (Gentoo; up to date; except
> that the kernel is 3.12.13-gentoo).
> 
> With all lyx-provided math packages set to "load always", including
> specifically amsmath and mathtools  (and with lyx restarted) I still
> only have access to two of the extended horizontal arrows: xleftarrow
> and xrightarrow; not to any of the others listed in the math help
> document; most importantly for me at the moment: "xrightleftharpoons".
> This seems to contradict what the math help doc says in section 6.1.
> 
> Help?

The documentation is a bit terse here. The commands are not available in the 
sense "known by LyX", i.e. recognized as symbols or appearing in a menu or 
toolbar, but available in the sense "known by LaTeX", i.e. if you enter them 
as ERT in a math box, then the PDF output will be correct. This works for me 
(I suppose you know that \xrightleftharpoons needs an argument).

Not that you do not need to restart LyX (this is a document setting), and 
you only need to set mathtools to "load always", amsmath can be left at 
auto.


If you like, you can file enhancement requests at 
http://www.lyx.org/trac/wiki/BugTrackerHome for

a) the documentation (it should make it clear that ERT is needed)

and

b) native support for the not yet supported macros from mathtools.sty.


If you do not get a correct PDF output you can also file a bug report, but 
please include a minimal test case, otherwise it will be likely to be closed 
as "worksforme".


Georg



Re: Re: esint.sty in RedHat/Centos 7. Where? Why omitted?

2015-04-07 Thread Georg Baum
Paul Johnson wrote:

 I believe this may not be entirely necessary, however.  The esint
 package is not truly required to compile an elementary document.
 However, inside LyX, there is a switch under document / settings that
 says use esint automatically. I think that doesn't work properly, it
 tries to use esint even on an
 ordinary integral.  If we change esint to do not load then the basic
 document compiles.

I believe that esint is only loaded when it is needed. Please note that some 
integrals compile without esint, but they do look differently. esint fixes 
some inconsistencies, see http://www.lyx.org/trac/ticket/1942 for details. 
Please file a bug if esint is loaded in cases where it is not needed, i.e. 
the document compiles and does not produce inconsistent integrals without 
loading esint.


Georg




Re: Re: esint.sty in RedHat/Centos 7. Where? Why omitted?

2015-04-07 Thread Georg Baum
Paul Johnson wrote:

 I believe this may not be entirely necessary, however.  The esint
 package is not truly required to compile an elementary document.
 However, inside LyX, there is a switch under document / settings that
 says use esint automatically. I think that doesn't work properly, it
 tries to use esint even on an
 ordinary integral.  If we change esint to do not load then the basic
 document compiles.

I believe that esint is only loaded when it is needed. Please note that some 
integrals compile without esint, but they do look differently. esint fixes 
some inconsistencies, see http://www.lyx.org/trac/ticket/1942 for details. 
Please file a bug if esint is loaded in cases where it is not needed, i.e. 
the document compiles and does not produce inconsistent integrals without 
loading esint.


Georg




Re: Re: esint.sty in RedHat/Centos 7. Where? Why omitted?

2015-04-07 Thread Georg Baum
Paul Johnson wrote:

> I believe this may not be entirely necessary, however.  The esint
> package is not truly required to compile an elementary document.
> However, inside LyX, there is a switch under document / settings that
> says use esint automatically. I think that doesn't work properly, it
> tries to use esint even on an
> ordinary integral.  If we change esint to "do not load" then the basic
> document compiles.

I believe that esint is only loaded when it is needed. Please note that some 
integrals compile without esint, but they do look differently. esint fixes 
some inconsistencies, see http://www.lyx.org/trac/ticket/1942 for details. 
Please file a bug if esint is loaded in cases where it is not needed, i.e. 
the document compiles and does not produce inconsistent integrals without 
loading esint.


Georg




Re: esint.sty in RedHat/Centos 7. Where? Why omitted?

2015-03-22 Thread Georg Baum
Paul Johnson wrote:

 I searched long enough to see there is some peculiar history with
 packaging of esint.sty. I DO find the Fedora package in rpmfind.net
 texlive-esint-  I will rebuild that on the EL7 systems if I have
 to. But I can't see why this is necessary at all.

I don't know why esint.sty is not properly packaged for Red Hat, but I would 
recommend to use vanilla texlive, and not the one provided by the 
distribution. Since texlive contains an own package manager for quite some 
time this is easy to do.


Georg



Re: esint.sty in RedHat/Centos 7. Where? Why omitted?

2015-03-22 Thread Georg Baum
Paul Johnson wrote:

 I searched long enough to see there is some peculiar history with
 packaging of esint.sty. I DO find the Fedora package in rpmfind.net
 texlive-esint-  I will rebuild that on the EL7 systems if I have
 to. But I can't see why this is necessary at all.

I don't know why esint.sty is not properly packaged for Red Hat, but I would 
recommend to use vanilla texlive, and not the one provided by the 
distribution. Since texlive contains an own package manager for quite some 
time this is easy to do.


Georg



Re: esint.sty in RedHat/Centos 7. Where? Why omitted?

2015-03-22 Thread Georg Baum
Paul Johnson wrote:

> I searched long enough to see there is some peculiar history with
> packaging of esint.sty. I DO find the Fedora package in rpmfind.net
> "texlive-esint-...".  I will rebuild that on the EL7 systems if I have
> to. But I can't see why this is necessary at all.

I don't know why esint.sty is not properly packaged for Red Hat, but I would 
recommend to use vanilla texlive, and not the one provided by the 
distribution. Since texlive contains an own package manager for quite some 
time this is easy to do.


Georg



Re: \biggg not working

2015-03-05 Thread Georg Baum
Richard Heck wrote:

 On 03/04/2015 04:07 PM, Georg Baum wrote:

 The idea is simply to give a better display for those users who use these
 packages. AFAIK these commands do not occur in any toolbar, menu or
 autocompletion (and if they would this would be a bug).
 
 That is a bit confusing for the user. Is there anything we can do?

Yes, it can be confusing. I think we have two options:

1) remove these macros from autocompletion
2) comment them in lib/symbols

I have no string preference. Which version do you prefer?


Georg



Re: \biggg not working

2015-03-05 Thread Georg Baum
Richard Heck wrote:

 On 03/04/2015 04:07 PM, Georg Baum wrote:

 The idea is simply to give a better display for those users who use these
 packages. AFAIK these commands do not occur in any toolbar, menu or
 autocompletion (and if they would this would be a bug).
 
 That is a bit confusing for the user. Is there anything we can do?

Yes, it can be confusing. I think we have two options:

1) remove these macros from autocompletion
2) comment them in lib/symbols

I have no string preference. Which version do you prefer?


Georg



Re: \biggg not working

2015-03-05 Thread Georg Baum
Richard Heck wrote:

> On 03/04/2015 04:07 PM, Georg Baum wrote:
>>
>> The idea is simply to give a better display for those users who use these
>> packages. AFAIK these commands do not occur in any toolbar, menu or
>> autocompletion (and if they would this would be a bug).
> 
> That is a bit confusing for the user. Is there anything we can do?

Yes, it can be confusing. I think we have two options:

1) remove these macros from autocompletion
2) comment them in lib/symbols

I have no string preference. Which version do you prefer?


Georg



Re: \biggg not working

2015-03-04 Thread Georg Baum
Jean-Marc Lasgouttes wrote:

 Is \biggg even supposed to exist? I see that LyX code pretends to
 support it, but I do not understand how.
 
 In lib/symbols, I see:
 
 # The following are not standard LaTeX, but defined in the lucida font
 # packages. No 'm' versions!
 # See lucidabr.dtx for a possible implementation if you want to use these
 # with other fonts.
 biggg big none
 biggglbig none
 bigggrbig none
 Biggg big none
 Biggglbig none
 Bigggrbig none
 
 
 Georg, this is your code. Do you remember what the reasoning was?

There are several commands in lib/symbols which do not work without user 
preamble code. They are there because mathed can easily display these 
symbols, and they do not load the required packages automatically since they 
would have side effects.

The idea is simply to give a better display for those users who use these 
packages. AFAIK these commands do not occur in any toolbar, menu or 
autocompletion (and if they would this would be a bug).


Georg



Re: \biggg not working

2015-03-04 Thread Georg Baum
Jean-Marc Lasgouttes wrote:

 Is \biggg even supposed to exist? I see that LyX code pretends to
 support it, but I do not understand how.
 
 In lib/symbols, I see:
 
 # The following are not standard LaTeX, but defined in the lucida font
 # packages. No 'm' versions!
 # See lucidabr.dtx for a possible implementation if you want to use these
 # with other fonts.
 biggg big none
 biggglbig none
 bigggrbig none
 Biggg big none
 Biggglbig none
 Bigggrbig none
 
 
 Georg, this is your code. Do you remember what the reasoning was?

There are several commands in lib/symbols which do not work without user 
preamble code. They are there because mathed can easily display these 
symbols, and they do not load the required packages automatically since they 
would have side effects.

The idea is simply to give a better display for those users who use these 
packages. AFAIK these commands do not occur in any toolbar, menu or 
autocompletion (and if they would this would be a bug).


Georg



Re: \biggg not working

2015-03-04 Thread Georg Baum
Jean-Marc Lasgouttes wrote:

> Is \biggg even supposed to exist? I see that LyX code pretends to
> support it, but I do not understand how.
> 
> In lib/symbols, I see:
> 
> # The following are not standard LaTeX, but defined in the lucida font
> # packages. No 'm' versions!
> # See lucidabr.dtx for a possible implementation if you want to use these
> # with other fonts.
> biggg big none
> biggglbig none
> bigggrbig none
> Biggg big none
> Biggglbig none
> Bigggrbig none
> 
> 
> Georg, this is your code. Do you remember what the reasoning was?

There are several commands in lib/symbols which do not work without user 
preamble code. They are there because mathed can easily display these 
symbols, and they do not load the required packages automatically since they 
would have side effects.

The idea is simply to give a better display for those users who use these 
packages. AFAIK these commands do not occur in any toolbar, menu or 
autocompletion (and if they would this would be a bug).


Georg



Re: Lyx winbuilds

2015-01-03 Thread Georg Baum
Hi Peter,

this is intersting, but I think it is better suited for the development 
list.


Peter Johansson wrote:

 Only issues you can see as automake failed to analyze my latest version of
 magic and I had to add the common win libs manually, in this, my first
 Lyx build run containing three interrupts, made those directly in the
 makefiles.

If libmagic was not installed in an unusual location please tell us about 
the needed settings, so that we can improve the configure logic.

 The only issue with this particular Lyx build was that I had to install a
 MSVC poisoned python. One positive development for Lyx, would be to
 abandon python setups and deploy QT setting dialogs as of Texmaker and
 Texstudio.

What means MSVC poisoned python, and why was it needed? I don't think the 
the use of python in LyX will be abandoned in the forseeable future, since 
it is used for much more than just settings.

 Well it's quite simple as I've chosen all work computerss not operated by
 me personally to be UX ones.
 
 But still, why not scrap MSVC altogether on Winbox distros ??.

The main reason is that our main windows developer uses MSVC. Apart from 
that we recently discovered also a technical problem with gcc:
The std::string implementation of GNU libstdc++ which comes with gcc is not 
C++11 conformant, and there are no plans to fix this (see 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21334). The std::string 
implementation which ships with MSVC is C++11-conformant. You might think 
that this is a theoretical issue onl, but it caused a real bug which was 
very hard to track down: http://www.lyx.org/trac/ticket/9336.

  gcc is under revolutionary development due to it's deployment on android
  and most of todays supercomputers.

I get a different impression: gcc development stalls, the most interesting 
compiler developments currently happen in llvm. Anyway, LyX users should be 
free to choose the compiler which suits them most, so any changes to improve  
compilation with mingw are welcome.

 Many thanks for the great src package to all of you developers, donations
 will be due if Lyx becomes productively deployed on any project associated
 to me.

You are welcome.


Georg



Re: Lyx winbuilds

2015-01-03 Thread Georg Baum
Hi Peter,

this is intersting, but I think it is better suited for the development 
list.


Peter Johansson wrote:

 Only issues you can see as automake failed to analyze my latest version of
 magic and I had to add the common win libs manually, in this, my first
 Lyx build run containing three interrupts, made those directly in the
 makefiles.

If libmagic was not installed in an unusual location please tell us about 
the needed settings, so that we can improve the configure logic.

 The only issue with this particular Lyx build was that I had to install a
 MSVC poisoned python. One positive development for Lyx, would be to
 abandon python setups and deploy QT setting dialogs as of Texmaker and
 Texstudio.

What means MSVC poisoned python, and why was it needed? I don't think the 
the use of python in LyX will be abandoned in the forseeable future, since 
it is used for much more than just settings.

 Well it's quite simple as I've chosen all work computerss not operated by
 me personally to be UX ones.
 
 But still, why not scrap MSVC altogether on Winbox distros ??.

The main reason is that our main windows developer uses MSVC. Apart from 
that we recently discovered also a technical problem with gcc:
The std::string implementation of GNU libstdc++ which comes with gcc is not 
C++11 conformant, and there are no plans to fix this (see 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21334). The std::string 
implementation which ships with MSVC is C++11-conformant. You might think 
that this is a theoretical issue onl, but it caused a real bug which was 
very hard to track down: http://www.lyx.org/trac/ticket/9336.

  gcc is under revolutionary development due to it's deployment on android
  and most of todays supercomputers.

I get a different impression: gcc development stalls, the most interesting 
compiler developments currently happen in llvm. Anyway, LyX users should be 
free to choose the compiler which suits them most, so any changes to improve  
compilation with mingw are welcome.

 Many thanks for the great src package to all of you developers, donations
 will be due if Lyx becomes productively deployed on any project associated
 to me.

You are welcome.


Georg



Re: Lyx winbuilds

2015-01-03 Thread Georg Baum
Hi Peter,

this is intersting, but I think it is better suited for the development 
list.


Peter Johansson wrote:

> Only issues you can see as automake failed to analyze my latest version of
> magic and I had to add the common win libs manually, in this, my first
> "Lyx build run" containing three interrupts, made those directly in the
> makefiles.

If libmagic was not installed in an unusual location please tell us about 
the needed settings, so that we can improve the configure logic.

> The only issue with this particular Lyx build was that I had to install a
> MSVC poisoned python. One positive development for Lyx, would be to
> abandon python setups and deploy QT setting dialogs as of Texmaker and
> Texstudio.

What means MSVC poisoned python, and why was it needed? I don't think the 
the use of python in LyX will be abandoned in the forseeable future, since 
it is used for much more than just settings.

> Well it's quite simple as I've chosen all work computerss not operated by
> me personally to be UX ones.
> 
> But still, why not scrap MSVC altogether on Winbox distros ??.

The main reason is that our main windows developer uses MSVC. Apart from 
that we recently discovered also a technical problem with gcc:
The std::string implementation of GNU libstdc++ which comes with gcc is not 
C++11 conformant, and there are no plans to fix this (see 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21334). The std::string 
implementation which ships with MSVC is C++11-conformant. You might think 
that this is a theoretical issue onl, but it caused a real bug which was 
very hard to track down: http://www.lyx.org/trac/ticket/9336.

>  gcc is under revolutionary development due to it's deployment on android
>  and most of todays supercomputers.

I get a different impression: gcc development stalls, the most interesting 
compiler developments currently happen in llvm. Anyway, LyX users should be 
free to choose the compiler which suits them most, so any changes to improve  
compilation with mingw are welcome.

> Many thanks for the great src package to all of you developers, donations
> will be due if Lyx becomes productively deployed on any project associated
> to me.

You are welcome.


Georg



Re: Unsupported math environments

2014-06-29 Thread Georg Baum
Rudi Gaelzer wrote:

 What I want and need is a means to implement the math ENVIRONMENTS defined
 by the mathtools package and that are not explicitly supported by LyX.
 Specifically for multiline equations.  LyX supports the standard AMS inner
 and outer environments, such as align (outer) and aligned (inner). 
 However, multline is only an outer env in the standard AMSmath.  The
 mathtools pack defines the corresponding inner multlined environment, and
 it seems that there is no way to use it other than ERTing the math input
 (see attached file). I guess the same tweak can be applied in order to use
 the other new environments defined by mathtools, such as dcases, rcases,
 drcases, psmallmatrix, bsmallmatrix, etc.

Unfortunately it is not possible to use unsupported math environments in LyX 
without putting the whole formula in ERT or do some advanced macro tricks. 
The reason for this is that the native LyX format for math formulas is 
LaTeX. This is implemented in such a way that _everything_ is parsed, so it 
is not possible to have a true ERT in mathed. The parser supports unknown 
commands somewhat (so they appear in red), but not environments.

This is of course a problem and needs to be fixed, but up to now nobody 
worked on it. If it does not exist already please file a bug report at 
http://www.lyx.org/trac/wiki/BugTrackerHome to support unknown environments 
in math.


Georg




Re: Unsupported math environments

2014-06-29 Thread Georg Baum
Rudi Gaelzer wrote:

 What I want and need is a means to implement the math ENVIRONMENTS defined
 by the mathtools package and that are not explicitly supported by LyX.
 Specifically for multiline equations.  LyX supports the standard AMS inner
 and outer environments, such as align (outer) and aligned (inner). 
 However, multline is only an outer env in the standard AMSmath.  The
 mathtools pack defines the corresponding inner multlined environment, and
 it seems that there is no way to use it other than ERTing the math input
 (see attached file). I guess the same tweak can be applied in order to use
 the other new environments defined by mathtools, such as dcases, rcases,
 drcases, psmallmatrix, bsmallmatrix, etc.

Unfortunately it is not possible to use unsupported math environments in LyX 
without putting the whole formula in ERT or do some advanced macro tricks. 
The reason for this is that the native LyX format for math formulas is 
LaTeX. This is implemented in such a way that _everything_ is parsed, so it 
is not possible to have a true ERT in mathed. The parser supports unknown 
commands somewhat (so they appear in red), but not environments.

This is of course a problem and needs to be fixed, but up to now nobody 
worked on it. If it does not exist already please file a bug report at 
http://www.lyx.org/trac/wiki/BugTrackerHome to support unknown environments 
in math.


Georg




Re: Unsupported math environments

2014-06-29 Thread Georg Baum
Rudi Gaelzer wrote:

> What I want and need is a means to implement the math ENVIRONMENTS defined
> by the mathtools package and that are not explicitly supported by LyX.
> Specifically for multiline equations.  LyX supports the standard AMS inner
> and outer environments, such as align (outer) and aligned (inner). 
> However, multline is only an outer env in the standard AMSmath.  The
> mathtools pack defines the corresponding inner multlined environment, and
> it seems that there is no way to use it other than ERTing the math input
> (see attached file). I guess the same tweak can be applied in order to use
> the other new environments defined by mathtools, such as dcases, rcases,
> drcases, psmallmatrix, bsmallmatrix, etc.

Unfortunately it is not possible to use unsupported math environments in LyX 
without putting the whole formula in ERT or do some advanced macro tricks. 
The reason for this is that the native LyX format for math formulas is 
LaTeX. This is implemented in such a way that _everything_ is parsed, so it 
is not possible to have a true ERT in mathed. The parser supports unknown 
commands somewhat (so they appear in red), but not environments.

This is of course a problem and needs to be fixed, but up to now nobody 
worked on it. If it does not exist already please file a bug report at 
http://www.lyx.org/trac/wiki/BugTrackerHome to support unknown environments 
in math.


Georg




Re: Korean Input Problem in tex Code mode on lyx 2.1.0

2014-06-20 Thread Georg Baum
Scott Kostyshak wrote:

 On Tue, Jun 17, 2014 at 8:55 AM, Seunghee shlee20...@gmail.com wrote:

 Hi, Scott,
 thank you for your reply.
 I have installed lyx2.2dev and tried to input Korean in the both of
 modes.

 In the 'Program Listing' mode the problem is fixed, but not in the 'tex
 mode'.

 I have found a difference between the both of modes.
 Wenn I input alphabets in the 'program Listing' mode, the following
 message appears:
 Font: Typewriter, text, Language: LaTeX

 But in the 'tex mode'the following message appears:
 Font: Typewriter, LaTex text, Language: LaTeX
 
 Georg, do you know what's going on here?

Yes. The behaviour is by design. The explanation of the reason is a bit 
technical: Since version 1.5.0 LyX uses unicode internally, and .lyx files 
are encoded in utf-8. The big advantage of that compared to previous 
versions is that LyX can process and display text in almost all languages on 
earth. However, when LyX exports the document in LaTeX format for 
typesetting production, the situation is much more complicated. There are 
the modern LaTeX compilers like XeLaTeX and LuaLaTeX, which (like LyX) use 
unicode natively and take utf8-encoded input files, and there is the 
traditional LaTeX compiler which uses an 8-bit encoding internally and takes 
input files in different encodings, or even using multiple encodings in one 
file.

The difference between 'Program Listing' and 'tex mode' is the following: 
'Program Listing' is typeset using the listings LaTeX package, and that 
package supports a variety of different encodings. Therefore, when a 
'Program Listing' is output, LyX tries to find a suitable encoding which is 
supported by the listings package, and then converts the contents of the 
'Program Listing' into that encoding. This works usually. However, 'tex 
mode' means that the contents of the ERT inset is output 1:1, no 
transformation is allowed by definition (otherwise it would not be raw TeX 
anymore). This means that the contents must either be encodable in the 
currently active output encoding, or output would fail. Unfortunately, due 
to an internal limitation, we don't know the currently active output 
encoding where we need to know it (for LyX developers: latex_language-
encoding() returns a static encoding, this needs to be dynamic and depend 
on the current environment). I want to change that in the long term, but 
this is the current situation.

Since you can get an uncodable document so easily with ERT insets, bug 9012 
was filed, and we fixed it by disallowing non-ASCII characters in ERT 
insets. Before the long term solution is implemented, we have two options: 
Reverting the fix for bug 9012, and live with the easy way to create 
uncodable documents, or do nothing and live with the fact that non-ASCII 
stuff does not work in ERT also in the cases when it would be encodable.

As a workaround for your problem, you can split your ERT inset in several 
parts, and put the korean text in standard mode.


Georg



Re: Korean Input Problem in tex Code mode on lyx 2.1.0

2014-06-20 Thread Georg Baum
Scott Kostyshak wrote:

 On Tue, Jun 17, 2014 at 8:55 AM, Seunghee shlee20...@gmail.com wrote:

 Hi, Scott,
 thank you for your reply.
 I have installed lyx2.2dev and tried to input Korean in the both of
 modes.

 In the 'Program Listing' mode the problem is fixed, but not in the 'tex
 mode'.

 I have found a difference between the both of modes.
 Wenn I input alphabets in the 'program Listing' mode, the following
 message appears:
 Font: Typewriter, text, Language: LaTeX

 But in the 'tex mode'the following message appears:
 Font: Typewriter, LaTex text, Language: LaTeX
 
 Georg, do you know what's going on here?

Yes. The behaviour is by design. The explanation of the reason is a bit 
technical: Since version 1.5.0 LyX uses unicode internally, and .lyx files 
are encoded in utf-8. The big advantage of that compared to previous 
versions is that LyX can process and display text in almost all languages on 
earth. However, when LyX exports the document in LaTeX format for 
typesetting production, the situation is much more complicated. There are 
the modern LaTeX compilers like XeLaTeX and LuaLaTeX, which (like LyX) use 
unicode natively and take utf8-encoded input files, and there is the 
traditional LaTeX compiler which uses an 8-bit encoding internally and takes 
input files in different encodings, or even using multiple encodings in one 
file.

The difference between 'Program Listing' and 'tex mode' is the following: 
'Program Listing' is typeset using the listings LaTeX package, and that 
package supports a variety of different encodings. Therefore, when a 
'Program Listing' is output, LyX tries to find a suitable encoding which is 
supported by the listings package, and then converts the contents of the 
'Program Listing' into that encoding. This works usually. However, 'tex 
mode' means that the contents of the ERT inset is output 1:1, no 
transformation is allowed by definition (otherwise it would not be raw TeX 
anymore). This means that the contents must either be encodable in the 
currently active output encoding, or output would fail. Unfortunately, due 
to an internal limitation, we don't know the currently active output 
encoding where we need to know it (for LyX developers: latex_language-
encoding() returns a static encoding, this needs to be dynamic and depend 
on the current environment). I want to change that in the long term, but 
this is the current situation.

Since you can get an uncodable document so easily with ERT insets, bug 9012 
was filed, and we fixed it by disallowing non-ASCII characters in ERT 
insets. Before the long term solution is implemented, we have two options: 
Reverting the fix for bug 9012, and live with the easy way to create 
uncodable documents, or do nothing and live with the fact that non-ASCII 
stuff does not work in ERT also in the cases when it would be encodable.

As a workaround for your problem, you can split your ERT inset in several 
parts, and put the korean text in standard mode.


Georg



Re: Korean Input Problem in tex Code mode on lyx 2.1.0

2014-06-20 Thread Georg Baum
Scott Kostyshak wrote:

> On Tue, Jun 17, 2014 at 8:55 AM, Seunghee  wrote:
>>
>> Hi, Scott,
>> thank you for your reply.
>> I have installed lyx2.2dev and tried to input Korean in the both of
>> modes.
>>
>> In the 'Program Listing' mode the problem is fixed, but not in the 'tex
>> mode'.
>>
>> I have found a difference between the both of modes.
>> Wenn I input alphabets in the 'program Listing' mode, the following
>> message appears:
>> "Font: Typewriter, text, Language: LaTeX"
>>
>> But in the 'tex mode'the following message appears:
>> "Font: Typewriter, LaTex text, Language: LaTeX"
> 
> Georg, do you know what's going on here?

Yes. The behaviour is by design. The explanation of the reason is a bit 
technical: Since version 1.5.0 LyX uses unicode internally, and .lyx files 
are encoded in utf-8. The big advantage of that compared to previous 
versions is that LyX can process and display text in almost all languages on 
earth. However, when LyX exports the document in LaTeX format for 
typesetting production, the situation is much more complicated. There are 
the modern LaTeX compilers like XeLaTeX and LuaLaTeX, which (like LyX) use 
unicode natively and take utf8-encoded input files, and there is the 
traditional LaTeX compiler which uses an 8-bit encoding internally and takes 
input files in different encodings, or even using multiple encodings in one 
file.

The difference between 'Program Listing' and 'tex mode' is the following: 
'Program Listing' is typeset using the listings LaTeX package, and that 
package supports a variety of different encodings. Therefore, when a 
'Program Listing' is output, LyX tries to find a suitable encoding which is 
supported by the listings package, and then converts the contents of the 
'Program Listing' into that encoding. This works usually. However, 'tex 
mode' means that the contents of the ERT inset is output 1:1, no 
transformation is allowed by definition (otherwise it would not be raw TeX 
anymore). This means that the contents must either be encodable in the 
currently active output encoding, or output would fail. Unfortunately, due 
to an internal limitation, we don't know the currently active output 
encoding where we need to know it (for LyX developers: latex_language-
>encoding() returns a static encoding, this needs to be dynamic and depend 
on the current environment). I want to change that in the long term, but 
this is the current situation.

Since you can get an uncodable document so easily with ERT insets, bug 9012 
was filed, and we fixed it by disallowing non-ASCII characters in ERT 
insets. Before the long term solution is implemented, we have two options: 
Reverting the fix for bug 9012, and live with the easy way to create 
uncodable documents, or do nothing and live with the fact that non-ASCII 
stuff does not work in ERT also in the cases when it would be encodable.

As a workaround for your problem, you can split your ERT inset in several 
parts, and put the korean text in standard mode.


Georg



Re: Embedding asymptote in Lyx

2014-06-07 Thread Georg Baum
Cyril wrote:

 Le 07/06/2014 04:52, Scott Kostyshak a écrit :

 I have little experience with this kind of thing, but you should take
 a look at the converters section in Help  Customization. You could
 create a format pdfA (or PDF (Asymptote) ) and then a converter
 latex - pdfA and add your commands there.

 Best,

 Scott


 Ty Scott,
 
 That is eactly what I did, but the problem is which commands ??.
 Since I have to execute 3 commands in just one converter. The
 documentation does'nt explain how to manage with this.

You need a wrapper script and define that one as converter. You can use the 
default converter shipped by LyX (scripts/convertDefault.py) as a template, 
and instead of calling convert, call your three commands in a row.


Georg



Re: Embedding asymptote in Lyx

2014-06-07 Thread Georg Baum
Cyril wrote:

 The converter is from what initial format ? I guess the final is PDF.
 But the initial one is LaTeX, LyX,...?

That depends. I guess you want to use pdflatex for direct pdf production. In 
that case, use LaTeX (pdflatex) (code name pdflatex in the preferences 
file), and your three commands are

pdflatex myfile.tex
asy myfile-*
pdflatex myfile.tex

If you use TeXLive, you can even use latexmk instead of a wrapper script 
(from 
http://asymptote.sourceforge.net/doc/LaTeX-usage.html):

latexmk -pdf myfile

The final format is the new PDF variant you need to define. Otherwise your 
new converter would overwrite the default, and this would cause errors for 
files without asymptote code. 


Georg



Re: Embedding asymptote in Lyx

2014-06-07 Thread Georg Baum
Cyril wrote:

 Le 07/06/2014 04:52, Scott Kostyshak a écrit :

 I have little experience with this kind of thing, but you should take
 a look at the converters section in Help  Customization. You could
 create a format pdfA (or PDF (Asymptote) ) and then a converter
 latex - pdfA and add your commands there.

 Best,

 Scott


 Ty Scott,
 
 That is eactly what I did, but the problem is which commands ??.
 Since I have to execute 3 commands in just one converter. The
 documentation does'nt explain how to manage with this.

You need a wrapper script and define that one as converter. You can use the 
default converter shipped by LyX (scripts/convertDefault.py) as a template, 
and instead of calling convert, call your three commands in a row.


Georg



Re: Embedding asymptote in Lyx

2014-06-07 Thread Georg Baum
Cyril wrote:

 The converter is from what initial format ? I guess the final is PDF.
 But the initial one is LaTeX, LyX,...?

That depends. I guess you want to use pdflatex for direct pdf production. In 
that case, use LaTeX (pdflatex) (code name pdflatex in the preferences 
file), and your three commands are

pdflatex myfile.tex
asy myfile-*
pdflatex myfile.tex

If you use TeXLive, you can even use latexmk instead of a wrapper script 
(from 
http://asymptote.sourceforge.net/doc/LaTeX-usage.html):

latexmk -pdf myfile

The final format is the new PDF variant you need to define. Otherwise your 
new converter would overwrite the default, and this would cause errors for 
files without asymptote code. 


Georg



Re: Embedding asymptote in Lyx

2014-06-07 Thread Georg Baum
Cyril wrote:

> Le 07/06/2014 04:52, Scott Kostyshak a écrit :
>>
>> I have little experience with this kind of thing, but you should take
>> a look at the converters section in Help > Customization. You could
>> create a format "pdfA" (or "PDF (Asymptote)" ) and then a converter
>> latex -> pdfA and add your commands there.
>>
>> Best,
>>
>> Scott
>>
>>
> Ty Scott,
> 
> That is eactly what I did, but the problem is "which commands ??".
> Since I have to execute 3 commands in just one converter. The
> documentation does'nt explain how to manage with this.

You need a wrapper script and define that one as converter. You can use the 
default converter shipped by LyX (scripts/convertDefault.py) as a template, 
and instead of calling convert, call your three commands in a row.


Georg



Re: Embedding asymptote in Lyx

2014-06-07 Thread Georg Baum
Cyril wrote:

> The converter is from what initial format ? I guess the final is PDF.
> But the initial one is LaTeX, LyX,...?

That depends. I guess you want to use pdflatex for direct pdf production. In 
that case, use "LaTeX (pdflatex)" (code name pdflatex in the preferences 
file), and your three commands are

pdflatex myfile.tex
asy myfile-*
pdflatex myfile.tex

If you use TeXLive, you can even use latexmk instead of a wrapper script 
(from 
http://asymptote.sourceforge.net/doc/LaTeX-usage.html):

latexmk -pdf myfile

The final format is the new PDF variant you need to define. Otherwise your 
new converter would overwrite the default, and this would cause errors for 
files without asymptote code. 


Georg



Re: Bug

2014-05-14 Thread Georg Baum
Patrick Dupre wrote:

  unusual contents found: [Unknown [sub [mathrm [char N mathalpha][char O
  mathalpha]] [char 2 mathalpha]]]

This means that LyX does not understand a math formula of that document. My 
first geuss would be that it has nothing to do with the OS our how you 
compiled LyX. This looks like a serious issue to me, which we need to 
investigate.

Could you please file a bug report at 
http://www.lyx.org/trac/wiki/BugTrackerHome and attach the document? If you 
can't publish it, you could also send it to me privately and I'll have a 
look, but without having the original document its is nearly impossible to 
investigate these kinds of bugs. If the document is really secret please do 
a bisection in with LyX 2.0.x and try to reduce it (removing first half of 
the document, seer if that fixes the problem, if yes continue with second 
half etc) until you find the formula which causes the problem.


Georg



Re: Bug

2014-05-14 Thread Georg Baum
Patrick Dupre wrote:

  unusual contents found: [Unknown [sub [mathrm [char N mathalpha][char O
  mathalpha]] [char 2 mathalpha]]]

This means that LyX does not understand a math formula of that document. My 
first geuss would be that it has nothing to do with the OS our how you 
compiled LyX. This looks like a serious issue to me, which we need to 
investigate.

Could you please file a bug report at 
http://www.lyx.org/trac/wiki/BugTrackerHome and attach the document? If you 
can't publish it, you could also send it to me privately and I'll have a 
look, but without having the original document its is nearly impossible to 
investigate these kinds of bugs. If the document is really secret please do 
a bisection in with LyX 2.0.x and try to reduce it (removing first half of 
the document, seer if that fixes the problem, if yes continue with second 
half etc) until you find the formula which causes the problem.


Georg



Re: Bug

2014-05-14 Thread Georg Baum
Patrick Dupre wrote:

>  unusual contents found: [Unknown [sub [mathrm [char N mathalpha][char O
>  mathalpha]] [char 2 mathalpha]]]

This means that LyX does not understand a math formula of that document. My 
first geuss would be that it has nothing to do with the OS our how you 
compiled LyX. This looks like a serious issue to me, which we need to 
investigate.

Could you please file a bug report at 
http://www.lyx.org/trac/wiki/BugTrackerHome and attach the document? If you 
can't publish it, you could also send it to me privately and I'll have a 
look, but without having the original document its is nearly impossible to 
investigate these kinds of bugs. If the document is really secret please do 
a bisection in with LyX 2.0.x and try to reduce it (removing first half of 
the document, seer if that fixes the problem, if yes continue with second 
half etc) until you find the formula which causes the problem.


Georg



Re: Lyx2.1 problem with metafile2eps converter

2014-05-13 Thread Georg Baum
aparsloe wrote:

 I was hasty in my response. In Adobe Reader X, under the Edit menu,
 there's the option Take a Snapshot. I assume this is the embedded tool
 referred to. When I copy a figure from the pdf and then go to paste it
 into LyX I get asked first to save the file, always as an .emf file
 although that can be changed to .png if I wish. The first one I paste
 into LyX reproduces the copied figure. Copying and pasting other figures
 (after saving in .emf format) generally insert into LyX  figures that
 are about 25 times too big. I have to scale to about 4% for the Adobe
 -- LyX -- Adobe round trip to reproduce a figure about the size of the
 original. But this doesn't happen always and seems to depend on whether
 I've saved a file at some point as .png (which seems to paste at the
 right size). So, it works for a one-off, but clearly not flawlessly for
 a number of copy-pastes.

Strange. We need somebody to debug LyX on windows.


Georg



Re: Lyx2.1 problem with metafile2eps converter

2014-05-13 Thread Georg Baum
aparsloe wrote:

 I was hasty in my response. In Adobe Reader X, under the Edit menu,
 there's the option Take a Snapshot. I assume this is the embedded tool
 referred to. When I copy a figure from the pdf and then go to paste it
 into LyX I get asked first to save the file, always as an .emf file
 although that can be changed to .png if I wish. The first one I paste
 into LyX reproduces the copied figure. Copying and pasting other figures
 (after saving in .emf format) generally insert into LyX  figures that
 are about 25 times too big. I have to scale to about 4% for the Adobe
 -- LyX -- Adobe round trip to reproduce a figure about the size of the
 original. But this doesn't happen always and seems to depend on whether
 I've saved a file at some point as .png (which seems to paste at the
 right size). So, it works for a one-off, but clearly not flawlessly for
 a number of copy-pastes.

Strange. We need somebody to debug LyX on windows.


Georg



Re: Lyx2.1 problem with metafile2eps converter

2014-05-13 Thread Georg Baum
aparsloe wrote:

> I was hasty in my response. In Adobe Reader X, under the Edit menu,
> there's the option Take a Snapshot. I assume this is the "embedded tool"
> referred to. When I copy a figure from the pdf and then go to paste it
> into LyX I get asked first to save the file, always as an .emf file
> although that can be changed to .png if I wish. The first one I paste
> into LyX reproduces the copied figure. Copying and pasting other figures
> (after saving in .emf format) generally insert into LyX  figures that
> are about 25 times too big. I have to scale to about 4% for the Adobe
> --> LyX --> Adobe round trip to reproduce a figure about the size of the
> original. But this doesn't happen always and seems to depend on whether
> I've saved a file at some point as .png (which seems to paste at the
> right size). So, it works for a one-off, but clearly not flawlessly for
> a number of copy-pastes.

Strange. We need somebody to debug LyX on windows.


Georg



Re: Lyx2.1 problem with metafile2eps converter

2014-05-12 Thread Georg Baum
aparsloe wrote:

 On 11/05/2014 8:31 a.m., didiergab...@free.fr wrote:
 Hi,

 I have problem wth lyx2.1 (on windows 7 64bits)... I often copy images
 from adobe reader with the embedded tool and paste directly on lyx
 (ctrl+V)... I have a error message Can not open Metafle to EPS converter
 printer (without i on Metafle :o)

 When I try the conversion directly from Lyx2.1 dir\bin\metafile2eps.exe
 the same error occur... Any idea ?

Is the virtual printer installed which is used by metafile2eps.exe? Maybe 
something wnet wrong during installation.

 I've also got LyX2.1 on  64 bit Windows 7, and Adobe Reader X, and the
 copy and paste works without problems, so this looks like a problem at
 your end rather than with LyX.

Also for copying vector images? metafile2eps.exe is not used for bitmap 
images or text. You can easily see whether a vector imagtes was copied by 
looking at the type of the copied image: If it is eps, the original image 
was in vector format, and metafile2eps.exe worked.


Georg



Re: Lyx2.1 problem with metafile2eps converter

2014-05-12 Thread Georg Baum
aparsloe wrote:

 On 11/05/2014 8:31 a.m., didiergab...@free.fr wrote:
 Hi,

 I have problem wth lyx2.1 (on windows 7 64bits)... I often copy images
 from adobe reader with the embedded tool and paste directly on lyx
 (ctrl+V)... I have a error message Can not open Metafle to EPS converter
 printer (without i on Metafle :o)

 When I try the conversion directly from Lyx2.1 dir\bin\metafile2eps.exe
 the same error occur... Any idea ?

Is the virtual printer installed which is used by metafile2eps.exe? Maybe 
something wnet wrong during installation.

 I've also got LyX2.1 on  64 bit Windows 7, and Adobe Reader X, and the
 copy and paste works without problems, so this looks like a problem at
 your end rather than with LyX.

Also for copying vector images? metafile2eps.exe is not used for bitmap 
images or text. You can easily see whether a vector imagtes was copied by 
looking at the type of the copied image: If it is eps, the original image 
was in vector format, and metafile2eps.exe worked.


Georg



Re: Lyx2.1 problem with metafile2eps converter

2014-05-12 Thread Georg Baum
aparsloe wrote:

> On 11/05/2014 8:31 a.m., didiergab...@free.fr wrote:
>> Hi,
>>
>> I have problem wth lyx2.1 (on windows 7 64bits)... I often copy images
>> from adobe reader with the embedded tool and paste directly on lyx
>> (ctrl+V)... I have a error message "Can not open Metafle to EPS converter
>> printer" (without "i" on "Metafle" :o)
>>
>> When I try the conversion directly from Lyx2.1 dir\bin\metafile2eps.exe
>> the same error occur... Any idea ?

Is the virtual printer installed which is used by metafile2eps.exe? Maybe 
something wnet wrong during installation.

> I've also got LyX2.1 on  64 bit Windows 7, and Adobe Reader X, and the
> copy and paste works without problems, so this looks like a problem at
> your end rather than with LyX.

Also for copying vector images? metafile2eps.exe is not used for bitmap 
images or text. You can easily see whether a vector imagtes was copied by 
looking at the type of the copied image: If it is eps, the original image 
was in vector format, and metafile2eps.exe worked.


Georg



Re: [GSoC 2014] Introduction

2014-04-28 Thread Georg Baum
Prannoy Pilligundla wrote:

 Hi Everyone,
 
 I am Prannoy Pilligundla, a second year undergrad from India. I will be
 working on Roundtrip Conversion from Lyx to ODT throughout the Summer as a
 part of Google Summer of Code 2014. First of all I want to thank the
 community for keeping faith in my abilities and selecting my proposal, I
 will definitely put in my best efforts to complete this project. Also
 Congratulations to the Co-GSoCer Sushant Raikar, all the best to you too.

Welcome to both of you! I might not always be the quickest one to respond, 
but I'll try to help wherever needed.


Georg



Re: [GSoC 2014] Introduction

2014-04-28 Thread Georg Baum
Prannoy Pilligundla wrote:

 Hi Everyone,
 
 I am Prannoy Pilligundla, a second year undergrad from India. I will be
 working on Roundtrip Conversion from Lyx to ODT throughout the Summer as a
 part of Google Summer of Code 2014. First of all I want to thank the
 community for keeping faith in my abilities and selecting my proposal, I
 will definitely put in my best efforts to complete this project. Also
 Congratulations to the Co-GSoCer Sushant Raikar, all the best to you too.

Welcome to both of you! I might not always be the quickest one to respond, 
but I'll try to help wherever needed.


Georg



Re: [GSoC 2014] Introduction

2014-04-28 Thread Georg Baum
Prannoy Pilligundla wrote:

> Hi Everyone,
> 
> I am Prannoy Pilligundla, a second year undergrad from India. I will be
> working on Roundtrip Conversion from Lyx to ODT throughout the Summer as a
> part of Google Summer of Code 2014. First of all I want to thank the
> community for keeping faith in my abilities and selecting my proposal, I
> will definitely put in my best efforts to complete this project. Also
> Congratulations to the Co-GSoCer Sushant Raikar, all the best to you too.

Welcome to both of you! I might not always be the quickest one to respond, 
but I'll try to help wherever needed.


Georg



Re: Using LyX for calculations (was Rendering of LyX's math screen fonts.)

2013-11-08 Thread Georg Baum
Jerry wrote:

 I know that LyX has hooks for some computer algebra systems (Mathematica,
 Maple, Maxima) and Octave. I have played with these a little (Octave and
 Mathematica) and it seems potentially useful but possibly not fully
 developed in LyX.

It is only very basic (and therefore not much advertised).

 I'm curious to know how you and others have used this corner of LyX.

I did not use this interface. I did manual calculations involving bigger 
equations that I would otherwise have done on paper. I used LyX only because 
I could easily incorporate corrections (and print the result again for final 
proof reading).


Georg



Re: Using LyX for calculations (was Rendering of LyX's math screen fonts.)

2013-11-08 Thread Georg Baum
Jerry wrote:

 I know that LyX has hooks for some computer algebra systems (Mathematica,
 Maple, Maxima) and Octave. I have played with these a little (Octave and
 Mathematica) and it seems potentially useful but possibly not fully
 developed in LyX.

It is only very basic (and therefore not much advertised).

 I'm curious to know how you and others have used this corner of LyX.

I did not use this interface. I did manual calculations involving bigger 
equations that I would otherwise have done on paper. I used LyX only because 
I could easily incorporate corrections (and print the result again for final 
proof reading).


Georg



Re: Using LyX for calculations (was Rendering of LyX's math screen fonts.)

2013-11-08 Thread Georg Baum
Jerry wrote:

> I know that LyX has hooks for some computer algebra systems (Mathematica,
> Maple, Maxima) and Octave. I have played with these a little (Octave and
> Mathematica) and it seems potentially useful but possibly not fully
> developed in LyX.

It is only very basic (and therefore not much advertised).

> I'm curious to know how you and others have used this corner of LyX.

I did not use this interface. I did manual calculations involving bigger 
equations that I would otherwise have done on paper. I used LyX only because 
I could easily incorporate corrections (and print the result again for final 
proof reading).


Georg



Re: Rendering of LyX's math screen fonts.

2013-11-07 Thread Georg Baum
Rudi Gaelzer wrote:

 So I ask you LyXperts: is it possible to configure the math mode editor so
 that it uses also mathabx and other different math fonts?  The roadmap to
 LyX 2.1 mentions enhanced support for math font selection (OpenType fonts)
 and support ofr cropped PDF/EPS.  However, AFAIU, these enhancements will
 have an effect on IP and on the exported document.  Seems to me that the
 math editor will still use the same screen fonts.  Or am I wrong?

You are right, the mentioned features do not affect the look of the math 
editor. However, there are some new symbols in 2.1, mainly from stmaryrd.sty 
and mathtools.sty. To some extent you can also add some on your own: The 
screen appearance of math symbols is defined in the file lib/symbols, which 
contains some very basic documentation for 2.1.
Basically, there are three kinds of symbol definitions in that file:

1) symbols supported by special insets (like the decorations)
2) symbols supported by fonts (like the ones from fontmath.ltx)
3) symbols without any builtin support

Adding symbols of type 1) and 2) requires some programming in LyX, and 2) 
requires also a true type font containing the symbols in a certain order, 
but symbols of type 3) can easily be added by users: All lines starting with 
\def are of this kind. For example, you could define \partialslash like 
this:

\def\partialslash{\partial\kern-12mu/}

The slash is a bit too short, but maybe there is a longer one already 
supported by mathed, which you could use instead. Although this looks like a 
TeX macro definition, it is not used for the output, only for display in 
LyX. There is basically no documentation how exactly this \def works, you 
have to use trial and error. You could also make the mathabx package load 
automatically if this symbol is used (works only for packages in the 
compiled in feature list of LyX, and mathabx is in there):

\def\partialslash{\partial\kern-12mu/} mathabx

I strongly advise against doing so, because this makes your LyX document 
depend on your personal installation, and it would not typeset on vanilla 
installations. This feature is rather for symbols distributed with the 
official symbols file.

Finally, if you want some symbols to appear officially in LyX, you could add 
them to bug , but please note that font changing packages like txfonts 
will not be used.


Georg


PS: It is funny that you also use the math editor for calculations. I used 
to do that a lot for my thesis, but always thought I was the only one.






Re: Rendering of LyX's math screen fonts.

2013-11-07 Thread Georg Baum
Rudi Gaelzer wrote:

 So I ask you LyXperts: is it possible to configure the math mode editor so
 that it uses also mathabx and other different math fonts?  The roadmap to
 LyX 2.1 mentions enhanced support for math font selection (OpenType fonts)
 and support ofr cropped PDF/EPS.  However, AFAIU, these enhancements will
 have an effect on IP and on the exported document.  Seems to me that the
 math editor will still use the same screen fonts.  Or am I wrong?

You are right, the mentioned features do not affect the look of the math 
editor. However, there are some new symbols in 2.1, mainly from stmaryrd.sty 
and mathtools.sty. To some extent you can also add some on your own: The 
screen appearance of math symbols is defined in the file lib/symbols, which 
contains some very basic documentation for 2.1.
Basically, there are three kinds of symbol definitions in that file:

1) symbols supported by special insets (like the decorations)
2) symbols supported by fonts (like the ones from fontmath.ltx)
3) symbols without any builtin support

Adding symbols of type 1) and 2) requires some programming in LyX, and 2) 
requires also a true type font containing the symbols in a certain order, 
but symbols of type 3) can easily be added by users: All lines starting with 
\def are of this kind. For example, you could define \partialslash like 
this:

\def\partialslash{\partial\kern-12mu/}

The slash is a bit too short, but maybe there is a longer one already 
supported by mathed, which you could use instead. Although this looks like a 
TeX macro definition, it is not used for the output, only for display in 
LyX. There is basically no documentation how exactly this \def works, you 
have to use trial and error. You could also make the mathabx package load 
automatically if this symbol is used (works only for packages in the 
compiled in feature list of LyX, and mathabx is in there):

\def\partialslash{\partial\kern-12mu/} mathabx

I strongly advise against doing so, because this makes your LyX document 
depend on your personal installation, and it would not typeset on vanilla 
installations. This feature is rather for symbols distributed with the 
official symbols file.

Finally, if you want some symbols to appear officially in LyX, you could add 
them to bug , but please note that font changing packages like txfonts 
will not be used.


Georg


PS: It is funny that you also use the math editor for calculations. I used 
to do that a lot for my thesis, but always thought I was the only one.






  1   2   3   4   5   6   7   8   9   10   >