-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consistent casing of file types. Best practice? #1558
Comments
I agree that this should be consistent, but have no strong opinion in which way. We should probably just reach an agreement during a devcall and document that. |
What a nightmare to rename all this with git+windows :( |
Can this be done using |
During the dev call we were not quite sure what the general scope of your question is @oscargus The general rule of thumb should be: the extension alone should be used in lowercase - if used in a sentence/context uppercase should be used ("Please select a PDF file"). |
Makes sense. I should have been more clear. These are some examples of current strings:
The "correct" should be
? |
@oscargus Yes, that is correct. |
Most (all?) of this is fixed in #1629. |
I know I'm a bit late to the party, but I'm not completely satisfied with On the other hand, |
Just my 0,02€, we should not spend too much on this, as I doubt that the normal user really thinks about if it is now BIB or bib or whatever. |
I agree with @Siedlerchr and close this again 😉 |
Currently the naming of file types is quite inconsistent: PDF, pdf, Zip, ZIP, AUX, aux, etc...
I'm not sure if I have a strong opinion here, but it would be nice to have it consistent.
Also, one one occasion it says
.bib file
, i.e. a dot before the file ending. Some of them have a dash, likeZip-archive
.Any opinions on the correct way of doing it? Lower case, except when starting a sentence, without a leading dot and no trailing dash?
The text was updated successfully, but these errors were encountered: