How to properly format the header of a php file according to standards?

Question

PHP

meaning block of comments in the header

/* vim: set expandtab tabstop=4 softtabstop=4 shiftwidth=4: */
// +---------------------------------------------------------------------------+
// | PHP version 5.6.11                                                        |
// +---------------------------------------------------------------------------+
// | Copyright (c) 2004-2015                                                   |
// +---------------------------------------------------------------------------+
// | 23 июл 2015                                                               |
// | Класс - Iptv                                                        |
// +---------------------------------------------------------------------------+
// | Author: Alexander Polyanin <[email protected]>                           |
// +---------------------------------------------------------------------------+
//
//

Answer 1

well, something like this , but isn't it easier to put all this into some kind of separate file, so that in the future people do not sit and read 20 lines of unnecessary information?
I have always believed and will continue to believe that this information is redundant and absolutely unnecessary.

Answer 2

By standards, no way.
in any case it is usually a dock block one line after <?php containing which package the file belongs to, author information + contact details and license information.

<?php

/*
 * This file is part of the Symfony package.
 *
 * (c) Fabien Potencier <[email protected]>
 *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.
 */

Information like "tabstop=4" is usually written in files like . editorconfig

Answer 3

The bottom line is that all these comments in the cap are not needed by anyone. It amuses me how any g-code necessarily contains a massive header with stupid information and a bunch of copyrights.
Please comment on the code!