Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use <sup> for exponentiation #4822

Merged
merged 3 commits into from
Feb 2, 2021
Merged

Use <sup> for exponentiation #4822

merged 3 commits into from
Feb 2, 2021

Conversation

martinthomson
Copy link
Member

This renders much better in HTML and the text format does not suffer for
it.

Conversion process was almost entirely mechanical:

sed -i -e 's/\^\([0-9][0-9]*\(\|\.[0-9][0-9]*\)\)/<sup>\1<\/sup>/g' draft-*.md
sed -i -e 's/<\/sup> - /<\/sup>-/' draft-*.md

Cleanup used emacs because I know that wraps reliably.

emacs $(git status --porcelain | cut -d ' ' -f 3 -)

With the macro sequence:

C-X ( C-s '<sup ENTER M-q C-x )

Then for each file it was basically just:

C-u 99 C-x e C-x C-s

Though I had to manually wrap the changelogs because emacs got greedy.

This renders much better in HTML and the text format does not suffer for
it.

Conversion process was mechanical:

```
sed -i -e 's/\^\([0-9][0-9]*\(\|\.[0-9][0-9]*\)\)/<sup>\1<\/sup>/g' draft-*.md
sed -i -e 's/<\/sup> - /<\/sup>-/' draft-*.md
```

Cleanup used emacs because I know that wraps reliably.

```
emacs $(git status --porcelain | cut -d ' ' -f 3 -)
```

With the macro sequence:

```
C-X ( C-s '<sup ENTER M-q C-x )
```
Then for each file it was basically just:

```
C-u 99 C-x e C-x C-s
```

Though I had to revert changes to the changelog.
@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport -tls -http labels Feb 2, 2021
Copy link
Contributor

@janaiyengar janaiyengar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also change this in the recovery draft? This does make it slightly odd that the HTML version will still say that "^ is exponentiation", but that's not incorrect, just redundant.

Copy link
Contributor

@janaiyengar janaiyengar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since recovery is only in the pseudocode, LGTM.

@martinthomson martinthomson merged commit d841a22 into master Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-http -tls -transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants