The file is solely about compiling for Windows, not for using it on
Windows or anything else. SO make it clearer.
A second advantage is that GitLab won't get confused. GitLab
automatically places a link called "ReadMe" on the overview page. It
links to the first file matching the glob "README*" in alphabetical
order. As "README.Windows.md" sorts lower than "README.md", the link
was pointing to a file explaining to the user how to compile for
Windows. Not the ideal landing page for a repository.
This mostly makes a difference on Windows where the operating system's
own buffer implementation isn't that good. Processing time for a 1.7
GB sample file went down from 1m43s to 3s.
Fixes#2166.
A side effect is that it's also a bit more efficient regarding I/O
operations. The result is that processing time for a 1.7 GB sample
file dropped from 2m4s to 1m43s on Windows.
Part of the improvements for #2166.
This mostly fails on timestamp elements as the original value is an
invalid date and the current value is the minimum that Qt's
`QDateTime` control allows at that moment. That's usually something
like 2000-01-01 00:00:00.
However, if the element isn't present in the file, then it doesn't
matter what the current value in the GUI is — it won't be written
anyway. Therefore it shouldn't be used in the decision whether or not
to ask the user to confirm discarding unsaved changes.
Fixes#2167.
The property element tables are initialized only once. At that point
the stored strings should be the English ones as
`translatable_string_c` instances so that they can be translated later
to whatever language is active at that moment.
The old code wasn't initializing the `translatable_string_c` instances
with the English texts, though, but with already translated
ones (e.g. German). This means that any later attempt to translate
them to the current locale (e.g. French) would fail as there's no
translation from e.g. German to French, only from English to French.
Fixes#2159.
See #2163 for progress on AppImage support.
If the command-line programs are run from the command line, they must
try to locate their translation files inside the mounted AppImage
directory.
The `getline` function tries to handle different line ending
styles (carriage returns, new lines, a mix of both). For that it has
to probe one more character after having found one of them. If that
probed character is not one of them, then the previous position has to
be restored — and that was wrongfully assuming that each character is
only one byte long. Which it isn't.
Fixes#2160.
Add Credits to top comments
Remove duplicate filetype extension
Not sure if this is needed, feel free to cherrypick out
Change mime type truetype detection to use font/ttf
Again I don't know the implications of changing this,
so some review would be good
Remove old truetype mime type
Add ttc extention to font/collection mime type
Revert "Remove old truetype mime type"
This reverts commit 6ef7a7c7c8b335c7cfc7273e6cd5bc7ea36656e4.
Remove font collection extention from old mime type
Revert "Change mime type truetype detection to use font/ttf"
This reverts commit 1cef3085d15eacff1216117578500d076457dcd5.
move extenions back to old truetype mimetype
