I am writing for the GCC Cheatsheet, I want to create a table which shows how GCC interprets the different file endings. The table I have prepared so far is defined as:
| ================================================== ============================ | C. The source code that should be pre-programmed. .i | C source code should not be pre-programmed. | .h | The C header file must be converted to a precompelled header. | S | Assembler Code | Others | An object file should be fed directly to the link. Any file name with a recognized suffix is treated like this. | ================================================== ============================== I have the problem that table total page Width stretches, but what I want is that each column is only widespread because it is a broad entry, and that the table will be only as intelligent as the need is.
In general, there is no good idea to mix content and layout rules inside the source file .
This is for a good reason: The layout definition of the table depends on the output format. If you use the example HTML as the backend of the document, then the document will be a suitable technique for layout. On the other hand, e.g. If you use a formatting object processor to create PDF files, then automatic table-layout is not supported by all the FO processors.
To answer your question: It depends on the output format, how a table layout will be correctly defined within ESIIDOC markup is a definition incorrectly in most cases.