context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.6 Coding Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . at docs/example.c and make sure you understand it. Then read the multi-threading section in docs/coding-overview.html. before coming back here to see an example of multi-threading. This example will create start up, and to clone this repeatedly to get new contexts that can be used on new threads. 2.6 Coding Style 2.6.1 Names Functions should be named according to one of the following schemes: • verb_noun

Release 1.24.2 10.8 How to Mark Searched Text This script searches for text and marks it: # -*- coding: utf-8 -*- import fitz # the document to annotate doc = fitz.open("tilted-text.pdf") # the text most of the available annotations. Look in the next sections for more special situations: # -*- coding: utf-8 -*- """ ------------------------------------------------------------------------------- Demo How to Use FreeText This script shows a couple of ways to deal with ‘FreeText’ annotations: # -*- coding: utf-8 -*- import fitz # some colors blue = (0,0,1) green = (0,1,0) red = (1,0,0) gold = (1,1,0)

context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.6 Coding Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . start up, and to clone this repeatedly to get new contexts that can be used on new threads. 2.6 Coding Style 2.6.1 Names Functions should be named according to one of the following schemes: • verb_noun to keep the object for longer than that, you have to either keep it or make your own copy. 2.6. Coding Style 19 MuPDF Documentation, Release 1.23.0 20 Chapter 2. Using MuPDF with C CHAPTER THREE

context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.6 Coding Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . used on new threads. 18 Chapter 2. Using MuPDF with C MuPDF Documentation, Release 1.25.0 2.6 Coding Style 2.6.1 Names Functions should be named according to one of the following schemes: • verb_noun In addition, we use floats (and avoid doubles when possible), assumed to be IEEE compliant. 2.6. Coding Style 19 MuPDF Documentation, Release 1.25.0 2.6.3 Reference counting Reference counting uses

context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.6 Coding Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . used on new threads. 18 Chapter 2. Using MuPDF with C MuPDF Documentation, Release 1.24.0 2.6 Coding Style 2.6.1 Names Functions should be named according to one of the following schemes: • verb_noun In addition, we use floats (and avoid doubles when possible), assumed to be IEEE compliant. 2.6. Coding Style 19 MuPDF Documentation, Release 1.24.0 2.6.3 Reference counting Reference counting uses

may follow. Each sequence of draws must be finished before the drawing is committed. The overall coding pattern looks like this: >>> img = page.newShape() >>> img.draw1(...) >>> img.draw2(...) >>> .. 'ANTIQUEWHITE3', 'ANTIQUEWHITE4', 'AQUAMARINE', 'AQUAMARINE1'] ... >>> # >>> # to see the full integer color coding >>> from fitz.utils import getColorInfoList >>> il = getColorInfoList() >>> il [('ALICEBLUE', 240