Single Column Indices

[Karthik Tayur]

Hi,
How does one obtain single column indices? This question has been raised
before as regards LaTeX. How does one do it with LyX?
Since the default processor appears to be xindy from the documentation, I
will need to modify the relevant style?

Regards
K

Re: Index does not print

[Karthik Tayur]

Sorry for the delayed reply.
I tried to replicate the problem in a file as small as possible (as
suggested). I couldn't reproduce it.
On that note, for some reason, I had encoding problems with the same .lyx
document. I used iconv to resolve that problem.



On 25 April 2017 at 18:40, Richard Heck  wrote:

> On 04/24/2017 11:41 PM, Karthik Tayur wrote:
>
> Replacing all special characters (Insert>Symbols) in the document allows
> me to print the indices. I had inserted the pilcrow symbol in the document.
> When resolving a problem with conversion I replaced all the symbols in my
> document with text.
> Any idea why this works? Are special symbols not allowed in footnote
> spaces?
>
>
> If you could produce a small file, as small as possible, that illustrates
> the problem, it would make it easier to investigate. The reason it should
> be small is so we can be sure where the problem really is.
>
> Richard
>
>
>
>
> On 25 April 2017 at 03:42, Karthik Tayur  wrote:
>
>> Hello,
>> I have been using LyX for some time now. It has been great. Previously
>> the multiple index function worked well.
>> Today, while I was able to insert indices, they wouldn't print. Only
>> disabling the multiple index option under Settings in a fresh document
>> allows printing of the singular index.
>> Any suggestions as to how I might go about solving this problem? I
>> suspect that the files needed for \printindex simply don't compile, as the
>> logs seem to suggest.
>>
>> System Details: Arch Linux with KDE, LyX 2.2.2
>>
>> Regards
>>
>
>
>

Re: texlive in Debian

[Wolfgang Engelmann]

Am 26.04.2017 um 20:43 schrieb Guenter Milde:

On 2017-04-25, Wolfgang Engelmann wrote:

I am frequently reminded by the Debian system to install texlive, which
is, however, of 2014, whereas I am using the one of 2016.
If I click the various texlive packages away (a bit cumbersome, around
14 or so packages) I am told that it is needed for removing a security
risk.
What should I do? I would rather like to stick to the 2015 version. Does
this version give me the security? Or should I install the 2016 version?
Or wait for the 2017 version?

You could install texlive 2016 from Debian/testing
--- or a "dummy texlive" to meet dependencies.

Günter


Thanks, Frank and Günter,
for your advices. I will use the way described in
https://www.tug.org/texlive/debian.html
under 'Integrating vanilla TeX Live with Debian'
and change in the summer to 2017, when it is available.
Wolfgang

Re: texlive in Debian

[Guenter Milde]

On 2017-04-25, Wolfgang Engelmann wrote:
> I am frequently reminded by the Debian system to install texlive, which 
> is, however, of 2014, whereas I am using the one of 2016.

> If I click the various texlive packages away (a bit cumbersome, around 
> 14 or so packages) I am told that it is needed for removing a security 
> risk.

> What should I do? I would rather like to stick to the 2015 version. Does 
> this version give me the security? Or should I install the 2016 version? 
> Or wait for the 2017 version?

You could install texlive 2016 from Debian/testing
--- or a "dummy texlive" to meet dependencies.

Günter

Re: LyX 2.3 alpha nomenclature

[Richard Heck]

On 04/26/2017 06:31 AM, F M Salter wrote:
>
> Nomenclature entries produce pdf showing  $x$ not /x!/
>

It would be helpful if you could produce a small (minimal) test file.
It would also be best sent to lyx-devel (cc'd here).

Richard

LyX 2.3 alpha nomenclature

[F M Salter]

Nomenclature entries produce pdf showing  $x$ not /x!/

Regards

Frank Salter

Re: texlive in Debian

[F M Salter]

On 25/04/17, Wolfgang Engelmann wrote:

> I am frequently reminded by the Debian system to install texlive,
> which is, however, of 2014, whereas I am using the one of 2016.If I
> click the various texlive packages away (a bit cumbersome, around 14
> or so packages) I am told that it is needed for removing a
> security risk.What should I do? I would rather like to stick to the
> 2015 version. Does this version give me the security? Or should I
> install the 2016 version? Or wait for the 2017 version?
I have used texlive with debian for several years and do not share the
same experience.  At the moment I have jessie installed and I am using 2
more virtual installations for testing purposes.  The same is true for
these installations.
 I believe the problem arises with another debian program which uses
latex.  I only install debian packages which do not requires latex
support.  For example if you install kde-full, it will install its own
version of texlive to meet its dependencies.
 A bash-script, using apt-get, to install the packages you actually
use is most helpful for easing this process.  I initially created one
from bash's history using grep and have refined it over time to select
some of debian's own packages and where appropriate obtain from other
sources.  The reason for one of virtual machines is to try the new 2.3.x
series of lyx with the 2017 texlive.
 Hope this is of some help.
> Thanks for help.
> Wolfgang
Regards
Frank Salter