From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: James N. V. Cash Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] avoid hard-coded assumptions in image scaling Date: Sun, 02 May 2021 16:56:33 -0400 Message-ID: <87bl9sonwe.fsf@gmail.com> References: <87eeeoopnt.fsf@gmail.com> <87fsz4g8pm.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18397"; mail-complaints-to="usenet@ciao.gmane.io" Cc: , emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 02 22:57:11 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ldJ9K-0004gP-Lz for ged-emacs-devel@m.gmane-mx.org; Sun, 02 May 2021 22:57:10 +0200 Original-Received: from localhost ([::1]:47544 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ldJ9J-0007S4-Pu for ged-emacs-devel@m.gmane-mx.org; Sun, 02 May 2021 16:57:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46758) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ldJ8n-00073H-GL for emacs-devel@gnu.org; Sun, 02 May 2021 16:56:37 -0400 Original-Received: from mail-qv1-f46.google.com ([209.85.219.46]:42651) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ldJ8m-0005ot-1p for emacs-devel@gnu.org; Sun, 02 May 2021 16:56:37 -0400 Original-Received: by mail-qv1-f46.google.com with SMTP id b14so1692044qvf.9 for ; Sun, 02 May 2021 13:56:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:cc:subject:in-reply-to:references :date:message-id:mime-version; bh=CG3x0aj+Vwy2+kpgQHNY0m8KIVqTKrzhVAvMO6H5BZs=; b=pOSllI4ta/T9h4SlwQAzr+pfciPQ9gAdf6JhwS3TXYtAFFHiWAqwqO4Ba4hJZo4IAI nM/cNVTePFEW9n924GZYo0eUO0R19dyLK4PtRVmSL8pp3guS/3MoOS4AZt5lgSwQodtw ABwoXg0Jr0Gv/X+Cae+FBHI5WhvjQbv7U/Ts/uNTLEmJjDQazOEvaALdlr13ybZm/5hW qW+rD6JEsuIF4ARMSZCeNlryiyUtJS1VbVe23WqrkwJ/4MgshnlvuVY5Rx75nH2aymlB Uc35HrXxBGfm0Fovu5HZeXwVJYwmHNEY2Si5CrXz2SNukdspl2hMsr+eE0t3LlUUO56i U/Lg== X-Gm-Message-State: AOAM533aHCY73K692aVR9uqFE/BDZJC6nd/Ekh2XN5Kpq45eD5Ywt08S O1sWvNvsffHFnxP2Ee7tHEvv98CHl+7OMA== X-Google-Smtp-Source: ABdhPJxCbYiLLSLBSPtaPs28L6ORWdf/TpC/N/P/8L43tzp2CZ08rB5hL5deBUSbddvzQwqoi3wU5g== X-Received: by 2002:a05:6214:a62:: with SMTP id ef2mr11132463qvb.31.1619988994965; Sun, 02 May 2021 13:56:34 -0700 (PDT) Original-Received: from gonk ([2607:fea8:10e2:9e00:4c3d:41a2:416f:1808]) by smtp.gmail.com with ESMTPSA id y24sm7009152qky.85.2021.05.02.13.56.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 02 May 2021 13:56:34 -0700 (PDT) In-Reply-To: <87fsz4g8pm.fsf@gnus.org> Received-SPF: pass client-ip=209.85.219.46; envelope-from=james.nvc@gmail.com; helo=mail-qv1-f46.google.com X-Spam_score_int: -9 X-Spam_score: -1.0 X-Spam_bar: - X-Spam_report: (-1.0 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:268783 Archived-At: Lars Ingebrigtsen writes: > The point of the heuristic here is that we want to scale images up on > HiDPI screens, so the current code gives me a scaling factor of 2.3. > (I've got a 14" 4K screen.) Oh, okay, that makes sense! I'm trying to track down why I've been seeing unexpected svg rendering issues on a 4k screen and came across this in the process. Sorry for the incorrect patch then!