mailing-list for TeXmacs Users

[Giovanni Piredda <address@hidden>]

On 20.11.21 12:07, Frank wrote:
> Meanwhile, I searched among the source code, but I failed to locate the 
> checker. There is a line related:
> https://github.com/arXiv/arxiv-submission-ui/blob/5cd67e15db72bb8aa4acf686fb3aa8b41727580a/submit/controllers/ui/new/process.py#L202
> but I don't see where the code could raise an error with reason containing "from 
> TeX", say, in
> https://github.com/arXiv/arxiv-submission-core/blob/develop/core/arxiv/submission/process/process_source.py

Perhaps there is some code here: 
https://github.com/arXiv/arxiv-submission-core/pull/77


> Maybe you could try start a petition at https://www.change.org/ and then 
> interested people sign it.


IMHO let us see first what is the effect of the pull request and (if 
that happens) requests to the help email from several people, then let 
us consider a petition.

G.



> Best,
> Frank
>
> 于 2021年11月20日 UTC 上午10:46:29, Giovanni Piredda <address@hidden> 写到:
> > Joris told me that he already did it, with no effect. But some time
> > passed, so maybe one can try again. If different people do the same
> > report, it may increase the chance of a response, so a good strategy
> > could be that *all* interested people submit an issue report.
> >
> > Giovanni
> >
> > On 20.11.21 11:31, Frank wrote:
> > > Hello,
> > >
> > > According to
> > > https://github.com/arXiv/arxiv-submission-ui/blob/develop/submit/controllers/ui/new/reasons.py
> > > we should report the issue to address@hidden
> > >
> > > Best,
> > > Frank
> > >
> > > 于 2021年11月19日 UTC 下午3:34:41, Giovanni Piredda <address@hidden> 写到:
> > > > I could post an issue in the bug tracker of the ArXiv
> > > > (https://github.com/arXiv/arxiv-base/issues), but I would like to hear
> > > >from you before I do that. Do you think it is better classifying it 
> > > > under "bug" or something else?
> > > >
> > > > G.
> > > >
> > > > Am 19.11.2021 um 16:29 schrieb TeXmacs:
> > > > > Dear Giovanni,
> > > > >
> > > > > If someone could get a patch accepted that solves this problem at ArXiv,
> > > > > then that would be very nice.  But I personally have no time for this;
> > > > > I just changed 'TeXmacs' to 'T e X m a c s' for the Pdf creator;
> > > > > this is a bit ugly, bit it will do for now.
> > > > >
> > > > > Best wishes, --Joris
> > > > >
> > > > >
> > > > > On Fri, Nov 19, 2021 at 02:48:15PM +0000, Giovanni Piredda wrote:
> > > > > > Maybe the examination of the code in https://github.com/arXiv could
> > > > > > also help.
> > > > > >
> > > > > > Perhaps they accept pull requests.
> > > > > >
> > > > > > Giovanni
> > > > > >
> > > > > >
> > > > > > Am 19.11.2021 um 11:49 schrieb TeXmacs:
> > > > > > > Dear Basile,
> > > > > > >
> > > > > > > Thanks for this extremely useful feedback.
> > > > > > >
> > > > > > > It is still annoying to not use our real name for the creator/producer.
> > > > > > > If I make it 'T e X m a c s', then does that work?
> > > > > > >
> > > > > > > Best wishes, --Joris
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Nov 19, 2021 at 07:49:47AM +0100, Basile Audoly wrote:
> > > > > > > > Dear Joris,
> > > > > > > >
> > > > > > > > I did a few more tests. Bottomline is that arXiv rejects any PDF document that matches 
> > > > > > > > the string "*tex*" in the /Creator or /Producer fields, and the match is 
> > > > > > > > case-insensitive.
> > > > > > > >
> > > > > > > > Changing fonts actually has no effect (contrary to what I was writing before).
> > > > > > > >
> > > > > > > > To be specific, changing both /Creator or /Producer to 'T.Xmacs' works, but 
> > > > > > > > changing to 'Texmacs' or 'GNU Texmacs' fails.
> > > > > > > >
> > > > > > > > TeX Gyre fonts (Bonum) works just as well, even though "TeX" appears in the 
> > > > > > > > /BaseFont field: this field seems to be ignored (which makes sense).
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Basile
> > > > > > > >
> > > > > > > > > Le 11 nov. 2021 à 19:54, TeXmacs <address@hidden> a écrit :
> > > > > > > > >
> > > > > > > > > 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