some raw string for pdf doc building in sage-on-gentoo

[kiwifb]

BAck in sage 9.1 we had issues with building pdf docs because of missing raw strings.

Some issues that were also happening in vanilla sage have been fixed and merged but sage-on-gentoo continued to carry a few extra ones.

This ticket is to merge those leftovers.

Component: documentation

Keywords: sd111

Author: François Bissey

Branch/Commit: 27aee93

Reviewer: Frédéric Chapoton

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

[kiwifb]

New commits:

d019743

use some more raw strings for pdf build on Gentoo

[kiwifb]

Branch: u/fbissey/trac31032

[kiwifb]

Author: François Bissey

[kiwifb]

Commit: d019743

[fchapoton]

comment:2

really keeping the double slash here in \\cdot ?

[kiwifb]

comment:3

Replying to @fchapoton:

really keeping the double slash here in \\cdot ?

I'd have to check, things were not failing on it so I may not have paid as much attention to it as I should have. But it does look suspicious.

[kiwifb]

comment:4

I introduced those back in sage 8.3 in fact, 9.1 is the latest time it was rebased. cschwan/sage-on-gentoo#509

And it was glossed over because it didn't cause anything to break. But it probably looks weird. I'll look at it tomorrow.

[kiwifb]

comment:5

I confirm, it looks incorrect since it is all escaped. Preparing a new commit.

[sagetrac-git]

Changed commit from d019743 to 27aee93

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

27aee93

correct the handling of cdot in raw string

[kiwifb]

comment:7

Fixed.

[fchapoton]

comment:8

ok, merci

[fchapoton]

Reviewer: Frédéric Chapoton

[mkoeppe]

Changed keywords from none to sd111

[vbraun]

Changed branch from u/fbissey/trac31032 to 27aee93