From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: smallcaps: Re: Experimental public branch for inline special blocks
Date: Tue, 05 Mar 2024 17:28:57 +0000 [thread overview]
Message-ID: <871q8o37vq.fsf@posteo.net> (raw)
In-Reply-To: <us7ib6$lij$1@ciao.gmane.io> (Max Nikulin's message of "Tue, 5 Mar 2024 23:47:32 +0700")
Max Nikulin <manikulin@gmail.com> escribió:
> If some type is used through the document multiple times then it is
> better to avoid style="font-variant:small-caps" and use a CSS class
> instead. Even for LaTeX it may be better to define a dedicated command
> to be closer to semantic markup.
>
> Moreover different decorations may be used in LaTeX and HTML. Some type
> may be typed in small caps in LaTeX, but in HTML it may use regular font
> and some color.
The "global attribute" concept implies that there should be (ideally)
the same result in all possible backends (naturally, if the output is
plain text, :color doesn't make much sense). Global attributes are a
quick and easy (for the user) way to create direct formatting, analogous
to the LaTeX commands \textcolor, \textsc, etc. Its casual use is the
most recommended, in my opinion. Let's imagine that a user wants to
color segments of text, in the same color, for LaTeX and odt, and does
not want to bother with predefined styles or macros in odt and LaTeX
respectively.
If a segment of text must have a different appearance, for example, in
LaTeX (small caps) and HTML (red color), you can put:
&_[:html style="color:red;" :prelatex \scshape{}]{text}
And if one wants to have more robust control, for example because many
text segments must have a certain treatment in HTML, odt or LaTeX,
styles, classes and macros can always be defined in the output format.
Additionally, there are the :odt-style, :latex-command, :html-tag and
:html-class attributes to override what is necessary. What's more, in
specific cases global attributes can be added.
I think that the current implementation is very flexible and gives rise
to many possible variations, and the combination of direct formatting
and styles to suit the user.
--
Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño editorial y ortotipografía
next prev parent reply other threads:[~2024-03-05 17:30 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 20:34 Experimental public branch for inline special blocks Juan Manuel Macías
2024-03-02 8:29 ` Stefan Nobis
2024-03-02 10:57 ` Juan Manuel Macías
2024-03-03 20:29 ` Juan Manuel Macías
2024-03-10 2:08 ` `:export' attribute?: " Juan Manuel Macías
2024-03-10 13:54 ` Juan Manuel Macías
2024-03-11 10:27 ` Max Nikulin
2024-03-11 13:59 ` Juan Manuel Macías
2024-03-11 17:01 ` Max Nikulin
2024-03-11 20:19 ` Juan Manuel Macías
2024-03-12 8:32 ` Stefan Nobis
2024-03-12 13:45 ` Juan Manuel Macías
2024-03-12 16:20 ` Max Nikulin
2024-03-12 17:41 ` Juan Manuel Macías
2024-03-13 16:08 ` Max Nikulin
2024-03-13 16:48 ` Juan Manuel Macías
2024-03-13 17:16 ` Juan Manuel Macías
2024-03-15 2:19 ` Juan Manuel Macías
2024-03-15 10:52 ` Max Nikulin
2024-03-15 13:10 ` Juan Manuel Macías
2024-03-15 17:21 ` Max Nikulin
2024-03-15 14:00 ` Ihor Radchenko
2024-03-15 11:11 ` Max Nikulin
2024-03-15 14:19 ` Ihor Radchenko
2024-03-15 16:26 ` Juan Manuel Macías
2024-03-16 14:07 ` Max Nikulin
2024-03-18 19:42 ` Juan Manuel Macías
2024-03-19 14:54 ` Max Nikulin
2024-03-19 17:47 ` Juan Manuel Macías
2024-03-21 10:26 ` inline-special-block: export rules (was: `:export' attribute?: Re: Experimental public branch for inline special blocks) Juan Manuel Macías
2024-03-26 16:56 ` inline-special-block: export rules Max Nikulin
2024-03-04 17:13 ` naming: Re: Experimental public branch for inline special blocks Max Nikulin
2024-03-04 17:29 ` Ihor Radchenko
2024-03-04 17:49 ` Juan Manuel Macías
2024-03-05 10:53 ` Max Nikulin
2024-03-05 11:04 ` Ihor Radchenko
2024-03-05 15:16 ` Suhail Singh
2024-03-05 15:23 ` Suhail Singh
2024-03-05 15:16 ` Juan Manuel Macías
2024-03-06 10:42 ` Max Nikulin
2024-03-06 10:56 ` Ihor Radchenko
2024-03-07 10:34 ` Max Nikulin
2024-03-07 14:12 ` Ihor Radchenko
2024-03-08 5:26 ` Samuel Wales
2024-03-08 16:32 ` Max Nikulin
2024-03-08 16:41 ` Ihor Radchenko
2024-03-04 18:07 ` Juan Manuel Macías
2024-03-04 22:17 ` Samuel Wales
2024-03-04 22:18 ` Samuel Wales
2024-03-05 16:47 ` smallcaps: " Max Nikulin
2024-03-05 17:28 ` Juan Manuel Macías [this message]
2024-03-06 10:55 ` Max Nikulin
2024-03-06 15:21 ` Juan Manuel Macías
2024-03-06 16:53 ` To avoid zero width space: " Max Nikulin
2024-03-06 18:27 ` Juan Manuel Macías
2024-03-06 21:13 ` Juan Manuel Macías
2024-03-07 10:57 ` false positives: " Max Nikulin
2024-03-07 11:06 ` Juan Manuel Macías
2024-03-07 11:18 ` Ihor Radchenko
2024-03-07 11:19 ` Juan Manuel Macías
2024-03-07 15:53 ` Juan Manuel Macías
2024-03-07 16:09 ` Ihor Radchenko
2024-03-07 16:57 ` Juan Manuel Macías
2024-03-07 18:21 ` Juan Manuel Macías
2024-03-08 13:58 ` Max Nikulin
2024-03-08 15:44 ` Juan Manuel Macías
2024-03-08 16:04 ` Max Nikulin
2024-03-08 16:15 ` Ihor Radchenko
2024-03-08 18:44 ` Juan Manuel Macías
2024-03-08 18:57 ` Juan Manuel Macías
2024-03-09 11:10 ` Max Nikulin
2024-03-09 11:48 ` Juan Manuel Macías
2024-03-09 15:24 ` Juan Manuel Macías
2024-03-10 7:11 ` Max Nikulin
2024-04-09 8:52 ` Ihor Radchenko
2024-04-09 10:51 ` Max Nikulin
2024-04-09 14:05 ` Ihor Radchenko
2024-04-10 23:00 ` Juan Manuel Macías
2024-04-11 12:26 ` Ihor Radchenko
2024-04-11 13:47 ` Juan Manuel Macías
2024-04-14 15:59 ` Attributes on images (was:: Experimental public branch for inline special blocks) Rick Lupton
2024-04-14 19:26 ` Ihor Radchenko
2024-04-11 11:06 ` Experimental public branch for inline special blocks Max Nikulin
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 \
--in-reply-to=871q8o37vq.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).