Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Large banner in output is inappropriate #32

Open
1 of 5 tasks
eyalroz opened this issue Oct 17, 2023 · 6 comments
Open
1 of 5 tasks

Large banner in output is inappropriate #32

eyalroz opened this issue Oct 17, 2023 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@eyalroz
Copy link

eyalroz commented Oct 17, 2023

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

  • Not useful to the user compiling a document (they know that each style file has a self-describing comment, plus there is CTAN documentation for packages, search engines etc.)
  • Contradicts the custom for (La)TeX packages
  • Clutters the log and hides meaningful messages

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.
* 
****************************************************
@eyalroz eyalroz added the bug Something isn't working label Oct 17, 2023
@Udi-Fogiel
Copy link

Udi-Fogiel commented Oct 24, 2023

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
Copy link
Author

eyalroz commented Oct 24, 2023

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
Copy link
Author

eyalroz commented Oct 24, 2023

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
Copy link
Owner

kvafa commented Oct 28, 2023

@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
Copy link
Author

eyalroz commented Oct 28, 2023

@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
Copy link

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants