Skip to content

Commit

Permalink
Wordsmithing
Browse files Browse the repository at this point in the history
  • Loading branch information
jmarshall committed Oct 11, 2022
1 parent 302becc commit 0dc7e3d
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions SAMv1.tex
Original file line number Diff line number Diff line change
Expand Up @@ -67,12 +67,13 @@ \section{The SAM Format Specification}
BAM file may optionally specify the version being used via the
{\tt @HD VN} tag. For full version history see Appendix~\ref{sec:history}.

SAM files are encoded in UTF-8.
SAM files are encoded in UTF-8, though most of their content is limited to ASCII.
They must not begin with a byte order mark, and non-ASCII characters are permitted only in certain field values as individually specified.%
\footnote{Equivalently, SAM files primarily contain US-ASCII characters in the usual single-byte encoding; certain field values as specified may contain other Unicode characters and are encoded as UTF-8.}
SAM file contents should be read and written using the POSIX / C locale.%
\footnote{Equivalently, SAM file content is primarily US-ASCII characters in the usual single-byte encoding; certain field values as specified may contain other Unicode characters and are encoded as UTF-8.}
Where it makes a difference, SAM file contents should be read and written using the POSIX\,/\,C locale.%
\footnote{For example, floating-point values in SAM always use `{\tt .}' (\textsc{Full Stop}) for the decimal-point character.}
The regular expressions in this specification have been written using the POSIX / IEEE Std 1003.1 extended syntax.

The regular expressions in this specification have been written using the POSIX\,/\,IEEE Std 1003.1 extended syntax.

\subsection{An example}\label{sec:example}
Suppose we have the following alignment with bases in lowercase
Expand Down

0 comments on commit 0dc7e3d

Please sign in to comment.