You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SAMv1.tex
+6-2Lines changed: 6 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -67,8 +67,12 @@ \section{The SAM Format Specification}
67
67
BAM file may optionally specify the version being used via the
68
68
{\tt @HD VN} tag. For full version history see Appendix~\ref{sec:history}.
69
69
70
-
Unless explicitly specified elsewhere, all fields are encoded using 7-bit US-ASCII \footnote{Charset ANSI\_X3.4-1968 as defined in RFC1345.} in using the POSIX / C locale.
71
-
Regular expressions listed use the POSIX / IEEE Std 1003.1 extended syntax.
70
+
SAM files are encoded in UTF-8.
71
+
They must not begin with a byte order mark, and non-ASCII characters are permitted only in certain field values as individually specified.%
72
+
\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.}
73
+
SAM file contents should be read and written using the POSIX / C locale.%
74
+
\footnote{For example, floating-point values in SAM always use `{\tt .}' (\textsc{Full Stop}) for the decimal-point character.}
75
+
The regular expressions in this specification have been written using the POSIX / IEEE Std 1003.1 extended syntax.
72
76
73
77
\subsection{An example}\label{sec:example}
74
78
Suppose we have the following alignment with bases in lowercase
0 commit comments