emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] manual: confusing example of adding attributes to a link (affiliated keywords)
Date: Sat, 25 Jun 2022 13:29:29 +0800	[thread overview]
Message-ID: <87zgi1ux8m.fsf@localhost> (raw)
In-Reply-To: <t8q71r$mgv$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

> Org Manual in info "(org) Links in HTML export" 
> https://orgmode.org/manual/Links-in-HTML-export.html has the following 
> example:
>
>> Org files can also have special directives to the HTML export
>> back-end. For example, by using ‘#+ATTR_HTML’ lines to specify new
>> format attributes to <a> or <img> tags. This example shows changing
>> the link’s title and style:
>> 
>> #+ATTR_HTML: :title The Org mode homepage :style color:red;
>> [[https://orgmode.org]]
>
> Likely I have seen similar suggestions in this list as well.
>
> Actually it assigns attribute to paragraphs in addition to links. That 
> is why, I think, this fragment should be removed from manual as a 
> confusing one since it gives impression of support of per-link attributes.

Could we clarify that the attributes will apply to the paragraph instead?

> It states that styles and similar stuff may solve the issue with 
> attributes for inline objects. From my point of view it is wrong and in 
> some cases per-object attributes are necessary. While <a rel="nofollow 
> noreferrer" href="..."> or <a target="_blank" href="..."> may be added 
> through style, attributes like "alt" for images, "title", "lang", etc. 
> for links are individual.

You examples are pretty much dedicated to html. Do you know if
per-object attributes could be actually useful for other export
backends?

Best,
Ihor


  reply	other threads:[~2022-06-25  5:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 16:25 [BUG] manual: confusing example of adding attributes to a link (affiliated keywords) Max Nikulin
2022-06-25  5:29 ` Ihor Radchenko [this message]
2022-06-25 10:12   ` Max Nikulin
2022-06-25 10:39     ` Ihor Radchenko
2022-06-25 11:55       ` Max Nikulin
2022-06-25 12:17         ` Ihor Radchenko

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=87zgi1ux8m.fsf@localhost \
    --to=yantar92@gmail.com \
    --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).