doxygen
doxygen copied to clipboard
Keep latex template files with Unix EOL
Windows (CRLF) encoding of *tex
files causes output to contain multiple empty lines.
This breaks final output (refman.tex
) resulting in (for example) attaching latex tags to project id on pdf main page.
Feel free to see an excerpt of my frustration #10609
All text type of files should be in the repository with *nix endings and should also be retrieved as such.
So probably some more file extensions could use the file endings.
I looked quickly in the my checked out repository (with the *nix utility file
) and saw the following files:
deps/libmscgen/mscgen_safe.c: C source, ASCII text, with CRLF line terminators
deps/libmscgen/mscgen_safe.h: C source, ASCII text, with CRLF line terminators
deps/libmscgen/mscgen_usage.h: C source, ASCII text, with CRLF line terminators
deps/libmscgen/mscgen_utf8.c: C source, ASCII text, with CRLF line terminators
deps/libmscgen/mscgen_utf8.h: C source, ASCII text, with CRLF line terminators
deps/spdlog/cmake/spdlogConfig.cmake.in: ASCII text, with CRLF line terminators
deps/spdlog/LICENSE: ASCII text, with CRLF line terminators
deps/spdlog/README.md: C source, ASCII text, with very long lines (463), with CRLF line terminators
deps/svg/svg-3.1.2.js: C++ source, Unicode text, UTF-8 text, with very long lines (458), with CRLF, LF line terminators
doc/translator.py: Python script, ASCII text executable, with CRLF, CR line terminators
It might also be depending on the LaTeX distribution used.
I'm not sure whether the chosen solution is correct for all platforms (in the past I've seen platforms with line endings \r\n
(Windows), \n
(*nix) and \r
((old?) Mac)).
Regarding the problem with files with CRLF in the repository (as mentioned in: https://github.com/doxygen/doxygen/pull/10610#issuecomment-1916421704), I've just pushed a proposed patch, pull request #10611
Hopefully the 3rd commit does not hit the *.png
, *.pdf
and *.lib
files.
Aren't the commits "XD" and "XDDD" containing the patch from #10611 as well?
Aren't the commits "XD" and "XDDD" containing the patch from #10611 as well?
Sorry. I forgot to create testing branch in my repository and I was pushing everything to master...
Hopefully the 3rd commit does not hit the
*.png
,*.lib
files.
In theory it shouldnt. I'll keep this PR closed for a while to test if files were altered
Alright. It seems only intended text files were affected. Checked svg, pdf and jpg files and they weren't affected by this PR
Looks like there are stil a few extra files:
Note you can also place the PR in draft mode:
Quality Gate passed
Kudos, no new issues were introduced!
0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication