[XeTeX] embedding PDF, 1.4 vs. 1.5

2014-06-17 Thread maxwell
Late last year, I ran into a problem in which I could embed a PDF v1.4, 
but not v1.5 (I have not tried this with newer versions of PDFs, which 
are now up to 1.7).  The problem and its work-around are described here:

   http://tug.org/mailman/htdig/xetex/2012-October/023677.html
also
   http://tug.org/pipermail/xetex/2012-December/023869.html
and in the preceding and following messages in those threads.

The problem bit us again today.  Fortunately, we now know the 
work-around.  But my question is whether this is likely to get fixed in 
some future version of xetex?  (We're using the TeXLive 2013 version = 
3.1415926-2.5-0..3-2013060708.)


   Mike Maxwell



--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex


Re: [XeTeX] embedding PDF, 1.4 vs. 1.5

2014-06-17 Thread maxwell

On 2014-06-17 11:31, maxwell wrote:

Late last year, I ran into a problem in which I could embed a PDF
v1.4, but not v1.5 (I have not tried this with newer versions of PDFs,
which are now up to 1.7).  The problem and its work-around are
described here:
   http://tug.org/mailman/htdig/xetex/2012-October/023677.html
also
   http://tug.org/pipermail/xetex/2012-December/023869.html


The above work around involved a double conversion using pdf2ps, from 
PDF to PS and back again to PDF.  If you happen to own a copy of Adobe 
Acrobat, Chris Green ran into another way to do it, documented here:

http://grok.lsu.edu/Article.aspx?articleId=9869
I don't know whether there are quality differences using these two 
routes.


   Mike Maxwell



--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex


Re: [XeTeX] embedding PDF, 1.4 vs. 1.5

2014-06-17 Thread Heiko Oberdiek
On 17.06.2014 17:38, maxwell wrote:
 On 2014-06-17 11:31, maxwell wrote:
 Late last year, I ran into a problem in which I could embed a PDF
 v1.4, but not v1.5 (I have not tried this with newer versions of PDFs,
 which are now up to 1.7).  The problem and its work-around are
 described here:
http://tug.org/mailman/htdig/xetex/2012-October/023677.html
 also
http://tug.org/pipermail/xetex/2012-December/023869.html
 
 The above work around involved a double conversion using pdf2ps, from
 PDF to PS and back again to PDF.

There are other less invasive options:

  pdftk old.pdf cat output new.pdf

Or use another PDF library for reading/writing. When the file
is written, PDF object compression of PDF-1.5 must be disabled.

Yours sincerely
  Heiko Oberdiek




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex


Re: [XeTeX] FakeBold vs TikZ

2014-06-17 Thread Ross Moore
Hi Stefan, Marcin, and others,

On 17/06/2014, at 7:29 AM, Stefan Solbrig wrote:

 Hi,
 
 Just compiled the document under TeX Live 2013 (all updates till the 
 freeze) and still no dot.

Interesting.

I just tried with TeXLive 2013 and 2014 on different Macs.

2013 has the dot!
2014 does *not* have the dot.

For the 2013 installation we have xdvipdfmx-0.7.9
For the 2014 installation,  xdvipdfmx  is version  20140317

I tried using  xelatex -no-pdf  to keep the  .xdv  file.
Then renamed these and copied to the other machine, for processing
with the other version of  xdvipdfmx .
If this would work, then it could identify whether the problem
was in  xdvipdfmx  or due to what is put into the .xdv  file.

No joy came from this test.
Instead, all I get is a fatal error:   Invalid TFM ID: 0 .


It seems that one cannot break up the processing any more,
or at least not in the simple-minded way.
Would one of the developers please explain how to do this 
kind of testing now.



Earlier testing with TeX Live 2012, with  xdvipdfmx-0.7.8 
was just giving the similar error

 Output written on Tikz-test.xdv (1 page, 4856 bytes).
 Transcript written on Tikz-test.log.
 /usr/local/texlive/2012/bin/x86_64-darwin/xdvipdfmx
 Tikz-test.xdv - Tikz-test.pdf
 [1
 ** ERROR ** TFM: Invalid TFM ID: 0
 
 Output file removed.




Cheers,

Ross


Ross Moore   ross.mo...@mq.edu.au 
Mathematics Department   office: E7A-206  
Macquarie University tel: +61 (0)2 9850 8955
Sydney, Australia  2109  fax: +61 (0)2 9850 8114





--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex


Re: [XeTeX] FakeBold vs TikZ

2014-06-17 Thread Herbert Schulz

On Jun 17, 2014, at 7:53 PM, Ross Moore ross.mo...@mq.edu.au wrote:

 
 Interesting.
 
 I just tried with TeXLive 2013 and 2014 on different Macs.
 
 2013 has the dot!
 2014 does *not* have the dot.
 

Howdy,

That's strange... I saw no dot with either 2013 or 2014, both on Mac. Was you 
test on Linux?

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)







--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex


Re: [XeTeX] FakeBold vs TikZ

2014-06-17 Thread Khaled Hosny
On Wed, Jun 18, 2014 at 10:53:40AM +1000, Ross Moore wrote:
 It seems that one cannot break up the processing any more,
 or at least not in the simple-minded way.
 Would one of the developers please explain how to do this 
 kind of testing now.

So called “native” fonts (AKA non-TFM fonts) are now stored in the XDV
files using their full path not font name, so you can’t process XDV
files using such fonts uless you have fonts in the exact same location
(but whether this relates to the error you are seeing or not, I don’t
no).

Regards,
Khaled




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex


Re: [XeTeX] FakeBold vs TikZ

2014-06-17 Thread Herbert Schulz

On Jun 17, 2014, at 11:04 PM, Khaled Hosny khaledho...@eglug.org wrote:

 On Wed, Jun 18, 2014 at 10:53:40AM +1000, Ross Moore wrote:
 It seems that one cannot break up the processing any more,
 or at least not in the simple-minded way.
 Would one of the developers please explain how to do this 
 kind of testing now.
 
 So called “native” fonts (AKA non-TFM fonts) are now stored in the XDV
 files using their full path not font name, so you can’t process XDV
 files using such fonts uless you have fonts in the exact same location
 (but whether this relates to the error you are seeing or not, I don’t
 no).
 
 Regards,
 Khaled

Howdy,

Another Hmmm... I have the Latin Modern otf fonts set up as System Fonts (in 
~/Library/Fonts). Could that be the reason I don't see the dot in either TL2013 
or TL2014?

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)







--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex