From: "Juan Manuel Macías" <firstname.lastname@example.org> To: orgmode <email@example.com> Subject: Re: text after sub headings? Date: Sun, 26 Dec 2021 09:17:29 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Max Nikulin's message of "Sat, 25 Dec 2021 20:15:36 +0700") [-- Attachment #1: Type: text/plain, Size: 1663 bytes --] Max Nikulin writes: > It is not necessary complex layout. It is a decoration similar to > pictures in fiction books. Unlike figures such additions are not > strictly important to understand material. In printed form it is like > figures however. Insets are appropriate in particular places, but > tolerate some shift due to paging. Generally, any scenario where graphic and textual content must be distributed and managed is already complex layout. Although there are several levels of complexity, and in many cases visual control is necessary. In any case, TeX is not intended for (stricto sensu) layout but for typesetting, which is where DTP programs often fail. This does not mean that highly complex pages cannot be achieved in TeX, but the strong point of TeX is the automation of processes and repeated structures, while the strong point of DTP programs is visual layout design, more focused on magazines, newspapers, posters, etc. There are "intermediate places", and in TeX there are still unresolved issues. For example: the possibility of working with independent text flows (for example, create two parallel TeX processes: one for even pages and another for odd pages) or grid typesetting (in LaTeX it is almost impossible and in ConTeXt some advances have been made) although I am very critical of the grid composition, which has become a plague lately. Anyway, in order not to get too off the topic, here are a couple of examples that I made (one of them with flowfram), exporting an inline task to LaTeX through an ad hoc filter: https://i.imgur.com/8ERXNWp.png https://i.imgur.com/mpFRL9h.png (code attached) Best regards, Juan Manuel [-- Attachment #2: tests.org --] [-- Type: application/vnd.lotus-organizer, Size: 16218 bytes --]
next prev parent reply other threads:[~2021-12-26 9:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-23 16:11 Robert Nikander 2021-12-23 16:54 ` Max Nikulin 2021-12-23 20:27 ` Juan Manuel Macías 2021-12-24 16:51 ` Max Nikulin 2021-12-24 20:17 ` Juan Manuel Macías 2021-12-25 13:15 ` Max Nikulin 2021-12-26 5:23 ` Ihor Radchenko 2021-12-26 9:17 ` Juan Manuel Macías [this message] 2021-12-23 23:12 ` Tim Cross 2021-12-23 21:21 Robert Nikander 2021-12-23 21:47 ` John Kitchin 2021-12-23 22:10 ` Juan Manuel Macías
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: text after sub headings?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).