Opened 21 years ago
Closed 21 years ago
#1509 closed defect (fixed)
Freetype sed command
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | high | Milestone: | 6.2.0 |
| Component: | BOOK | Version: | SVN |
| Severity: | medium | Keywords: | |
| Cc: |
Description
The bytecode interpreter patch for the FreeType instructions has been replaced with a sed command. The command is cryptic and not self-explanatory at all. The text in the book which explains this sed is that it "uncomments configuration options".
We can do better than this. This command needs to explain what it does, and why we are *changing* these configuration options.
Change History (3)
comment:1 by , 21 years ago
comment:2 by , 21 years ago
You should also consider to inform the user about a possible patent infringement issue when enabling the Bytecode Interpreter, see:
http://freetype.sourceforge.net/patents.html
There's a reason why the usual Linux box has a fuzzy font-look ... ;)
comment:3 by , 21 years ago
| Milestone: | future → 6.2 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Clarified the explanation of the sed command that enables the bytecode interpreter in the FreeType instructions. Additionally, I sent a note to the -dev list about the possibility of patent infringement.
Closing the bug however, and if it is determined that we need to revisit the patent thing, we'll create a new bug.

Maybe: This command enables compilation of the bytecode interpreter by uncommenting its line in the configuration options file.