zeripath 6e22605793 Ensure that plain files are rendered correctly even when containing ambiguous characters (#22017) ... As recognised in #21841 the rendering of plain text files is somewhat incorrect when there are ambiguous characters as the html code is double escaped. In fact there are several more problems here. We have a residual isRenderedHTML which is actually simply escaping the file - not rendering it. This is badly named and gives the wrong impression. There is also unusual behaviour whether the file is called a Readme or not and there is no way to get to the source code if the file is called README. In reality what should happen is different depending on whether the file is being rendered a README at the bottom of the directory view or not. 1. If it is rendered as a README on a directory - it should simply be escaped and rendered as `<pre>` text. 2. If it is rendered as a file then it should be rendered as source code. This PR therefore does: 1. Rename IsRenderedHTML to IsPlainText 2. Readme files rendered at the bottom of the directory are rendered without line numbers 3. Otherwise plain text files are rendered as source code. Replace #21841 Signed-off-by: Andrew Thornton <art27@cantab.net> Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>		2022-12-17 22:22:25 +02:00
..
webhook
branches.tmpl
collaboration.tmpl
deploy_keys.tmpl
githook_edit.tmpl
githooks.tmpl
lfs_file_find.tmpl
lfs_file.tmpl	Ensure that plain files are rendered correctly even when containing ambiguous characters (#22017)	2022-12-17 22:22:25 +02:00
lfs_locks.tmpl
lfs_pointers.tmpl
lfs.tmpl
nav.tmpl
navbar.tmpl
options.tmpl
protected_branch.tmpl
tags.tmpl