Support auto-LTWA in .bib file

[koppor]

On https://link.springer.com/journal/10270/submission-guidelines#Instructions%20for%20Authors, there is written

Always use the standard abbreviation of a journal’s name according to the ISSN List of Title Word Abbreviations

We do have LTWA support in JabRef.

JabRef supports save actions - https://docs.jabref.org/finding-sorting-and-cleaning-entries/saveactions

Wish:

As user, I can configure the library to always abbreviate the journal using LTWA.

Tests should cover https://link.springer.com/journal/10270/submission-guidelines#Instructions%20for%20Authors_References

---

Refs #8701

[faneeshh]

/assign-me

[jabref-machine]

Thank you for your continued work in JabRef. At this point, you probably already know the basics and the important links. If not, our contributing guidelines is the place you should go to.

At this point in time, you raised 15 pull request(s) of which 60% (9/15) have been merged.

[faneeshh]

Just a minor suggestion. On the documentation https://docs.jabref.org/finding-sorting-and-cleaning-entries/saveactions. It says

Field formats can be tidied up when saving the library. That ensures your entries to have consistent formatting. In Library → Library properties, check "Enable save actions".

It could be changed to "Enable field formatters" just so it matches the checkbox name and it's easier to follow for the general audience.

[github-actions]

A pull request addressing the issue has been created. You can try out the pull request by following the steps at How to try out any JabRef pull request?.

For any feedback, add a comment to the pull request at #15517.

[subhramit]

As time passes, we generally encourage contributors to gradually contribute bigger features instead of picking up good first/second issues. They are mostly intended for newcomer onboarding into the codebase.

@faneeshh we appreciate your involvement, however please note that this is your 16th issue. If you really wish to be involved in simpler issues, you can do so by adding you comments for refinement (like you did here), helping newcomers who take the issue, reviewing their PR, etc.

[faneeshh]

As time passes, we generally encourage contributors to gradually contribute bigger features instead of picking up good first/second issues. They are mostly intended for newcomer onboarding into the codebase.

@faneeshh we appreciate your involvement, however please note that this is your 16th issue. If you really wish to be involved in simpler issues, you can do so by adding you comments for refinement (like you did here), helping newcomers who take the issue, reviewing their PR, etc.

I'll keep that in mind.