From 2543789c4062d83c7d4a4352827a4eed37313b2e Mon Sep 17 00:00:00 2001 From: James Bonfield Date: Mon, 29 Jan 2024 16:27:53 +0000 Subject: [PATCH] Trivial: change type of non-breaking space in SAM spec. The use of \textsc{cr\>lf} breaks pdfTeX 3.14159265-2.6-1.40.18. Switching to \textsc{cr\,lf} cures it. Visually they're almost identical and it's only a footnote anyway. --- SAMv1.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SAMv1.tex b/SAMv1.tex index c1d76d1a..4dd87570 100644 --- a/SAMv1.tex +++ b/SAMv1.tex @@ -75,7 +75,7 @@ \section{The SAM Format Specification} Alternatively and equivalently, SAM files are encoded in UTF-8 but non-ASCII characters are permitted only within certain field values as explicitly specified in the descriptions of those fields.% \footnote{Hence in particular SAM files must not begin with a byte order mark~(BOM) and lines of text are delimited by ASCII line terminator characters only. % Unicode identifies VT and FF as line break characters as well, but no one uses them in SAM. -In addition to the local platform's text file line termination conventions, implementations may wish to support \textsc{lf} and \textsc{cr\>lf} for interoperability with other platforms.} +In addition to the local platform's text file line termination conventions, implementations may wish to support \textsc{lf} and \textsc{cr\,lf} for interoperability with other platforms.} Where it makes a difference, SAM file contents should be read and written using the POSIX\,/\,C locale. For example, floating-point values in SAM always use `{\tt .}' for the decimal-point character.