From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id MOJOKy8NX2EcNAAAgWs5BA (envelope-from ) for ; Thu, 07 Oct 2021 17:07:27 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id mHYGJy8NX2GMKgAAB5/wlQ (envelope-from ) for ; Thu, 07 Oct 2021 15:07:27 +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 103FA35285 for ; Thu, 7 Oct 2021 17:07:27 +0200 (CEST) Received: from localhost ([::1]:53400 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mYUzW-00070a-4f for larch@yhetil.org; Thu, 07 Oct 2021 11:07:26 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:56884) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mYUyI-0006wN-FG for emacs-orgmode@gnu.org; Thu, 07 Oct 2021 11:06:10 -0400 Received: from ciao.gmane.io ([116.202.254.214]:36288) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mYUyG-00051p-U7 for emacs-orgmode@gnu.org; Thu, 07 Oct 2021 11:06:10 -0400 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1mYUyE-00008s-MI for emacs-orgmode@gnu.org; Thu, 07 Oct 2021 17:06:06 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: emacs-orgmode@gnu.org From: Max Nikulin Subject: Re: Inequalities in math blocks Date: Thu, 7 Oct 2021 22:05:57 +0700 Message-ID: References: <2477519.1633606219@apollo2.minshall.org> <874k9tdlto.fsf@gmail.com> 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:78.0) Gecko/20100101 Thunderbird/78.13.0 In-Reply-To: <874k9tdlto.fsf@gmail.com> Content-Language: en-US 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: 8 X-Spam_score: 0.8 X-Spam_bar: / X-Spam_report: (0.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=-1.964, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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." 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 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1633619247; 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=VIphrK9pBOyDrBPkQagKdjVgyAhaTnALoTz3Os2R5kk=; b=AgiK8KtMxcsJ3+CT0Addhu/VEpKkEmGYIiorYHd/+884fctB0VVbti7gChMaTf/6reZHZD 5daxFu9HA9T1E48VbBN+pQCxv3/VgDzxQBb7eZRiuvc7osK3XMZxSJKKwjGtaUkD7HWQx1 RlFPYwkD0cnI/Ilje+fb9KpRIKUnuQc37lRtql6EKDhtUnTyIteLrv0WLvUXpgRwEWqhX3 Pl59gspntQfLqTmHvHFoJu6iGwPn1dXP/Ecuq5the15SBejzCAAPQOYzua4Z14Fk8vso/B bV0To6O+Vt8yaCUeNYnuJsn8TCv2HGtG8SYOjOAq6LpNq5IW1/T7nR8JFL6pfA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1633619247; a=rsa-sha256; cv=none; b=bcSH/7gl+zf8m+Gc8ScHLpy8T3lnSCu3Sapb4n+rg3b9IB4qY3wrCxFO8Ex+I7HlmPxQA0 uYSpASFevPNZOTOBbIvuiG2u04y2nfBxscbTpqGbGB5tSmGds++TUAwIISJbQDKqtSqq48 RdPvUlksmR4Oq80kfgkTDMUtbopEqyRPFwP0xENHPnwks3zxZD/Txn8Eg60xtDiHrN7pLJ Cc4sQvyZJo5dMnoN6MTuMz8at/RdR4sFs7TK+K7xmmDImJI3oGqFXE3c15HVfQ9qXI30bQ uNPqGwsiXkSc9Tn5ZcjWHe7WQ71H6mJRyw03vOthRA6J9Q8kfjHkuC/y0bYMZg== 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@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Spam-Score: -0.32 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@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 103FA35285 X-Spam-Score: -0.32 X-Migadu-Scanner: scn0.migadu.com X-TUID: tJFL/F4in+On On 07/10/2021 20:05, Timothy wrote: >> Org should rewrite < and > to < and > to avoid broken HTML, or as < and in general. > > I think we’ve drifted a bit to the differences in processing (where the `\( ... \)' > vs `$ ... $' comments are most pertinent), but as you say for valid HTML < and > > should be rewritten. I don’t think I’ve seen an issue because MathJax seems to > take care of it, but it looks like MathJax is also fine with < and &rt;. "<" and ">" characters are valid only markup elements in HTML (part of tags, comments). MathJax interprets text content. Normally, to add text "<" or ">", "<" or ">" should be used in HTML sources. Browsers may pass "<" and ">" from source to text content if they are totally confused by invalid markup that does not resemble tags or something else. I do not think, it should be abused. I cited MathJax docs just to show a temporary workaround till the bug will be fixed in Org. It is quite strange that Org properly converts "<>&" to entities in text but leaves them as is in math snippets. Unsure whether git history might clarify some reasons of such behavior. On 06/10/2021 14:39, Rudolf Adamkovič wrote > I wrote the following: "[…] every term $t\in{}q$ with $idf(t)>c$ for > some constant $c$ […]", and the "idf(t) > c" part got exported as > "idf(t)". I cannot fix the paper at this point. Uh-oh! If you submitted HTML file, you might suggest to open sources to make it obvious that the mistake was not intentional. "$idf(t)>c$" means "i*d*f(t) > c". A bit more markup required to make "idf" typed in straight font instead of italics and to avoid additional space between characters. It is matter of taste, but "{}" after "\in" looks a bit strange for me. "$t\in q$ is even shorter, "$t \in q$", having the same length, is more readable from my point of view.