This is a question concerning two areas. OSs and creating pdf-documents from LaTex-scripts.
The point is the following. When I create a pdf-file under Linux using pdflatex, I can open the file under Windows only with some very specific and often proprietary tools. I have installed
Texlive on my Computer running Ubuntu here. This file-opening-thing was already an issue in a print-shop where only Windows was running and the owner was not willed (and able) to try to open e.g with Sumatra-pdf, what could have worked. ...
I had to and could fix the problem by compiling the code under Windows where I have installed the MikTex-distribution (I think it also uses
pdfLaTeX) and everything worked. Unfortunately a simple unix2dos won't do the task, unix2dos only converts depending on the conversion-direction carriage-returns and can do some recoding I think.
Whatsoever, I tried it anyway and it tells me that a binary symbol 0x1C was found in line 8. I did a little research. This is the control charakter (fs) - file seperator. It is possible, that at this position a png-file is placed. In this thread someone resolved the problem not via "ghostscripting" but via converting png to pdf. How to overcome Acrobat Reader error 131 with a pdfLaTeX doc?
Anyway, I think such procedures should not be necessary. What could be the reason that all
MikTex-documents can be opened under Linux but not vice versa? Is this a bug with in the programme
pdfLaTeX or rather something else just depending on my installation or a unpredictably occurring thing? But against that stands that it works very well with `MikTeX. What can we do to overcome that.