From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id kBkEOQZIf2CiSQAAgWs5BA (envelope-from ) for ; Tue, 20 Apr 2021 23:30:46 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id 6AO8NAZIf2B/VgAA1q6Kng (envelope-from ) for ; Tue, 20 Apr 2021 21:30:46 +0000 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 5EEFA26DB7 for ; Tue, 20 Apr 2021 23:30:46 +0200 (CEST) Received: from localhost ([::1]:45166 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lYxxE-0007Oi-LE for larch@yhetil.org; Tue, 20 Apr 2021 17:30:44 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:49376) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lYxwm-0007OX-J1 for emacs-orgmode@gnu.org; Tue, 20 Apr 2021 17:30:16 -0400 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]:51885) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lYxwk-0004Os-7P for emacs-orgmode@gnu.org; Tue, 20 Apr 2021 17:30:16 -0400 Received: by mail-wm1-x329.google.com with SMTP id z6so3225658wmg.1 for ; Tue, 20 Apr 2021 14:30:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=HMxNWni8wyrp+FBTjNtXsdRYT9iCA8lhgOxHWaOWZqo=; b=HWCb95Dkm1JiuIbHp3UMbYQtPVpQirAOZbpkFGMCFWO7yk0dMaaNukLnjqy6lMrLzQ l1PNFxBhhkeAtCsgpItLzafMacfs6RXLJjwYybKdpYDU2829+Q94Wfohen1JFByCP3Jg oMv5wHT+RNuzZUXYI5jHM+LGdNwU9NNl3x+w6RnQQa+UUhFk+CTl7fYSJ9AAUyM2iYu0 IOgkA1EXbNQdDHi5Ui18ASb6tz+JsdVQlSvmRZPrOMzt7cIuBuV9FJc8XIs9rnXjAtsb /fbL7QeLCEiiuLCBeWrTN+8RZEiWphRzYARdC1duHW4AW7HYtluJYQSe+pS16IdlMOJD 3A3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=HMxNWni8wyrp+FBTjNtXsdRYT9iCA8lhgOxHWaOWZqo=; b=ed/Mcg70jdBKOh8zvYFP8owJRkVXtsI/3lsuQjmYfp8dETnd5Za3OuwQMB/1JtSMO/ rLtdZcr3ct7U59Y04u26Hgj7+eDY5K3RXW3frujqPAjJzrhZZ/G3bLirkvx61hUGcHve i46oKm13qfvSpmv5bjcNpqjo6l7hMlkX54Tgv4rDIRgkXJ3owrTV71eap0sOFj8oR7xN 8/EfDlCPEK4Ko2K4pQsa9EJCWv0pg7aJzbCkhA/3wJhahhf1FRKt8kQqoU6arAw1boGW V7+8Pd2AVbHyXxzNKrpyF4yv23bqvSqzZo5OZukjZiGjdD7Q0emsF7jWTLc+rtmSlhpv 7GuQ== X-Gm-Message-State: AOAM530wWoPlT9FeQZQuUZZW8oKp2s+IiHW+rBlJw5FzSj9eevqpzCMX ISLDV1E5/641O5Nb/iH9pcMFAmAK9qjWzlnz4ok= X-Google-Smtp-Source: ABdhPJyV9m+fggm1CxIZR8TuO8bzxRcrR3ZA4P9kP1kGH9eWPM/TrKZ82UGSyXNlB2uJk1Mv3DECaxAj6EjVGbPpg4g= X-Received: by 2002:a05:600c:19d1:: with SMTP id u17mr6177429wmq.111.1618954212336; Tue, 20 Apr 2021 14:30:12 -0700 (PDT) MIME-Version: 1.0 References: <87fszly7zg.fsf@kyleam.com> <871rb5ft6a.fsf@wi.uni-muenster.de> In-Reply-To: <871rb5ft6a.fsf@wi.uni-muenster.de> From: Tim Visher Date: Tue, 20 Apr 2021 17:29:36 -0400 Message-ID: Subject: Re: ox-html Incorrectly (?) Puts HTML Into the `` Tag To: Kyle Meyer <kyle@kyleam.com>, Tim Visher <tim.visher@gmail.com>, Emacs Org Mode mailing list <emacs-orgmode@gnu.org> Content-Type: multipart/alternative; boundary="000000000000bbe7ec05c06e2606" Received-SPF: pass client-ip=2a00:1450:4864:20::329; envelope-from=tim.visher@gmail.com; helo=mail-wm1-x329.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org> List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>, <mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe> List-Archive: <https://lists.gnu.org/archive/html/emacs-orgmode> List-Post: <mailto:emacs-orgmode@gnu.org> List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help> List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>, <mailto:emacs-orgmode-request@gnu.org?subject=subscribe> Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" <emacs-orgmode-bounces+larch=yhetil.org@gnu.org> X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1618954246; 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:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=HMxNWni8wyrp+FBTjNtXsdRYT9iCA8lhgOxHWaOWZqo=; b=udSO2JNxjKT1e5YrgRku5Kt0MKG0iewY6bSzSxkjhap3Y/uVg4oZZ2dX+gWj5A0rsFHLgC rVIRZtgWneM3eWzZRTP4q7aYGo6EL8q2RpKAxSDZVDKw0AfVc7ilWw4fu4Pa9C5QZysSfe 6mdqXFPEUoOufal5SHo6WMclb0NsOUUgqcXolHcGmCysxdD/2ycOtEEYvYNOQPKB2svi68 lL7dugkIkXhl31Ios1k8zrcIF4hCKVVSb74GTw9XwrUfoVMFv+sP3oyyP6frowIWgJngua 8UeEBOV6k7RdzX4eleStENqckXzOP42DmYFyizHHTX+MrCoAOLtPepuq+P7P3g== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1618954246; a=rsa-sha256; cv=none; b=ieoPBOLzbKQyr4lwf0tMfYfmg+CwTLWcTDP+bWIs8FYip7g8gfMJwIUk4lKWt/KNVflJDP YtcK50qVMN91Ab5s0q8AvwkeNRjXWtWV8hdp78gMsx4wkW8xnMm6wYaf5WXnAEObX+x/AY g/HHj8qO+KlH+LVQJHv6bNfIGZHlLHkA8eQBdk5vfJOMxsosqA907xRVMw/ffxXmP8Bvwd dk29J9fd40VYocBbAfwmMGtZ1EWP3omHugVjPFg1t7XKrCCvX/GqZl2eMcTa24mRRYa2Ve LfOPmI/qKaHslSj14frNHpDtVKM7xvxPBkilp70O2UaAcNOZaHA4e6s8X9KoEQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=HWCb95Dk; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Spam-Score: -3.14 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=HWCb95Dk; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 5EEFA26DB7 X-Spam-Score: -3.14 X-Migadu-Scanner: scn0.migadu.com X-TUID: VjnjUQpftp4f --000000000000bbe7ec05c06e2606 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks so much for getting back to me, Jens. On Tue, Apr 20, 2021 at 12:59 AM Jens Lechtenboerger < jens.lechtenboerger@wi.uni-muenster.de> wrote: > On 2021-04-19, Kyle Meyer wrote: > > > Tim Visher writes: > > > >> Unfortunately, the title now is essentially the exact text of the org > >> heading, which is awkward in terms of readability for a general audien= ce > >> (and probably for SEO etc.). I know I said in my original message that= I > >> think stripping all the markup characters would be going too far but > now I > >> think I've come full circle and rendering the title as nothing but the > >> plain text without any markup information feels like the right solutio= n > >> given what the title is supposed to convey. > >> > >> So, would we be willing to accept a patch to that effect? :) > > > > I don't have an informed opinion about the above, but providing a patch > > might prompt those that do (including TEC, the author of the above > > commit, as well as Jens, who provided reviews) to give their input. > > The following is not a strong opinion: The author writes =E2=80=9Cwhat th= e > title is supposed to convey=E2=80=9D. If there is *emphasis*, why not > export that as ASCII markup to HTML? > > With an additional option, authors could choose. > I guess I don't have a super strong opinion here either. Ironically, coming from someone who spends a significant portion of their day reading raw org/markdown documents with no problem, something about even the ASCII style markup in the title looks wrong to me. I don't do SEO and nothing in MDN's article <https://developer.mozilla.org/en-US/docs/Web/HTML/Element/title> indicates that non word characters have a negative affect anyway but it just looks strange to my eyes. I guess regardless it sounds like if I were to go to the trouble of making a patch for this it would be good to make sure that it was behind an option and probably defaulting to the current HEAD behavior of including the ASCII markup with an option to strip the non-word characters from it. -- In Christ, Timmy V. https://blog.twonegatives.com http://five.sentenc.es --000000000000bbe7ec05c06e2606 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div>Thanks so much for getting back to m= e, Jens.</div><div><br></div><div></div></div><div dir=3D"ltr">On Tue, Apr = 20, 2021 at 12:59 AM Jens Lechtenboerger <<a href=3D"mailto:jens.lechten= boerger@wi.uni-muenster.de">jens.lechtenboerger@wi.uni-muenster.de</a>> = wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote= " style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);= padding-left:1ex">On 2021-04-19, Kyle Meyer wrote:<br> <br> > Tim Visher writes:<br> ><br> >> Unfortunately, the title now is essentially the exact text of the = org<br> >> heading, which is awkward in terms of readability for a general au= dience<br> >> (and probably for SEO etc.). I know I said in my original message = that I<br> >> think stripping all the markup characters would be going too far b= ut now I<br> >> think I've come full circle and rendering the title as nothing= but the<br> >> plain text without any markup information feels like the right sol= ution<br> >> given what the title is supposed to convey.<br> >><br> >> So, would we be willing to accept a patch to that effect? :)<br> ><br> > I don't have an informed opinion about the above, but providing a = patch<br> > might prompt those that do (including TEC, the author of the above<br> > commit, as well as Jens, who provided reviews) to give their input.<br= > <br> The following is not a strong opinion: The author writes =E2=80=9Cwhat the<= br> title is supposed to convey=E2=80=9D.=C2=A0 If there is *emphasis*, why not= <br> export that as ASCII markup to HTML?<br> <br> With an additional option, authors could choose.<br></blockquote><div><br><= /div><div>I guess I don't have a super strong opinion here either. Iron= ically, coming from someone who spends a significant portion of their day r= eading raw org/markdown documents with no problem, something about even the= ASCII style markup in the title looks wrong to me. I don't do SEO and = nothing in <a href=3D"https://developer.mozilla.org/en-US/docs/Web/HTML/Ele= ment/title">MDN's article</a>=C2=A0indicates that non word characters h= ave a negative affect anyway but it just looks strange to my eyes.</div><di= v><br></div><div>I guess regardless it sounds like if I were to go to the t= rouble of making a patch for this it would be good to make sure that it was= behind an option and probably defaulting to the current HEAD behavior of i= ncluding the ASCII markup with an option to strip the non-word characters f= rom it.</div><div><br></div><div>--<br><br>In Christ,<br><br>Timmy V.<br><b= r><a href=3D"https://blog.twonegatives.com">https://blog.twonegatives.com</= a><br><a href=3D"http://five.sentenc.es">http://five.sentenc.es</a><br></di= v></div></div> --000000000000bbe7ec05c06e2606--