Typos in sage/rings/arith.py

[jdemeyer]

Component: documentation

Author: Jeroen Demeyer

Reviewer: André Apitzsch

Merged: sage-4.6.1.alpha1

Issue created by migration from https://trac.sagemath.org/ticket/10210

[jdemeyer]

Author: Jeroen Demeyer

[nexttime]

comment:2

A height bound may be specified...

[nexttime]

comment:3

sufficiently small polynomial

[nexttime]

comment:4

requires height_bound to be set

Shouldn't sqrt(2) be typeset in math mode?

(Though I generally hate that: For every "p" in p-adic an image is generated by TeX for the HTML documentation, which takes by far more than half of the docbuild time.)

[jdemeyer]

comment:6

Requested changes done

[a-andre]

comment:7

It should be default*:*** (with colon)

[jdemeyer]

comment:8

Attachment: 10210_algdep_doc.patch.gz

Replying to @a-andre:

It should be default*:*** (with colon)

Done.

[a-andre]

Reviewer: André Apitzsch

[johanrosenkilde]

comment:10

Replying to @nexttime:

requires height_bound to be set

Shouldn't sqrt(2) be typeset in math mode?

(Though I generally hate that: For every "p" in p-adic an image is generated by TeX for the HTML documentation, which takes by far more than half of the docbuild time.)

Surely Sphinx caches and reuses these bits and pieces of TeX-generated images. A small grep for some of the more often used images (like $A$) seemed to indicate that at least...

[nexttime]

comment:11

Replying to @johanrosenkilde:

Replying to @nexttime:

requires height_bound to be set

Shouldn't sqrt(2) be typeset in math mode?

(Though I generally hate that: For every "p" in p-adic an image is generated by TeX for the HTML documentation, which takes by far more than half of the docbuild time.)

Surely Sphinx caches and reuses these bits and pieces of TeX-generated images. A small grep for some of the more often used images (like $A$) seemed to indicate that at least...

Might be true. Nevertheless, then even generating a single image file for every used math character (or short math-typeset identifier) takes a big amount of time, and btw. looks pretty ugly for e.g. p-adic in the HTML documentation. (The latter is what disturbs me more, but such mark-up is widely used in Sage, even for numbers in a word like 2-descent. If we one day build the documentation in parallel, too, the former is less of an issue, though it also takes more disk space. The ratio build:doc:ptestlong is about 3:2:3 on my newer machines; on older machines ptestlong takes longer.)

[jdemeyer]

Merged: sage-4.6.1.alpha1