Fix #8161, e31def197: Lang files may have LF EOL #8163
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Yexo
approved these changes
May 19, 2020
glx22
added
the
backport requested
rasputino
pushed a commit
to rasputino/OpenTTD
that referenced
this pull request
Jun 1, 2020
LordAro
pushed a commit
to LordAro/OpenTTD
that referenced
this pull request
Jun 1, 2020
LordAro
pushed a commit
that referenced
this pull request
Jun 1, 2020
freprec
pushed a commit
to freprec/OpenTTD
that referenced
this pull request
Jun 19, 2020
LordAro
added
backported
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Nightly binaries are built from a source archive made on linux, so using LF EOL. As
translations.vbsexpects CRLF in lang files, it silently fails to parse them and skip thedescriptionlines, generating incomplete, and unusable,ob[gms]files.