- From: TeXmacs <address@hidden>
- To: address@hidden
- Subject: Re: working around arXiv' overshoot
- Date: Thu, 11 Nov 2021 19:54:05 +0100
Hi Basile,
This is a very interesting hack.
It would be nice to have some volunteers to investigate this further.
Question 1: if you replace 'TeXmacs' by 'Texmacs' or 'GNU Texmacs' instead of
'T.Xmacs', does it still work?
Question 2: could someone please try with any of the TeX Gyre fonts (which
also have TeX in their name)?
Question 3: if you replace 'Computer Modern' with 'Knuth's Modern Font' and
(if necessary) occurrences of
CMR, CMMI, CMEX, etc. with something else (just on lines with /FontName or
/BaseFont), then does this
also do the trick?
Best wishes, --Joris
On Sat, Jul 10, 2021 at 06:52:11PM +0200, Basile Audoly wrote:
>
Hi everyone,
>
>
arXiv incorrectly identifies PDF documents produced by TeXmacs as if they
>
had been produced by LaTeX and blocks them, see my previous email.
>
>
Here a dirty but simple hack to work around this:
>
* change the document font from Computer Modern (a.k.a. Roman) to
>
Optima—any other font except CM will probably work as well
>
* export to PDF
>
* open the PDF document in emacs, search for the string "TeXmacs" and
>
replace the two occurrences corresponding to the PDF Creator and Producer
>
with "T.Xmacs"
>
>
Of course, this prevents arXiv from being aware of the full content of the
>
document. Exporting to LaTeX is still a viable (but more complicated)
>
alternative.
>
>
Basile
>
- Re: working around arXiv' overshoot, TeXmacs, 11/11/2021
Archive powered by MHonArc 2.6.19.