Replace all \$([ceg-hmnz])\$ with \$\mathrm{$1}\$ using Libre Open Office with match case and regular expressions ticked as options. #626
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nkdest where not in text mode
…nkdest where not in text mode
…nkdest where not in text mode Jwordbytes
Using Libre Open Office with match case and regex.
…rm{p}} => T_{\mathrm{g}}T_{\mathrm{p}}
…nkdest where not in text mode
Add \pagebreak[1]s which removes many empty lines
Add Davey2002_zbMATH01748069 ref + typo + List of mathematical symbols
hypertargets lines 500–599
hypertargets lines 646–662
hypertargets lines 871–882 exec params
\hypertarget{normal_halting_function_H}{normal_halting_function_H}
changed ordering of receipt items to correct client implementation
… match math order; ", \eg by \cite{ECDSAcerticom}."
\cite{Keccak}
\hyperlink{execenv}{execution environment} and linkdest
L_{R} hypertargets and links
\hyperlink zhalt, hhalt
\hyperlink{Gamma}{\Gamma}
\hyperlink{Omega}{\Omega}
consolidated => consolidating
providing ``consumers'' with the ability to make micro-payments
`set -e` seems to be non-effective in Travis build
link{R__block}
change ordering of ECDSAPUBKEY, ECDSASIGN and ECDSARECOVER in text to…
Move \hypertarget{v}{}
\hyperlink{v}{v}
Make sure that Travis fails when latex fails
…fice with regular expressions ticked as an option.
jamesray1
changed the title
jamesray1
changed the title
pirapira
suggested changes
Feb 20, 2018
| @@ -181,7 +181,7 @@ \section{Conventions}\label{ch:conventions} | |||
|
|
|||
| Tuples are typically denoted with an upper-case letter, \eg $T$, is used to denote an Ethereum transaction. This symbol may, if accordingly defined, be subscripted to refer to an individual component, \eg \hyperlink{transaction_nonce}{$T_{\mathrm{n}}$}, denotes the nonce of said transaction. The form of the subscript is used to denote its type; \eg uppercase subscripts refer to tuples with subscriptable components. | |||
|
|
|||
| Scalars and fixed-size byte sequences (or, synonymously, arrays) are denoted with a normal lower-case letter, \eg $n$ is used in the document to denote a \hyperlink{transaction_nonce}{transaction nonce}. Those with a particularly special meaning may be Greek, \eg $\delta$, the number of items required on the stack for a given operation. | |||
| Scalars and fixed-size byte sequences (or, synonymously, arrays) are denoted with a normal lower-case letter, \eg $\mathrm{n}$ is used in the document to denote a \hyperlink{transaction_nonce}{transaction nonce}. Those with a particularly special meaning may be Greek, \eg $\delta$, the number of items required on the stack for a given operation. | |||
There was a problem hiding this comment.
I think this edit is mistaken about the normal lower-case letter. Scalars and fixed-size byte sequences should be typeset with italic.
There was a problem hiding this comment.
Hmm, OK, I guess I changed it like this (overlooking this part) because n, etc, are also used as a field, e.g. of transactions, accounts, blocks, where they are typeset in roman font. So it seems like a bit of a contradiction that they are typeset differently.
There was a problem hiding this comment.
Let's keep it inconsistent for now, and tidy up the document first.
There was a problem hiding this comment.
So what, just leave this PR open and make a decision whether to merge or close it some time later? Why not make a decision now? I guess we want to avoid merge conflicts.
There was a problem hiding this comment.
If you want a decision now, here
- scalar or fixed-length without subscripts
$x$ - scalar or fixed-length component of a record
$T_{\mathrm{n}}$ - scalar of fixed-length component of an array specified by an index
$R_i$ - variable-length
$\mathbb{x}$ - variable-length component of a record
$\mu_{\mathbb s}$
There was a problem hiding this comment.
Interesting conventions, is there a style guide for that?
There was a problem hiding this comment.
No, just observing what's happening now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.