Skip to content
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

Enhance "Recommended" settings for field formatters (which are e.g. used to cleanup entries) #8790

Open
ThiloteE opened this issue May 12, 2022 · 3 comments

Comments

@ThiloteE
Copy link
Member

ThiloteE commented May 12, 2022

Prerequisites

  1. Be a beginner.
  2. Have a library with bibliographic metadata.
  3. Know nothing about UTF8 and encoding.
  4. Know you want to use this library with LaTeX, Microsoft Word and OpenOffice/LibreOffice or other external programs.

Problems:

  1. Bibliographic data is formatted the "wrong" way (especially after import from external databases).

    • in other words:
      • it can be that this data cannot be read with LaTeX engines
      • or vice versa, it will create wrong output when exporting to OO/LO
      • or MS-Word
      • or using this data for HTML
      • or ...

    Hence the need to (manually or automatically) format the data into the "proper" format depending on which external program is supposed to be used. We have some field formatters for this. They are utilized by cleanup actions (field formatters as can be seen in Enhance "Recommended" settings for field formatters (which are e.g. used to cleanup entries) #8790 (comment)) and save actions. Cleanup actions can be found in the UI via Quality > Cleanup entries (ALT + F8). Save actions can be found via right clicking on the library tab and choosing library properties > saving > save actions. Typical examples for field formatters are latex2unicode or unicode2latex, but there are more.

  2. There are (too) many field formatters that all would manually have to be set up.

Draft Solution:

  1. Enhance "recommended" settings for field formatters.

  2. Go beyond what the older feature could do: Give recommended settings for various "states" the library could be in.

    Example:

    state program user wants to use recommended cleanup actions / save actions
    Data formatted in LaTeX syntax OpenOffice/LibreOffice LaTeX2Unicode, normalize date, ...
    Data formatted in UTF8 syntax LaTeX Unicode2LaTeX, normalize date, ...
    Data formatted in LaTeX syntax UnicodeAwareLaTeX LaTeXtoUnicodAwareLaTeX (does not yet exist. See Add cleanup action for "LaTeX to LaTeX aware Unicode" #8715 though, ...
    Data formatted in UTF8 syntax Microsoft Word no change (i think?)
    Data formatted in UTF8 syntax OpenOffice/LibreOffice no change (i think?)
    ... ... ...

    Maybe it would be good to tie this to library modes, but I am not sure how that could look like exactly...

Additional context

@Siedlerchr
Copy link
Member

grafik

Is that what you mean?

@ThiloteE
Copy link
Member Author

Ah sorry, yes. field formatters. My bad. Will edit my post.

@ThiloteE ThiloteE changed the title (Re-) Introduce "Recommended" settings to "cleanup actions" and "save actions" Enhance "Recommended" settings for field formatters (which are used to cleanup entries and by save actions) May 12, 2022
@ThiloteE
Copy link
Member Author

Should be better now :-)

@ThiloteE ThiloteE changed the title Enhance "Recommended" settings for field formatters (which are used to cleanup entries and by save actions) Enhance "Recommended" settings for field formatters (which are e.g. used to cleanup entries) May 12, 2022
@ThiloteE ThiloteE added the ui label Jun 16, 2022
@koppor koppor moved this to Normal priority in Features & Enhancements Nov 7, 2022
@koppor koppor moved this to Normal priority in JabRef UI Improvements Nov 11, 2022
@github-project-automation github-project-automation bot moved this to Normal priority in Prioritization Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Normal priority
Development

No branches or pull requests

2 participants