Re: Aliasing, xyling, ps2pdf

[Maria Gouskova]

On Wed, Jan 6, 2016 at 5:14 PM, Georg Baum
 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.


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?

Re: Aliasing, xyling, ps2pdf

[Guenter Milde]

On 2016-01-07, Georg Baum wrote:
>> On Wed, Jan 6, 2016 at 5:14 PM, Georg Baum

...

> BTW, pdftops is better than pdf2ps according to 
> http://stefaanlippens.net/pdf2ps_vs_pdftops and also my own experience.

To sum this up: 
  
  Problem with pdf2ps: fonts are converted to bitmap fonts 
  
  With pdftops [...], the conversion takes less time, the resulting file
  is smaller, and fonts are better preserved. 


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?  

Should I file a bug report?  


Thanks,

Günter

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

[Michael Berger]

On 01/07/2016 10:39 PM, Georg Baum wrote:

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

Good morning,
I follow this with great interest but as a simple user can only report 
what I observed.

And there is more, may be or may not be related to this very issue:
With 'Mark foreign languages' _*always ON*_ in Tools > Preferences > 
Language settings, the foreign (secondary languages) sometimes do and 
sometimes do not show blue underlines apparently depending on the 
citation style (and/or biblatex?).


For instance I have no blue underlinings with
apa, natbib author-year, jurabib

And I do have blue underlinings with
chicago, oscola

So, 'Mark foreign languages' seems to be overruled by some other more 
dominant setting.
Again all my many documents correctly print 'page' (and NOT 'Seite') 
with "Set languages globally" deactivated.
Furthermore, it does so regardless whether the secondary language(s) is 
given before the primary language or not.


Cheers,
Michael Berger

Re: Aliasing, xyling, ps2pdf

[Georg Baum]

Maria Gouskova wrote:

> On Wed, Jan 6, 2016 at 5:14 PM, Georg Baum
>  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'

[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

[Maria Gouskova]

On Thu, Jan 7, 2016 at 3:35 PM, Georg Baum
 wrote:
> Maria Gouskova wrote:
>
>> On Wed, Jan 6, 2016 at 5:14 PM, Georg Baum
>>  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
>

Okay, thanks--I probably won't do this since I have found a workaround
for my original problem, and the figures and trees all come out
looking good now. I don't usually use ps2pdf anyway, it was only
because of xyling's peculiarity.

By the way, if anyone stumbles upon this discussion in the future, the
solution was to edit the xyling.sty file as follows:

Original:
\RequirePackage[color,all, dvips]{xy}

Change to:
\RequirePackage[color,all]{xy}

This will take away the ability to create color branches in a tree,
which is probably not a big loss. I can't remember ever seeing colored
branches in a published linguistics paper.