@@ -299,7 +299,7 @@ msgid ""
299299"Because SWIG goes a long way to keep the Python and the C level in sync, "
300300"everything works fine, if a certain set of rules is being strictly "
301301"followed. For example: **never access** a :ref:`Page` object, after you "
302- "have closed (or deleted or set to * None* ) the owning :ref:`Document`. Or,"
302+ "have closed (or deleted or set to `` None`` ) the owning :ref:`Document`. Or,"
303303" less obvious: **never access** a page or any of its children (links or "
304304"annotations) after you have executed one of the document methods "
305305"*select()*, *delete_page()*, *insert_page()* ... and more."
@@ -347,14 +347,14 @@ msgstr "ページが所有するドキュメントを失ったり、それ自体
347347
348348#: ../../app3.rst:189 45355fbf65294031ad4b66db204e52a7
349349msgid ""
350- "If a document is closed (or deleted or set to * None* ) or if its structure"
350+ "If a document is closed (or deleted or set to `` None`` ) or if its structure"
351351" has changed, then similarly all currently existing pages and their "
352352"children will be made unusable, and corresponding C-level deletions will "
353353"take place. \" Structure changes\" include methods like *select()*, "
354354"*delePage()*, *insert_page()*, *insert_pdf()* and so on: all of these "
355355"will result in a cascade of object deletions."
356356msgstr ""
357- "ドキュメントが閉じられたり(または削除されたり、 * None* "
357+ "ドキュメントが閉じられたり(または削除されたり、 `` None`` "
358358"に設定されたり)したり、構造が変更されたりすると、同様に現在存在するすべてのページとその子要素は使用できなくなり、対応するCレベルの削除が行われます。「構造の変更」とは、"
359359" *select()* 、 *delete_page()* 、 *insert_page()* 、 *insert_pdf()* "
360360"などのメソッドを含みます。これらのすべてはオブジェクトの削除の連鎖を引き起こします。"
@@ -710,8 +710,8 @@ msgstr ""
710710
711711#: ../../app3.rst:328 a9e91d5d77994064a013f1a5c5f281cb
712712msgid ""
713- "In ** PDF** , the origin `(0, 0)` of a page is located at its **bottom-left"
714- " point**. In ** MuPDF** , the origin `(0, 0)` of a page is located at its "
713+ "In | PDF| , the origin `(0, 0)` of a page is located at its **bottom-left"
714+ " point**. In | MuPDF| , the origin `(0, 0)` of a page is located at its "
715715"**top-left point**."
716716msgstr ""
717717
@@ -727,41 +727,41 @@ msgstr ""
727727msgid ""
728728"Typical document page sizes are **ISO A4** and **Letter**. A **Letter** "
729729"page has a size of **8.5 x 11 inches**, corresponding to **612 x 792 "
730- "points**. In the ** PDF** coordinate system, the top-left point of a "
730+ "points**. In the | PDF| coordinate system, the top-left point of a "
731731"**Letter** page hence has the coordinate `(0, 792)` as **the y-axis "
732- "points upwards**. Now we know our document size the ** MuPDF** coordinate "
732+ "points upwards**. Now we know our document size the | MuPDF| coordinate "
733733"system for the bottom right would be coordinate `(612, 792)` (and for "
734- "** PDF** this coordinate would then be `(612,0)`)."
734+ "| PDF| this coordinate would then be `(612,0)`)."
735735msgstr ""
736736
737737#: ../../app3.rst:339 681786d37c9c4b979f9dbabaa1ee27b6
738738msgid ""
739739"Theoretically, there are **infinitely many** coordinate positions on a "
740- "** PDF** page. In practice however, at most the first 5 decimal places are"
740+ "| PDF| page. In practice however, at most the first 5 decimal places are"
741741" sufficient for a reasonable precision."
742742msgstr ""
743743
744744#: ../../app3.rst:342 035cc1ebe8414b0a825095ad85d803ab
745745msgid ""
746- "In ** MuPDF** , multiple document formats are supported - ** PDF** just "
746+ "In | MuPDF| , multiple document formats are supported - | PDF| just "
747747"being one among **over a dozen others**. Images are also supported as "
748- "documents in ** MuPDF** (therefore having one page usually). This is one "
749- "of the reasons why ** MuPDF** uses a coordinate system with the origin "
748+ "documents in | MuPDF| (therefore having one page usually). This is one "
749+ "of the reasons why | MuPDF| uses a coordinate system with the origin "
750750"`(0, 0)` being the **top-left** point of any document page. **The y-axis "
751- "points downwards**, like with images. Coordinates in ** MuPDF** in any "
752- "case are floats, like in ** PDF** ."
751+ "points downwards**, like with images. Coordinates in | MuPDF| in any "
752+ "case are floats, like in | PDF| ."
753753msgstr ""
754754
755755#: ../../app3.rst:344 cb7651396e85454e93793fd64ceed6d0
756756msgid ""
757- "A rectangle `Rect(0, 0, 100, 100)` for instance in ** MuPDF** (and thus "
758- "** PyMuPDF** ) therefore is a square with edges of length 100 points (= "
757+ "A rectangle `Rect(0, 0, 100, 100)` for instance in | MuPDF| (and thus "
758+ "| PyMuPDF| ) therefore is a square with edges of length 100 points (= "
759759"1.39 inches or 3.53 centimeters). Its top-left corner is the origin. To "
760- "switch between the two coordinate systems ** PDF** to ** MuPDF** , every "
760+ "switch between the two coordinate systems | PDF| to | MuPDF| , every "
761761":ref:`Page` object has a :attr:`Page.transformation_matrix`. Its inverse "
762762"can be used to compute a rectangle's PDF coordinates. In this way we can "
763- "conveniently find that `Rect(0, 0, 100, 100)` in ** MuPDF** is the same as"
764- " `Rect(0, 692, 100, 792)` in ** PDF** . See this code snippet::"
763+ "conveniently find that `Rect(0, 0, 100, 100)` in | MuPDF| is the same as"
764+ " `Rect(0, 692, 100, 792)` in | PDF| . See this code snippet::"
765765msgstr ""
766766
767767#: ../../app3.rst:355 16f6a104e25d4e4ab18569c129ad0a9f
0 commit comments