kvafa / bidi

Bidirectional typesetting in plain TeX and LaTeX, using XeTeX
https://ctan.org/pkg/bidi
6 stars 1 forks source link

Large banner in output is inappropriate #32

Open eyalroz opened 11 months ago

eyalroz commented 11 months ago

Whenever I use the bidi.sty package/style file, I get a long banner (25 lines!) introducing it. This boilerplate is:

Please remove it entirely, or at the very list - limit yourself to a single package-describing line.

Check/indicate

Minimal example showing the issue

% !TEX TS-program = XeLaTeX
% !TEX encoding = UTF-8 Unicode

\documentclass{article}            % or some other class

  % Any packages other than the bidi package must be loaded here

  % The bidi package must be loaded as the last package
\usepackage[%
    % Any bidi package option goes here
]{bidi}

  % Any preamble code goes here

\begin{document}

Hello world

\end{document}

Expected behavior

Log should say:

(/usr/share/texlive/texmf-dist/tex/xelatex/bidi/bidi.sty)

and that's it.

Log and PDF files

Relevant part:

(/usr/share/texlive/texmf-dist/tex/xelatex/bidi/bidi.sty
****************************************************
* 
* bidi package (Bidirectional typesetting in
* plain TeX and LaTeX, using XeTeX engine)
* 
* Description: A convenient interface for
* typesetting bidirectional texts in plain TeX
* and LaTeX. The package includes adaptations
* for use with many other commonly-used packages.
* 
* Copyright (c) 2007--2023 Vafa Khalighi
* Copyright (c) 2018--2020 bidi-tex GitHub organization
* 
* v39.7 (Release Serge Lang), 2023/01/18
* 
* License: LaTeX Project Public License, version
* 1.3c or higher (your choice)
* 
* Location on CTAN: /macros/xetex/latex/bidi
* 
* Issue tracker: https://github.com/kvafa/bidi/issues
* 
* Discussions: https://github.com/kvafa/bidi/discussions
* 
* Primary author of bidi package: Vafa Khalighi.
* 
****************************************************
Udi-Fogiel commented 10 months ago

Until it will be fixed, you can do the following workaround

\documentclass{article} 
\let\origtypeout\typeout
\def\typeout#1{\let\typeout\origtypeout}
\usepackage{bidi}
\begin{document}

    Hello world

\end{document}
eyalroz commented 10 months ago

You might also want to disable the bidi's enddocument hook as the release information is for some reason cluttering the pdf custom properties

This is interesting, but is a matter for another bug report. Can you please file it and explain what exactly is being cluttered and what the result is?

eyalroz commented 10 months ago

Until it will be fixed, you can do the following workaround

I might do that in my own document, but I'm a document class author, and it's probably better for me to avoid such tricks.

kvafa commented 10 months ago

@eyalroz Thanks for your bug report. This is for historical reasons and it has existed for many years. Although I can not remove it entirely, I am happy to add an option to disable it. If you are happy with this, please let me know. I am quite occupied by other commitment and I'm afraid the new versions will not appear on CTAN anytime soon.

@Udi-Fogiel You are giving false information by mixing things. I am not sure what is your agenda and what you are trying to achieve but whatever it is you are not doing anything constructive.

The options logo and pdfinfo when they were introduced, were on by default and the polyglossia issue you are referring to is about the option logo. David Carlisle asked me to make it off by default and I exactly did this when it was introduced.In other words, this issue does not exist for many years.

The other issue you are referring to is a technical issue which needs to be fixed and it is unrelated to the rest of your false claims. I just have not had enough time to look into my TeX packages recently as I am occupied by other commitments but as soon as I can find some free time, I will look into it.

The custom properties have existed for many years. No one has ever complained about them as far as I know and it is a feature not a bug.

eyalroz commented 10 months ago

@kvafa : An option to disable it would be nice, although we'd need to get it pushed into polyglossia, which is where the bidi package is often used. I don't mind if it'll take a while - after all, this isn't a bug, it's just an annoyance. However - I do think it would be better if no-large-banner would be the default rather than something one opts into; I think that makes more sense.

@Udi-Fogiel , @kvafa : Let us please move all of this discussion of what happens at the end of a document to a separate issue, since it really does not belong on this one. Kindly suggest that the comments about it be removed and made again (perhaps in summary) on a new issue page.

Udi-Fogiel commented 10 months ago

@Udi-Fogiel , @kvafa : Let us please move all of this discussion of what happens at the end of a document to a separate issue, since it really does not belong on this one. Kindly suggest that the comments about it be removed and made again (perhaps in summary) on a new issue page.

Done at #33