From bugzilla at redhat.com Thu Jun 18 12:55:52 2015 Content-Type: multipart/mixed; boundary="===============4994991665870857467==" MIME-Version: 1.0 From: Red Hat Bugzilla To: i18n-bugs at lists.fedoraproject.org Subject: [Fedora-i18n-bugs] [Bug 517789] Droid Sans overrides default Japanese desktop font Date: Tue, 08 Sep 2009 14:54:17 -0400 Message-ID: <200909081854.n88IsHKH028159@bz-web2.app.phx.redhat.com> In-Reply-To: bug-517789-269801@bugzilla.redhat.com --===============4994991665870857467== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=3D517789 Nicolas Mailhot changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |needinfo?(besfahbo(a)redha= t.c | |om) --- Comment #19 from Nicolas Mailhot 2009-= 09-08 14:54:16 EDT --- (In reply to comment #13) > (In reply to comment #11) > > 3. You should also alias back "Droid Sans Japanese" and "Droid Sans Fal= lback" > > to "Droid Sans" now that we are renaming those. > = > That's a really good idea, I don't know why I didn't before, I probably w= as > just afraid of the whole thing BTW we use two different patterns for aliasing right now: 1. "use font Y to complete font X" (for a font which is installed bug with limited coverage): X Y 2. "use font Y when asked for font X" (for fonts that may not be installed) X Y Which pattern is more appropriate for this case? Also, can we use the same logic to fixup at fontconfig level fonts with bad naming metadata (all the stuff that fails WWS and takes ages to be fixed in= the font files upstream)? For example would the following pattern be something = that could be generalised? Or do you have objections/better ideas? Letters Laughing at their Execution Letters Laughing at their Execution Regular Letters Laughing at their Execution Fantasy Letters Laughing