Mailing-List: contact ooo-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-issues@incubator.apache.org
From: bugzilla@apache.org
To: ooo-issues@incubator.apache.org
Subject: 3.4_release_blocker requested: [Bug 119170] Do not use cat-B fonts
 when category B is disabled.
Date: Tue, 03 Apr 2012 15:10:31 +0000
Message-ID: <bug-119170-248469-MjDmhWNCB4@https.issues.apache.org/ooo/>
In-Reply-To: <bug-119170-248469@https.issues.apache.org/ooo/>
References: <bug-119170-248469@https.issues.apache.org/ooo/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

Andre <af@a-w-f.de> has asked  for 3.4_release_blocker:
Bug 119170: Do not use cat-B fonts when category B is disabled.
https://issues.apache.org/ooo/show_bug.cgi?id=119170

------- Additional Comments from Andre <af@a-w-f.de>
@Pedro:

> ?? I was mentioning a license limitation. We currently copy them unmodified
> AFAICT.

I was referring to your earlier remark in comment 2:

>> 2 - There's only one font under Category A, but it still has some grey issue

>> concerning renaming it,


> I thought my patch did the trick, but of course my approach was very basic.

I extended that a bit so that 

1) the category B fonts are not downloaded by default (you may have downloaded
a category B free source release and may not want the category B fonts
downloaded automatically at build time.)

2) the build does not break because of missing fonts (mostly changes in scp2).