[ 
https://issues.apache.org/jira/browse/TIKA-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133181#comment-18133181
 ] 

ASF GitHub Bot commented on TIKA-5005:
--------------------------------------

tballison opened a new pull request, #3443:
URL: https://github.com/apache/tika/pull/3443

   …er images; add IPA and WenQuanYi CJK fonts
   
   <!--
     Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
     regarding copyright ownership.  The ASF licenses this file
     to you under the Apache License, Version 2.0 (the
     "License"); you may not use this file except in compliance
     with the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
     Unless required by applicable law or agreed to in writing,
     software distributed under the License is distributed on an
     "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
     KIND, either express or implied.  See the License for the
     specific language governing permissions and limitations
     under the License.
   -->
   
   Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! 
Your help is appreciated!
   
   Before opening the pull request, please verify that
   * there is an open issue on the [Tika issue 
tracker](https://issues.apache.org/jira/projects/TIKA) which describes the 
problem or the improvement. We cannot accept pull requests without an issue 
because the change wouldn't be listed in the release notes.
   * the issue ID (`TIKA-XXXX`)
     - is referenced in the title of the pull request
     - and placed in front of your commit messages surrounded by square 
brackets (`[TIKA-XXXX] Issue or pull request title`)
   * commits are squashed into a single one (or few commits for larger changes)
   * Tika builds and unit tests pass with `./mvnw clean install` (`clean test` 
alone cannot resolve the pipes plugin zips)
   * if you used a generative AI tool: follow the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) (`Generated-by: 
<tool>` in the commit message), and consider running the pre-flight in 
`.skills/devs/pr-review/SKILL.md` — fix what it finds; don't paste its report 
here
   * there should be no conflicts when merging the pull request branch into the 
*recent* `main` branch. If there are conflicts, please try to rebase the pull 
request branch on top of a freshly pulled `main` branch
   * if you add new module that downstream users will depend upon add it to 
relevant group in `tika-bom/pom.xml`.
   
   We will be able to faster integrate your pull request if these conditions 
are met. If you have any questions how to fix your problem or about using Tika 
in general, please sign up for the [Tika mailing 
list](http://tika.apache.org/mail-lists.html). Thanks!
   




> replace ttf-mscorefonts-installer with metric-compatible fonts (Liberation, 
> Carlito, Caladea)
> ---------------------------------------------------------------------------------------------
>
>                 Key: TIKA-5005
>                 URL: https://issues.apache.org/jira/browse/TIKA-5005
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>
> I was recently annoyed that we had a failed build because of sourceforge: 
> [https://github.com/apache/tika/actions/runs/40508823275] . 
>  
> Then I looked a bit more at licensing, and I think we should try to drop 
> mscorefonts.
> :robot:'s input:
> {noformat}
> The -full and tika-grpc images install ttf-mscorefonts-installer, which 
> downloads the 
> fonts from SourceForge at build time, once per architecture. A mirror outage 
> failed the 
> arm64 snapshot push (run 40508823275). Earlier, the same package forced 
> linux/arm/v7 off 
> the platform list. Shipping an image  with the fonts already installed also 
> amounts to 
> redistributing them under the MS EULA. Proposal: remove it (plus 
> cabextract/wget if nothing 
> else needs them) and add fonts-crosextra-carlito and fonts-crosextra-caladea. 
> Before deciding, 
> scan the PDF corpus for non-embedded fonts whose BaseFont is Verdana, 
> Georgia, Trebuchet, 
> Comic Sans, Impact, Webdings or Andale Mono, to bound how many documents 
> would be affected.
>  {noformat}
> Let me know what you think?
>  



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to