Task #900

Non-free Microsoft font files included in sources

Added by apo almost 4 years ago. Updated about 3 years ago.

Status:Fixed% Done:

100%

Priority:NormalSpent time:-
Assignee:IR4T4
Category:General
Target version:2.75
OS:Linux Arch:

Description

ET: Legacy ships two non-free font files

etmain/fonts/courbd.ttf
etmain/fonts/ariblk.ttf

Both belong to Microsoft’s core fonts for the web.

https://en.wikipedia.org/wiki/Core_fonts_for_the_Web

The EULA does not allow modification, reverse engineering etc:

http://www.microsoft.com/typography/fontpack/eula.htm

That means that your current source package can only be distributed in the non-free section of Debian or not at all. Package maintainers are forced to remove those fonts but we would generally prefer that they are not included at all. You should at least mention the license terms somewhere.

Are all other files under etmain/* still covered by the GNU General Public License 3 or later?


Related issues

Related to ET: Legacy Development - Feature #581: Add TrueType Unicode font for the ingame console Fixed 25.12.2018
Duplicates ET: Legacy Development - Task #218: Replace assets with our own New 29.12.2013

Associated revisions

Revision b7d5c46a
Added by IR4T4 about 3 years ago

misc: non free font files removed, free font files added refs #900

Revision 97bd660d
Added by IR4T4 about 3 years ago

misc: let ETL use free fonts

Revision 3e66d96b
Added by IR4T4 about 3 years ago

misc: let mods load ttf again

Revision 23613222
Added by Spyhawk about 3 years ago

misc: added original free fonts and fixed readme, refs #900

Revision 1d3b3857
Added by Spyhawk about 3 years ago

misc: use Courier Prime for better glyphs coverage, refs #900

Revision a76e9e68
Added by Spyhawk about 3 years ago

misc: use Courier Prime font with cyrillic support, refs #900

History

#1 Updated by Spyhawk almost 4 years ago

  • Tracker changed from Bug to Task
  • Priority changed from Normal to Low

Are all other files under etmain/* still covered by the GNU General Public License 3 or later?

No. Apart from the files distributed with the ET-GPL source code package, all assets are still covered by the original, proprietary WolfET license. See #218 for the ticket tracking assets replacement.

Note that ET:Legacy can’t be used without the original assets. There is no way Debian could distribute this program in its free repository in the foreseeable future.

#2 Updated by apo almost 4 years ago

Spyhawk wrote:

Are all other files under etmain/* still covered by the GNU General Public License 3 or later?

No. Apart from the files distributed with the ET-GPL source code package, all assets are still covered by the original, proprietary WolfET license. See #218 for the ticket tracking assets replacement.

Note that ET:Legacy can’t be used without the original assets. There is no way Debian could distribute this program in its free repository in the foreseeable future.

I have already created a working Debian package for ET: Legacy and I think it is eligible for inclusion into Debian’s contrib section depending on the status of the etmain/* directory which is actually shipped with your source tarball from github.com.

https://github.com/etlegacy/etlegacy/archive/v2.74.tar.gz

I have made a complete license check for all files included in this source tarball. Everything seems fine but I am unsure about the included etmain source folder. According to your license terms it should be covered by the GPL-3+ license. If this is not the case, I have to remove all files within it. You really should prominently mention the original EULA terms in your source tarball releases. I am fully aware of that players still need pak0.pk3, pak1.pk3 and pak2.pk3. They are even worse than non-free because they are non-distributable for Debian but it is completely legal to download them from splashdamage.com. This can be easily done with Debian’s game-data-packager from testing/sid by running

game-data-packager enemy-territory

and by manually installing the resulting Debian package.

If I remove the complete etmain/* directory in your source tarball, the game fails to build from source. Is there a chance to provide the engine without those files or to work around this issue?

#3 Updated by Spyhawk almost 4 years ago

If I remove the complete etmain/* directory in your source tarball, the game fails to build from source. Is there a chance to provide the engine without those files or to work around this issue?

You might be able to actually build the engine without the included assets in /etmain. However, the package will simply be unusable, as they are needed to correctly load the game (the whole UI depends on them, for example) and can’t be shipped separately. Again, ET:Legacy won’t make it to debian free before a very long time (if ever at all). You should aim at the non-free repo.

#4 Updated by Spyhawk almost 4 years ago

  • Category changed from General to Mod pak3.pk3
  • Target version changed from 2.75 to ALL

#5 Updated by apo almost 4 years ago

  • Category changed from Mod pak3.pk3 to General
  • Target version changed from ALL to 2.75

Spyhawk wrote:

If I remove the complete etmain/* directory in your source tarball, the game fails to build from source. Is there a chance to provide the engine without those files or to work around this issue?

You might be able to actually build the engine without the included assets in /etmain. However, the package will simply be unusable, as they are needed to correctly load the game (the whole UI depends on them, for example) and can’t be shipped separately. Again, ET:Legacy won’t make it to debian free before a very long time (if ever at all). You should aim at the non-free repo.

Ok, that’s a shame. I thought the original pak{0,1,2}.pk3 files were the only files needed to play the game and the rest was free software. But if you say that all files in

https://github.com/etlegacy/etlegacy/tree/master/etmain

are covered by the original EULA, then I can’t even package the game for non-free because the EULA does not allow redistribution. I am afraid but then I am no longer interested in packaging the game for Debian because my hope was that it could be legally included in the contrib section and that interested users just had to download the assets from splashdamage.com.

I will open another bug report with my current packaging work. Perhaps someone else might find it useful.

#6 Updated by Spyhawk almost 4 years ago

  • Related to Task #218: Replace assets with our own added

#7 Updated by Spyhawk almost 4 years ago

  • Status changed from New to Invalid
  • % Done changed from 0 to 100

Yes, we’re aware the current situation isn’t ideal, but on the bright side it is only damageable to Debian, from a pragmatic point of view.

#8 Updated by Spyhawk almost 4 years ago

  • Related to deleted (Task #218: Replace assets with our own)

#9 Updated by Spyhawk almost 4 years ago

  • Duplicates Task #218: Replace assets with our own added

#10 Updated by apo almost 4 years ago

Spyhawk wrote:

Yes, we’re aware the current situation isn’t ideal, but on the bright side it is only damageable to Debian, from a pragmatic point of view.

Well, it is perhaps because Debian is one of the distributions that takes the law seriously. If you distribute files which should not be distributed in the first place, you are on your own here. Good luck to everyone.

#11 Updated by IR4T4 almost 4 years ago

  • Status changed from Invalid to In Progress
  • Priority changed from Low to High

We’ll solve the MS font files issue asap.

Edit: As far as I can see we don’t have to ship these for Debian:
https://packages.debian.org/squeeze/ttf-mscorefonts-installer

#12 Updated by IR4T4 almost 4 years ago

  • Priority changed from High to Normal

#13 Updated by IR4T4 almost 4 years ago

  • Target version changed from 2.75 to 2.78

#14 Updated by Dragonji over 3 years ago

I still think it’s a good idea to replace MS fonts seeing that there are free alternatives (Courier, Arial).

#15 Updated by Spyhawk over 3 years ago

An alternative doesn’t mean it is adequate. Ideally, the fonts should be free/open source, metrically compatible, visually similar and should cover a wide range of Unicode (at least all extended Latin and Cyrillic).

I did play with Liberation, but I wasn’t pleased with the result.

#16 Updated by IR4T4 about 3 years ago

  • Target version changed from 2.78 to 2.76

#17 Updated by IR4T4 about 3 years ago

  • Status changed from In Progress to Feedback

#18 Updated by Spyhawk about 3 years ago

The alternative to courrier (cour10p_b.ttf) looks ok, but Liberation-Sans looks ugly imho. Google commissioned a free variation named "Arimo", we might have a look at that one.

Note: It’s actually not that bad in hirez.

#19 Updated by Spyhawk about 3 years ago

  • Status changed from Feedback to Fixed
  • Assignee set to IR4T4
  • Target version changed from 2.76 to 2.75

Had a look, Arimo is actually the very same as Liberation. Liberation 2.0 is based on it too.
Also looked at Courier Prime, but it’s rendering isn’t better than cour10p.

Guess I’ll need some time to adjust to the new fonts.

#20 Updated by Spyhawk about 3 years ago

Courier 10 Pitch has some issue with Polish glyphs, so we’ll use Courier Prime Bold instead.

#21 Updated by IR4T4 about 3 years ago

  • Related to Feature #581: Add TrueType Unicode font for the ingame console added

Also available in: Atom PDF