EOL problems less common now. - online edit of handbook/computing/regular.html

This commit is contained in:
Expo on server
2023-03-04 16:14:33 +00:00
parent 0eca181225
commit 83f4f12073

View File

@@ -30,8 +30,10 @@
<h3>Wallets and Surveyscans</h3> <h3>Wallets and Surveyscans</h3>
<h4>2020#00</h4> <h4>2020#00</h4>
<p> The <b>#00</b> wallet directory (e.g. /2020/2020<b>#00</b>/ ) contains orphan files that have been found on the expo laptop in odd places, or have been scanned from bits of notebook found inside other documents. Keep an eye on it and re-file the contents as you discover what they are. <p> The <b>#00</b> wallet directory (e.g. /2020/2020<b>#00</b>/ ) contains orphan files that have been found on the expo laptop in odd places, or have been scanned from bits of notebook found inside other documents. Keep an eye on it and re-file the contents as you discover what they are.
<h4>EOL</h4> <h4>EOL and UTF8</h4>
<p>Run dos2unix to convert any uploaded Windows text files to the format expected by our software. e.g. <pre><code>cd expofiles/surveyscans <p>This is much less of a prpblem now that we have nearly all the file uploading done by troggle forms.
<p>The most common <a href="https://en.wikipedia.org/wiki/UTF-8">UTF8</a> problem is with files uploaded conting German language umlaut characters which have been encoded using an extended-ASCII code such as ISO-8055-1 or Windows-1251.
<p>To fix EOL problems, use <var>dos2unix</var> to convert any uploaded Windows text files to the format expected by our software. e.g. <pre><code>cd expofiles/surveyscans
find . -not -type d -exec file "{}" ";" | grep CRLF >crlf.txt find . -not -type d -exec file "{}" ";" | grep CRLF >crlf.txt
`awk -F: '// {print "dos2unix \"" $1 "\""}' crlf.txt`</code></pre> `awk -F: '// {print "dos2unix \"" $1 "\""}' crlf.txt`</code></pre>
<p>Also a good idea to run on all of expofiles once every few years as many GPX exports <p>Also a good idea to run on all of expofiles once every few years as many GPX exports