From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id GOTZBhunsGJKNAEAbAwnHQ (envelope-from ) for ; Mon, 20 Jun 2022 18:58:03 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id xqTtBRunsGI8xwAAG6o9tA (envelope-from ) for ; Mon, 20 Jun 2022 18:58:03 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id C036028A90 for ; Mon, 20 Jun 2022 18:58:02 +0200 (CEST) Received: from localhost ([::1]:55678 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o3Kiv-0006If-ST for larch@yhetil.org; Mon, 20 Jun 2022 12:58:01 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59294) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o3KiJ-0006IR-6m for emacs-orgmode@gnu.org; Mon, 20 Jun 2022 12:57:25 -0400 Received: from ciao.gmane.io ([116.202.254.214]:42256) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o3KiH-0001ed-Ly for emacs-orgmode@gnu.org; Mon, 20 Jun 2022 12:57:22 -0400 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1o3KiF-0004Q1-W5 for emacs-orgmode@gnu.org; Mon, 20 Jun 2022 18:57:19 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: emacs-orgmode@gnu.org From: Max Nikulin Subject: Re: About 'inline special blocks' Date: Mon, 20 Jun 2022 23:57:12 +0700 Message-ID: References: <87a6b8pbhg.fsf@posteo.net> <875ykwvmz7.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Content-Language: en-US In-Reply-To: <875ykwvmz7.fsf@posteo.net> Received-SPF: pass client-ip=116.202.254.214; envelope-from=geo-emacs-orgmode@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: 28 X-Spam_score: 2.8 X-Spam_bar: ++ X-Spam_report: (2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1655744282; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=AlULls3yA+LbFy361sqU3R6X34kVWQIJOs2di6LypOc=; b=q88+Bqyfy492i6zilOAMGd9BKwy8lcLENsjEbAcqMgUVAbcGgx/R3WtYLzehKEEsVi2WaA HCnfCslW6FqqNl4msefmUgdWJczCw/CmLFkWHiplIrPD93vYgg4Loy+9y1TfXouot7A/Dl EsKw/1ngEP/KV6ol2MuBdHPVse72C8PDtO5+bZVWCxud3Ww32oomvkifk3FTuAav3yQNn9 Ef61Kr2psAIpLTW8Q0ypmecZu2/IzMxbO5a6Y5qS0mQAAsZ9Jx2h9l4BSAyrFQOgUvEMeG DzTXULCjf3FzBj0ZJ/8gPT+PS+4PJ6PKTcLy1yjPK6/3uyDYJ9Hhkd4Gtmz6PA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1655744282; a=rsa-sha256; cv=none; b=U1HnQwsvfJw0XZ5Me4YQp3JBwdV6zEAbSeOfKz3igNHMAJl5YYvmv3/Rb9Jm9wmlytsYj2 GzejMy+OQzsGCReRHAcgIWOUCdj4KqImV/QSJTj2YF10b2o4BeYGm7CfebXTCtMdNwLuir ICINtXH2OOREkhjA0lpL6MLdcYs+8VBkiB+SK+OYFHA9Fm/G6NgSkeTG0VlMvE57B7KxIJ OUleca3EmYg3NYRnJTUF7yI+g5cV/j0+jSzp+Muvvv1tHxWGoljhxr+cbgju6v2xpK5hu/ h8fSxZyqeTqXM1DtyJIw23L4zv9AMTLuG7CMltCuejFa5E0Qbxw1F0aquhrNzA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: 3.43 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: C036028A90 X-Spam-Score: 3.43 X-Migadu-Scanner: scn0.migadu.com X-TUID: mY9du02PkynB On 19/06/2022 19:47, Juan Manuel Macías wrote: > > I am more and more convinced that inline special blocks, by their > nature, should not support fine tune options or anything like > attr_latex, attr_html, etc. like its older brothers, as it would produce > an overly complicated syntax. I would like to stress that styles can not be a rescue in some important cases. Let's leave aside ad hoc final tuning of formatting. In the case of HTML export there are still Description and attributes that are namely per-object, not part of style. I was going to raise this issue for several months, so I just have sent to following bug report: Max Nikulin to emacs-orgmode. [BUG] manual: confusing example of adding attributes to a link (affiliated keywords) Mon, 20 Jun 2022 23:25:29 +0700. https://list.orgmode.org/t8q71r$mgv$1@ciao.gmane.io I have not heard that PDF offers something similar, but e.g. link with title may be exported as footnote with title text and URL instead of inline link. However to handle such cases generic attributes available to all export backends should be introduced. Even when styles are enough in principle, attributes may be more convenient since the latter may be composable, so making unnecessary defining every possible (or used) combination of styles. > in html: > > contents> Concerning vs. , is it the same for assistive technologies like screen readers to add text (or text) and text with "font-weight: bolder;" in CSS?